docs(getff-any-stack-trace): S2b + R1 dispatch inputs (operator-invited) + meta-launch amendment

[artyhoo]

What

Operator-invited insertion (2026-07-26) into the getff-any-stack-trace umbrella:

• S2b dispatch input — close the python lane's empty git-hook rung. Task 0 is the missing prior-art verdict: SSOT feat(meta-orchestrator): §1.7 PR-body authoring mandate in kickoff template #216 REJECTed pre-commit as a delivery scaffolder, and python-delivery-v0/kickoff.md:97-98 consumed that as a verdict on the enforcement channel — pre-commit in its actual RUNNER role was never verdicted. S2b runs that verdict (criteria: zero installed prerequisites > augment-first > Node-free) and delivers the rung per its outcome, with a RED/GREEN firing proof that goes THROUGH git.
• R1 dispatch input — a lane × channel-rung parity audit (npm / python / cargo + verify-go-absent, 7 rungs): every EXISTS cell needs firing evidence, every GAP cell a provenance classification (DECIDED-AGAINST / MISDECIDED / DEFERRED / SILENTLY-MISSED). One research patch, zero code.
• Meta-launch amendment — launch-table rows, S2→S2b→S3 gate rewiring (R1 non-gating), declared S2b∥R1 parallelism with the full write-set enumeration (disjoint incl. the SSOT: one writer, one reader).

Review findings

Cold Phase -1 review of all three artefacts: REVISE — 1 BLOCKER, 4 MAJOR, 3 MINOR, every finding verified against the tree before applying:

• BLOCKER — R1's kickoff was silent on the fidelity-verdict-in-pr-body required check, which has no paths filter and rejects skipped once a ## Provenance substrate is declared (packages/core/hooks/checks/pr-body-fidelity.ts:19); an autonomous worker harvested through aif would have hit an unpassable red check. R1 §7 now carries both legal shapes and who produces the GO block.
• MAJOR ×4 — the S2b fidelity trap omitted the ## Fidelity verdict H2-heading requirement (pr-body-fidelity.ts:35); R1's scope comment claimed executor-tier dispatch without a marker (claim removed — routing follows project defaults); the meta-launch retained three parallelism statements contradicting the new declared S2b∥R1 pair (all three scoped to the spec stages); the amendment's S2b write-set was undercounted (missing the SSOT row + the likely hook template — the same enumeration-undercount class as S2's ban-encoding BLOCKER).
• MINOR ×3 — excluded-columns rationale for R1's matrix (production audit / mutation gates named as exclusions, column 1 widened to lane-native edit-time channels); a bare-remote note for the pre-push fixture variant; an accept-time instruction to diff the test file for the new arm's existence (host-verify passes trivially without it — T14).

Gates: principle 12 → 7/7 PASS; host-verify.sh --list parses both kickoffs (S2b fence; R1 explicit ≥20-char opt-out).

Deliberately NOT done in this PR

No dispatch. The operator paused the session on limits; the next session merges this, re-probes in-flight, dispatches S2b + R1 to aif in parallel, and arms monitors. done.md remains S4's.

Fidelity verdict

FIDELITY: skipped — dispatch-input authoring plus a meta-launch amendment, no implementation surface, no substrate produced this diff; authored and cold-reviewed in-session with the findings enumerated above, applied at .claude/orchestrator-prompts/getff-any-stack-trace-s2b/kickoff.md:1 and getff-any-stack-trace-r1/kickoff.md:1; the stage PRs these kickoffs dispatch each carry their own cold verdict.

§1.7 Skipped: additive dispatch-input authoring and a meta-launch amendment across three orchestrator-prompt kickoff files — a path doc-authority-hierarchy.md §2 explicitly exempts from authority headers (tracked-but-header-exempt filename-convention transients). No discipline surface is created, extended, or superseded; the stage PRs these kickoffs dispatch carry the forward/backward sections where their diffs reach the trigger paths.