M6 event pathway: govern the react_template fast path (parity with TIME) — Sam ruling t250-Q4

[MSD21091969]

Sam's t250 ruling 4 (recorded 93c86ce, per-question elicitation via the governance seat): the M6 event pathway must stage proposals like the TIME pathway — runtime.go:570-579 currently auto-applies react_template results ungoverned (FP-fruits finding v, F-a-class). Exception path: if Wolfram demonstrates the fast path is load-bearing, it gets DECLARED as intended with its own guard instead.

Work sketch (same class as the #50/#51 color-gate lane):

1. Read the M6 apply path + inventory which live react_templates (if any) depend on immediate application.
2. Either: route event-pathway emissions through the WF13 governance_proposal staging the TIME pathway uses (sweep parity), or: document + guard the fast path explicitly (declared allowlist, logged firings).
3. Tests: event-trigger → proposal staged (not applied) unless allowlisted; replay unaffected.

Refs: FP-fruits dev/design/manifold-bump-4_0/20260708-t249-fp-fruits.md (finding v) · ruling record dev/design/manifold-bump-4_0/20260708-t250-ag-questions-for-zappa.md §4.4 · #50/#51 precedent (data-driven → THEN fail-closed).

GATE: runtime code PR-route; no HG writes from this issue.

authored-by: agent:claude-cowork.hp-z440 / session:sam.z440-cowork-workspace / t250-testing-ontology

🤖 Generated with Claude Code