[codex] unify walker planning with pinned upstream core - #1832
Merged
Conversation
Contributor
|
Important Review skippedToo many files! This PR contains 210 files, which is 110 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (12)
📒 Files selected for processing (210)
You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
chsami
marked this pull request as ready for review
August 5, 2026 19:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Skretzo/shortest-path@ff8e961b32120175709df9630ece9468cc11347fWhy
Microbot's walker had drifted from the upstream shortest-path planner while planner ownership, mutable state, and transport execution were spread across several runtime paths. That made upstream synchronization difficult and made it unsafe to judge planner authority from route shape alone.
This change establishes one owned planning contract, keeps the current local planner as the default authority, and makes upstream convergence measurable. The current canary remains deliberately match-gated: it only selects the pinned planner for eligible F2P routes after semantic agreement, and any divergence or failure retains the local route. Members routes remain shadow-only.
Impact
LOCALEvidence
The tracked evidence at
docs/evidence/walker/2026-08-05/records:0.407(555.2 ms/1365.3 ms)Validation
./gradlew :client:runUnitTests— passedpython3 -m unittest discover -s scripts/tests -p 'test_*.py'— 100 passedReview guidance
The commits are organized from the planner boundary and pinned core, through rollout/performance gates, to the final durable evidence and members shadow slice. ADR 0006 and
docs/walker-planner-selection-gate.mddescribe the authority boundary and remaining exit criteria.