chore(registrar): register 14 repository prefixes, retire NET-WP and OPS-WP

Qualifying ad-hoc identifiers requires every repo to own a registered prefix,
and 13 of the 17 affected repos were absent from the registry despite using a
prefix consistently across dozens of files. None collided with an existing
owner or a retired prefix.

net-kingdom and ops-bridge each used two forms. NK-WP (229 ids vs NET-WP's 49)
and BRIDGE-WP (73 vs OPS-WP's 16) are the owners, ruled by Bernd. OPS-WP is
additionally retired for naming an ops family rather than a repository - the
same defect ADR-007 retired RAILIANCE-WP and PRJ-WP for. Existing NET-WP and
OPS-WP ids stay as they are; only their prefixes are closed to new work.

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

config/workplan-prefix-registry.yaml

@@ -10,6 +10,12 @@ canon:
   - the-custodian/canon/standards/project-repository-flavor_v0.1.md
 
 retired:
+  - prefix: NET-WP
+    reason: second prefix in net-kingdom; NK-WP is the repository's form (229 ids vs 49)
+    successors: [NK-WP]
+  - prefix: OPS-WP
+    reason: names an ops family, not a repository; collides in spirit with ops-warden and ops-mason
+    successors: [BRIDGE-WP]
   - prefix: PRJ-WP
     reason: flavor marker; never a valid prefix
   - prefix: RAIL-BS-WP
@@ -40,6 +46,20 @@ owners:
   USER-WP: user-engine
   TEN-WP: tenant-engine
 
+  ACTIVITY-WP: activity-core
+  ADAPTIVE-WP: adaptive-pricing
+  AGENTIC-WP: agentic-resources
+  GROUND-WP: ground-game
+  ITC-WP: info-tech-canon
+  KAIZEN-WP: kaizen-agentic
+  LLM-WP: llm-connect
+  NK-WP: net-kingdom
+  BRIDGE-WP: ops-bridge
+  WARDEN-WP: ops-warden
+  QONTO-WP: qonto-assistant
+  RAIL-HO-WP: railiance-infra
+  SECRETS-WP: secrets-engine
+  TAMQ-WP: tmux-amq
 historical_collisions:
   - id: RAILIANCE-WP-0015
     repos: [railiance-platform, railiance-apps]