Repository navigation
chore(upstream): track the compaction message queue fix - #789
Merged
Merged
Conversation
Upstream divergenceBoth sides are compared with upstream at the in-order tip
No upstream file changes how much it differs from upstream. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
incognitojam
force-pushed
the
styal/track-compaction-queue-fix
branch
from
October 13, 2026 11:03
e088027 to
9033105
Compare
incognitojam
enabled auto-merge (squash)
October 13, 2026 11:13
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.
Problem
Messages sent during context compaction can be rejected as steering instead of queued. Upstream #12824 addresses this regression and is still open.
Change
Add an ordinary watch entry explaining the regression and why we are waiting for upstream merge and chronological intake. The lag and intake reports keep the fix visible without changing queue order.
Scope and approval
Maintainer-requested update to the existing upstream watch list, limited to
.github/upstream-tracked-prs.json.Verification
vp test run scripts/upstream/lib/tracked-prs.test.ts: all six tests pass, covering watch-entry validation and report/status behavior.decodeTrackedPRsandvp fmt --check.node scripts/upstream/tracked-prs-report.ts --fork-ref HEADshows fix(v2): queue messages sent while context compaction runs pingdotgg/t3code#12824 as open, with the expected watch reason and no provisional snapshot.Written by an agent (Codex, gpt-6.1-sol).