[thalida]

Serves the six endpoints the approved client designs need, and deletes the three they replaced.
15 operations become 18.

Spec: docs/specs/2026-09-03-statusboard-client-design.md
Plan: docs/plans/2026-09-03-statusboard-api.md, left as written — a plan records what was
intended, including where it turned out to be wrong.

What changes

Every trackable thing is a ServiceComponent. One component collection replaces the service
list and both nested service routes, so Discover, a service's parts, a component's descendants
and an event's affected list are one query with different parameters.

A severity change nobody explains becomes an event. A provider can move a component to
Degraded and never write an incident. Reconcile now opens a ServiceEvent of its own, and a
provider's later post claims it rather than making a second card. detected_by records who
found the outage first, because a claim fills in the provider's id and would otherwise destroy
that fact.

Ancestry is a closure table. ComponentAncestor holds one row per pair of components, one
above the other, with real foreign keys. An array of ids held no reference: deleting a component
left its id in every descendant, and only a poll of that service cleared it, which for an
untracked service never comes. The table cascades instead, and the model, the admin's bulk
delete and the cascade each close a path that left ancestry stale.

Archived components are not served anywhere — every list, every count, every badge, and the
detail. A guard test enumerates the readers, because three of them had already forgotten.

Also: catalog.ServiceRequest gives the Add-by-URL dead end somewhere to send a URL, featuring
moved onto components and is managed only in the component admin, and the phase filter's two
states are a choices class published through /meta/ rather than a bare list of tuples.

Fixes outside the plan

• GET /meta/?fields= was a complete no-op. The view hand-built its response and never
  instantiated its serializer. Dotted paths now reach into enums.
• ?fields= naming an unknown field returned 200 {} while the contract promised 400.
• The contract disagreed with the code about response codes on eight operations, including a
  409 nothing returned and a 502 that was hidden. A test now compares the two.
• bin/check_prose.py counted a multi-word code span as two words, and reported success when
  run from a directory where it scanned nothing.

Verification

just check green in the image CI uses: 630 tests, coverage 96.77% against an 85% floor, ruff,
the docs cross-check, the prose check, the bin/ tests, and makemigrations --check.

api/tests/test_contract.py holds the code and docs/api/openapi.yaml together in both
directions, now including response codes, and a probe map asserted to equal the contract's
documented GET paths means a new endpoint cannot ship without proving ?fields= prunes it.

Known open, deliberately

• EVENT_CLAIM_WINDOW_SECONDS needs adding to the deployment repository's .env.example,
  default 3600. That repository is not in this checkout.
• A component that somebody tracks and that is later archived disappears from their board with
  no notice, and an event card's link to a since-archived component 404s. Both follow from
  excluding archived everywhere.
• GET /events/?dashboard= still reaches through archived components, deliberately: archiving
  writes the closing "no longer published" update, so hiding the event would hide an outage's
  ending.
• The response-code check compares codes, not bodies, and cannot see a view that returns a code
  its own annotation does not declare.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YTrc91QNqcM31iyvkeijEi