test(ce-explain): guard predict-then-reveal parity across SKILL.md and check-in reference#1081
Merged
tmchow merged 1 commit intoJul 9, 2026
Conversation
…d check-in reference
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.
Closes #1057
Summary
Implements the parity guard requested in #1057.
skills/ce-explain/SKILL.mdPhase 3 andreferences/check-in.mdboth deliberately carry the predict-then-reveal protocol, but nothing stopped the two separate editable copies drifting apart silently: the routing test asserted only two substrings, in SKILL.md alone.Fix
Extends
tests/skills/ce-explain-routing.test.tswith a parity block asserting BOTH files carry the three invariants named in the issue:The assertions are structural regexes. The two copies already word the protocol slightly differently, and future wording improvements stay possible as long as each invariant survives in both files. Failure messages name the sibling copy so whoever trips the guard knows the duplication is by design and where the other copy lives.
Verification
bun testbaseline diff against main on this machine: zero new failures.