@lifeaitools/rdc-skills 0.9.36 → 0.9.38

package/skills/release/SKILL.md

@@ -1,342 +1,88 @@
 ---
 name: rdc:release
-description: "Usage `rdc:release [promote <slug>|rdc-skills|clauth]` — Promote develop→main and deploy to production for any LIFEAI repo (clauth, rdc-skills, regen-root, etc.), or promote a staged app with rdc:release promote <slug>. Requires dev verification first."
+description: "Usage `rdc:release <repo> [version|--patch|--minor|--major|--dry-run]` — bump, commit, tag, push, wait for CI/publish, install, and verify a package or project using repo-local release metadata."
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw git/npm/CI dumps.
 > One checklist upfront, updated in place, shown again at end with 1-line verdict.
 
-> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag — checklist runs, each destructive step echoes `[RDC_TEST] skipping <step>` instead of mutating state.
+> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag.
 
-# rdc:release — Atomic LIFEAI Release
-
-## Purpose
-
-One skill. All repos. No confusion about which release path to use.
-
-When user says **"release"**, **"publish"**, **"promote"**, **"deploy to main"**, **"ship"**, or **"bump the version"** — this is the skill. Always. No exceptions.
-
-Dave has Bash access. He should never be asked to run commands. This skill runs the complete loop and shows one checklist + one verdict.
+# rdc:release — Generic Release
 
 ## When to Use
-- User says "release", "publish", "promote", "deploy to main", "ship", or "bump the version"
-- A package, plugin, or app needs to be versioned and pushed to its distribution channel
-- After landing significant changes that must be published (clauth, rdc-skills, regen-media, gws)
-- After develop is verified and staging passes — promoting to main
-- User says "promote studio", "release studio to production", "ship the app" — use `promote <slug>` mode
-
-**Never release autonomously.** This skill ONLY runs when the user explicitly invokes it. Never push to main on your own initiative.
 
-## Arguments
+- The user explicitly asks to release, publish, promote, ship, tag, or bump a repo.
+- A package or app needs versioning plus verification.
+- A repo provides release metadata in `package.json`, `.rdc/release.json`, README release instructions, or CI config.
 
-- `rdc:release <repo>` — patch bump (default), full loop
-- `rdc:release <repo> <version>` — explicit version (e.g. `1.6.0`)
-- `rdc:release <repo> --minor` | `--major` | `--patch` — semver bump
-- `rdc:release <repo> --dry-run` — show checklist and planned version, do nothing
-- `rdc:release promote <slug>` — promote a specific deployed app from staging → production
-- `rdc:release promote <slug> --dry-run` — show what would happen, do nothing
-- `rdc:release` (no args) — list known repos, ask which
+Never release without explicit user authorization.
 
-## Known Repos — The Single Lookup Table
+## Inputs
 
-Resolve `<repo>` here. If not in this table, ask Dave for source path + deploy mechanism before proceeding.
+- `rdc:release <repo>` — patch release by default.
+- `rdc:release <repo> <version>` — explicit version.
+- `rdc:release <repo> --patch|--minor|--major`
+- `rdc:release <repo> --dry-run`
 
-| Repo | Type | Source path | Release mechanism | Post-release |
-|------|------|-------------|-------------------|--------------|
-| `clauth` | npm package | `C:/Dev/clauth` | bump + tag → GitHub Actions → npm publish | `npm install -g @lifeaitools/clauth@latest` → daemon restart |
-| `rdc-skills` | local install | `C:/Dev/rdc-skills` | bump + tag → `install.sh` | copy to `~/.claude/skills/user/` + project |
-| `regen-root` | monorepo | `C:/Dev/regen-root` | merge develop→main via GitHub PR → Coolify auto-deploys | run `rdc:deploy <affected-slug>` gate checks |
-| `regen-media` | MCP server (in monorepo) | `C:/Dev/regen-root/mcp-servers/regen-media` | part of regen-root release — use `rdc:release regen-root` | Coolify redeploys `regen-media-mcp` from main |
-| `gws` | MCP server (in monorepo) | `C:/Dev/regen-root/mcp-servers/gws` | part of regen-root release — use `rdc:release regen-root` | Coolify redeploys from main |
+If `<repo>` is not resolvable from the current workspace, ask for its local path or GitHub slug.
 
-> **MCP servers inside the monorepo** (`regen-media`, `gws`) are released as part of `regen-root`. Coolify watches main and auto-deploys each app by its `watch_paths`. Don't release them separately.
-
----
-
-## Checklists
-
-### Package release checklist (clauth, rdc-skills)
+## Checklist
 
 ```
-rdc:release: <repo> vX.Y.Z → vA.B.C
+rdc:release: <repo> vX.Y.Z -> vA.B.C
 [ ] Source path resolved
-[ ] Working tree clean (git status)
-[ ] Current version detected (package.json)
+[ ] Release metadata read
+[ ] Working tree clean or user-approved dirty scope identified
+[ ] Current version detected
 [ ] New version computed
-[ ] Dry-run gate (if --dry-run, stop here and print planned commands)
-[ ] package.json bumped
+[ ] Dry-run gate handled
+[ ] Version files updated
+[ ] Tests/self-test passed
 [ ] Commit created
-[ ] Tag vA.B.C created + pushed
-[ ] CI completion event received via clauth channel (mcp__claude_ai_clauth__channel_list)
-[ ] CI concluded successfully (failure → pull logs via gh run view --log-failed)
-[ ] npm registry shows vA.B.C (npm view @lifeaitools/<repo> version)
-[ ] Local install executed
-[ ] Installed version verified
-[ ] Post-install action (daemon restart if clauth)
+[ ] Tag created
+[ ] Branch and tag pushed
+[ ] CI/publish status verified
+[ ] Registry/package/deploy target shows vA.B.C, if applicable
+[ ] Local install/update executed, if applicable
+[ ] Installed/runtime version verified
 [ ] Smoke test passed
-✅ rdc:release <repo>: vA.B.C live
-```
-
-### App promote checklist (promote <slug>)
-
-This mode promotes a single deployed app. It does NOT push `git push origin main` directly — it uses the GitHub PR merge API, which bypasses the `block-main-push` hook by design. The hook blocks autonomous pushes; explicit promotion via this skill is authorized by the user invoking it.
-
-```
-rdc:release promote: <slug> → <domain>
-[ ] Registry lookup (slug, coolify_uuid, domain, staging_slug, staging_domain, app_version)
-[ ] Staging health gate (HTTP 200 on staging_domain)
-[ ] Staging TLS valid
-[ ] develop branch clean and pushed
-[ ] Commits ahead of main: <N> commits
-[ ] Dry-run gate (if --dry-run, stop here and print planned commands)
-[ ] app package.json version bumped on develop
-[ ] Version bump committed + pushed to develop
-[ ] GitHub PR develop→main: created or located
-[ ] PR merged via GitHub API (merge method: merge)
-[ ] Coolify auto-deploy confirmed started (polling <slug> deployments)
-[ ] Deployment reached "finished" state
-[ ] Gate: HTTP 200 on <domain>
-[ ] Gate: TLS valid on <domain>
-[ ] deployment_registry updated (last_deploy_at, status='active')
-✅ rdc:release promote <slug>: <domain> live
+✅ rdc:release <repo>: vA.B.C live and verified
 ```
 
-### Monorepo release checklist (regen-root)
+## Resolution Order
 
-```
-rdc:release: regen-root — develop → main
-[ ] Source path: C:/Dev/regen-root
-[ ] develop branch clean and pushed (git status + git push)
-[ ] Commits ahead of main summarised (git log main..develop --oneline)
-[ ] Dry-run gate (if --dry-run, stop here)
-[ ] Root package.json version bumped on develop
-[ ] Version bump committed + pushed to develop
-[ ] GitHub PR: develop → main created (or existing PR located)
-[ ] PR merged via GitHub API (merge method: merge)
-[ ] main pulled locally (git fetch origin main)
-[ ] Coolify auto-deploy confirmed in progress (poll deployment status)
-[ ] Affected apps gate-checked via rdc:deploy health probes
-[ ] deployment_registry updated (last_deploy_at)
-✅ rdc:release regen-root: main promoted, Coolify deployed
-```
+1. Current repo if `<repo>` is `.` or omitted and the user clearly refers to the current workspace.
+2. Sibling directory matching `<repo>`.
+3. GitHub slug `<owner>/<repo>`.
+4. Repo-local `.rdc/release.json` if present.
+5. Ask for the missing path or release mechanism.
 
----
+## Generic Commands
 
-## Execution Details
+Use repo-local package tooling when available. Examples:
 
-> **Notification paths by repo type:**
-> - **Public repos** (rdc-skills, clauth): GitHub Actions POSTs to clauth channel on publish — wait for `mcp__claude_ai_clauth__channel_list` event, not a polling loop
-> - **Private repos** (regen-root): Coolify webhook is wired to Supabase — check `deployment_registry` for deploy completion, not the clauth channel
-
-### Package repos (clauth, rdc-skills)
-
-#### 1. Version bump
-- Read `package.json`, parse `version`
-- Apply: patch (default), minor, major, or explicit
-- Rewrite all `version` fields (some packages have `claude.version` too)
-
-#### 2. Commit + tag + push
 ```bash
-cd <source_path>
-git add package.json
+npm version patch --no-git-tag-version
+npm test
+git add package.json package-lock.json
 git commit -m "chore(release): vA.B.C"
 git tag vA.B.C
-git push && git push --tags
-```
-Never `--no-verify`. Never `--force`. Fix pre-commit hook failures at root cause.
-
-#### 3. Wait for CI via clauth channel (rdc-skills and clauth)
-
-Both repos have a GitHub Actions workflow that POSTs to `https://clauth.prtrust.fund/channel` on publish completion. **Do not poll `gh run list` in a loop.** Use the Monitor tool or check the channel:
-
-```
-# Check clauth channel for the completion event:
-mcp__claude_ai_clauth__channel_list (since: <tag-push-timestamp>)
-# Wait for event with text containing "vA.B.C" and status "success" or "failure"
-# If no event after 10 min → fallback: gh run list --repo LIFEAI/<repo> --limit 3
-```
-
-If the channel event shows failure, pull the run logs before proceeding:
-```bash
-gh run view <databaseId> --repo LIFEAI/<repo> --log-failed
-```
-
-#### 4. Verify npm registry
-
-```bash
-npm view @lifeaitools/<repo> version   # must equal vA.B.C
-```
-
-Only run this after the channel event confirms success — don't poll npm independently.
-
-#### 5. Install
-- **clauth:** `npm install -g @lifeaitools/clauth@latest`
-- **rdc-skills:** `node C:/Dev/rdc-skills/scripts/install-rdc-skills.js`
-  - If install script fails, fall back:
-    `cp -r C:/Dev/rdc-skills/skills/* ~/.claude/plugins/cache/rdc-skills/rdc-skills/latest/skills/`
-
-#### 6. Verify
-- **clauth:** `curl -s http://127.0.0.1:52437/ping | python3 -c "import sys,json; print(json.load(sys.stdin)['app_version'])"` — must match vA.B.C
-- **rdc-skills:** `ls ~/.claude/skills/user/rdc-release/SKILL.md` — must exist
-- **npm:** `npm list -g --depth=0 @lifeaitools/clauth` — version matches
-
-#### 7. Post-install
-- **clauth:** `curl -s -X POST http://127.0.0.1:52437/restart` → wait 3s → ping again
-- **rdc-skills:** none
-
-#### 8. Smoke test
-- **clauth:** `curl -s http://127.0.0.1:52437/v/supabase-anon` — expect a non-empty JWT string
-- **rdc-skills:** read frontmatter of one new/updated SKILL.md — parse succeeds
-
----
-
-### App promote (promote <slug>)
-
-#### 1. Registry lookup
-```sql
-SELECT slug, display_name, domain, staging_slug, staging_domain, coolify_uuid, monorepo_path, environment
-FROM deployment_registry
-WHERE slug = '<slug>';
-```
-If no `staging_slug` or `staging_domain`, ask Dave before proceeding — don't assume.
-
-#### 2. Staging health gate
-```bash
-curl -s -o /dev/null -w "%{http_code}" https://<staging_domain>/
-# Must return 200. TLS must be valid (no -k flag).
-```
-If staging is not healthy, STOP with `[!]` — don't promote a broken staging.
-
-#### 3. Git state check
-```bash
-cd C:/Dev/regen-root
-git status          # must be clean on develop
-git push origin develop
-git log origin/main..develop --oneline   # show what's going to main
-```
-
-#### 4. Version bump
-- Read `apps/<app>/package.json` (use `monorepo_path` from registry), parse `version`
-- Apply patch bump (default) or use explicit version if provided
-- Commit: `chore(release): <slug> vA.B.C`
-- Push to develop
-
-#### 5. GitHub PR merge
-```
-# Check for existing open PR develop→main
-mcp__claude_ai_Github_Proxy_MCP__list_pull_requests (base: main, head: develop)
-
-# If none: create one
-mcp__claude_ai_Github_Proxy_MCP__create_pull_request (base: main, head: develop, title: "chore(release): <slug> vA.B.C")
-
-# Merge it
-mcp__claude_ai_Github_Proxy_MCP__merge_pull_request (merge_method: merge)
-```
-**Note:** This uses the GitHub API — it does NOT run `git push origin main`. The `block-main-push` hook only blocks direct git push, not API merges.
-
-#### 6. Coolify deploy poll
-```bash
-# Use clauth to get Coolify token, then poll the app's deployments
-# Wait for status = "finished" — poll every 15s, 15min timeout
-curl -s -H "Authorization: Bearer $COOLIFY_TOKEN" \
-  "https://deploy.regendevcorp.com/api/v1/applications/<coolify_uuid>/deployments?per_page=1"
-```
-
-#### 7. Gate checks
-```bash
-curl -s -o /dev/null -w "%{http_code}" https://<domain>/   # must return 200
-curl -s -I https://<domain>/ | grep -i "strict-transport"   # TLS
-```
-
-#### 8. Update registry
-```sql
-UPDATE deployment_registry SET last_deploy_at = now(), status = 'active' WHERE slug = '<slug>';
-```
-
----
-
-### Monorepo release (regen-root)
-
-#### 1. Git state check
-```bash
-cd C:/Dev/regen-root
-git status          # must be clean on develop
-git push origin develop   # ensure latest is pushed
-git log origin/main..develop --oneline   # summarise what's going to main
-```
-
-#### 2. Bump root version on develop
-```bash
-# Read current version from package.json, apply patch bump
-# Commit: "chore(release): vA.B.C — promote develop → main"
-git add package.json && git commit -m "chore(release): vA.B.C"
-git push origin develop
+git push origin HEAD
+git push origin vA.B.C
+npm view <package-name> version
 ```
 
-#### 3. GitHub PR: develop → main
-- Check for open PR from develop→main: `gh pr list --repo LIFEAI/regen-root --base main --head develop`
-- If exists: use it. If not: create it via `mcp__claude_ai_Github_Proxy_MCP__create_pull_request`
-- Merge via `mcp__claude_ai_Github_Proxy_MCP__merge_pull_request` with `merge_method: merge`
+Never use `--force` or bypass hooks. If a hook fails, fix the cause.
 
-#### 4. Confirm Coolify auto-deploy
+## RDC Skills Package
 
-regen-root is a **private repo**. Coolify's webhook is wired to Supabase — deployment events land there automatically. Do NOT poll the Coolify REST API in a loop. Check Supabase:
+For this package, prefer the npm installer binary after publish:
 
-```sql
--- Wait for the affected app's deployment to show status = 'finished'
-SELECT slug, last_deploy_at, status, notes
-FROM deployment_registry
-WHERE slug IN (<affected slugs>)
-ORDER BY last_deploy_at DESC;
-```
-
-If the registry hasn't updated within 2 minutes of the PR merge, check Coolify directly:
 ```bash
-curl -s -H "Authorization: Bearer $(curl -s http://127.0.0.1:52437/v/coolify-api)" \
-  "https://deploy.regendevcorp.com/api/v1/applications/<uuid>/deployments?per_page=1"
+npm install -g @lifeaitools/rdc-skills@latest
+rdc-skills-install --profile core
 ```
 
-#### 5. Gate checks
-For each affected app, verify: HTTP 200, TLS valid, container running.
-Use `rdc:deploy diagnose <slug>` for any that fail.
-
-#### 6. Update registry
-```sql
-UPDATE deployment_registry SET last_deploy_at = now() WHERE slug IN (<affected slugs>);
-```
-
----
-
-## Failure Modes
-
-| Failure | Marker | Action |
-|---------|--------|--------|
-| Dirty working tree | `[!]` | Abort — show one-line diff summary, ask to commit or stash |
-| Pre-commit hook fails | `[!]` | Fix root cause, re-stage, retry — NEVER `--no-verify` |
-| CI fails | `[!]` | Print run URL + last 20 log lines |
-| npm not registered | `[!]` | Check CI actually published — not a silent skip |
-| PR merge blocked | `[!]` | Show blocker (branch protection, conflict) — resolve and retry |
-| Coolify deploy failed | `[!]` | Run `rdc:deploy diagnose <slug>` — fix before declaring done |
-| Gate non-200 | `[!]` | Don't update registry until fixed |
-
-Show full checklist with `[!]` markers even on failure.
-
----
-
-## Hard Rules
-
-- **Never push directly to `main`** — always via GitHub PR merge (`mcp__claude_ai_Github_Proxy_MCP__merge_pull_request`)
-- **Never `--force`, never `--no-verify`, never `--no-gpg-sign`**
-- **Never declare success** without verified install or verified Coolify gate
-- **Never release without an explicit `rdc:release` invocation** from the user
-- **Monorepo MCP servers** (`regen-media`, `gws`) are released via `rdc:release regen-root` — not separately
-
----
-
-## Related
-
-- `.claude/context/clauth.md` — clauth release source of truth
-- `.claude/context/coolify-deployment.md` — Coolify watch_paths, deploy rules
-- `memory/feedback_version_bump_must_tag.md` — never bump without tagging
-- `memory/feedback_use_rdc_release.md` — "promote/deploy to main" always triggers this skill
+Use `--profile lifeai` only on a workstation that intentionally has the LIFEAI project layout and services.

package/skills/self-test/SKILL.md

@@ -31,7 +31,7 @@ description: "Usage `rdc:self-test [--strict]` — Validate all rdc:* skills, pl
 Launch the interactive menu — pick tier, pick skill, see live output:
 
 ```bash
-node C:/Dev/rdc-skills/scripts/self-test-ui.mjs
+node {RDC_SKILLS_ROOT}/scripts/self-test-ui.mjs
 ```
 
 Menu options:
@@ -45,9 +45,9 @@ Test output streams live to the terminal. No server, no extra processes.
 
 1. **Run the linter (direct or via UI):**
    ```bash
-   node C:/Dev/rdc-skills/scripts/self-test.mjs
+   node {RDC_SKILLS_ROOT}/scripts/self-test.mjs
    # or interactively:
-   node C:/Dev/rdc-skills/scripts/self-test-ui.mjs
+   node {RDC_SKILLS_ROOT}/scripts/self-test-ui.mjs
    ```
 
 2. **Interpret exit codes:**

package/skills/terminal-config/SKILL.md

@@ -1,217 +1,62 @@
 ---
 name: rdc:terminal-config
-description: "Usage `rdc:terminal-config <task>` — read and safely modify Windows Terminal settings and cell startup sequencing. Contains canonical file locations, profile GUIDs, keybinding map, and what NEVER to change."
+description: "Usage `rdc:terminal-config <task>` — read and safely modify Windows Terminal settings, shell profiles, and agent startup sequencing without relying on machine-specific paths."
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.
 
-# rdc:terminal-config — Windows Terminal & Cell Startup Reference
+# rdc:terminal-config — Terminal & Agent Startup
 
 ## When to Use
-- Before modifying any terminal setting, profile, or keybinding
-- When setting up a new profile (Claude, Codex, cell cells)
-- When cell startup is broken (wrong `--append-system-prompt`, wrong cwd, wrong CELL_ROLE)
-- When keybindings conflict or are missing
 
-## ⛔ ABSOLUTE RULES — READ BEFORE TOUCHING ANYTHING
+- Before modifying Windows Terminal settings, shell profiles, keybindings, startup scripts, or agent launch commands.
+- When setting up a Claude, Codex, or project-specific cell profile.
+- When startup is broken because the wrong cwd, shell, env var, or prompt file is being loaded.
 
-1. **NEVER change profile GUIDs** — Windows Terminal uses these as identity. Changing a GUID orphans all pinned shortcuts and window layouts.
-2. **NEVER remove `"id": null` keybinding entries** — these intentionally UNBIND enter/shift-enter/ctrl-enter so Claude Code's interactive prompt works without the terminal swallowing keystrokes.
-3. **NEVER change `firstWindowPreference`** — it's `persistedWindowLayout`, which restores Dave's exact pane/tab layout on restart.
-4. **NEVER change `defaultProfile`** — it's `{574e775e-...}` (PowerShell Core). Changing it breaks new-tab behavior.
-5. **ALWAYS read the file before editing** — never write from memory.
-6. **ALWAYS validate JSON** before saving — a syntax error silently resets all settings on next Terminal launch (no error shown, settings wiped).
+## Rules
 
----
-
-## File Locations
-
-| File | Path | Purpose |
-|------|------|---------|
-| **Terminal settings** | `C:\Users\DaveLadouceur\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json` | Main config — profiles, keybindings, color schemes |
-| **Cell init script** | `C:\Dev\regen-root\scripts\cell-init.ps1` | Launched by each cell profile (PowerShell 7). Sets CELL_ROLE, prints banner, runs `claude --append-system-prompt` |
-| **Cell state dir** | `C:\Dev\regen-root\.cell-state\` | PID lockfiles per cell (`sv.lock`, `cell-portal.lock`, etc.) |
-| **Claude keybindings** | `C:\Users\DaveLadouceur\.claude\keybindings.json` | Claude Code keybindings (separate from Terminal) |
-| **Claude settings** | `C:\Dev\regen-root\.claude\settings.json` | Project-level Claude Code settings, hooks, permissions |
-| **Claude user settings** | `C:\Users\DaveLadouceur\.claude\settings.json` | User-level Claude Code settings |
-
----
-
-## Profile Inventory
-
-Every profile has a fixed GUID. Do not change them.
+1. Read the current settings file before editing.
+2. Never change existing profile GUIDs unless the user explicitly wants a new profile identity.
+3. Never remove intentionally null keybindings without explaining the consequence.
+4. Validate JSON before saving.
+5. Use environment-derived paths:
+   - Terminal settings: `$env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json`
+   - Claude user settings: `$env:USERPROFILE\.claude\settings.json`
+   - Codex user config: `$env:USERPROFILE\.codex\config.toml`
+   - Project startup scripts: `{PROJECT_ROOT}\scripts\...`
 
-| GUID | Name | Tab Color | Purpose |
-|------|------|-----------|---------|
-| `{574e775e-4f2a-5b96-ac1e-a2962a402336}` | PowerShell | — | **Default profile** — PowerShell 7 Core |
-| `{e7c1128b-e51f-4eba-bcdb-85f550c31b97}` | SV | `#1A6B3C` (green) | Supervisor cell — full repo access, runs `cell-init.ps1 sv` |
-| `{190a2f39-f6ad-4638-8fef-e4c7aa58c349}` | Claude | `#B91C1C` (red) | Claude conversation cell, runs `cell-init.ps1 sv` |
-| `{2d0248ef-7bb7-4b9e-b381-c4aa1f570f49}` | Codex | `#0F766E` (teal) | Codex AI cell — runs `pwsh.exe -NoLogo -NoExit -Command codex` |
-| `{767642b0-606c-468c-89a0-4573df6fcdaf}` | VS Code | `#2D5986` (blue) | Launches `code-safe C:\Dev\regen-root` |
-| `{6cbd327a-5b5e-4e83-96f6-041615382d36}` | PowerShell (Admin) | `#1E3A5F` (dark blue) | Elevated PowerShell — uses `LIFEAI Slate` color scheme |
-| `{0caa0dad-35be-5f56-a8ff-afceeeaa6101}` | Command Prompt | — | Legacy CMD — visible but rarely used |
-| `{574e775e...}` and others | `hidden: true` | — | Windows PowerShell, Azure Shell, VS DevTools — all hidden |
-
-### Profile commandlines
+## Safe Edit Procedure
 
 ```
-SV / Claude:   pwsh.exe -NoLogo -NoExit -ExecutionPolicy Bypass -File "C:\Dev\regen-root\scripts\cell-init.ps1" sv
-Codex:         pwsh.exe -NoLogo -NoExit -Command codex
-VS Code:       cmd.exe /c start "" code-safe C:\Dev\regen-root
-Admin PS:      powershell.exe -NoLogo   (+ elevate: true)
-```
-
-All cell profiles set `"startingDirectory": "C:\\Dev\\regen-root"`.
-SV / Claude / Codex all run on **PowerShell 7 (`pwsh.exe`)** — never bare `powershell.exe` (that resolves to legacy Windows PowerShell 5.1).
-
----
-
-## Keybinding Map
-
-### Critical: intentionally unbound keys (never restore these)
-
-```json
-{ "id": null, "keys": "shift+enter" }
-{ "id": null, "keys": "ctrl+enter" }
-{ "id": null, "keys": "enter" }
+rdc:terminal-config: <task>
+[ ] Current settings file located from environment
+[ ] File read before edit
+[ ] Existing GUIDs preserved
+[ ] Null keybindings preserved or explicitly approved
+[ ] JSON/TOML syntax validated
+[ ] Startup command uses the intended shell, cwd, and project root
+[ ] Verification command run
+✅ rdc:terminal-config: <result>
 ```
 
-**Why:** Without these null bindings, Windows Terminal intercepts Enter/Shift-Enter/Ctrl-Enter before Claude Code's interactive prompt sees them. Sessions break silently.
-
-### Pane navigation (safe to change)
-
-| Keys | Action |
-|------|--------|
-| `ctrl+alt+v` | Split pane right (duplicate) |
-| `ctrl+alt+h` | Split pane down (duplicate) |
-| `ctrl+alt+left/right/up/down` | Move focus between panes |
-| `ctrl+alt+shift+left/right` | Resize pane |
-| `ctrl+shift+z` | Toggle pane zoom |
-| `ctrl+shift+w` | Close pane |
-| `alt+shift+d` | Split pane auto (duplicate) |
-
-### Standard overrides
-
-| Keys | Action |
-|------|--------|
-| `ctrl+c` | Copy (singleLine: false) |
-| `ctrl+v` | Paste |
-| `ctrl+shift+f` | Find |
-
----
-
-## Color Schemes
-
-Four custom schemes live in the `schemes` array. Do not rename them — profiles reference by name.
-
-| Name | Background | Used by |
-|------|-----------|---------|
-| `Dimidium` | `#282A36` (dark purple) | Default for all cell profiles |
-| `LIFEAI Claude` | `#1A0F0A` (dark brown) | Available, not currently assigned |
-| `LIFEAI Dark` | `#0D1F17` (dark green) | Available, not currently assigned |
-| `LIFEAI Slate` | `#0F1923` (dark blue) | PowerShell Admin profile |
-| `Dracula` | `#282A36` | Available, not currently assigned |
-
----
-
-## Global Settings (safe reference)
+## Windows Terminal Notes
 
-```json
-"copyOnSelect": true          // highlight = copied. Don't change — muscle memory.
-"copyFormatting": "all"       // preserves ANSI colors on copy
-"firstWindowPreference": "persistedWindowLayout"  // restores last layout on open. NEVER CHANGE.
-"defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}"  // PowerShell Core. NEVER CHANGE.
-"theme": "dark"
-"showTabsFullscreen": true
-"initialRows": 40
-```
+- Prefer `pwsh.exe` for PowerShell 7 profiles.
+- Keep `startingDirectory` explicit for project profiles.
+- Use a newly generated GUID for each new profile:
 
-Font defaults (in `profiles.defaults`):
-```json
-"face": "Consolas"
-"size": 12
-"cellHeight": "1.2"
-"cellWidth": "0.6"
-"weight": "normal"
+```powershell
+"{$([System.Guid]::NewGuid().ToString())}"
 ```
 
----
-
-## Cell Startup Sequencing
-
-`cell-init.ps1` is the PowerShell 7 startup script for all cell profiles. It:
-
-1. Accepts `Role` arg (`sv`, `cell-portal`, `cell-data`, `cell-cs2`, `cell-mktg`, `cell-infra`, `specialist`)
-2. Looks up `Label`, `Color`, `Scope`, `Paths`, `Prompt` from the `$roles` hashtable
-3. Prints a colored banner
-4. Writes a PID lockfile to `.cell-state\<role>.lock`
-5. Runs `git log` filtered to that cell's path scope
-6. Launches: `claude --append-system-prompt "<Prompt>"`
-
-### Cell role → prompt scope mapping
-
-| Role arg | Claude system prompt |
-|----------|---------------------|
-| `sv` | "You are the SUPERVISOR cell. You have full repo access. Coordinate across all packages and apps." |
-| `cell-portal` | Portal cell — frontend apps only (apps/prt, apps/rdc, packages/ui, models/) |
-| `cell-data` | Data cell — packages/supabase, virtue-engine, pal, hail, daf-intelligence |
-| `cell-cs2` | CS2 cell — packages/cs2, quad-pixel, planetary-ontology, models/ |
-| `cell-mktg` | Marketing cell — rdc-marketing-engine, canvas, sites/, email-templates |
-| `cell-infra` | Infra cell — Coolify, CI/CD, root config, scripts/ |
-| `specialist` | Specialist cell — repo-wide reviews, cleanup, docs, audits |
-
----
-
-## Safe Edit Procedure
-
-### When adding or modifying a profile
-
-1. Read the current file first (never edit from memory)
-2. Generate a new GUID with: `[System.Guid]::NewGuid().ToString('B')` (PowerShell) — wrap in `{}`
-3. Copy the SV profile as a template
-4. Set `commandline`, `startingDirectory`, `environment`, `tabColor`, `icon`, `name`
-5. Do NOT set `guid` to an existing value
-6. Validate JSON: `Get-Content settings.json | ConvertFrom-Json` (errors = syntax problem)
-7. Save and reopen Terminal to verify
-
-### When adding a keybinding
-
-1. Add to the `keybindings` array
-2. Check for conflicts with the null-bound keys (`enter`, `shift+enter`, `ctrl+enter`) — NEVER override them
-3. Validate JSON before saving
-
-### When editing cell startup
-
-Edit `C:\Dev\regen-root\scripts\cell-init.ps1` — it's in the repo, so changes are tracked.
-- Adding a new role: add a new entry to the `$roles` hashtable with all five keys (`Label`, `Color`, `Scope`, `Paths`, `Prompt`)
-- Changing scope: update `Paths` and `Prompt` only — don't touch banner/lockfile/git logic
-
----
-
-## Validation Commands
+- Validate settings before restarting Terminal:
 
 ```powershell
-# Validate JSON syntax before saving
 Get-Content "$env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json" | ConvertFrom-Json
-
-# Check cell lockfiles
-Get-Content C:\Dev\regen-root\.cell-state\sv.lock
-
-# Generate a new GUID for a profile
-"{$([System.Guid]::NewGuid().ToString())}"
 ```
 
----
-
-## WezTerm Alternative
-
-If Windows Terminal settings keep getting corrupted or misedited, **WezTerm** is the recommended migration:
-- Config is a Lua file (`~/.wezterm.lua` or `C:\Users\<user>\.config\wezterm\wezterm.lua`)
-- Committed to git — every change is a reviewable diff, not an opaque JSON blob
-- Startup layouts (tabs, panes, commands) are defined programmatically
-- Equivalent to current setup: `wezterm.mux.spawn_window()` per cell with `args` set to `pwsh.exe -NoLogo -NoExit -File cell-init.ps1 <role>`
-- Download: https://wezfurlong.org/wezterm/installation.html
+## Startup Scripts
 
-Migration path: copy existing color schemes as `wezterm.color.get_default_colors()` override tables, map keybindings to `config.keys` array, define tab bar with cell roles.
+If a project uses role/cell startup scripts, keep those scripts under the project root and commit them with the project. Do not bake one user's absolute machine paths into shared RDC skill files.