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

config/workplan-prefix-registry.yaml

@@ -13,9 +13,6 @@ 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
@@ -62,6 +59,7 @@ owners:
   TAMQ-WP: tmux-amq
   RAIL-FAB-WP: railiance-fabric
   WHYNOT-WP: whynot-design
+  OPS-WP: ops-hub
 historical_collisions:
   - id: RAILIANCE-WP-0015
     repos: [railiance-platform, railiance-apps]