feat(nonlinear-static-newton-raphson): step 1 - nonlinear-static-domain-contract

docs/nonlinear-static-newton-raphson/implementation-plan.md

@@ -43,7 +43,7 @@
 - Missing decisions: none.
 - Missing required comparison files: none for declared blocking/reference families.
 - Planning can proceed: yes.
-- `.harness/config.json`: absent during planning inspection. Each Step must recheck at execution time and use it first if it appears.
+- `CMakePresets.json` tracks the approved `windows-msvc-ninja-debug` contract. The ignored `.harness/config.json` selects the matching configure/build/test presets and `.harness/build-ninja-msvc-debug` binary directory.
 
 ## Global Constraints
 
@@ -56,6 +56,7 @@
 - Implementation and Harness execution remain unauthorized by this materialized plan until the user separately requests Executor execution.
 - Preserve source label/instance identity, deterministic row order, deterministic diagnostics, finite checks, and docs/TOLERANCE.md exactly.
 - Preserve `U1/U2/U3` blocking and `UR1/UR2/UR3` warning-only. For shellNL, preserve constrained `RF1/RF2`, `RF3`, physical spatial `RM1/RM2` blocking, and exclude `RM3` plus stress from numeric comparison.
+- Launch every Harness process from VsDevCmd with `-arch=x64 -host_arch=x64` and inherit `FESA_GTEST_SOURCE_DIR`, `MKL_DIR`, `TBB_DIR`, and `HDF5_DIR`. The tracked preset selects Ninja and MSVC Debug without hard-coding machine-local dependency paths.
 
 ## Repository Seam Map
 
@@ -113,19 +114,15 @@
 
 - Add C++ sources to `src/fesa/CMakeLists.txt` under existing `fesa_solver`.
 - Add unit tests to `fesa_unit_tests`, integration tests to `fesa_integration_tests`, reference tests to `fesa_reference_tests`.
-- Preserve current executable-wide labels. Use focused regex such as `ctest --test-dir .harness/build -C Debug -R "NonlinearStaticReference|ReferenceTolerance|Mitc4Reference" --output-on-failure`.
+- Preserve current executable-wide labels. Use focused regex such as `ctest --preset windows-msvc-ninja-debug -R "NonlinearStaticReference|ReferenceTolerance|Mitc4Reference" --output-on-failure`.
 - If scoped per-test labels are introduced, the Step that introduces the mechanism must test it and avoid changing labels for unrelated discovered tests.
 - Configure/build/test commands:
 
 ```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
+cmake --preset windows-msvc-ninja-debug
+cmake --build --preset windows-msvc-ninja-debug
+ctest --preset windows-msvc-ninja-debug --show-only=json-v1
+ctest --preset windows-msvc-ninja-debug --output-on-failure
 ```
 
 ## Data Flow Contract
@@ -218,18 +215,15 @@ Step 11 must not run original reference input paths directly. It snapshots exact
 
 Each Step must:
 
-1. Recheck `.harness/config.json`. If present, use the configured Harness build/test commands.
-2. If absent, use:
+1. Use the ignored `.harness/config.json` preset contract and tracked `CMakePresets.json`.
+2. Confirm the Harness parent environment was initialized by VsDevCmd x64 and contains `FESA_GTEST_SOURCE_DIR`, `MKL_DIR`, `TBB_DIR`, and `HDF5_DIR`.
+3. Run:
 
 ```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
+cmake --preset windows-msvc-ninja-debug
+cmake --build --preset windows-msvc-ninja-debug
+ctest --preset windows-msvc-ninja-debug --show-only=json-v1
+ctest --preset windows-msvc-ninja-debug --output-on-failure
 ```
 
 Focused CTest commands are written explicitly in each `stepN.md`.