feat(RMGR-WP-0008): add workplan and register receiving surfaces

This commit is contained in:
tegwick 2026-08-21 17:15:21 +02:00
parent 5502afc1fd
commit 859df9aae7
15 changed files with 1501 additions and 11 deletions

View file

@ -4,11 +4,11 @@ type: workplan
title: "Receiving surface for work records and repository registers"
domain: infotech
repo: repo-manager
status: proposed
status: active
owner: codex
topic_slug: infotech
created: "2026-08-20"
updated: "2026-08-20"
updated: "2026-08-21"
parent_project: prj-state-hub-retirement
parent_workplan: SHR-WP-0001
related:
@ -69,7 +69,7 @@ surfaces index and govern them, they do not become a second source of truth.
```task
id: RMGR-WP-0008-T01
status: todo
status: done
priority: high
```
@ -83,6 +83,14 @@ Unblocks slice **A2b** (~9 routes plus `table:workplans`).
Follow the RMGR-WP-0002 dual-run shape — writeback, reconcile, mutation meter —
rather than inventing a second mechanism.
Result (2026-08-21): `rmgr workplan create|update|delete` now owns the
file-backed mutation path. Update accepts canonical ids or State Hub UUIDs;
delete is a confirmed, recoverable archive operation. All three operations use
optimistic HEAD checks, idempotency, Git evidence, reindexing, normalized
events, mutation metering, and optional push-seal. State Hub has the matching
`rm_update_workplan` compatibility adapter. Repo Manager's full suite and the
adapter's focused compatibility tests pass.
## Intake records
```task
@ -131,7 +139,7 @@ Unblocks slice **A2e** (~6 items) and the dependency routes inside A2b.
```task
id: RMGR-WP-0008-T05
status: todo
status: progress
priority: high
```
@ -152,6 +160,14 @@ Treat as one register spine with per-kind schemas rather than six unrelated
features — they share repo scoping, append-mostly write patterns, and the same
file-backed-authority rule.
Progress (2026-08-21): the shared spine is live for all six kinds as versioned
`registers/<kind>.yaml` files, with parser/index support and governed
`put`/`defer`/`note` commands. Kind-specific required fields cover the existing
State Hub create contracts, and the generic `rm_update_register_entry` adapter
can route compatibility writes. Remaining before `done`: lockfile ingestion,
licence/copyleft derived reports, route-level cutover fixtures, and migration of
the live register rows.
## Topic and classification contract
```task

View file

@ -4,7 +4,7 @@ type: workplan
title: "Coding-assistant commit provenance trailers"
domain: infotech
repo: repo-manager
status: proposed
status: ready
owner: codex
topic_slug: infotech
created: "2026-08-21"