docs: point reverse-attach links at openab-computer after rename

Dockerfile

@@ -102,7 +102,7 @@
 # The listener default is loopback, and the runtime refuses an off-loopback bind
 # while it holds no TLS key. Reachability is the deployment's job — a tailscale
 # sidecar sharing the network namespace — not this image's.
 ENV HOME=/workspace \
     RUST_LOG=info \
     PTY_LISTEN=127.0.0.1:8090 \
     PTY_COMMAND=/usr/bin/bash \
@@ -117,7 +117,7 @@
     # container has filled with *.tar.gz; this image fetches nothing itself.
     PTY_SEED_DIR="" \
     # Reverse-attached tools plane, off by default. Set to a loopback address
-    # (e.g. 127.0.0.1:8091) to let a Mac lend its instance-mcp tools to a session
+    # (e.g. 127.0.0.1:8091) to let a Mac lend its OpenAB Computer tools to a session
     # through GET /tools/attach/{session}; the CLI then finds them at the URL in
     # OPENAB_TOOLS_MCP_URL. Off means: no listener, and /tools/attach refuses.
     PTY_TOOLS_LISTEN="" \

README.md

@@ -97,7 +97,7 @@ session** by dialling in (`WS /tools/attach/{session}`, per-session secret minte
 by the admin plane); the coding CLI inside the session reaches them through a
 loopback MCP URL in its environment. The pod initiates nothing and stores only a
 hash. §9 of the client contract has the wire shape; the design is
-[reverse attach](https://github.com/openabdev/instance-mcp/blob/main/docs/adr/reverse-attach.md).
+[reverse attach](https://github.com/openabdev/openab-computer/blob/main/docs/adr/reverse-attach.md).
 
 A session shell *can* reach the listener over loopback, so the split is what keeps
 a compromised shell from managing its siblings: the shell never holds the admin

deploy/ecs/entrypoint.sh

@@ -71,7 +71,7 @@ scrollback_replay = false
 filter_terminal_responses = ${PTY_FILTER_TERMINAL_RESPONSES}
 admin_credential_hash = "${PTY_ADMIN_HASH}"
 seed_dir = "${PTY_SEED_DIR:-}"
-# Reverse-attached tools (a Mac lends its instance-mcp tools to one session).
+# Reverse-attached tools (a Mac lends its OpenAB Computer tools to one session).
 # Empty disables the plane; the runtime refuses anything but loopback here.
 tools_listen = "${PTY_TOOLS_LISTEN:-}"
 tools_attach_ttl = "${PTY_TOOLS_ATTACH_TTL:-24h}"

deploy/k8s/pod-tailscale.yaml

@@ -107,7 +107,7 @@ spec:
           value: 12h
         - name: PTY_IDLE_TTL
           value: 8h
-        # Reverse-attached tools (instance-mcp on a Mac dials in and lends its
+        # Reverse-attached tools (OpenAB Computer on a Mac dials in and lends its
         # tools to one session). Loopback only; the sidecar forwards inbound
         # tailnet TCP to any loopback port, so no `serve` config is needed for
         # GET /tools/attach/{session}. Leave unset to keep the plane off.

docs/k8s-howto.md

@@ -149,7 +149,7 @@ into `~/.kiro/settings/mcp.json` (and `@computer/*` trust into existing agent
 files), so there is no `mcp add` step; the hook's log lines appear in the
 runtime's container log at startup.
 The pod initiates nothing and stores only a hash. Design:
-[reverse attach](https://github.com/openabdev/instance-mcp/blob/main/docs/adr/reverse-attach.md);
+[reverse attach](https://github.com/openabdev/openab-computer/blob/main/docs/adr/reverse-attach.md);
 wire contract: §9 of [`../runtime/CLIENT-CONTRACT.md`](../runtime/CLIENT-CONTRACT.md).
 
 ```bash

runtime/CLIENT-CONTRACT.md

@@ -283,7 +283,7 @@ a takeover.
 This section is for a **different client**: not the terminal, but the machine
 whose tools a coding CLI inside a session should be able to call — in practice
 `oab-instance-mcp` on a Mac. Design of record:
-[reverse attach](https://github.com/openabdev/instance-mcp/blob/main/docs/adr/reverse-attach.md).
+[reverse attach](https://github.com/openabdev/openab-computer/blob/main/docs/adr/reverse-attach.md).
 The rule that shaped it: **the pod initiates nothing.** The Mac dials in, the pod
 stores only a hash, and the CLI talks to a loopback URL with no credential in it.
 

runtime/src/tools.rs

@@ -2,7 +2,7 @@
 //! session by **dialling in**, and the coding CLI inside that session reaches
 //! them over a plain loopback MCP endpoint.
 //!
-//! Design of record: `docs/adr/reverse-attach.md` in `openabdev/instance-mcp`;
+//! Design of record: `docs/adr/reverse-attach.md` in `openabdev/openab-computer`;
 //! runtime issue openabdev/openab-pty#37. The shape, and why each half is where
 //! it is:
 //!