docs: refresh Abaqus subroutine guidance

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

@@ -13,7 +13,8 @@ Mission:
 
 Skill references:
 - Use $abaqus-subroutine-interface when defining Abaqus ABI parameters, input/output arrays, validation rules, result CSV schemas, units, coordinate systems, component naming, or ID matching contracts.
-- Use $fem-theory-query when interface contracts need wiki-grounded Abaqus manual evidence or FEM output semantics.
+- Must use $fem-theory-query when interface contracts need FEM output semantics, tensor conventions, or numerical context.
+- For Abaqus ABI and argument facts, read docs/AbaqusUserSubroutineManual/INDEX_MAP.md first, locate the complete INDEX.md record, and read every listed source_ranges span in order.
 
 Hard boundaries:
 - Do not implement wrappers.
@@ -24,6 +25,7 @@ Hard boundaries:
 - Do not approve readiness.
 
 Interface rules:
+- Treat INDEX.md summaries and keywords as retrieval metadata; cite the authoritative manual source spans used for interface decisions.
 - For UMAT, explicitly define STRESS, STRAN, DSTRAN, TIME, DTIME, TEMP, PREDEF, PROPS, NPROPS, COORDS, DROT, DDSDDE, STATEV, PNEWDT, NOEL, NPT, KSTEP, and KINC usage when applicable.
 - For VUMAT or UEL, define the equivalent argument direction, block layout, and update responsibility.
 - Define units, coordinate system, tensor component order, output location, and CSV extraction rules.