docs(doctrine): challenge route rides the first challenge call; summary Advisor row; feat/bugfix skip the end call on clean gates

This commit is contained in:
bchanot committed 2026-11-18 14:57:07 +01:00
1 parent 858bd41782
commit 2b7aeb8605
14 files changed
+59 -34

No files matched your search

+17 -9
View File
@@ -115,15 +115,23 @@ triggers in CLAUDE.global.md § Workflow):
(a contract micro-gate, an early escalation, the STOP diagnosis) and
never enters an executor brief.
3. Before proposing a merge (`gitflow finish`) or calling a long task
done. Wired at the end step of feat, bugfix, ship-feature,
init-project, a11y, guardrails, audit-delta and tour, and at the
release gate of release-candidate: one end-of-run call per skill
run, never skipped for an earlier plan or stuck call; audit-delta
and tour skip it when the run applied no fix. In the six flows that
run the gates, the main loop first prints the run's diff stat, a fix
the answer drives goes back through the gates, and a later proposal
reuses the answer and says it predates the newer commits. Elsewhere
the answer is reported only and a fix it calls for is a new run.
done. Wired at the commit step of feat and bugfix, at the end step
of ship-feature, init-project, a11y, guardrails, audit-delta and
tour, and at the release gate of release-candidate: one end-of-run
call per skill run, never skipped for an earlier plan or stuck call.
Two skips only: audit-delta and tour when the run applied no fix;
feat and bugfix when GATE 0 said MET, the verifier CONFORME and
security PASS (not DEGRADED), each on its first attempt (any other
verdict, a retry, a loop iteration or a verdict no longer in view
runs the call), their summary then reading
`skipped (gates clean on first pass)`. A skipped call discharges
its point and the trigger it covers. In the six flows that run the
gates (feat, bugfix, ship-feature, init-project, a11y, guardrails),
the main loop first prints the run's diff stat, a fix the answer
drives goes back through the gates, and a later merge proposal
reuses the last run's answer, or its skip, and names any code commit
made after it (doc and memory commits excepted). Elsewhere the
answer is reported only and a fix it calls for is a new run.
Inside a skill run, the points above also cover the triggers of
CLAUDE.global.md § Workflow; no second call for the same recommendation.