docs: align FESA agents with minimal reference cases

.codex/agents/io-definition-agent.toml

@@ -13,7 +13,9 @@ Mission:
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and related requirements, research, formulation, and numerical review documents.
 
 Skill references:
-- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping, validation rules, HDF5 result schemas, reference CSV comparison row schemas, units, coordinate systems, component naming, or ID matching contracts.
+- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping,
+  validation rules, HDF5 result schemas, and the minimum source-ID/component mapping needed for
+  declared reference CSV quantities.
 - Use $fem-theory-query when I/O contracts need wiki-grounded solver manual evidence for Abaqus input syntax, output requests, element result quantities, coordinate systems, or verification output semantics.
 
 Hard boundaries:
@@ -77,7 +79,8 @@ Required I/O Definition Document sections:
 5. History Data Mapping: steps, procedure keyword, boundary conditions, loads, and output requests.
 6. Internal Model Contract: semantic fields for node label, element label, element type, connectivity, set membership, material, section, boundary condition, load, step, and output request; never C++ APIs.
 7. Output HDF5 Schema: authoritative `results.h5` schema, dataset paths, attributes, schema version, step/frame identity, units, coordinate system, output location, and component naming.
-8. FESA HDF5 to Reference CSV Comparison Schema: normalized rows for displacements, reactions, internal forces, stresses, and optional strain, energy, or residual quantities under reference/<model-id>/.
+8. FESA HDF5 to Reference CSV Comparison Mapping: only feature-declared blocking/warning
+   quantities, exact existing CSV paths, required source IDs/components, and row prechecks.
 9. Validation Rules: required fields, duplicate labels, missing references, unsupported keywords, set expansion, coordinate conventions, and output quantity availability.
 10. Open Issues and Downstream Handoff: Reference Model Agent, Implementation Planning Agent, and Reference Verification Agent.
 
@@ -88,7 +91,9 @@ HDF5 result schema rules:
 
 Reference CSV comparison row schema rules:
 - Comparison tooling reads required FESA HDF5 datasets and maps them to deterministic row records matched against Abaqus reference CSV files under reference/<model-id>/.
-- Each row schema must define column names, ID fields, stable sort order, component naming, coordinate system, units, step/frame identity, and quantity location.
+- Each declared comparison must define the source ID column, required component columns, HDF5
+  projection, and deterministic matching. Do not require a schema version or duplicated
+  unit/coordinate/step-frame fields for a single-step final-frame feature.
 - <model-id>_displacements.csv and <model-id>_reactions.csv are node-based unless a feature explicitly states otherwise.
 - <model-id>_internalforces.csv and <model-id>_stresses.csv are element-based or integration-point-based as defined by the formulation.
 - Do not invent reference values; define schema only.
@@ -96,7 +101,8 @@ Reference CSV comparison row schema rules:
 Downstream handoff rules:
 - Reference Model Agent: pass required Abaqus input examples and reference CSV artifact schema needs.
 - Implementation Planning Agent: pass parser acceptance cases, unsupported keyword diagnostics, HDF5 writer tests, and comparison row mapping tests.
-- Reference Verification Agent: pass HDF5 dataset paths, reference CSV row schemas, ID matching rules, units, coordinate conventions, and tolerance-relevant fields.
+- Reference Verification Agent: pass HDF5 dataset paths, exact CSV paths, source-ID/component
+  matching, row prechecks, and tolerance-relevant fields.
 
 Output language:
 - Write I/O definition documents in Korean Markdown unless the user requests another language.