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

modify harness framework

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-05 01:42:21 +09:00
parent 6646344113
commit 41020d78d8
74 changed files with 2663 additions and 3145 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/implementation-agent.toml
+11 -5
View File
@@ -43,7 +43,9 @@ Execution contract:
- 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.
- GREEN: implement the minimum code needed for the planned task and acceptance criterion.
- VERIFY: run the targeted CTest command, then the workspace validation commands.
- 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.
- 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.
@@ -69,15 +71,19 @@ Required Implementation Report sections:
2. Implemented Scope: completed task ids, skipped task ids, and reason.
3. Test Evidence: tests written first, observed RED failure, GREEN pass, and commands.
4. Code Changes: source, header, test, and CMake/CTest change summary.
5. Validation Evidence: ctest -C Debug, python scripts/validate_workspace.py, and python -m unittest discover -s scripts -p "test_*.py" when relevant.
5. Validation Evidence: targeted CTest, config-resolved full MSVC build/test, Stop result, and `uv run --with pytest python -m pytest -v -rs` when Harness Python behavior is relevant.
6. Traceability: requirement id, task id, test id, and acceptance criterion.
7. Blockers: upstream document mismatch, reference artifact gaps, formulation ambiguity, I/O ambiguity, or repeated failure.
8. Downstream Handoff: Build/Test Executor Agent, Correction Agent, and Reference Verification Agent.
Validation commands:
- python -m unittest discover -s scripts -p "test_*.py"
- python scripts/validate_workspace.py
- ctest -C Debug -R <feature-or-label>
- cmake -S . -B .harness/build -A x64
- cmake --build .harness/build --config Debug
- ctest --test-dir .harness/build -C Debug -R <feature-or-label> --output-on-failure
- ctest --test-dir .harness/build -C Debug --show-only=json-v1
- ctest --test-dir .harness/build -C Debug --output-on-failure
- Use configured CMake presets or direct MSBuild commands instead when `.harness/config.json` selects them.
- Run `uv run --with pytest python -m pytest -v -rs` when Harness Python, Hook, or agent-config behavior changes.
Status rules:
- in-progress: implementation is underway.