Sprint delivery orchestration — landed evidence

This record is evidence for one independently authorised slice of the source plan. It does not claim that the execution ledger, MCP sprint validation surface, or full resumability work has landed.

Sprint plans and evidence form a DAG whose ready nodes run in isolated worktrees before orchestrator integration and cleanup.

Delivered

/reckon-ship S1, project-qualified sprint handles, and explicit plan/sprint disambiguation.
Transitive plan and section dependency expansion, topological execution waves, and research-before/evidence-after gates.
A provider-neutral one-below capability policy with orchestrator-level retention for physics, safety, coupled changes, conflicts, and synthesis.
Detached worktree-first delegation, orchestrator-owned integration, and conservative cleanup that refuses dirty or unmerged worktrees.
A clear handoff: reckon-sprint manages sprint state; reckon-ship executes it.

Verification

Gate	Result	Evidence
Implementation	pass	Commit `36d5bdd`; 777 insertions and 174 deletions across seven files.
Skill contracts	pass	Both skill packages passed `quick_validate.py`.
Focused tests	pass	6 tests passed, including real temporary repositories for dirty and unreachable cleanup refusal.
Full suite	pass	1,181 tests passed in 26.97 seconds.
Git delivery	pass	Commit pushed to `origin/main`.

Errors and resolutions

Error	Resolution	Improvement signal
The standalone skill validator lacked PyYAML.	Ran it through `uv run --with pyyaml`.	Bundle validator dependencies or provide a project-native validation command.
Angle brackets in skill frontmatter were rejected.	Rephrased frontmatter while retaining syntax examples in the skill body.	Validator diagnostics should point to the exact offending field and character.
Two initial contract assertions were brittle to prose wrapping.	Normalised whitespace and asserted semantic phrases.	Prefer parsed skill-contract tests over raw formatting-sensitive matches.

Remaining source-plan work

The portable execution ledger, bounded MCP proposal/validate/close operations, mounted-checkout digests, resumable event persistence, broader interruption/failure coverage, and provenance prerequisites remain open. The source plan therefore remains active and partial.