# Step 12: execution-closure-and-evidence-docs ## 읽어야 할 파일 - `AGENTS.md` - `docs/PRD.md` - `docs/ARCHITECTURE.md` - `docs/ADR.md` - `docs/CODINGSTYLE.md` - `docs/TOLERANCE.md` - `docs/nonlinear-static-newton-raphson/implementation-plan.md` - `docs/nonlinear-static-newton-raphson/requirements.md` - `docs/nonlinear-static-newton-raphson/numerical-review.md` - `docs/nonlinear-static-newton-raphson/reference-model.md` - `docs/nonlinear-static-newton-raphson/io.md` - `phases/nonlinear-static-newton-raphson/index.json` - Step 0-11 modified source/test/CMake files ## 이전 Step 전제 Steps 0-11 have implemented and verified CLI lifecycle, Domain contract, nonlinear MITC4, controls, tangent solver, log, state, HDF5 schema v1, full prepared procedure, and reference comparison tests. ## 소유 파일 - Modify: `docs/PRD.md` - Modify: `docs/ARCHITECTURE.md` - Modify: `docs/ADR.md` - Create: `docs/nonlinear-static-newton-raphson/implementation-report.md` - Create: `docs/nonlinear-static-newton-raphson/build-test.md` - Create: `docs/nonlinear-static-newton-raphson/reference-comparison.md` No C++ production file is owned by this Step. ## 인터페이스 Evidence documents must record actual observed outputs: ```text implementation-report.md: RED/GREEN/VERIFY command log, Step summaries, diagnostics, implementation-owned decisions. build-test.md: fresh configure/build/discovery/full CTest commands, exit codes, duration, stdout/stderr tail, warning audit, failure classification. reference-comparison.md: exact artifact inventory, HDF5 paths, projection, row prechecks, tolerance, per-family decisions, classification, no-change assertion. ``` ## RED Before writing evidence docs, run an evidence freshness audit by checking that the three evidence docs do not already contain current command outputs from this final Step. - `NSNR-EVID-001`: missing or stale `implementation-report.md` is a failing precondition. - `NSNR-EVID-002`: missing or stale `build-test.md` is a failing precondition. - `NSNR-EVID-003`: missing or stale `reference-comparison.md` is a failing precondition. - `NSNR-EVID-004`: PRD/ARCHITECTURE/ADR still contain directly superseded global CLI/procedure/output statements. - `NSNR-EVID-005`: reference artifact pre-run SHA inventory must match Step 11 values. Expected: evidence freshness audit fails before this Step writes docs. If it unexpectedly passes with current evidence already present, stop and report to Coordinator. ## GREEN - Run fresh MSVC x64 Debug configure/build/discovery/full CTest. - Run focused nonlinear reference comparison repeat. - Run deterministic repeat/reference checks required by Step 11. - Run warning audit from build output. - Run `git diff --check` and `git status --short`. - Run reference artifact post-run SHA audit and compare to pre-run values. - Update only directly superseded PRD/ARCHITECTURE/ADR statements for CLI removal, prepared linear/nonlinear procedure boundary, output naming, log lifecycle, and nonlinear HDF5 schema. - Create the three Stage 6 evidence docs from actual command outputs only. ## VERIFY Recheck `.harness/config.json`. If absent, use: ```powershell cmake --fresh -S . -B .harness/build -G "Visual Studio 18 2026" -A x64 ` "-DFESA_GTEST_SOURCE_DIR=$gtestSource" ` "-DMKL_DIR=$mklDir" ` "-DTBB_DIR=$tbbDir" ` "-DHDF5_DIR=$hdf5Dir" 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 ctest --test-dir .harness/build -C Debug -R "NonlinearStaticReference" --output-on-failure git diff --check git status --short ``` Record command, exit code, duration, stdout/stderr tail, and failure classification for every command in the evidence docs. ## 상태 기록 Update only Step 12 status and one-line payload. Executor owns timestamps, commits, retry, top-level phase completion, and advancement. ## 금지사항 - Do not claim success before the commands above actually pass. 이유: Stage 6 evidence docs must be output-backed. - Do not broadly rewrite global docs. 이유: Step 12 only synchronizes directly superseded CLI/procedure/output statements. - Do not change reference artifact content. 이유: SHA pre/post immutability is part of the acceptance evidence. - Do not run `scripts/execute.py` from this Step. 이유: Executor already owns Harness execution.