docs: replace stale bash-first framing with Python-stdlib-first

The project started life as bash scripts and got rewritten to Python
(documented in docs/research/bash-vs-python-vs-go.md). Several docs
still carried the old "bash-first" framing — misleading for anyone
reading them now (8.7k lines of Python vs. ~130 lines of bash, all
in scripts/demo*.sh).

- CLAUDE.md "What this is" + "Conventions": orchestrator is Python,
  posture is stdlib-first.
- docs/prds/0010-cred-proxy.md, docs/research/manifest-format-and-
  grouping.md: quoted CLAUDE.md's old wording — re-quote.
- docs/research/built-in-supervisor-design.md, landscape-containerized-
  claude.md, agent-sandbox-landscape.md, pipelock-assessment.md,
  network-egress-guard.md: drop "bash-first" claims about the project,
  keep accurate descriptions of external tools' bash usage.

Leaves untouched: bash code-fence syntax in examples, README's
literal `bash scripts/demo.sh` invocation (the demo IS bash),
Claude Code's "Bash tool" references, IVIJL/devbox bash description
(that project actually is bash), and the bash-vs-python-vs-go
research note that records the rewrite decision.

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

docs/research/pipelock-assessment.md

@@ -270,7 +270,7 @@ its own scanner. This avoids a second container but introduces the
 the proxy run in the same failure domain.
 
 The sidecar topology is recommended for claude-bottle because it matches
-the existing bash-orchestrated multi-container model (the SSH key agent
+the existing Python-orchestrated multi-container model (the SSH key agent
 already uses a separate process), keeps pipelock outside the agent's kill
 reach, and avoids the `--best-effort` issue on macOS Docker Desktop.