Repository navigation
docs(skills): analog-emulation traps from the compile-answer retry (Closes #12637) - #12638
Conversation
…loses #12637) Three trap lines: the success gate of a driver change runs with the lane-built driver and the new summary line shows which driver ran; a rule over a tool's text output lives in a sealed spec and the old unit test pays for the glue; a path no live run exercised is reported with its live count of 0. Refs #10486 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Summary by t27-beesThis PR adds three trap entries to the analog-emulation skill document, documenting lessons learned from PR #12539 about gate execution with lane-built drivers, moving rules to pure functions in sealed specs, and reporting unexercised paths with live counts. Worth a lookNothing stood out. Read: 1 files, +3 -0, the whole diff. Head |
|
Merge basis (read at 13:02 +07, head
Merging with 🤖 Addressed by Claude Code |
|
Post-merge read (13:05 +07): 🤖 Addressed by Claude Code |
What
Three trap lines at the end of "Traps" in
.claude/skills/analog-emulation/SKILL.md, from the work of #12539 (PR 12636).Closes #12637. Refs #10486.
Changes
tri mutatedriver runs with the driver built from the lane; the new summary line (Compile answers ...) shows which driver ran.cli/tri/src/mutate.rs).Checks run
git diff --stat).foreign-budget,own-language,secret-gate) passed on the commit.Not claimed
No speed claim. The figures quoted (223 killed, 2 survived, 27 hung, 0 unviable, exit 0; 34 added, 47 deleted) are the ones already recorded in the merge basis of PR 12636.
🤖 Generated with Claude Code