br: added crr package and checkpoint advancer

[YuJuncen]

What problem does this PR solve?

Issue Number: close #67416

Problem Summary:

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[pantheon-ai]

Review failed due to infrastructure/execution failure after retries. Please re-trigger review.

_{ℹ️ Learn more details on Pantheon AI.}

[codecov]

Codecov Report

❌ Patch coverage is 70.30935% with 883 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.6756%. Comparing base (864cba9) to head (ca80c30).
⚠️ Report is 161 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #66913        +/-   ##
================================================
+ Coverage   77.6911%   78.6756%   +0.9844%     
================================================
  Files          2012       1982        -30     
  Lines        550857     567693     +16836     
================================================
+ Hits         427967     446636     +18669     
+ Misses       121174     119960      -1214     
+ Partials       1716       1097       -619     

Flag	Coverage Δ
integration	44.2756% <6.2401%> (-3.8803%)	⬇️
unit	76.6563% <69.8049%> (+0.3950%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	61.5065% <ø> (+4.7091%)	⬆️
parser	∅ <ø> (∅)
br	64.6325% <71.0872%> (+3.7092%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-03-30 06:00:01.40596355 +0000 UTC m=+158406.611323627: ☑️ agreed by Leavrth.
• 2026-04-07 03:13:59.202255633 +0000 UTC m=+839644.407615689: ☑️ agreed by RidRisR.

[hawkingrei]

/retest

[D3Hunter]

obj store part lgtm

[D3Hunter]

maybe make them enum

[YuJuncen]

These contants should be provided by the AWS s3 SDK IMO.

[D3Hunter]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, Leavrth, RidRisR

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [D3Hunter,Leavrth,RidRisR]
• br/OWNERS [Leavrth]
• pkg/objstore/OWNERS [D3Hunter,Leavrth]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Leavrth]

/retest

[tiprow]

@YuJuncen: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tidb_parser_test	ca80c30	link	true	/test tidb_parser_test
fast_test_tiprow	ca80c30	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.