# Nonlinear Static Newton-Raphson Build and Test Report

## Metadata

| key | value |
| --- | --- |
| feature_id | `nonlinear-static-newton-raphson` |
| owner_agent | `implementation-agent` |
| working directory | `C:\git\FESADev\.worktrees\nonlinear-static-newton-raphson` |
| configuration | `windows-msvc-ninja-debug`, x64 Debug |
| compiler | MSVC `cl.exe` from VS 18, toolset `14.51.36231` |
| generator | Ninja |
| dependency configuration | `FESA_GTEST_SOURCE_DIR=C:/git/googletest`; MKL `2026.1`; TBB `2023.1`; HDF5 `2.1.1` |
| final classification | none; all commands passed |

## Fresh command log

| stage | command | exit | duration | output tail |
| --- | --- | ---: | ---: | --- |
| configure | `cmake --preset windows-msvc-ninja-debug` | 0 | 1.066 s | `Configuring done`; `Generating done`; build files written to `.harness/build-ninja-msvc-debug` |
| build | `cmake --build --preset windows-msvc-ninja-debug` | 0 | 0.113 s | `ninja: no work to do.` |
| discovery | `ctest --preset windows-msvc-ninja-debug --show-only=json-v1` | 0 | 0.219 s | 302 tests discovered |
| focused control/log | `ctest --preset windows-msvc-ninja-debug -R "^(NonlinearConvergence|NewtonIterationLog)\." --output-on-failure` | 0 | 0.471 s | 14/14 passed |
| focused procedure/writer | `ctest --preset windows-msvc-ninja-debug -R "^(NonlinearStaticProcedure|NonlinearHdf5ResultsWriter)\." --output-on-failure` | 0 | 2.524 s | 7/7 passed |
| nonlinear reference | `ctest --preset windows-msvc-ninja-debug -R "^NonlinearStaticReference\." --output-on-failure` | 0 | 905.404 s | 9/9 passed |
| extended reference | `ctest --preset windows-msvc-ninja-debug -R "^(NonlinearStaticReference|ReferenceTolerance|Mitc4Reference)\." --output-on-failure` | 0 | 930.617 s | 9/9 matched tests passed |
| full CTest | `ctest --preset windows-msvc-ninja-debug --output-on-failure` | 0 | 956.498 s | 302/302 passed; integration 16, unit 256, reference 30 |

The full CTest output reported no failed-test inventory. The build emitted no compiler/linker
output beyond `ninja: no work to do.`; the build tree audit found no new `warning C####` or
`: warning:` record. The only diagnostic setup issue was that standalone HDF5 inspection tools
need Intel `libmmd.dll` on `PATH`; this did not affect the staged test executables, CMake build, or
CTest and is not a product failure.

## Results and handoff

The selected `.harness/config.json` preset was used throughout. All commands were run from the
repository root in an x64 VsDevCmd environment. The final status is
`pass-for-physics-evaluation`; no Harness Python command was required because this Step did not
change Python, hooks, or agent configuration.

This Step changed documentation and its own phase status only. It did not modify C++ production,
tests, CMake, Harness configuration, tolerance, reference artifacts, or output data. The immutable
reference artifact audit before and after comparison was identical; see `reference-comparison.md`.