# Step 11: Shell HDF5 Output

## 담당 역할과 필수 스킬

- 담당 역할: `implementation-agent`
- 필수 스킬: `harness`, `fesa-cpp-msvc-tdd`

## 읽어야 할 파일

- `/.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/implementation-plans/linear-static-mitc4-shell-implementation-plan.md`
- `/docs/requirements/linear-static-mitc4-shell.md` Requirements 039-048
- `/docs/research/linear-static-mitc4-shell-research.md`
- `/docs/formulations/mitc4-shell-formulation.md`
- `/docs/numerical-reviews/linear-static-mitc4-shell-review.md`
- `/docs/io-definitions/linear-static-mitc4-shell-io.md` Section 6 exact schema
- `/docs/reference-models/linear-static-mitc4-shell-reference-models.md`
- phase indexes, `step11.md`, completed Steps 9/10 paths and summaries
- `/include/fesa/results/results_writer.hpp`
- `/include/fesa/io/hdf5/hdf5_results_writer.hpp`
- `/src/fesa/io/hdf5/hdf5_results_writer.cpp`
- `/tests/unit/io/hdf5/hdf5_results_writer_test.cpp`

## 작업

1. `MITC4-H5-001..004`를 먼저 작성한다.
2. Generic `ResultsWriter::write(path,Domain,AnalysisState,diagnostics)` 경계를 유지한다.
3. I/O contract exact metadata, four-node element identity, director/frame,
   materials/sections, masks/prescribed values, fixed locations와 all mandatory shell
   result/global datasets를 schema v0에 additive하게 기록한다.
4. Exact shapes/dtypes/component attributes/unit dimensions/coordinate/location/step/frame
   identity와 finite/order를 self-check한다.
5. Output request와 무관하게 mandatory inventory를 기록하고 drilling paths/S33/S13/S23를
   만들지 않는다.
6. Existing same-directory temp, flush/close, read-only reopen/self-check, atomic replace를 재사용한다.

## Acceptance Criteria

```powershell
$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_unit_tests
ctest --test-dir .harness/build -C Debug -R "Hdf5ResultsWriter" --output-on-failure
```

Missing shell schema/atomic validation RED 후 minimal GREEN. 이후:

```powershell
cmake --build .harness/build --config Debug --target fesa_unit_tests
ctest --test-dir .harness/build -C Debug -R "Hdf5ResultsWriter|ResultRecovery|AnalysisState" --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
```

## 검증 및 상태 갱신

RED/schema/focused/full evidence를 기록하고 current Step 상태 payload만 갱신한다.

## 금지사항

- B33 dataset 의미를 migrate/reinterpret하지 마라.
- CSV를 solver output으로 만들거나 partial final HDF5를 남기지 마라.
- Drilling/calibration output을 추가하지 마라.
- 직접 commit/hook 실행 또는 reference/upstream 변경을 하지 마라.
