# Step 8: validation-report-handoff

## Read First

Read these files before editing:

- `/AGENTS.md`
- `/docs/AGENT_RULES.md`
- `/docs/build-test-reports/README.md`
- `/docs/PROGRESS.md`
- `/docs/WORKNOTE.md`
- `/phases/domain-model-foundation/index.json`
- All Domain files created by previous steps

## Task

Run final verification and write the handoff evidence.

Allowed files:

- Create `/docs/build-test-reports/domain-model-foundation-build-test.md`
- Modify `/docs/PROGRESS.md`
- Modify `/docs/WORKNOTE.md` only if a failed approach, environment issue, or trap was encountered
- Modify `/phases/domain-model-foundation/index.json`
- Modify `/phases/index.json`

The build/test report must include:

- command log summary with exit codes
- command discovery path
- configure/build/CTest status
- failure classification or `N/A`
- failed test inventory or `N/A`
- no-change assertion for reference artifacts and tolerance policies

## Tests To Write First

This is a validation/reporting step. Do not write new C++ production behavior.

## Acceptance Criteria

Run:

```powershell
git status --short --branch
git remote -v
python -m unittest discover -s scripts -p "test_*.py"
python scripts/validate_workspace.py
ctest --test-dir build/msvc-debug --output-on-failure -C Debug -R domain
git diff --check
```

Update:

- `/phases/domain-model-foundation/index.json` step 8 with `completed`, `error`, or `blocked`.
- `/phases/index.json` phase status to `completed` only if all steps are completed.
- `/docs/PROGRESS.md` with the executed validation evidence.

## Do Not

- Do not claim MITC4 implementation, numerical correctness, reference comparison success, or release readiness.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not edit reference artifacts.