test(suite): replace plan-label references with self-contained wording

Rust test comments/assert messages and deep-research script docstrings
cited numbered requirement labels (R3/R5) and task labels (TASK-016,
TASK-021) that are defined only in an external plan document. Reword
each to say what it means on its own: fail-safe crash guards, the
validator's fallback-capture warning, task-queue anchors.

assets/agents/deep-research/README.md

@@ -263,7 +263,7 @@ pass — every fault is visible to the reviewer or the caller — and some
 end node always renders its sentinel, so the graph degrades instead of
 dying.
 
-All 11 scripts also carry a top-level crash guard (R3): a script that
+All 11 scripts also carry a top-level crash guard: a script that
 throws records a fault and fails forward where the flow allows it (a
 crashed `reflexion_gate` proceeds to `synthesize`; a crashed
 `verify_sources` reports that sources were NOT checked) instead of

assets/agents/deep-research/scripts/bootstrap_research.py

@@ -7,7 +7,7 @@ the RAG knowledge lookup) as a single super-step. The validator requires
 declared parallel-branch script outputs, so we emit an empty JSON object
 explicitly here.
 
-Fail-safe (R3): the node reads no state and computes nothing, so its
+Fail-safe: the node reads no state and computes nothing, so its
 happy-path output IS the sane degraded output — the guard emits the same
 empty object on any crash. No PIPELINE-FAULT is recorded: appending one
 would require reading state (the very thing that crashed) or clobbering

assets/agents/deep-research/scripts/combine_findings.py

@@ -14,7 +14,7 @@ surface their collected output_key). This script lifts such findings into
 `pipeline_faults` (deduplicated, since a reflexion or feedback loop can
 re-run the map) so dead lanes surface in the report's Pipeline notes.
 
-Fail-safe (R3): on a crash (e.g. malformed GRAPH_STATE), `findings`
+Fail-safe: on a crash (e.g. malformed GRAPH_STATE), `findings`
 becomes the fault text itself and a PIPELINE-FAULT entry is recorded —
 the pipeline proceeds visibly degraded, and the human approval gate is
 the backstop. Existing faults are preserved best-effort.

assets/agents/deep-research/scripts/incorporate_feedback.py

@@ -11,7 +11,7 @@ budget.
 
 Routing (`_next`): always research_each_question.
 
-Fail-safe (R3): a crash here means the user's feedback text cannot be
+Fail-safe: a crash here means the user's feedback text cannot be
 recovered, but their INTENT — another research pass — is unambiguous
 (they chose neither accept nor reject). The degraded route therefore
 still loops to `research_each_question`, with a generic feedback note

assets/agents/deep-research/scripts/parse_request.py

@@ -10,7 +10,7 @@ Routing (`_next`):
   - prompt present -> (no _next; static next: plan)
   - prompt empty   -> ask_topic
 
-Fail-safe (R3): a crash here (e.g. malformed GRAPH_STATE) means the
+Fail-safe: a crash here (e.g. malformed GRAPH_STATE) means the
 caller's prompt cannot be read at all, so proceeding silently is
 meaningless — the degraded route is `ask_topic`, which asks the user for
 the topic directly, plus a PIPELINE-FAULT entry so the loss is visible in

assets/agents/deep-research/scripts/reflexion_gate.py

@@ -16,7 +16,7 @@ Reflexion is a best-effort quality booster, not a hard gate: once the
 budget is spent the workflow proceeds anyway, and the human approval
 step is the final backstop.
 
-Fail-safe (R3): a crash here fails FORWARD to `synthesize` — the same
+Fail-safe: a crash here fails FORWARD to `synthesize` — the same
 direction as the existing malformed-critique PASS default — with a
 PIPELINE-FAULT entry recorded (best-effort preserving existing faults),
 so a broken gate costs the run its automated critique routing, never the

assets/agents/deep-research/scripts/verify_sources.py

@@ -15,7 +15,7 @@ rendered section when `pipeline_faults` is non-empty and the empty
 string otherwise, keeping the happy-path `{{report}}{{pipeline_notes}}`
 output byte-identical to the pre-hardening `{{report}}`.
 
-Fail-safe (R3): per-URL probes were already guarded; the top level now
+Fail-safe: per-URL probes were already guarded; the top level now
 is too. On a crash the summary says sources were NOT checked, a
 PIPELINE-FAULT is recorded (best-effort preserving existing faults), and
 pipeline_notes still renders — the approval gate remains the backstop.