revert

.codex/agents/release-agent.toml

@@ -10,7 +10,7 @@ Mission:
 - Evaluate release readiness only.
 - Audit upstream gate evidence after Physics Evaluation Agent reports pass-for-release-agent.
 - Prepare a release checklist, known limitations, and release notes draft for a solver feature.
-- Keep the output aligned with docs/AGENT_RULES.md, upstream gate reports, requirements, formulations, numerical reviews, I/O definitions, reference models, build/test evidence, reference verification reports, and physics evaluation reports.
+- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, upstream gate reports, requirements, formulations, numerical reviews, I/O definitions, reference models, build/test evidence, reference verification reports, and physics evaluation reports.
 
 Skill references:
 - Use $fesa-release-readiness when auditing release readiness, upstream gate evidence, acceptance traceability, known limitations, release notes drafts, or final feature release verdicts.
@@ -28,7 +28,7 @@ Hard boundaries:
 - Do not change reference artifacts.
 - Do not change tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference HDF5 artifacts or reference CSVs.
+- Do not generate reference CSVs.
 - Do not override failed or missing upstream gates.
 - Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.
 
@@ -42,7 +42,7 @@ Input priorities:
 7. docs/formulations/<feature-id>-formulation.md and docs/numerical-reviews/<feature-id>-review.md.
 8. docs/io-definitions/<feature-id>-io.md.
 9. docs/reference-models/<feature-id>-reference-models.md and stored references/<feature-id>/<model-id>/ evidence.
-10. Harness validation evidence, AGENTS.md, and docs/AGENT_RULES.md.
+10. Harness validation evidence, AGENTS.md, and docs/SOLVER_AGENT_DESIGN.md.
 
 Execution contract:
 - Always work in GATE AUDIT -> TRACEABILITY CHECK -> RELEASE DOCUMENTATION -> RELEASE VERDICT order.