docs: remove pipelock references from README, examples, and test docs

Pipelock was removed in PR #193. Update the five remaining places
where current documentation (README, examples/bottles/claude.md,
tests/README.md, docs/ci.md, sidecar_bundle.py comment) still
described the old pipelock + cred-proxy topology.

tests/README.md

@@ -11,16 +11,19 @@ tests/
   fixtures.py                       # JSON manifest builders (shared)
   _docker.py                        # docker-availability skip helper (shared)
   unit/
-    test_pipelock_classify.py
-    test_pipelock_allowlist.py
-    test_pipelock_yaml.py
+    test_egress.py
+    test_egress_addon_core.py
+    test_manifest_egress.py
+    test_dlp_detectors.py
     test_manifest_runtime.py
+    ...                             # many others; see unit/ directory
   integration/
-    test_pipelock_sidecar_smoke.py
+    test_sidecar_bundle_image.py
+    test_sidecar_bundle_compose.py
     test_dry_run_plan.py
     test_orphan_cleanup.py
-  canaries/
-    test_pipelock_image.py          # opt-in; see below
+    ...
+  canaries/                         # opt-in; see below (currently empty)
 ```
 
 Classification falls out of the directory — no hand-maintained list to
@@ -32,7 +35,7 @@ keep in sync.
 python -m unittest discover -t . -s tests/unit -v         # unit only
 python -m unittest discover -t . -s tests/integration -v  # integration only
 python -m unittest discover -t . -s tests -v              # both (recursive)
-python -m unittest tests.unit.test_pipelock_yaml          # one file
+python -m unittest tests.unit.test_manifest_egress        # one file
 ```
 
 Discovery is invoked with `-t .` (top-level dir = repo root) so the
@@ -46,18 +49,18 @@ Discovery is invoked with `-t .` (top-level dir = repo root) so the
 - `test_orphan_cleanup.py` — `network_remove` is idempotent against
   missing resources, so the EXIT trap can call it unconditionally.
 - `test_sidecar_bundle_image.py` — builds Dockerfile.sidecars and
-  probes that pipelock / gitleaks / mitmdump / supervise are all
-  reachable inside the bundle.
+  probes that gitleaks / mitmdump / supervise are all reachable
+  inside the bundle.
 - `test_sidecar_bundle_compose.py` — end-to-end compose-up of an
   agent + bundle pair; verifies the agent reaches the bundle via
   the legacy network aliases.
 
 ## Canaries
 
-`tests/canaries/` holds upstream-regression checks (e.g. the pinned
-pipelock digest's binary still runs). These are gated on
+`tests/canaries/` holds upstream-regression checks gated on
 `BOT_BOTTLE_RUN_CANARIES=1` and not part of the per-push suite.
-They're invoked by the scheduled `canaries` workflow.
+They're invoked by the scheduled `canaries` workflow. Currently
+no canaries are defined.
 
 ```bash
 BOT_BOTTLE_RUN_CANARIES=1 python -m unittest discover -t . -s tests/canaries -v
@@ -67,7 +70,7 @@ BOT_BOTTLE_RUN_CANARIES=1 python -m unittest discover -t . -s tests/canaries -v
 
 - `bot_bottle/ssh.py` end-to-end (would need a fake SSH host inside
   the container).
-- A live SSH-through-pipelock tunnel against a real Tailscale-style IP.
+- A live SSH-through-git-gate tunnel against a real Tailscale-style IP.
 - DLP false-positive measurements.
 - TLS handling / cert pinning behavior.