Repository navigation
Add a read-only Delivery page - #5
Merged
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosNo All 64 scenario measurements
Baseline: unavailable · PR result: 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. |
InTheta
marked this pull request as ready for review
November 16, 2026 10:09
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.
Adds a read-only Delivery page for tickets backed by a deployment-provided evidence service. It displays the reviewed patch, independent QA, token usage, current PR commit, and the CI evidence commit. Refresh reads the service again and marks earlier passing CI stale when the PR head changes.
The client uses a documented same-origin GET contract. Development proxy configuration is supplied at runtime.
Validation: targeted Vite+ formatting and lint, web type checking, and a Windows browser run against a disposable sidecar and PR. The same page showed passing CI before a push and stale CI after refresh. The exact PR head also passed the same check in the Windows Electron app using a separate development profile. After a disposable PR push, Refresh showed the new head and marked the earlier CI result stale. The independent QA verdict remained tied to the original reviewed patch.
Windows T3 Delivery rehearsal
The isolated Windows Electron build opened the real pull request URL for canary PR pingdotgg#307 through the read-only Dell sidecar. Before the fixture push, CI run 43712783443 passed on 02e3d2b. After a content-neutral commit advanced the head to 4be3f16, Delivery reported the new run as pending and Claude QA remained attached to f35232f. The final display shows successful CI run 43835487225 for 4be3f16 alongside stale run 43712783443 for 02e3d2b. The Dell fork tree and the Windows rehearsal tree match. Web typecheck, targeted lint, and focused sidecar tests passed.