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/continuous_research.toml

@@ -28,6 +28,9 @@ default_team_template = "continuous_research"
 kind      = "research"
 order_idx = 0
 [phases.config]
+# 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`, not a new `read` kind. An unrecognised kind falls through to
@@ -71,6 +74,9 @@ commit_policy = "always"
 kind      = "research"
 order_idx = 1
 [phases.config]
+# 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"
 task = """