# V1 Block 10 — Testing, Documentation, and Handoff

Status: Planned

Purpose: Ensure the V1 scheduling core is understandable, tested, and ready for future UI work.

## Chunk 10.1 — Final scheduling rule coverage audit

Recommended Codex level: high

Tasks:

Audit the full V1 test suite and fill remaining coverage gaps for:

- flexible insert into free slot
- flexible insert pushing other flexible tasks
- locked blocks never moved
- inflexible tasks never moved
- critical tasks remain visible/required
- push to next available
- push to tomorrow top of queue
- push to backlog
- end-of-day rollover
- required task states
- surprise task overlaps
- child task parent completion
- timeline state mapping
- persistence-sensitive model behavior

Rules:

- This is a final coverage audit, not a place to add large new features.
- If a missing behavior is found, implement the smallest domain fix needed and test it.
- Do not duplicate tests already added in earlier block-specific regression chunks unless the duplicate provides clearer final coverage.
- Tests should name the business rule being verified.
- Avoid brittle tests that only check implementation details.

Acceptance criteria:

- Test matrix exists as either a Markdown checklist or clearly grouped test names.
- Every V1 implemented behavior has at least one meaningful test.
- Edge-case tests added in Blocks 06–09 are represented in the final coverage audit.
- `dart analyze` and `dart test` pass.

BREAKPOINT: Stop here. Confirm `medium` mode before final verification and documentation sync.

## Chunk 10.2 — Full verification pass

Recommended Codex level: medium

Tasks:

Run and record the standard verification commands:

```bash
dart pub get
dart format lib test
dart analyze
dart test
git diff --check
```

Rules:

- Do not mark this chunk complete unless all commands pass.
- If formatting changes files, include those changes in the same work block.
- If any command cannot run because of the local environment, document the exact reason and do not claim it passed.

Acceptance criteria:

- Verification results are recorded in the completed plan note or commit summary.
- No failing analyze/test/format/diff-check issues remain.

## Chunk 10.3 — Documentation sync

Recommended Codex level: medium

Tasks:

Update docs to reflect implemented behavior:

- README summary.
- Human Documentation product/design notes if affected.
- Relevant current plan statuses.
- Any architecture notes.
- Any TODOs moved to wishlist/future notes.
- Any known limitations that remain after V1.

Acceptance criteria:

- No docs claim V2 features are implemented in V1.
- MVP exclusions remain clear.
- Plan files accurately distinguish complete, active, and future work.
- Breakpoints and recommended Codex levels remain accurate after any renumbering.

BREAKPOINT: Stop here. Confirm `low` mode before archiving completed plans.

## Chunk 10.4 — Archive completed plans

Recommended Codex level: low

Tasks:

For every completed block plan:

- Mark status complete.
- Move completed plan to `Codex Documentation/Archived plans/`.
- Leave active/incomplete plans in Current Software Plan.
- Commit archive moves.

Rules:

- Completed plans must not remain in `Codex Documentation/Current Software Plan/`.
- Incomplete or partially complete plans must not be archived.
- All completed work must be committed with a conventional commit message.

Acceptance criteria:

- Completed plans are not left in Current Software Plan.
- Archive folder contains completed plans.
- Commit message follows conventional commit style.

Commit suggestion:

```text
docs(plan): archive completed v1 planning blocks
```