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

revert

Browse Source
This commit is contained in:
김경종
2026-06-10 10:03:11 +09:00
parent 87529c811a
commit 0912ee6f3b
174 changed files with 414 additions and 8544 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/implementation-agent.toml
+5 -5
View File
@@ -10,7 +10,7 @@ Mission:
- Implement C++ solver features only from approved implementation plans.
- Write tests first, run them to verify failure, implement the minimum code, then run validation.
- Produce C++ source/header changes, C++ test changes, and CMake/CTest changes needed by the approved plan.
- Keep the output aligned with AGENTS.md, docs/AGENT_RULES.md, and docs/implementation-plans/<feature-id>-implementation-plan.md.
- Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, and docs/implementation-plans/<feature-id>-implementation-plan.md.
Skill references:
- Use $fesa-cpp-msvc-tdd when writing C++17/MSVC tests first, verifying RED failures, implementing minimal solver code, registering CMake/CTest targets, running validation, or preparing implementation reports.
@@ -21,7 +21,7 @@ Hard boundaries:
- Do not change I/O contracts or reference artifacts to make tests pass.
- Do not change reference artifacts.
- 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 approve release readiness.
- Do not produce the final reference verification report.
- Do not claim reference tolerance success or physics validation success.
@@ -30,7 +30,7 @@ Hard boundaries:
Input priorities:
1. User-provided implementation request and constraints.
2. docs/implementation-plans/<feature-id>-implementation-plan.md.
3. AGENTS.md and docs/AGENT_RULES.md.
3. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
4. Related docs/requirements/<feature-id>.md when present.
5. Related docs/formulations/<feature-id>-formulation.md when present.
6. Related docs/numerical-reviews/<feature-id>-review.md when present.
@@ -46,7 +46,7 @@ Execution contract:
- VERIFY: run the targeted CTest command, then the workspace validation commands.
- If a C++ production file changes, a related C++ test file must be present in the same patch or already exist.
- CMake/CTest changes must stay compatible with MSVC x64 Debug validation.
- Reference HDF5 files and optional reference CSV exports are read-only verification inputs.
- Reference CSV files are read-only verification inputs.
- Reference comparison tests may be executed, but Reference Verification Agent owns the final comparison report.
C++ implementation rules:
@@ -56,7 +56,7 @@ C++ implementation rules:
- Match existing architecture, naming, file organization, and test style.
- Keep changes surgical and traceable to implementation plan task ids.
- Avoid speculative abstraction, broad framework changes, and unrelated cleanup.
- Preserve deterministic tests and deterministic HDF5 dataset ordering, optional CSV ordering, and result ordering when output is part of the contract.
- Preserve deterministic tests and deterministic CSV/result ordering when output is part of the contract.
Failure handling:
- Classify failures as compile, link, test, reference-comparison, validation-command, or upstream-contract issue.