feat(WP-0011): warden route lookup CLI over the pointer catalog

Add a read-only `warden route` command group (list/show/find) that reads
registry/routing/catalog.yaml and tells a worker which subsystem owns a need
and which wiki/canon doc to follow. ops-warden still executes exactly one lane
(SSH); routed entries return a pointer and never call any subsystem.

- src/warden/routing/: models.py + catalog.py loader; enforces the
  no-double-source rule (non-SSH entries with steps/cert_command fail validation),
  dup-id and schema checks.
- route list (active-only unless --all, --tag), route show (SSH appends steps +
  cert pattern; routed ends with "next action on <owner> — see <wiki_ref>"),
  route find (keyword ranking, --json).
- tests/test_routing.py: load/validation, find ranking, CLI JSON shapes, plus a
  drift guard (every wiki_ref anchor resolves; every entry has a reviewed date).
- Docs: wiki/AccessRouting.md CLI section, README quick reference, SCOPE A3 -> A4.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

src/warden/routing/__init__.py

@@ -0,0 +1,17 @@
+"""Routing lookup — read-only pointer layer over registry/routing/catalog.yaml.
+
+This package never calls OpenBao, flex-auth, key-cape, ops-bridge, or any other
+subsystem. It loads the machine-readable routing catalog and answers "who owns
+this need and where is the authoritative doc". The one lane ops-warden executes
+(SSH certificate issuance) is the only entry that carries authored steps.
+"""
+from warden.routing.catalog import Catalog, CatalogError, find_catalog_path, load_catalog
+from warden.routing.models import RouteEntry
+
+__all__ = [
+    "Catalog",
+    "CatalogError",
+    "RouteEntry",
+    "find_catalog_path",
+    "load_catalog",
+]