docs: move backlog to forge issue tracker, extract boundary doc

CLAUDE.md

@@ -6,9 +6,11 @@ when you need depth on a subsystem. This file is the index +
 scratchpad.
 
 - High-level project intro: **[README.md](README.md)**.
-- Open work + backlog: **[TODO.md](TODO.md)**.
-- Deployment / ops / boundaries / gateway backlog:
-  **[TODO-ops.md](TODO-ops.md)**.
+- Open work + backlog: the **[forge issue
+  tracker](http://localhost:3000/hyperhive/hyperhive/issues)**.
+- Operator/agent trust-boundary design:
+  **[docs/boundary.md](docs/boundary.md)** (`area:ops` issues
+  for the deployment/gateway/privsep work).
 
 ## File map
 
@@ -286,8 +288,9 @@ Prune freely.
   `/answer-question/{id}` (CORS shim `with_cors` on that
   route), never the per-agent socket — keeps the
   operator-authority path off the agent's own socket. See
-  `TODO-ops.md` for the boundary rationale + the deployment/
-  gateway/privsep cluster.
+  `docs/boundary.md` for the boundary rationale; the
+  deployment/gateway/privsep work is tracked as `area:ops`
+  forge issues.
 - **Just landed:** sub-agents get a read-only view of their own
   config repo. `set_nspawn_flags` now adds
   `--bind-ro={proposed_dir}:/agents/<name>/config` for every
@@ -607,7 +610,7 @@ Prune freely.
   <details data-restore-key> survival, prompt-on-submit pattern.
 - **Open threads:** two-step spawn, notes compaction,
   unprivileged containers, Bash allow-list, xterm.js. The
-  deployment / gateway / privsep cluster is tracked in
-  `TODO-ops.md`. (Landed since this note was first written:
+  deployment / gateway / privsep cluster is tracked as
+  `area:ops` forge issues. (Landed since this note was first written:
   extra per-agent MCP servers, per-agent send allow-list,
   telemetry + the `/stats` page.)