docs(recipes): annotate the keys that do nothing

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
2026-09-22 15:00:24 -05:00
parent eb91ae0496
commit 4a3f1cc2f9
5 changed files with 23 additions and 0 deletions
@@ -21,6 +21,9 @@ order_idx = 0
 # `pdf` dropped — PDF rendering was removed from the delivery path and
 # artifacts are served as Markdown, so asking for it named a format nothing
 # generates. `security_hardening` was corrected for this; this recipe was not.
+# INERT. `produces` is listed in phase_config::DECLARED_BUT_UNREAD —
+# artifact rendering is not driven by it. Kept because it states the
+# intent, annotated because a reader should not take it for a setting.
 produces         = ["md"]
 default_topology = "hub_spoke"
 # This recipe had NEITHER of the two keys below, which is the same defect