Merge pull request #67 from pylon-code/docs/pylon-product-name-sweep

docs: call the product Pylon

Author: rynfar

docs/README.md

@@ -1,6 +1,6 @@
-# T3 Code docs
+# Pylon docs
 
-## Using T3 Code
+## Using Pylon
 
 - [Install and first run](./user/install.md)
 - [Permission modes](./user/permission-modes.md)
@@ -19,7 +19,7 @@ Mobile app: [apps/mobile/README.md](../apps/mobile/README.md)
 
 ---
 
-## Working on T3 Code
+## Working on Pylon
 
 Everything below is for maintainers. Setup lives in the [root README](../README.md);
 policy in [CONTRIBUTING.md](../CONTRIBUTING.md); agent rules in [AGENTS.md](../AGENTS.md).

docs/internals/ci.md

@@ -1,6 +1,6 @@
 # CI quality gates
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
 [`.github/workflows/ci.yml`](../../.github/workflows/ci.yml) runs three jobs on pull requests and
 pushes to `pylon`:

docs/internals/connection-runtime.md

@@ -1,6 +1,6 @@
 # Connection Runtime
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
 The connection runtime is shared by web and mobile. It owns connectivity,
 authentication, retries, transport lifetime, cached environment data, and

docs/internals/environment-auth.md

@@ -1,6 +1,6 @@
 # Environment Authentication Profile
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
 The environment server and the relay use separate credentials, issuers, and trust
 boundaries. They intentionally use a similar OAuth-shaped model so that permission

docs/internals/glossary.md

@@ -1,8 +1,8 @@
 # Glossary
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
-This is a living glossary for T3 Code. It explains what common terms mean in this codebase.
+This is a living glossary for Pylon. It explains what common terms mean in this codebase.
 
 ## Table of contents
 

docs/internals/overview.md

@@ -1,8 +1,8 @@
 # Architecture
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
-T3 Code is a server runtime that owns agent sessions, workspaces, and version control, plus clients
+Pylon is a server runtime that owns agent sessions, workspaces, and version control, plus clients
 (web, desktop, mobile) that talk to it over one authenticated Effect RPC WebSocket. The server is the
 execution boundary: every provider process, terminal, git operation, and filesystem read happens
 there, never in the client.

docs/internals/prime-agent-native-parity.md

@@ -1,6 +1,6 @@
 # Prime Agent native parity plan
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
 ## Acceptance bar
 

docs/internals/providers.md

@@ -1,8 +1,8 @@
 # Provider architecture
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
-A provider is the agent runtime that does the actual work. T3 Code supports several, and the
+A provider is the agent runtime that does the actual work. Pylon supports several, and the
 orchestration layer does not know which one is behind a thread.
 
 ## Built-in drivers

docs/internals/remote.md

@@ -1,6 +1,6 @@
 # Remote Architecture
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
 Remote environments are shipped, not planned. Direct, bearer-paired, relay-tunneled, Tailscale, and
 desktop-managed SSH access all exist today. This document describes the model they share and where

docs/internals/resource-telemetry.md

@@ -1,6 +1,6 @@
 # Resource telemetry architecture
 
-> For maintainers. Using T3 Code? See [docs/user](../user/).
+> For maintainers. Using Pylon? See [docs/user](../user/).
 
 Status: implemented