test(rendering): slice 13 — shadow parity suite (legacy vs new pipeline in CI)#441
Merged
Juliusolsson05 merged 1 commit intoJul 7, 2026
Conversation
…ne in CI) Runs the exact comparison useRenderShadow performs live — legacy selectMergedEntries + deriveFeedRenderModel vs adapter + ledger, diffed by shadowDiff — over constructed runtimes, so divergence triage starts in CI with a minimal repro, not in a soak console. Seven scenarios from the incident trail: idle conversation, live turn + work, claude whole-turn suppression, empty session, stuck-tool ghost renders, sidecar ghost hidden, and the #239 buried-prompt class (both sides now agree at the unit grain — parity pinned, not just divergence tolerated). All seven pass with ZERO divergences on first run. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The Stage 2 diff run, executed inside CI: the exact comparison
useRenderShadowperforms live — legacyselectMergedEntries+deriveFeedRenderModelvscreateLedgerInputAdapter+createSessionLedger, diffed byshadowDiff— over constructedSessionRuntimestates, so divergence triage starts in a test with a minimal repro rather than in a soak console with a live session attached.Seven scenarios from the incident trail:
All seven pass with zero divergences on first run — including #7, meaning legacy and the new pipeline agree at the unit grain on every scenario tested so far. The suite is structured so a legitimate future disagreement (the new pipeline fixing a legacy bug) must be asserted explicitly with an issue reference — no blanket "known to differ" escape hatch.
79 pipeline tests total; tsc gate (node + web) clean.
Left open for review per request — not self-merging this one.
🤖 Generated with Claude Code