T-E — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede #20

New issue

Open

opened 2026-09-11 09:02:12 +00:00 by bart · 0 comments

bart commented

2026-09-11 09:02:12 +00:00

Collaborator

Parent

Row T-E in docs/12-implementation-plan.md (branch, owned paths and doc section are defined there).

What to build

A planner triggers a run through the API; the worker builds a PlanningSnapshot from the database, calls the engine and validator, writes a plan_version with assignments, findings and unassigned jobs, and exposes it via the plans, runs, tasks and opportunities endpoints. Publishing supersedes per date and moves jobs open → planned → open. Until T-C/T-D merge, a stub engine/validator under tests/ returns fixture results.

Acceptance criteria

Exhaustive transition tables for solver_run and plan_version state machines, every transition through a domain service with an audit row
Publish/supersede integration test: publishing v2 for a date supersedes v1 for that date only; published assignments are never mutated
GET /tasks/{id} reports task progress; opportunities endpoint returns computed opportunities
Snapshot built from seeded data round-trips through the contracts
No stub crosses into src/; docs/04 plan-version rules updated

Blocked by

#15 — API surface: every DTO and endpoint from docs/09-api.md stubbed, openapi.json committed
#14 — Seed: sample FleetPulse feed, catalogue, three crews, week of shifts, dev persons
#6 — Worker skeleton: claim loop, task handler registry, jobs discovery, heartbeat

## Parent Row **T-E** in `docs/12-implementation-plan.md` (branch, owned paths and doc section are defined there). ## What to build A planner triggers a run through the API; the worker builds a `PlanningSnapshot` from the database, calls the engine and validator, writes a `plan_version` with assignments, findings and unassigned jobs, and exposes it via the plans, runs, tasks and opportunities endpoints. Publishing supersedes per date and moves jobs `open → planned → open`. Until T-C/T-D merge, a stub engine/validator under `tests/` returns fixture results. ## Acceptance criteria - [ ] Exhaustive transition tables for `solver_run` and `plan_version` state machines, every transition through a domain service with an audit row - [ ] Publish/supersede integration test: publishing v2 for a date supersedes v1 for that date only; published assignments are never mutated - [ ] `GET /tasks/{id}` reports task progress; opportunities endpoint returns computed opportunities - [ ] Snapshot built from seeded data round-trips through the contracts - [ ] No stub crosses into `src/`; docs/04 plan-version rules updated ## Blocked by - #15 — API surface: every DTO and endpoint from docs/09-api.md stubbed, openapi.json committed - #14 — Seed: sample FleetPulse feed, catalogue, three crews, week of shifts, dev persons - #6 — Worker skeleton: claim loop, task handler registry, jobs discovery, heartbeat

bart added the

ready-for-agent

label

2026-09-11 09:02:12 +00:00

bart added a new dependency

2026-09-11 09:02:25 +00:00

#15 PH1.7 — API surface: every DTO and endpoint from docs/09-api.md stubbed, openapi.json committed

bart added a new dependency

2026-09-11 09:02:25 +00:00

#14 PH1.6 — Seed: sample FleetPulse feed, catalogue, three crews, week of shifts, dev persons

bart added a new dependency

2026-09-11 09:02:25 +00:00