Repository navigation
docs(statechart): use upstream's report wording everywhere - #30
Conversation
Three docs and the help router still described the statechart report in the port's words. Use upstream 0.15.36's sentences, so every page says what the restored skill says. The skill reports the shortest path to each state that breaks a rule. The adaptation reasons in upstream.json no longer claim the wording fix, and the README reason describes the byte-for-byte skill.
|
Verdict: PASS+NOTES Head Check 1. Byte parity with upstream. PASS. Check 2. Sentence fact-check. PASS+NOTES, four CONFIRMED, one WRONG.
Check 3. Adaptation reasons still describe real divergence. PASS+NOTES.
Check 4. Gate commands. PASS. Notes. The single WRONG sentence is upstream's own wording, and this PR's goal is exact upstream parity, so I do not block on it. Raise the 500-state qualifier upstream rather than diverging here. The same applies to the temporal-counterexample coverage this PR removes, which is real behavior at |
Why
/statechartshould read and work exactly like Lauren Tan's 0.15.36 skill. PR #29 restored the skill, but four other pages still described its report in the port's words. This PR uses upstream's sentences on all four.What changed
docs/guide/06-verify-and-ship.md,create-formal-verification-skill, and thepoteto-helproute now use upstream's statechart sentence verbatim.upstream.jsonmatch the files again.Scope
Blast Radius
Docs and help text only. No code, test, or dependency changes.
Verification
bun run check:contentandbun run typecheckpass.