modify documents

docs/MULTI_AGENT_RESEARCH_PLAN.md

@@ -8,10 +8,12 @@ No solver code should be implemented from this plan directly. Each agent should
 ## Project Context
 FESA is a C++17 finite element structural analysis solver. Phase 1 targets a linear static MITC4 shell solver with linear elastic material, nodal loads, fixed boundary conditions, an Abaqus input subset, HDF5-oriented results, and reference-result comparison.
 
-The user will provide Abaqus input files and solved reference result files under a repository `reference/` folder. Abaqus is not available locally, so validation must compare against stored reference artifacts.
+The user provides Abaqus input files and solved reference result files under the repository `references/` folder. Abaqus is not available locally, so validation must compare against stored reference artifacts.
 
 ## Current Architecture Constraints
-- Follow `AGENTS.md`, `docs/ARCHITECTURE.md`, and `docs/ADR.md`.
+- Follow `AGENTS.md`, `PROGRESS.md`, `PLAN.md`, `docs/README.md`, `docs/HARNESS_ENGINEERING.md`, `docs/ARCHITECTURE.md`, and `docs/ADR.md`.
+- Use `PLAN.md` for future task ownership, priority, and open questions.
+- Use `PROGRESS.md` for completed work, verification notes, blockers, and risks.
 - Follow the technical dossier documents:
   - `docs/NUMERICAL_CONVENTIONS.md`
   - `docs/ABAQUS_INPUT_SUBSET.md`
@@ -36,6 +38,7 @@ The user will provide Abaqus input files and solved reference result files under
 - Require singular system diagnostics.
 - Defer mesh quality diagnostics in Phase 1.
 - Map Abaqus `S4` to FESA `MITC4`; defer `S4R`.
+- Use the Planner -> Generator -> Evaluator harness from `docs/HARNESS_ENGINEERING.md` for nontrivial implementation and phase execution.
 
 ## Created Codex Agents
 The first recommended batch has been created under `.codex/agents/`.
@@ -46,7 +49,7 @@ The first recommended batch has been created under `.codex/agents/`.
 
 2. `verification_benchmark_researcher`
    - File: `.codex/agents/verification-benchmark-researcher.toml`
-   - Role: research benchmark cases, reference folder contracts, comparison methods, and acceptance criteria.
+   - Role: research benchmark cases, `references/` contracts, comparison methods, and acceptance criteria.
 
 3. `mitc4_formulation_researcher`
    - File: `.codex/agents/mitc4-formulation-researcher.toml`
@@ -56,6 +59,18 @@ The first recommended batch has been created under `.codex/agents/`.
    - File: `.codex/agents/abaqus-compatibility-researcher.toml`
    - Role: research the Phase 1 Abaqus input subset and parser compatibility rules.
 
+5. `harness_sprint_planner`
+   - File: `.codex/agents/harness-sprint-planner.toml`
+   - Role: convert PLAN.md tasks and phase steps into testable sprint contracts.
+
+6. `implementation_generator`
+   - File: `.codex/agents/implementation-generator.toml`
+   - Role: implement exactly one accepted sprint contract using TDD.
+
+7. `harness_sprint_evaluator`
+   - File: `.codex/agents/harness-sprint-evaluator.toml`
+   - Role: independently pass/fail sprint output against the contract, docs, tests, and reference artifacts.
+
 ## Recommended Agent Execution Order
 1. Run `fem_literature_researcher`.
 2. Run `verification_benchmark_researcher`.
@@ -64,6 +79,8 @@ The first recommended batch has been created under `.codex/agents/`.
 
 This order keeps theory, verification targets, element formulation, and input compatibility aligned before implementation planning.
 
+Before asking `phase_planner` or `harness_sprint_planner` to create implementation steps, review `PROGRESS.md`, `PLAN.md`, `docs/README.md`, and `docs/HARNESS_ENGINEERING.md`; list any unchecked Implementation Readiness Checklist items in the planning output.
+
 ## Later Agent Candidates
 These agents should be created after the first four produce dossiers.
 
@@ -85,16 +102,21 @@ These agents should be created after the first four produce dossiers.
 6. `architecture_guardrail_reviewer`
    - Reviews dossiers, phase plans, and future implementation against project rules and ADRs.
 
+7. `reference_artifact_curator`
+   - Reviews user-provided `references/` artifacts for CSV/manifest completeness, result schema consistency, source solver metadata, tolerance clarity, and comparison path validity.
+
+8. `numerical_conventions_reviewer`
+   - Reviews implementation plans for drift from DOF, unit, sign, precision, reaction recovery, and singular diagnostic rules.
+
 ## User-Provided Inputs Needed
 The following inputs should be requested from the user as the research matures:
 
-1. Confirmation or revision of the proposed `reference/` folder layout in `docs/VERIFICATION_PLAN.md`.
-2. At least one simple Abaqus `.inp` file and its solved reference result artifact.
-3. Preferred reference result format if available: `.dat`, `.rpt`, exported `.csv`, JSON, HDF5, or another structured format.
-4. Preferred numerical tolerances for reference comparison, or permission for agents to propose initial tolerances per benchmark.
-5. The Abaqus version used to generate reference artifacts.
-6. Whether the first implementation plan should target CMake, another build system, or a project-specific build layout.
-7. The final default scale for artificial drilling stiffness, after formulation research.
+1. Additional small Abaqus `.inp` files and solved result artifacts under `references/`.
+2. Reaction-force reference exports when available, preferably using a documented `*_reactions.csv` convention.
+3. Preferred numerical tolerances for reference comparison, or permission for agents to propose initial tolerances per benchmark.
+4. The Abaqus version used to generate each reference artifact when it is not evident from the `.inp` file header.
+5. Whether the first implementation plan should target CMake, another build system, or a project-specific build layout.
+6. The final default scale for artificial drilling stiffness, after formulation research.
 
 ## Seed Sources
 - Abaqus input syntax rules: https://abaqus-docs.mit.edu/2017/English/SIMACAEMODRefMap/simamod-c-inputsyntax.htm