chore(brand): rebrand product and technical identifiers to Platon Code

.agents/skills/ios-debugger-agent/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ios-debugger-agent
-description: Build, launch, inspect, and drive iOS apps with the repository-configured XcodeBuildMCP server. Use on macOS for iOS Simulator builds, focused native test runs, semantic UI automation, screenshots, logs, or debugging, including T3 Code Mobile verification.
+description: Build, launch, inspect, and drive iOS apps with the repository-configured XcodeBuildMCP server. Use on macOS for iOS Simulator builds, focused native test runs, semantic UI automation, screenshots, logs, or debugging, including Platon Code Mobile verification.
 ---
 
 # iOS Debugger Agent

.agents/skills/ios-simulator-browser/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ios-simulator-browser
-description: Stream an explicit iOS Simulator through pinned serve-sim into the T3 Code in-app browser or another agent browser. Use on Apple Silicon macOS when the user should watch simulator verification live or when browser-visible simulator evidence is needed.
+description: Stream an explicit iOS Simulator through pinned serve-sim into the Platon Code in-app browser or another agent browser. Use on Apple Silicon macOS when the user should watch simulator verification live or when browser-visible simulator evidence is needed.
 ---
 
 # iOS Simulator Browser
@@ -11,7 +11,7 @@ Use serve-sim as the shared visual feed for an iOS Simulator. Use `ios-debugger-
 
 serve-sim `0.1.45` requires Apple Silicon macOS, Xcode command-line tools, and Node.js 20 or newer. If the host is unsupported, continue with XcodeBuildMCP screenshots and report that live streaming was unavailable.
 
-When running inside T3 Code, use its product-native browser MCP to open the stream. Other agent hosts may use their own browser or preview surface.
+When running inside Platon Code, use its product-native browser MCP to open the stream. Other agent hosts may use their own browser or preview surface.
 
 Keep serve-sim on its default `127.0.0.1` binding. Do not expose its preview to a LAN or tunnel unless the user explicitly requests that access and the network is trusted; the preview includes a token-gated shell-execution route.
 

.agents/skills/ios-simulator-browser/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "iOS Simulator Browser"
   short_description: "Stream iOS Simulator in the browser"
-  default_prompt: "Use $ios-simulator-browser to stream the selected iOS Simulator into the T3 Code in-app browser."
+  default_prompt: "Use $ios-simulator-browser to stream the selected iOS Simulator into the Platon Code in-app browser."

.agents/skills/test-t3-app/SKILL.md → .agents/skills/test-platon-app/SKILL.md

@@ -1,24 +1,24 @@
 ---
-name: test-t3-app
-description: Launch, retain, and test the T3 Code web app in isolated development environments, including first-try browser authentication with one-time pairing URLs, pairing-token recovery, worktree-safe state directories, cross-turn dev server lifecycle, and direct SQLite inspection or fixture seeding. Use when an agent needs to run T3 locally, iteratively test UI behavior with a human, recover from an expired or consumed pairing token, isolate dev state, or prepare test data in state.sqlite.
+name: test-platon-app
+description: Launch, retain, and test the Platon Code web app in isolated development environments, including first-try browser authentication with one-time pairing URLs, pairing-token recovery, worktree-safe state directories, cross-turn dev server lifecycle, and direct SQLite inspection or fixture seeding. Use when an agent needs to run T3 locally, iteratively test UI behavior with a human, recover from an expired or consumed pairing token, isolate dev state, or prepare test data in state.sqlite.
 ---
 
 # Test T3 App
 
-Use this skill for the web client. For iOS Simulator, Android Emulator, or physical-device testing against an isolated T3 backend, use the sibling [`test-t3-mobile`](../test-t3-mobile/SKILL.md) skill.
+Use this skill for the web client. For iOS Simulator, Android Emulator, or physical-device testing against an isolated T3 backend, use the sibling [`test-platon-mobile`](../test-platon-mobile/SKILL.md) skill.
 
 ## Start an isolated web environment
 
 1. Run commands from the repository root.
 2. Choose a base directory that belongs only to the current worktree or test:
-   - Use the repository's ignored `.t3` directory for reusable worktree-local state.
-   - Use `mktemp -d /tmp/t3code-test.XXXXXX` for disposable state and retain the printed absolute path.
-3. Start the full web stack with `vp run dev`. Add `--share` when the user needs to open it from another tailnet device. In a linked worktree it defaults to that worktree's gitignored `.t3`; pass `--home-dir <base-dir>` only when the test needs a different isolated directory.
+   - Use the repository's ignored `.platon` directory for reusable worktree-local state.
+   - Use `mktemp -d /tmp/platon-code-test.XXXXXX` for disposable state and retain the printed absolute path.
+3. Start the full web stack with `vp run dev`. Add `--share` when the user needs to open it from another tailnet device. In a linked worktree it defaults to that worktree's gitignored `.platon`; pass `--home-dir <base-dir>` only when the test needs a different isolated directory.
 4. Keep the terminal session alive and read the selected server port, web port, base directory, and pairing URL from its output.
 
-Treat a base directory as disposable only when it was created or deliberately selected for the current test. Never delete or directly seed the shared `~/.t3` directory. Prefer starting with a new temporary base directory over clearing state of uncertain ownership.
+Treat a base directory as disposable only when it was created or deliberately selected for the current test. Never delete or directly seed the shared `~/.platon` directory. Prefer starting with a new temporary base directory over clearing state of uncertain ownership.
 
-The worktree-local default deliberately outranks an ambient `T3CODE_HOME`; do not pass the shared home through to a worktree dev server.
+The worktree-local default deliberately outranks an ambient `PLATON_CODE_HOME`; do not pass the shared home through to a worktree dev server.
 
 Ports are derived from the worktree path but can shift when occupied. Always read the actual values from the `[dev-runner]` line.
 
@@ -28,7 +28,7 @@ The dev runner disables browser auto-open by default. Do not pass `--browser` du
 
 ### Verify a shared environment before human handoff
 
-When another person will use the printed pairing URL, first open the shared origin without the pairing path or fragment in the controlled browser and confirm the T3 Code app loads. This browser navigation is required even when curl succeeds because browsers block some otherwise reachable ports before making a network request.
+When another person will use the printed pairing URL, first open the shared origin without the pairing path or fragment in the controlled browser and confirm the Platon Code app loads. This browser navigation is required even when curl succeeds because browsers block some otherwise reachable ports before making a network request.
 
 Do not open the other person's complete pairing URL during this reachability check; doing so consumes its one-time token. If the agent also needs an authenticated browser, create and consume a separate pairing token, then leave a fresh token for the other person.
 
@@ -57,28 +57,28 @@ Treat pairing URLs as secrets. Do not copy them into final responses, screenshot
 Create another token against the same database and web URL as the running dev server:
 
 ```bash
-T3CODE_PORT=<server-port> node apps/server/src/bin.ts auth pairing create \
+PLATON_CODE_PORT=<server-port> node apps/server/src/bin.ts auth pairing create \
   --base-dir <base-dir> \
   --dev-url <web-url> \
   --base-url <web-url> \
   --ttl 15m \
   --label agent-ui-test
 ```
 
-Use the `Pair URL` from this command once. Derive `<server-port>` and `<web-url>` from the current dev-runner output, including any automatically selected port offset. Setting `T3CODE_PORT` keeps the administrative CLI from probing for an unrelated free port.
+Use the `Pair URL` from this command once. Derive `<server-port>` and `<web-url>` from the current dev-runner output, including any automatically selected port offset. Setting `PLATON_CODE_PORT` keeps the administrative CLI from probing for an unrelated free port.
 
-Always pass `--dev-url` for a dev-runner environment so the generated pairing URL uses the current web origin. An explicit base directory stores runtime state in `<base-dir>/userdata`; the `<base-dir>/dev` fallback is only used by an implicit dev home. A worktree-local `.t3` counts as explicit, so its state lives in `<worktree>/.t3/userdata`. Use `auth pairing list` to inspect active token metadata; it intentionally cannot reveal token secrets.
+Always pass `--dev-url` for a dev-runner environment so the generated pairing URL uses the current web origin. An explicit base directory stores runtime state in `<base-dir>/userdata`; the `<base-dir>/dev` fallback is only used by an implicit dev home. A worktree-local `.platon` counts as explicit, so its state lives in `<worktree>/.platon/userdata`. Use `auth pairing list` to inspect active token metadata; it intentionally cannot reveal token secrets.
 
 ## Inspect or seed SQLite state
 
 Read [references/sqlite-fixtures.md](references/sqlite-fixtures.md) before changing the database.
 
-- Use `node apps/server/scripts/t3-sqlite-state.ts query` for schema discovery and read-only checks.
-- Stop the dev server before using `node apps/server/scripts/t3-sqlite-state.ts exec`, then restart it with the same base directory.
+- Use `node apps/server/scripts/platon-sqlite-state.ts query` for schema discovery and read-only checks.
+- Stop the dev server before using `node apps/server/scripts/platon-sqlite-state.ts exec`, then restart it with the same base directory.
 - Seed projection tables only for disposable UI fixtures. Use application commands and APIs when testing business behavior or projection correctness.
 - Use the auth CLI, not direct `auth_*` table edits, for pairing and sessions.
 
-The helper refuses to write to the shared `~/.t3` directory by default and creates a database backup before each mutation.
+The helper refuses to write to the shared `~/.platon` directory by default and creates a database backup before each mutation.
 
 ## Tear down only when the testing loop is finished
 

.agents/skills/test-platon-app/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "T3 App Testing"
+  short_description: "Launch and retain isolated T3 test environments"
+  default_prompt: "Use $test-platon-app to launch an isolated Platon environment and iteratively test it in the browser while preserving state."

.agents/skills/test-t3-app/references/sqlite-fixtures.md → .agents/skills/test-platon-app/references/sqlite-fixtures.md

@@ -13,25 +13,25 @@ Start the target runtime once before seeding so all migrations have run. Use an
 List tables:
 
 ```bash
-node apps/server/scripts/t3-sqlite-state.ts query \
+node apps/server/scripts/platon-sqlite-state.ts query \
   --base-dir <base-dir> \
   --sql "SELECT name FROM sqlite_schema WHERE type = 'table' ORDER BY name"
 ```
 
 Inspect current columns before writing a fixture:
 
 ```bash
-node apps/server/scripts/t3-sqlite-state.ts query \
+node apps/server/scripts/platon-sqlite-state.ts query \
   --base-dir <base-dir> \
   --sql "PRAGMA table_info(projection_threads)"
 ```
 
 Apply a SQL fixture from a file:
 
 ```bash
-node apps/server/scripts/t3-sqlite-state.ts exec \
+node apps/server/scripts/platon-sqlite-state.ts exec \
   --base-dir <base-dir> \
-  --file /tmp/t3-seed.sql
+  --file /tmp/platon-seed.sql
 ```
 
 Use one statement per invocation for both `query` and `exec`; the helper wraps writes in a transaction and prints the backup path after a successful mutation. Use a single insert with multiple value rows when a fixture needs several records.