docs(engine-plan): step 7 is a measured backlog; sequence the JSON workstream - #7479
Merged
Conversation
added 2 commits
August 6, 2026 05:59
…rkstream The step cited two traps that are both resolved (#7395 closed, #7396 closed as fixed-by-#7421). Replace it with the measured backlog from the 2026-08-06 public-baseline sweep, worst-first, with the JSON workstream sequenced behind its correctness gate: #7477 (DirectParser float divergence -- node agrees with the tape) before #7478 (reparse-on-materialize). Records the win to protect (roundtrip 194 ms vs bun 221) and the measured dead ends so they are not re-walked. Explicitly parallel with the GC-correctness layers: no dependency in either direction, and agent-delegable because every claim checks against the node oracle.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe engine plan now uses measured performance findings to sequence JSON-related work. The changelog records the updated plan, including DirectParser correctness work, tape materialization, validation requirements, and rejected optimization approaches. ChangesPerformance plan
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
This was referenced Aug 6, 2026
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
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.
Step 7 cited two traps that are both resolved (#7395 closed, #7396 closed as fixed-by-#7421). It now carries the measured backlog from the 2026-08-06 public-baseline sweep, worst-first vs bun, with the JSON workstream sequenced behind its correctness gate — #7477 before #7478 — the roundtrip win to protect (194 ms vs bun 221), and the measured dead ends recorded so they are not re-walked.
Explicitly noted as parallel with the GC-correctness layers: no dependency in either direction, and agent-delegable because every claim checks against the node oracle (
PERRY_JSON_TAPE=0/1checksum parity).Summary by CodeRabbit