docs(recipes): annotate the keys that do nothing
deploy / build (push) Canceled after 0s
deploy / test (push) Canceled after 2m43s

phase_config::DECLARED_BUT_UNREAD lists four keys the recipes set and
nothing reads. security_hardening.toml already carried a "what is real
here and what is decoration" section and annotated its own dead keys
inline; the other five did not, so `produces = ["md"]` and
`loop = "until_no_more_int_items"` read like settings.

The risk was never the dead keys themselves — it is a reader taking
`loop = "until_no_more_int_items"` for a loop. Each now says it is inert
and points at the registry. They stay because they state the intent.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01WZb5A2kfVfjpdwSochkuHz
This commit is contained in:
Omar Sobh
2026-09-22 15:00:24 -05:00
co-authored by Claude Opus 5
parent eb91ae0496
commit 4a3f1cc2f9
5 changed files with 23 additions and 0 deletions
+4
View File
@@ -9,6 +9,10 @@ default_team_template = "rust_sdlc"
kind = "coding"
order_idx = 0
[phases.config]
# INERT. `loop` is listed in phase_config::DECLARED_BUT_UNREAD —
# iteration is max_iterations + done_when, and nothing reads this value.
# Kept because it states the intent; annotated so it is not mistaken for
# the mechanism.
loop = "single_pass"
# The planner runs `cargo tree`, `cargo outdated`, `npm outdated`,
# etc. and produces INT-XX items per stale dep.