# Step 10: 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/analysis-model-objects/index.json`

## Task

Run final verification and write handoff evidence.

Allowed files:

- Create `/docs/build-test-reports/analysis-model-objects-build-test.md`
- Modify `/docs/PROGRESS.md`
- Modify `/docs/WORKNOTE.md` only if new traps or failed approaches occurred
- Modify `/phases/analysis-model-objects/index.json`
- Modify `/phases/index.json`

The build/test report must include command log summary, exit codes, configure/build/CTest status, failure classification or `N/A`, and no-change assertions for reference artifacts and tolerance policy.

## 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|model-object"
git diff --check
```

Update:

- `/phases/analysis-model-objects/index.json` step 10 with `completed`, `error`, or `blocked`.
- `/phases/index.json` phase status to `completed` only if all steps are completed.
- `/docs/PROGRESS.md` with validation evidence.

## Do Not

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