[kvlonge]

Why

The UI's maintenance panel shows a target's recorded moves, the old-name views kept for them, and janitor cleanups. All three are already mirrored into the control store, but nothing read them back.

Changes

• GET /api/control/locations/{location}/targets/{target}/maintenance?node=&limit= returns {migrations, old_name_views, janitor_events}. It needs view on the whole target, like the check listing.
• Migrations come newest first, optionally only moves into one model. origin_model is nullable.
• The response includes every recorded old-name-view step of the returned moves, joined on the move's warehouse event ID within the same location and target, oldest first. Steps written at the same instant are not in step order.
• Janitor events come newest first and are empty when node is set, because cleanups are not tied to models.
• limit defaults to 100 and is capped at 1000 for moves and janitor events each.
• New indexes for the move filter and the step join. Control stores from earlier pre-release versions are refused and must be recreated.
• Check reads moved into a new warehouse_history module with these reads.
• TypeScript client regenerated.
• Test fix: the worker contract now renews its 30 s scheduler lease, which expired on a slow Windows runner (Fenced).

Verification

• cargo test -p sqlbuild-orchestration --all-features: one endpoint test, on SQLite and PostgreSQL, covers:
  • per-model filtering and the limit=1 cut;
  • a step of an older move left out when only the newest move is returned;
  • a step recorded under another target never appearing (confirmed by mutation);
  • a denial on a target the person has no role on.
• make check-ci, public-repository scan.
• Review: one read-only pass, no blockers. Its two test gaps are covered above. view_sql in old-name views is the generated projection over relation and column names, not model SQL, so it stays readable with view.
• DuckShop: maintenance_history.json edge case.