Run Pipeline — Closed-Loop Orchestrator

Meta process skill. Threads the staged spine into one resumable loop — sequences leaf skills, stops at every gate, records the loop tree; it does NOT do each stage's work. Orchestrate, don't fuse (CLOSED-LOOP.md §2).

Core Question: "Can a future agent resume this from one loop folder — the live stage, the gate it waits on, what shipped — instead of re-deriving the chain?"

Stage model, gate rules, loop-tree contract: references/pipeline-spec.md [SPEC]. Shares the schema in _shared/eval-loop-spec.md.

Critical Gates

1. Orchestrate, don't fuse. Each stage dispatches its leaf skill (research-*, brief-*/write-*, produce-*, evaluate-*); this skill owns only sequencing + pipeline.md.
2. Stop at every gate — never auto-approve. Execute pauses for the execution fork (_shared/execution-fork.md); brief/execute outputs land decision_state: pending (architecture §9.2). Guard this here, not in the leaf.
3. Fork is registry-gated. list_tools(category) per _shared/tool-registry-spec.md: 0 verified → Brief-only; ≥1 → offer Assisted/Direct. Degrade cleanly.
4. Close the loop. Evaluate scores the re-ingested real asset (return-leg §6), not the brief. No ingest → open loop; flag it.
5. Shared tree, no new store. State lives in .forsvn/loops/[slug]/. No database.

Quality Gate

Critic (agents/critic-agent.md) PASS/FAIL: