test(cli): embedded/remote parity matrix (RFC-009 Phase 1)#208
Open
aaltshuler wants to merge 1 commit into
Open
test(cli): embedded/remote parity matrix (RFC-009 Phase 1)#208aaltshuler wants to merge 1 commit into
aaltshuler wants to merge 1 commit into
Conversation
The referee before any unification moves: every forked verb runs once against the local graph and once against a spawned server on a twin copy of the same fixture, with the SAME actor (--as locally; bearer-resolved remotely) and the SAME Cedar bundle on both arms — like-for-like enforcement is part of the harness (a tokens-only server is default-deny by design; comparing that against a bare local arm measures configuration, not the fork). Declared-volatile fields (ids, wall-clock, transport locations) scrub to placeholders; everything else must match exactly, and exit codes must match for shared failures. Headline result: 11 rows green with an EMPTY divergence ledger — the arms agree on every verb today. The ledger (KNOWN_DIVERGENCES) exists so any future divergence is pinned or filed, never silently repaired; repairs are Phase 3's job, gated by this referee staying green. One engine observation surfaced and filed (#207): inline execution with a declared-but-unbound param matches ALL rows on both arms, while the stored-query invoke path hard-errors — a cross-path asymmetry the matrix pins as agreeing behavior pending a deliberate fix. Documented exclusions (graphs list, ingest/load-over-/ingest, storage-plane verbs) map to RFC-009 Phases 4-5. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
aaltshuler has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
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.
The referee, landed before anything moves — per RFC-009's ordering (and the storage-collapse playbook).
What it does
parity_matrix.rs: every forked verb (query, schema show/plan-adjacent reads, snapshot, branch list/create/delete/merge, commit list, mutate, load) runs once embedded and once against a spawned server on a twin copy of the same fixture — same actor on both arms (--asvs bearer-resolved, equal by construction), same Cedar bundle on both arms (the harness's key insight: a tokens-only server is default-deny by design, so unmatched policy measures configuration, not the fork). Declared-volatile fields scrub to placeholders; the rest is byte-exact, plus exit-code equality for shared failures.Results
KNOWN_DIVERGENCESledger + a guard test make any future divergence a pinned, deliberate decision.graphs list,load-rides-/ingest, storage-plane verbs) map forward to RFC-009 Phases 4–5; theparity_loadrow is where Phase 5's/loadflip becomes visible.RFC-009 Phase 1 ticked with the outcome recorded;
testing.mdrow added. Full workspace gate green (58 suites — the matrix is the 58th).🤖 Generated with Claude Code