modify documents

.codex/skills/abaqus-fortran-tdd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: abaqus-fortran-tdd
-description: Use when planning, implementing, validating, or correcting Abaqus User Subroutine Fortran work with Intel oneAPI, no-Abaqus tests, Abaqus opt-in validation, and RED/GREEN/VERIFY evidence.
+description: Use when planning, implementing, validating, or correcting Abaqus User Subroutine Fortran work with Intel oneAPI, no-Abaqus tests, externally generated result artifacts, and RED/GREEN/VERIFY evidence.
 ---
 
 # Abaqus Fortran TDD
@@ -26,7 +26,7 @@ Read first:
 4. GREEN: implement the minimum Fortran kernel, Abaqus wrapper, or manifest change needed for the task.
 5. VERIFY: run the targeted command, then `python scripts/validate_fortran.py`, `python scripts/validate_reference_artifacts.py`, and `python scripts/validate_workspace.py`.
 6. Use Intel oneAPI Fortran discovery. Prefer `ifx`; use `ifort` when `ifx` is unavailable.
-7. For failure triage, classify as `fortran-compile | link | no-abaqus-test | abaqus-validation | reference-artifact | harness | environment | upstream-contract`.
+7. For failure triage, classify as `fortran-compile | link | no-abaqus-test | external-result-validation | reference-artifact | harness | environment | upstream-contract`.
 
 ## Output Contract
 
@@ -35,7 +35,7 @@ Produce one of these, depending on role: `docs/implementation-plans/<feature-id>
 ## Boundaries
 
 - Do not change requirements, formulations, interface contracts, test model contracts, reference artifacts, or tolerance policies unless explicitly asked.
-- Do not run Abaqus unless `HARNESS_ABAQUS_VALIDATION=run` and explicit commands are provided.
+- Do not run Abaqus analyses. Use externally generated ODB-extracted CSV artifacts for solver-result evidence.
 - Do not generate reference CSVs.
 - Do not approve release readiness.
 - Do not expand scope beyond the approved implementation plan.