Repository navigation
v1.23.2
The RULE SECTIONS shape no longer reads as a list split by /. The red 1.23.0 e2e run wrote
its sections with / between them, copying ✅ / N/A (reason), …, where / meant "or";
check_lines counted one section against 3 applicable and stopped the run at Gate 1 (fail-closed,
not false-green).
- Changed (skill text —
analysis,quick; templateticket.md): the shape now shows two
entries,§<id> (<source>) ✅ <what it constrains>, §<id> (<source>) N/A because <reason>, …, and
statesSeparate entries with,only.TheN/A because <reason>form the prose already required
is now in the shape itself.check_lines's canonical form,validate.py's rule-first check and
docs/reference/lines.mdfollow it. - Not changed: the checker.
/is still not a separator, so a line written that way still fails
the count — a new envelope test pins both the,pass and the/fail. - Size:
analysis3621 → 3620 words,ticket.md4273 → 4272 (a redundant clause cut in each). - Smoke guard:
multi-clause-want(mapped toanalysis) green, 57/57, fresh run. That fixture
does not emit aRULE SECTIONSline, so it shows the edit broke nothing it covers, not that agents
now write the line correctly; the golden e2e is that check.quickhas no mapped fixture.