Repository navigation
v1.23.1
Three defects the 1.23.0 golden e2e found (3 runs on 1865fb1: 2 green, 1 red; the red run is
explained under Not changed below). Scripts only: no skill, agent, principle or template text changed.
- DISCLOSURE no longer claims a review ran.
run_contract.py disclosure-seedwroteON — the rule-book-grounded reviewer ranandON — the ticket-blind challenger ranbefore any phase had
run. A run that stopped at Gate 1 carried both claims; the agent had to correct them by hand. Line
one now readsON — enabled for this run, and states that whether the seat ran is the review phase's
record. proof.pyreads aunittest discovercommand. The unittest preset put-vbeforediscover,
which unittest rejects (unrecognized arguments: -s tests -t .), so a design naming
python3 -m unittest discover -s tests -t .wascould-not-run.-vnow goes afterdiscover.
The run disclosed it and measured with--command; nothing read clean.ticket_stats.pyreads an embedded working doc. Underwork_doc_mode: embedthe header sits
below the separator, after the ticket's own##sections; both green runs printedlane=unknown scope=unknown(exit 3). The script now reads below the separator, throughcheck_lines's own
reading of it, and also reads the backticked header shape (`TIER: full`).- Not changed: the red run. It wrote
RULE SECTIONSwith/between the sections;
check_linescounted one section against3 applicableand the gate stayed closed, so the run
stopped at Gate 1 with a correct account. The shape inskills/analysisreads✅ / N/A (reason), …,
where/means "or"; making that unambiguous is a skill edit and needs its smoke guard, so it is
left to its own change.