modify documents

docs/AGENT_RULES.md

@@ -88,7 +88,7 @@ Repeated failures must be routed back to the owning upstream stage instead of co
 - Each Agent writes the artifact for its stage and records downstream handoff items.
 - Every must requirement needs a verification method and acceptance criteria.
 - Every formulation needs clear DOF, coordinate, unit, sign, Jacobian, integration, and recovery rules.
-- Every I/O contract needs supported syntax, unsupported behavior, internal mapping, schema, units, component names, and matching rules.
+- Every I/O contract needs supported syntax, unsupported behavior, internal mapping, HDF5 result schema or explicitly approved CSV export schema, units, component names, and matching rules.
 - Every reference model contract needs model purpose, compared quantities, artifacts, provenance, and limitations.
 - Every implementation plan needs test-first tasks, target commands, candidate files, and traceability to upstream requirements.
 - Every verification report needs compared rows, missing/extra rows, max absolute error, max relative error, worst id/component, pass/fail, and failure classification.
@@ -96,6 +96,7 @@ Repeated failures must be routed back to the owning upstream stage instead of co
 ## Current Project Defaults
 - Initial feature id: `mitc4-linear-static-shell`.
 - Initial result/reference format: HDF5.
+- Local HDF5 default install: `C:\Program Files\HDF_Group\HDF5\2.1.1`; use `HDF5_ROOT` for this root or `HDF5_DIR` for `C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`.
 - Reference policy: stored Abaqus S4R is primary for pass/fail; Abaqus S4 is diagnostic.
 - Required compared quantities: nodal displacement, reaction, element internal force/resultant, and stress.
 - Agents must preserve OpenSees-inspired architecture while using modern C++17 RAII and FESA ownership boundaries.