The reviewer/planner gate in fusion was rejecting the original
incident-routing payload because it lacked the markers fusion expects
of an engineering specification. The triage agent looped on PROMPT.md
revisions because each rewrite still had no explicit Mission, File
Scope, Steps with verifiable outcomes, Testing Requirements, or
Acceptance Criteria.
Reshape buildIncidentDescription so the task body is recognized as a
spec on first pass: explicit Mission line, Background (preserves the
alert + signal context the agent needs to investigate), domain-aware
File Scope with allowed/disallowed paths, five numbered Steps each
with its own acceptance line, Dependencies, Testing Requirements
referencing the incident fingerprint, Documentation Deliverables for
the executor's work-log + QA's fix-patterns memory entry, Acceptance
Criteria checklist, and severity-aware Routing Notes. The raw Grafana
payload is kept at the bottom as an audit-trail block.
fileScopeForDomain() picks include/exclude lists from the upstream
domain hint: backend → API surface, frontend/product → web surface,
unknown → API. Critical-path directories (auth, payments, billing,
subscriptions, migrations, schema, ecosystem.config.js, lockfile)
are always in the disallow list so the executor stops before
modifying them — keeps human-approval policy enforceable.
f26c459e41