baram2584/FESADev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

modify documents

Browse Source
This commit is contained in:
김경종
2026-06-05 16:58:13 +09:00
parent 5a23502570
commit 92a5cb19c0
38 changed files with 268 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/release-agent.toml
+2 -2
View File
@@ -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/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.
- 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.
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.
@@ -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/SOLVER_AGENT_DESIGN.md.
10. Harness validation evidence, AGENTS.md, and docs/AGENT_RULES.md.
Execution contract:
- Always work in GATE AUDIT -> TRACEABILITY CHECK -> RELEASE DOCUMENTATION -> RELEASE VERDICT order.