docs: remove retired workflow instructions and repair references

phases/shell-surface-pressure-load/step2.md

@@ -1,5 +1,8 @@
 # Step 2: reject-invalid-pressure-input
 
+> 과거 개발 계획이다. 아래 작업·상태·예시는 현재 실행 지시가 아니다.
+> 현재 구현과 검증 한계는 [기능 요약](../../docs/shell-surface-pressure-load/README.md)을 따른다.
+
 ## 실행 범위와 상태 소유권
 
 이 Step의 단일 책임은 Step 1의 pressure input/model mapping에 deterministic fail-closed negative semantics, duplicate rules, diagnostics and atomic commit behavior를 완결하는 것이다. 동일 Step 안에서 RED부터 full green까지 끝낸다.
@@ -9,17 +12,17 @@ Implementation Agent는 Executor-selected Step 2만 수행하고 task index의 S
 ## 읽어야 할 파일
 
 - `AGENTS.md`
-- `docs/ARCHITECTURE.md`
-- `docs/ADR.md`
-- `docs/CODINGSTYLE.md`
-- `docs/HARNESS.md`
-- `docs/HARNESS_WORKFLOW.md`
+- `../../docs/solver-core/README.md`
+- `../../docs/solver-core/README.md`
+- `../../docs/solver-core/README.md`
+- `../../docs/solver-core/README.md`
+- `../../docs/solver-core/README.md`
 - `.codex/hooks.json`
-- `docs/shell-surface-pressure-load/requirements.md`
-- `docs/shell-surface-pressure-load/formulation.md`
-- `docs/shell-surface-pressure-load/numerical-review.md`
-- `docs/shell-surface-pressure-load/io.md`
-- `docs/shell-surface-pressure-load/implementation-plan.md`
+- `../../docs/shell-surface-pressure-load/README.md`
+- `../../docs/shell-surface-pressure-load/formulation.md`
+- `../../docs/shell-surface-pressure-load/README.md`
+- `../../docs/shell-surface-pressure-load/README.md`
+- `../../docs/shell-surface-pressure-load/README.md`
 - `include/fesa/core/ascii.h`
 - `include/fesa/core/diagnostic.h`
 - `include/fesa/model/source_target_resolver.h`
@@ -71,10 +74,7 @@ Add these named tests first:
 
 Run before production edits:
 
-```powershell
-cmake --build .harness/build --config Debug --target fesa_unit_tests
-ctest --test-dir .harness/build -C Debug --output-on-failure -R "^(ShellSurfacePressureInput|ShellSurfacePressureDomain)\."
-```
+과거 도구 실행·출력 지시는 정리했으며, 현재 검증 방법은 기능 요약을 따른다.
 
 Expected RED: the Step 1 happy-path mapper accepts at least one unsupported form, lacks complete stable diagnostics, or does not distinguish exact same-side normalization from conflicting-side failure. Record command, exit, duration and tail. Unexpected pass is an evidence gap; unrelated failure is regression and must be resolved/classified before GREEN.
 
@@ -89,16 +89,9 @@ Expected RED: the Step 1 happy-path mapper accepts at least one unsupported form
 
 ## VERIFY and Acceptance Criteria
 
-If `.harness/config.json` exists, use its resolved commands first. Otherwise run:
+If 과거 검증 자료(정리됨) exists, use its resolved commands first. Otherwise run:
 
-```powershell
-cmake --build .harness/build --config Debug --target fesa_unit_tests
-ctest --test-dir .harness/build -C Debug --output-on-failure -R "^(ShellSurfacePressureInput|ShellSurfacePressureDomain)\."
-ctest --test-dir .harness/build -C Debug --output-on-failure -R "^(InpDomainMapping|DomainMappingComponents|InpSyntax)\."
-cmake --build .harness/build --config Debug
-ctest --test-dir .harness/build -C Debug --show-only=json-v1
-ctest --test-dir .harness/build -C Debug --output-on-failure
-```
+과거 도구 실행·출력 지시는 정리했으며, 현재 검증 방법은 기능 요약을 따른다.
 
 Acceptance requires every named negative test and legacy parser/domain test green, exact diagnostic tuple `(severity,code,file,line,keyword,entity_identity,message)`, repeated-run diagnostic order exact, no partial Domain, nonzero CTest discovery, no new warning and full CTest pass. Let Stop hook run automatically.
 
@@ -117,5 +110,3 @@ Trace: `FESA-REQ-SHELL-PRESSURE-002`–`004`, `013`–`017`; `io.md` §§2–6,
 - Do not implement the evaluator/assembler, change tolerance, rewrite artifacts or refactor the general parser. 이유: 이 Step의 negative semantic scope 밖이다.
 - Do not weaken the valid multi-explicit-instance contract from Step 1.
 - Do not modify upstream docs, HDF5 writers, source reference files or phase statuses other than Step 2's Executor-selected record.
-- Do not run Abaqus, create output JSON, invoke `scripts/execute.py`, advance Step 3, commit or push.
-