modify documents

.codex/skills/harness-review/SKILL.md

@@ -7,7 +7,7 @@ description: "Use when reviewing this Abaqus User Subroutine Harness repository:
 
 ## Overview
 
-Use this skill to review Harness work against repository rules, Abaqus User Subroutine workflow, Fortran TDD, no-Abaqus validation, reference artifact contracts, and explicit Abaqus opt-in validation requirements. Prioritize bugs, regressions, missing tests, and rule violations.
+Use this skill to review Harness work against repository rules, Abaqus User Subroutine workflow, Fortran TDD, no-Abaqus validation, reference artifact contracts, and externally generated extracted CSV validation requirements. Prioritize bugs, regressions, missing tests, and rule violations.
 
 ## Review Process
 
@@ -30,7 +30,7 @@ Use this skill to review Harness work against repository rules, Abaqus User Subr
 | Tests | Are new or changed Fortran behaviors covered by no-Abaqus Fortran/Python tests or harness tests? |
 | TDD Guard | Would Fortran production edits be blocked without related tests? |
 | References | Do reference artifacts include `.inp`, source hash, Abaqus version, compiler version, msg/dat/log tail, and extracted CSV contracts when required? |
-| Abaqus Opt-in | Is `HARNESS_ABAQUS_VALIDATION=run` used only when explicitly configured? |
+| External Results | Are solver-result checks based on externally generated ODB-extracted CSV artifacts rather than local solver runs? |
 | Build | Do the Python, Fortran, reference artifact, and workspace validation commands pass or report expected skips? |
 
 ## Output Format
@@ -44,7 +44,7 @@ If there are findings, list them first in severity order with file and line refe
 | Tests | PASS/FAIL | {detail} |
 | TDD Guard | PASS/FAIL | {detail} |
 | Reference Artifacts | PASS/FAIL | {detail} |
-| Abaqus Opt-in | PASS/FAIL | {detail} |
+| External Results | PASS/FAIL | {detail} |
 | Validation | PASS/FAIL | {detail} |
 
 When there are no findings, say that clearly, then mention commands not run or remaining risk.