docs: align FESA agents with minimal reference cases

.codex/skills/fesa-physics-sanity/SKILL.md

@@ -17,7 +17,7 @@ Read these first:
 - Reference Verification report with `pass-for-physics-evaluation`
 - `docs/reference-models/<feature-id>-reference-models.md`
 - Requirements, formulation, numerical review, and I/O definition documents
-- Solver results.h5, Abaqus reference CSV files under reference/<model-id>/, and optional FESA debug CSV views as read-only evidence
+- Solver results.h5, feature-declared Abaqus reference CSV files, and optional FESA debug CSV views as read-only evidence
 
 ## Workflow
 
@@ -29,7 +29,8 @@ Read these first:
 6. Check symmetry or expected zero conditions when the model defines them.
 7. Check element force balance and element internal force sign conventions when documented.
 8. Check stress/strain component naming, coordinate system, output location, and sign.
-9. Check rigid body mode symptoms, nonfinite values, energy/residual evidence, and model coverage.
+9. Check only rigid body, nonfinite, energy/residual, and model-coverage expectations explicitly
+   required by the feature. Do not invent expanded portfolios or calibration gates.
 10. Classify failures and route them to the owning agent.
 
 ## Output Contract
@@ -60,7 +61,7 @@ Produce or revise `docs/physics-evaluations/<feature-id>-physics-evaluation.md`
 
 - A physics pass requires documented expectations and reference verification pass evidence.
 - Use `needs-upstream-decision` when physical expectations, sign convention, or model purpose is missing.
-- Use `needs-reference-model` when the model does not cover the claimed feature.
+- Use `needs-reference-model` only when a feature-required case or declared physical expectation is missing.
 - `pass-for-release-agent` means Release Agent can audit release readiness; it is not release approval.
 
 ## Handoff