tegwick 906cc2d7a9 fix(registrar): OPS-WP belongs to ops-hub, not retirement ... I retired OPS-WP on the reasoning that it names an ops family rather than a repository, without checking whether a repo owns it. ops-hub does: all 14 of its workplans use it. The anomaly is the reverse of what I wrote - the 16 OPS-WP ids in ops-bridge are the strays, against its 73 BRIDGE-WP ids. Recorded as debt rather than fixed here: re-keying those 16 to BRIDGE-WP is a separate migration with its own hub retirements, and today's pass is scoped to ad-hoc identifiers. WHYNOT-WP stays with whynot-design (26 ids vs whynot-control's 6), ruled by Bernd. whynot-control's 6 are the same class of stray. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006		2026-08-28 00:58:57 +02:00
..
assistant-provenance.yaml	feat: advance repository records and provenance	2026-08-21 22:07:48 +02:00
dual-run.pilot.example.yaml	feat(RMGR-WP-0003): production pilot dual-run config, bulk, push	2026-08-11 02:32:14 +02:00
fleet-namespace.yaml	feat(identifier): declare helixforge fleet namespace	2026-08-21 23:57:03 +02:00
hub-record-authority.yaml	feat: finish register receiving and authority routing	2026-08-21 23:15:48 +02:00
work-record-types.yaml	fix(identity): enforce qualified ad-hoc identifiers	2026-08-23 14:45:26 +02:00
workplan-prefix-registry.yaml	fix(registrar): OPS-WP belongs to ops-hub, not retirement	2026-08-28 00:58:57 +02:00