---
name: fesa-release-readiness
description: Use when auditing FESA solver release readiness, upstream gate evidence, acceptance traceability, known limitations, release notes, and final feature release verdicts.
---

# FESA Release Readiness

Use this skill to audit whether a solver feature is ready for internal release closure after all technical gates pass.

## Inputs

Read these first:

- `AGENTS.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `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 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,
   unresolved defects, accepted risks, and known limitations.
6. RELEASE DOCUMENTATION: prepare a release checklist, Known Limitations, and Release Notes Draft.
7. RELEASE VERDICT: issue `ready-for-release` only when all required evidence is present and passing.

## Output Contract

Produce or revise `docs/<feature-id>/release.md` with:

- Metadata
- Release Scope
- Gate Evidence Inventory
- Acceptance Traceability
- Validation Evidence
- Known Limitations
- Release Notes Draft
- Release Verdict
- Handoff Recommendation
- No-Change Assertion
- Open Issues

## Boundaries

- Do not implement code.
- Do not edit source code, tests, CMake files, requirements, formulations, I/O contracts, reference artifacts, or tolerance policies.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate or modify Abaqus reference CSV files.
- Do not override failed or missing gates.
- Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.

## Quality Gate

- 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
  files, or unavailable validation commands block release readiness. Canonical naming, README,
  metadata, provenance, or unrequested portfolio expansion do not.

## Handoff

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.
