# 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 — Scheduling rule test matrix

Recommended Codex level: high

Tasks:

Create a test matrix covering:

- 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
- surprise task overlaps
- child task parent completion

Acceptance criteria:

- Tests clearly name the business rule being verified.
- Avoid brittle tests that only check implementation details.

## Chunk 10.2 — Documentation sync

Recommended Codex level: medium

Tasks:

Update docs to reflect implemented behavior:

- README summary.
- Relevant current plan statuses.
- Any architecture notes.
- Any TODOs moved to wishlist/future notes.

Acceptance criteria:

- No docs claim V2 features are implemented in V1.
- MVP exclusions remain clear.

BREAKPOINT: Stop here. Confirm mode switch if needed before final cleanup.

## Chunk 10.3 — 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.

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
```