refactor: make coordinator the main workflow agent

.codex/skills/fesa-release-readiness/SKILL.md

@@ -13,17 +13,24 @@ Read these first:
 
 - `AGENTS.md`
 - `docs/SOLVER_AGENT_DESIGN.md`
-- `docs/releases/README.md`
-- Physics Evaluation report with `pass-for-release-agent`
-- Reference Verification report with `pass-for-physics-evaluation`
-- Build/Test report with `pass-for-reference-verification`
-- Requirements, formulation, numerical review, I/O definition, reference model, implementation, and correction reports
+- `docs/<feature-id>/requirements.md`
+- `docs/<feature-id>/research.md`
+- `docs/<feature-id>/formulation.md`
+- `docs/<feature-id>/numerical-review.md`
+- `docs/<feature-id>/reference-model.md`
+- `docs/<feature-id>/io.md`
+- `docs/<feature-id>/implementation-plan.md`
+- `docs/<feature-id>/implementation-report.md`
+- `docs/<feature-id>/build-test.md` with passing full validation evidence
+- `docs/<feature-id>/reference-comparison.md` with `pass-for-physics-evaluation`
+- `docs/<feature-id>/corrections.md` when correction occurred
+- `docs/<feature-id>/physics-evaluation.md` with `pass-for-release-agent`
 
 ## Workflow
 
 1. Follow `GATE AUDIT -> TRACEABILITY CHECK -> RELEASE DOCUMENTATION -> RELEASE VERDICT`.
 2. GATE AUDIT: confirm required reports exist, share the same `feature_id`, are not stale or contradictory, and carry required pass statuses.
-3. Require `pass-for-reference-verification`, `pass-for-physics-evaluation`, and `pass-for-release-agent`.
+3. Require passing full validation evidence, `pass-for-physics-evaluation`, and `pass-for-release-agent`.
 4. TRACEABILITY CHECK: confirm each `must` requirement maps to acceptance criteria, test evidence,
    feature-required reference evidence when applicable, and release scope.
 5. Record deferred requirements, unsupported Abaqus keywords, missing required comparison files,
@@ -33,7 +40,7 @@ Read these first:
 
 ## Output Contract
 
-Produce or revise `docs/releases/<feature-id>-release.md` with:
+Produce or revise `docs/<feature-id>/release.md` with:
 
 - Metadata
 - Release Scope
@@ -58,7 +65,7 @@ Produce or revise `docs/releases/<feature-id>-release.md` with:
 
 ## Quality Gate
 
-- Do not issue `ready-for-release` without `pass-for-release-agent`, `pass-for-physics-evaluation`, and `pass-for-reference-verification`.
+- Do not issue `ready-for-release` without `pass-for-release-agent`, `pass-for-physics-evaluation`, and passing full build/test evidence.
 - Every `must` requirement traces to release scope, acceptance criteria, test or reference evidence, and final disposition.
 - Known limitations and deferred issues are included in the Release Notes Draft.
 - Missing required evidence, contradictory reports, unresolved defects, missing declared comparison
@@ -67,4 +74,4 @@ Produce or revise `docs/releases/<feature-id>-release.md` with:
 
 ## Handoff
 
-Send `ready-for-release` to Coordinator Agent for final workflow closure. Send missing documentation to Release Agent revision, missing verification to Reference Verification Agent or Physics Evaluation Agent, and implementation defects to Correction Agent.
+Return `docs/<feature-id>/release.md`, status, evidence summary, blockers, and a closure recommendation to Coordinator Agent. Return missing implementation/build/comparison evidence, missing physics evidence, upstream gaps, or documentation gaps to Coordinator Agent for the owning sub-agent; do not advance or close the workflow directly.