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

docs: bind implementation agents to Harness steps

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-12 15:16:01 +09:00
parent ab69a3d0e2
commit 713b41b771
2 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/implementation-agent.toml
+18
View File
@@ -15,6 +15,11 @@ Mission:
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.
Mandatory Harness reading:
- Read .agents/skills/harness/SKILL.md, docs/HARNESS.md, docs/HARNESS_WORKFLOW.md, and
.codex/hooks.json before executing a Harness Step; inspect the relevant phase indexes and
supplied Step file as well.
Hard boundaries:
- Do not change requirements, formulations, I/O contracts, numerical review reports, reference artifacts, or tolerance policies unless the user explicitly asks.
- Do not change formulations directly to make implementation easier.
@@ -39,6 +44,13 @@ Input priorities:
9. Existing source, tests, CMake files, harness scripts, and stored reference artifacts when present.
Execution contract:
- Require an approved implementation plan, materialized phase files, and the Executor-selected
current Step (`Executor-selected current Step`). Do not fall back to the broad plan or start a
later pending Step.
- Execute this recipe within the current Step: approved plan + materialized phase files +
Executor-selected current `stepN.md` -> read prerequisites and previous summaries -> RED ->
observe expected failure -> minimal GREEN -> focused/full VERIFY -> update only current Step
status plus `summary`/`error_message`/`blocked_reason` -> stop without starting the next Step.
- Always work in RED -> GREEN -> VERIFY order.
- RED: write the planned C++ unit, integration, parser/I/O, or reference-comparison test first.
- RED: run the targeted test and verify failure before production implementation.
@@ -46,6 +58,12 @@ Execution contract:
- VERIFY: run the targeted CTest command, then the full MSVC build/test commands resolved from `.harness/config.json` or the Harness defaults.
- VERIFY: record RED and GREEN evidence explicitly; PreToolUse only checks that a related test file exists.
- VERIFY: allow Stop to rerun whole-project MSVC build/test before the Step ends.
- `.codex/hooks.json` is authoritative: PreToolUse runs `scripts/hooks/pre_tool_use.py` and Stop
runs `scripts/hooks/stop_validation.py` automatically. Hooks do not prove RED, and their Python
entry points must not be manually invoked as substitutes for registered hooks.
- The Executor owns timestamps, retry control, commits, and next-Step selection. Do not write
`started_at`, `completed_at`, `failed_at`, `blocked_at`, task timestamps, or top-level phase
status from the Implementation Agent.
- 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.
- Abaqus reference CSV files are read-only verification inputs.