WP03: Contract integration and API-only acceptance

⚡ Do This First: Load Agent Profile

Run spec-kitty agent profile show implementer-ivan and spec-kitty charter context --action implement --json. Apply the resolved initialization and boundaries.

Objective

Register new concern-module commands, update upstream contract census/envelope version compatibly, publish Python semantic delivery profile and Go mappings, no false Go conformance. Write red-first black-box journey tests before registry changes; fixture init precedes first API, thereafter all content/commit via API. Cover single_branch and coordination topology, invalid/stale/decision cases and ready work. Run existing targeted API/contracts/doc census plus directly affected services, ruff/mypy; independent reviewer checks aggregate before ready-for-squad. Publish PR to main and request Stijn/Nik without merging.

Implementation Command

spec-kitty agent action implement WP03 --mission orchestrator-two-planning-01M4AB7R --agent codex

Definition of Done

Real acceptance starts red in a separate test commit, then turns green; all owned production branches have meaningful validation. Preserve existing application authorities and user scope. New branch complexity at most15; no broad suppressions. Record targeted commands/counts, do not run whole-repo/heavy suites. Reviewer is distinct from implementer. No merge or main push.

Validation

Run owned API test files and directly implicated canonical service tests; existing API module fast tier and contract census at integration. Ruff on touched files, strict mypy as configured. Never full tests/architectural, e2e, performance or make test-full.

Activity Log

2026-10-07: Created under mission #5846; see spec and plan for complete acceptance, interface and authority laws.

Integration scope clarification: WP03 owns additive contract census/version updates, generated CLI references, changelog and index entries, and the public next query mission-guard correction. Approved dependency lane heads remain immutable.

Completion-fact correction: expose a narrow read-only native issued-step fact from the existing query, run-index and snapshot authorities; pending design inputs remain unissued. No second cursor or runtime mutation.

Spec Kitty

Kanban Board