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

templates/workflows/research_and_code.toml

@@ -21,6 +21,9 @@ kind      = "research"
 order_idx = 0
 [phases.config]
 # `pdf` names a format nothing generates — artifacts are served as Markdown.
+# 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"
 # Research PLANS; coding BUILDS. Without this the split is a fiction:
@@ -74,6 +77,10 @@ order_idx = 1
 # DECLARED_BUT_UNREAD — "NOT IMPLEMENTED — phase iteration uses
 # max_iterations + done_when". It is kept only so the intent stays
 # visible next to the keys that actually drive the loop.
+# 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            = "until_no_more_int_items"
 # The real loop. Without `done_when` the phase never enters
 # `evaluating`, is never judged, and reports `completed` whatever it