[sweep] strip Fxxx audit-ID tokens + trim bloated comments/docstrings + add behavior-change docs

Post-audit sweep over the 135 audit-fix commits since 19a474d3:

1. Stripped every # Fxxx: audit-ID token from comments AND every Fxxx token
   from docstring openings across 211 blocks / ~626 lines. The CEO flagged
   these twice: audit-issue IDs in code confuse future devs/agents. The
   descriptive text is preserved; only the Fxxx token is removed (and bloated
   narrative blocks trimmed to 1-3 lines keeping the one non-obvious invariant).
2. Trimmed bloated comments/docstrings to the concise standard (1-3 lines).
3. Added missing behavior-change docs for the audit-fix batch: prompts/roles
   (documenter, pr_reviewer, qa), user-facing docs (api auth, websockets,
   agent-gateway, megatask, merge-model, task-lifecycle, grok, resilience,
   conventions, panel, security, troubleshooting), and the RAG corpus (cell-pm,
   main-pm, pr-reviewer, qa roles; conventions; messaging-tools; escalation;
   megatask; task-claiming workflows).

Comment/docstring/prose ONLY — zero code-line edits (verified: the diff
contains no def/class/return/if/for/await/assignment/call lines). Gates green:
ruff format + ruff check clean, mypy clean on roboco/. The only pytest failures
are the pre-existing sync_branch tracing-decision gap (B1, 250be5c2) — not
sweep-caused and tracked separately.

tests/unit/gateway/test_claim_guards_blocked.py

@@ -1,12 +1,6 @@
-"""F018 — ``already_active_guard`` must treat a ``blocked`` task as active.
-
-``_ACTIVE_BLOCKING_STATUSES`` excluded ``blocked``, so a developer with a
-blocked task could claim a second task (the guard passed). When the blocked
-task was later unblocked via ``unblock_with_restore`` it resumed to
-``in_progress`` — leaving the dev silently holding TWO ``in_progress`` tasks,
-violating the one-active-task-per-dev invariant the guard exists to enforce.
-A blocked task is still owned and will resume to active, so it must block a
-new claim.
+"""``already_active_guard`` must treat a ``blocked`` task as active. A blocked
+task is still owned and will resume to ``in_progress`` on unblock, so it must
+block a new claim (preserves the one-active-task-per-dev invariant).
 """
 
 from __future__ import annotations
@@ -25,7 +19,7 @@ def _task(*, status: str) -> MagicMock:
 
 
 def test_already_active_guard_blocks_when_agent_has_blocked_task() -> None:
-    """A blocked task the dev still owns must block a new claim (F018)."""
+    """A blocked task the dev still owns must block a new claim."""
     target_id = uuid4()
     blocked = _task(status="blocked")
     env = already_active_guard([blocked], target_id)