TASK-001G: Tests and Verification

• Status: Ready
• Parent: TASK-001
• Spec: SLICE-001
• Depends on: TASK-001D, TASK-001E, TASK-001F

Goal

Harden the first slice with the minimum automated verification promised by the requirements and the spec.

Scope

• tests for start preconditions and guard logic
• tests for stop versus abort terminal behavior
• tests for critical fault transition and recovery guard behavior
• tests for bounded or coalesced streaming policy
• small manual verification checklist updates if needed

Non-Scope

• broad snapshot testing
• exhaustive UI automation
• performance benchmarking beyond what is needed to verify bounded behavior

AI Execution Profile

• Model class: Balanced
• Reasoning effort: Medium
• Use the default strong coding model
• Escalate only if the test seams are hard to isolate

Files Or Areas Expected To Change

• Tests project
• small production seams needed for deterministic verification

Acceptance Targets

• automated tests cover the minimum required first-slice behavior
• tests verify behavior without needing the full UI to launch
• the repo has a clear verification baseline for future changes

Copy/Paste Prompt

Implement only TASK-001G: Tests and Verification in this repository.

Read first:
- docs/requirements.md
  Focus on Sections 9.10, 12, 13.2, and 13.3
- docs/specs/SLICE-001-first-strong-vertical-slice.md
  Focus on Acceptance Criteria and Verification Notes
- docs/tasks/slice-001/TASK-001G-tests-and-verification.md

Goal:
- Add the minimum automated verification required for the first slice.

Scope:
- Add tests for start precondition guards.
- Add tests for stop versus abort terminal behavior.
- Add tests for critical fault transition to Faulted and recovery guard behavior.
- Add tests for bounded or coalesced streaming behavior at the application boundary.
- Add only the smallest production seams needed to make the behavior testable.

Do not:
- Add heavy UI automation unless absolutely necessary
- Expand test scope far beyond the first slice
- Re-architect production code just to satisfy test style preferences

Verification:
- Run the tests if possible
- Report what behavior is covered and what still requires manual verification

Important:
- Implement only this task
- Do not preemptively implement later tasks