Repository navigation
Reuse verified sources in staged replan reads - #8304
loopx-agent wants to merge 1 commit into
Conversation
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
|
This pull request has merge conflicts with Choose the remote for the base repository, not an out-of-date fork. git fetch upstream
git rebase upstream/main
# Resolve each conflict, git add the resolved files, then git rebase --continue.
git push --force-with-lease origin HEADFor a same-repository clone whose Keep the DCO |
Problem context
A captured replan view verifies the original decision before exposing review, acceptance, or writeback. The legacy Turn path then recomputes the same complete hash while building several reader commands. Large Goals also pay for allocating code-point arrays while hashing outcomes.
Change
Reuse the source hash only within the read that verified it. Build the action projection's reader commands once. Share the existing Unicode code-point comparator and index an identical captured outcome object once per projection. Distinct objects keep their own validation and hashing, including different revisions of the same outcome.
Validation
8225c89ceaea. All eight staged File/SQLite, populated, and unbound review results matched byte for byte, with equal RPC payload sizes, including replay on the final head. These measurements cover local reads and projection time. Model adoption and task-level costs are unmeasured.046c5aceef69bf5f562b6ed874e7753a352a47cc. The same four preflight cases fail at the same--decision-output-rootassertion on the exact basedee54966327e09406b3f7b17d155b03cd633b234. TypeScript 102 passed, isolated wheel 7 passed, and the installed TypeScript source matched the commit byte for byte. Type checking and Ruff passed. Standard local premerge ran 5 direct and 16 selected checks with zero blocking failures.