docs: remove retired workflow instructions and repair references

2026-10-17 22:37:04 +09:00
parent abfe0ee0ce
commit 4bd19f5bf0
120 changed files with 1436 additions and 3130 deletions
@@ -1,23 +1,19 @@
 # Step 13: Shell Reference Comparison

-## 담당 역할과 필수 스킬
-
- 담당 역할: `implementation-agent`
- 필수 스킬: `harness`, `fesa-cpp-msvc-tdd`
- 이 Step은 test-only reference module을 소유하며 solver production module을 소유하지 않는다.
+> 과거 개발 계획이다. 아래 작업·상태·예시는 현재 실행 지시가 아니다.
+> 현재 구현과 검증 한계는 [기능 요약](../../docs/linear-static-mitc4-shell/README.md)을 따른다.

 ## 읽어야 할 파일

- `/.agents/skills/harness/SKILL.md`, `/.codex/skills/fesa-cpp-msvc-tdd/SKILL.md`
- `/AGENTS.md`, `/docs/PRD.md`, `/docs/ARCHITECTURE.md`, `/docs/ADR.md`
- `/docs/HARNESS.md`, `/docs/HARNESS_WORKFLOW.md`, `/.codex/hooks.json`
- `/docs/linear-static-mitc4-shell/implementation-plan.md`
- `/docs/linear-static-mitc4-shell/requirements.md` Requirements 053/058-072
- `/docs/linear-static-mitc4-shell/research.md`
- `/docs/linear-static-mitc4-shell/formulation.md`
- `/docs/linear-static-mitc4-shell/numerical-review.md`
- `/docs/linear-static-mitc4-shell/io.md` Section 7
- `/docs/linear-static-mitc4-shell/reference-model.md`
+- `/AGENTS.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/linear-static-mitc4-shell/README.md`
+- `../../docs/linear-static-mitc4-shell/README.md` Requirements 053/058-072
+- `../../docs/linear-static-mitc4-shell/README.md`
+- `../../docs/linear-static-mitc4-shell/formulation.md`
+- `../../docs/linear-static-mitc4-shell/README.md`
+- `../../docs/linear-static-mitc4-shell/README.md` Section 7
+- `../../docs/linear-static-mitc4-shell/README.md`
 - phase indexes, `step13.md`, completed Steps 11/12 paths and summaries
 - `/tests/reference/reference_comparison.hpp`와 cpp/test는 B33 identity/report precedent
 - Candidate new `/tests/reference/mitc4_reference_comparison.hpp`
@@ -55,42 +51,11 @@

 먼저 exact expected hashes를 검증한다.

-```powershell
-$expectedReferenceHashes=[ordered]@{
-  "reference/shell/shell.inp"="4005851E1AB22FD3A16AC17A8D5DA3E051233F69F37419079F3553AD134ECFCF"
-  "reference/shell/shell displacements.csv"="C81D94E0B4A849F87AA0F79C83A79B94D5661AC79E44ED826919AB432C87746B"
-}
-foreach($p in $expectedReferenceHashes.Keys){
-  if((Get-FileHash -Algorithm SHA256 -LiteralPath $p).Hash -ne $expectedReferenceHashes[$p]){
-    throw "Reference artifact changed: $p"
-  }
-}
-$requiredBuildPaths=@("C:/git/googletest","C:/Program Files (x86)/Intel/oneAPI/mkl/2026.1/lib/cmake/mkl","C:/Program Files (x86)/Intel/oneAPI/tbb/2023.1/lib/cmake/tbb","C:/Program Files/HDF_Group/HDF5/2.1.1/cmake")
-foreach($p in $requiredBuildPaths){if(-not(Test-Path -LiteralPath $p)){throw "Missing $p"}}
-cmake --fresh -S . -B .harness/build -G "Visual Studio 18 2026" -A x64 `
-  "-DFESA_GTEST_SOURCE_DIR=C:/git/googletest" `
-  "-DMKL_DIR=C:/Program Files (x86)/Intel/oneAPI/mkl/2026.1/lib/cmake/mkl" `
-  "-DTBB_DIR=C:/Program Files (x86)/Intel/oneAPI/tbb/2023.1/lib/cmake/tbb" `
-  "-DHDF5_DIR=C:/Program Files/HDF_Group/HDF5/2.1.1/cmake"
-cmake --build .harness/build --config Debug --target fesa_reference_tests
-ctest --test-dir .harness/build -C Debug -R "Mitc4ReferenceComparison|Mitc4S4Reference" --output-on-failure
-```
+과거 도구 실행·출력 지시는 정리했으며, 현재 검증 방법은 기능 요약을 따른다.

 기존 mixed-tolerance 구현에 대한 fixed-boundary RED를 확인하고 test-only minimal GREEN. 이후:

-```powershell
-cmake --build .harness/build --config Debug --target fesa_reference_tests
-ctest --test-dir .harness/build -C Debug -R "Mitc4ReferenceComparison|Mitc4S4Reference" --output-on-failure
-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
-foreach($p in $expectedReferenceHashes.Keys){
-  if((Get-FileHash -Algorithm SHA256 -LiteralPath $p).Hash -ne $expectedReferenceHashes[$p]){
-    throw "Reference artifact changed: $p"
-  }
-}
-git diff --check
-```
+과거 도구 실행·출력 지시는 정리했으며, 현재 검증 방법은 기능 요약을 따른다.

 ## 검증 및 상태 갱신