# Step 5: integration-validation-report

## Read First

Read these files before editing:

- `/AGENTS.md`
- `/docs/PRD.md`
- `/docs/ARCHITECTURE.md`
- `/docs/ADR.md`
- `/docs/io-definitions/abaqus-input-parser-io.md`
- `/src/fesa/io/abaqus/input_parser.hpp`
- `/tests/unit/abaqus_input_parser_mesh_test.cpp`
- existing parser/model tests added by prior steps

Review all completed step summaries in `/phases/abaqus-input-parser/index.json`.

## Task

Add an integration-level parser test and a build/test report.

Required behavior:

- Add a small integration test that parses a V0 Abaqus `.inp` string containing
  the supported parser subset and validates the resulting `Domain` and
  `AnalysisStep` data.
- Keep the test in memory; do not create or modify Abaqus reference CSV
  artifacts.
- Write `/docs/build-test-reports/abaqus-input-parser.md` with command evidence,
  exit codes, and known limitations.

## Tests To Write First

Add `/tests/integration/abaqus_input_parser_integration_test.cpp` before any
final integration adjustments. Confirm it fails for the missing integrated
behavior, then make it pass with the minimum implementation-owned changes.

## Acceptance Criteria

```powershell
ctest --test-dir build/msvc-debug --output-on-failure -C Debug -R abaqus_input_parser
python -m unittest discover -s scripts -p "test_*.py"
python scripts/validate_workspace.py
```

## Verification Procedure

1. Run the acceptance criteria commands.
2. Confirm no reference artifacts were generated or modified.
3. Update step 5 status with summary or a concrete error/blocked reason.

## Forbidden

- Do not claim reference comparison, physics sanity, or release readiness.
- Do not generate, restore, or modify Abaqus reference CSV files.