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/correction-agent.toml
+5 -4
View File
@@ -48,8 +48,9 @@ Execution contract:
- MINIMAL FIX: modify only implementation-owned source, header, test, or CMake files needed to fix the classified failure.
- MINIMAL FIX: keep changes surgical and traceable to the failure report or implementation plan acceptance criterion.
- VERIFY: rerun the targeted command that reproduced the failure first.
- VERIFY: run python scripts/validate_workspace.py after the targeted command.
- VERIFY: run python -m unittest discover -s scripts -p "test_*.py" when harness, hook, or agent config behavior is involved.
- VERIFY: run the full MSVC build/test commands resolved from `.harness/config.json` or Harness auto detection after the targeted command.
- VERIFY: run `uv run --with pytest python -m pytest -v -rs` when Harness Python, Hook, or agent config behavior is involved.
- VERIFY: allow Stop to rerun whole-project MSVC build/test before the correction Step ends.
- If the same classification repeats after two focused correction attempts, stop and hand off to Coordinator Agent or the relevant upstream agent.
- If a fix requires changing requirements, formulations, I/O contracts, reference artifacts, tolerance policies, or reference provenance, stop with needs-upstream-decision.
- If the failure is environment-owned, do not work around it with code changes; classify it as needs-environment-fix.
@@ -61,7 +62,7 @@ Failure classification:
- link: linker, symbol resolution, library registration, or target dependency failed.
- test: CTest, unit, integration, parser/I/O, or ordinary regression test failed.
- reference-comparison: deterministic reference comparison test failed against stored artifacts.
- harness: Python harness self-test, TDD guard, hook, or validation script failed.
- harness: Python Harness test, PreToolUse/Stop Hook, config loading, discovery, or adapter validation failed.
- environment: MSVC, CMake, Python, path, permission, generator, or local dependency issue.
- upstream-contract: requirements, formulation, I/O, reference artifact, tolerance, or implementation plan is incomplete or inconsistent.
@@ -70,7 +71,7 @@ Required Correction Report sections:
2. Failure Triage: classification, first failed command, failed target or test, and evidence tail.
3. Root Cause Summary: implementation defect, test defect, CMake registration issue, environment issue, or upstream-contract issue.
4. Correction Scope: changed source, header, test, and CMake files plus excluded upstream contract files.
5. Verification Evidence: targeted command, python scripts/validate_workspace.py, and Python harness self-test when relevant.
5. Verification Evidence: targeted command, config-resolved full MSVC build/test, Stop result, and Harness Python pytest when relevant.
6. Traceability: requirement id, task id, test id, failing command, corrected file, and acceptance criterion.
7. Handoff Recommendation: Implementation Agent, Build/Test Executor Agent, Reference Verification Agent, Physics Evaluation Agent, upstream agent, or Coordinator Agent.
8. Stop Condition: repeated failure, upstream ambiguity, reference artifact gap, or environment blocker.