modify documents

.codex/skills/fesa-reference-models/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fesa-reference-models
-description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, and implementation-planning handoffs.
+description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required HDF5 reference artifacts, optional CSV export artifacts, coverage matrices, and implementation-planning handoffs.
 ---
 
 # FESA Reference Models
@@ -26,8 +26,8 @@ Read these first:
 2. Build a model inventory: smoke, analytical, patch test, benchmark, regression, and negative/invalid-input models.
 3. For each model, record `model_id`, purpose, verified requirements, analysis type, element type, material, boundary conditions, loads, expected quantities, tolerance, source, and status.
 4. Define `references/<feature-id>/<model-id>/` artifact bundle requirements.
-5. Require `model.inp`, `metadata.json`, `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and `README.md` unless explicitly not applicable.
-6. Define optional `strains.csv` and `energy_or_residual.csv` only when upstream acceptance criteria require them.
+5. Require `model.inp`, `metadata.json`, `results.h5`, and `README.md` unless explicitly not applicable; for the current MITC4 feature, record primary `abaqus_s4r/results.h5` and diagnostic `abaqus_s4/results.h5` when both are required.
+6. Define optional CSV exports such as `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, `strains.csv`, or `energy_or_residual.csv` only when upstream acceptance criteria require them.
 7. Define metadata provenance, units, coordinate system, output requests, artifact status, and limitations.
 8. Build a Coverage Matrix mapping requirement id, model id, compared quantity, artifact file, tolerance, verification method, and status.
 
@@ -42,7 +42,8 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
 - Abaqus Input Requirements
 - Artifact Bundle Contract
 - Metadata JSON Contract
-- Reference CSV Requirements
+- Reference HDF5 Requirements
+- Optional CSV Export Requirements
 - Coverage Matrix
 - Artifact Acceptance Checklist
 - Open Issues and Downstream Handoff
@@ -53,7 +54,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
 - Do not implement parsers.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not compare solver results.
 - Do not approve release readiness.
 
@@ -61,9 +62,9 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
 
 - Every `must` requirement maps to at least one model and compared quantity.
 - `model.inp` stays within the supported Abaqus keyword subset or records an open issue.
-- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and CSV schema version.
-- Missing required CSVs keep the model at `needs-reference-artifacts`.
+- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and HDF5 schema version.
+- Missing required HDF5 artifacts keep the model at `needs-reference-artifacts`.
 
 ## Handoff
 
-Send model order and tests that should fail first to Implementation Planning Agent. Send schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
+Send model order and tests that should fail first to Implementation Planning Agent. Send HDF5 schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.