@lifeaitools/rdc-skills 0.9.28 → 0.9.30

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.9.25",
+  "version": "0.9.28",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight unattended builds with work-item tracking and TDD enforcement.",
   "author": {
     "name": "LIFEAI",

package/guides/agents/verify.md

@@ -37,6 +37,23 @@ If you're about to write any of these, STOP:
 
 Run these in order. All must pass. Capture output.
 
+### 0. Checklist decomposition quality
+
+Before code verification, inspect each work item checklist and the matching plan section.
+
+Required plan evidence:
+- `## Checklist Decomposition Matrix`
+- `## Checklist Quality Gate`
+- `verdict: PASS`
+
+Required work item evidence:
+- At least one `decomp-*` checklist item for every implementation work item
+- At least one `test-*` checklist item for every implementation work item
+- Each `decomp-*` item includes a route or file path, one action, one expected result, and one evidence artifact
+- Each `decomp-*` item is independently pass/fail; vague rows like "UI complete", "theme management works", or "integration verified" are failures
+
+If this check fails, stop validation for that item and reopen it. Do not mark a work item `done` when the checklist itself is not decomposed enough to prove completion.
+
 ### 1. Per-package vitest (every package touched)
 
 ```bash
@@ -107,6 +124,7 @@ $ npx tsc --noEmit --project packages/hail/tsconfig.json
 (no output — clean)
 
 ### Status
+Checklist quality: PASS
 PASS — safe to mark tasks done.
 ```
 
@@ -124,6 +142,7 @@ If any step fails: do NOT claim completion. Report the failure, fix it, re-run t
 When dispatching a verification agent, give them:
 - Exact list of packages/apps to verify
 - Explicit ban on `pnpm build` / `pnpm test` / `pnpm -r`
+- Work item checklists and the matching plan doc so `decomp-*` quality can be verified first
 - Required output format (above)
 - Instruction: "If any command fails, STOP and report. Do not fix. Do not continue."
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.9.28",
+  "version": "0.9.30",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight builds",
   "keywords": [
     "claude-code",

package/skills/build/SKILL.md

@@ -97,6 +97,10 @@ Read the task title and description, then:
    |-----------|--------|
    | No child tasks returned | → Invoke `rdc:plan` on this epic. Do NOT proceed with build. |
    | Tasks exist but all have empty `description` fields | → Invoke `rdc:plan` on this epic. Tasks without descriptions cannot be safely dispatched. |
+   | Plan doc missing `## Checklist Decomposition Matrix` | → Invoke `rdc:plan` on this epic. Do NOT dispatch agents. |
+   | Plan doc missing `## Checklist Quality Gate` with `verdict: PASS` | → Invoke `rdc:plan` on this epic. Do NOT dispatch agents. |
+   | Any implementation task lacks `decomp-*` checklist items | → Invoke `rdc:plan` on this epic. Coarse checklists cannot be safely dispatched. |
+   | Any `decomp-*` item lacks route/file, action, expected result, or evidence artifact | → Invoke `rdc:plan` on this epic. Do NOT dispatch agents. |
    | Tasks exist and have descriptions | → Continue with build. |
 
    **Re-planning is not a failure — it is correct behavior.** The build skill is the last gate before agent dispatch; catching an under-specified epic here is cheaper than a wasted agent run.
@@ -126,17 +130,53 @@ Read the task title and description, then:
    
    **If design decisions exist: follow them.** Include the summary in the agent prompt.
 
-3. **Load the plan** (if exists): check `.rdc/plans/` for matching topic (fallback: `.rdc/plans/`).
+3. **Load the plan** (mandatory): check `.rdc/plans/` for matching topic (fallback: `.rdc/plans/`).
+
+3b. **Checklist decomposition quality gate (mandatory before code):**
+
+   `rdc:build` is the final gate before implementation. It MUST reject any plan or work item that is too coarse for an agent to execute and verify independently.
+
+   Required plan sections:
+   - `## Checklist Decomposition Matrix`
+   - `## Checklist Quality Gate`
+   - `verdict: PASS`
+
+   Required task checklist shape:
+   - Every implementation work item has at least one `decomp-*` checklist row and one `test-*` checklist row.
+   - Every `decomp-*` row names a concrete route or file path.
+   - Every `decomp-*` row names one user/agent action.
+   - Every `decomp-*` row names one expected UI/API/DB result.
+   - Every `decomp-*` row names one verification artifact: test name, route probe, Playwright screenshot, SQL query, API response, type-check, migration proof, or CLI transcript.
+
+   Atomicity rubric:
+   - One observable behavior per `decomp-*` row.
+   - The row can pass or fail without reading hidden intent from the plan narrative.
+   - The row is small enough for a worker to implement, tick, and cite evidence for directly.
+   - Vague rows such as "theme management works", "UI implemented", "verified", "all screens", or "integration complete" are failures.
+
+   Minimum decomposition heuristics:
+   - UI route: at least empty/loading/loaded/error or the documented reason a state does not apply.
+   - CRUD surface: at least list, create, edit, detail, duplicate/delete/archive where applicable, and validation failure.
+   - API route: at least successful read/write, validation failure, and unauthorized/forbidden or documented auth bypass.
+   - DB/migration task: at least schema object, relationship/guard, policy/permission, seed/fixture or backfill, and smoke query.
+   - Editor/sidebar/CLI workflow: at least start, attach/open, enqueue action, observe result, timeout/error, and live refresh where applicable.
+
+   If the gate fails:
+   - Interactive: show the failing rows and invoke `rdc:plan <epic-id>` to repair the matrix before dispatch.
+   - Unattended: invoke `rdc:plan <epic-id> --unattended`, reload tasks, and run this gate once more.
+   - If the second gate fails, abort the build and return the failure list. Do not dispatch implementation agents.
+
+   **Plan verifier escalation:** A separate verifier agent is optional, not default. Dispatch one only when the plan touches 5+ UI routes, 3+ data/API boundaries, auth/security, production deployment, or when this rubric fails twice. The verifier reads the plan and work-item checklists only; it does not write code.
 
 4. **Read CLAUDE.md files** for all affected packages.
 
 5. **Classify each task** → assign agent type from the table above.
 
-5b. **Write a checklist into every work item before dispatching:**
-    For each task, append a checklist to its notes BEFORE setting to `in_progress`:
+5b. **Write or refresh the checklist into every work item before dispatching:**
+    For each task, append the exact `decomp-*` and `test-*` checklist rows to its notes BEFORE setting to `in_progress`:
     ```sql
     SELECT update_work_item_status('<id>'::uuid, 'in_progress',
-      '["CHECKLIST: [ ] <deliverable 1>, [ ] <deliverable 2>, [ ] tsc clean, [ ] route 200, [ ] committed"]'::jsonb
+      '["CHECKLIST: [ ] decomp-ui-route-state: <route/file> | action=<action> | expect=<result> | evidence=<artifact>, [ ] test-smoke-route: <route probe>, [ ] committed"]'::jsonb
     );
     ```
     The agent must complete every item on this checklist and return it checked off in AGENT_COMPLETE.
@@ -191,6 +231,13 @@ Read the task title and description, then:
      - **`"When done, set your work item to 'review' (NOT 'done') and return AGENT_COMPLETE with a verification field. The validator closes work items — you do not."`**
      - **`"COMPLETION PROOF REQUIRED in AGENT_COMPLETE: list every file written, the exact commit hash, and paste the vitest/tsc output. A report without this evidence will be rejected."`**
      - **`"If you find that a file or feature already exists: you MUST still verify it satisfies the full task spec before marking review. Finding a file is not completion. Run verification, check every requirement, and report what you found vs. what was required."`**
+     - **The decomposition items from the work item's checklist** (all `decomp-*` prefixed items). Include them verbatim in the prompt and instruct the agent:
+       ```
+       DECOMPOSITION CHECKLIST — you MUST implement/verify each row and tick it immediately via update_checklist_item:
+       - decomp-ui-xxx: <route/file> | action=<action> | expect=<result> | evidence=<artifact>
+       - decomp-api-xxx: <route/file> | action=<action> | expect=<result> | evidence=<artifact>
+       Tick each item as soon as that specific behavior is implemented and proven. Do NOT batch.
+       ```
      - **The test plan items from the work item's checklist** (all `test-*` prefixed items). Include them verbatim in the prompt and instruct the agent:
        ```
        TEST PLAN — you MUST implement/verify each of these and tick them off via update_checklist_item:
@@ -263,6 +310,11 @@ Read the task title and description, then:
     - Runs `npx tsc --noEmit` for every touched app/package
     - Starts the dev server and probes every modified route (expects HTTP 200, not 500)
     - Runs vitest for every touched package
+    - **Verifies checklist decomposition quality per work item before functional validation:**
+      - Every implementation work item has at least one `decomp-*` item and one `test-*` item
+      - Every `decomp-*` item includes route/file, action, expected result, and evidence artifact
+      - Any unchecked `decomp-*` item with `required: true` = work item CANNOT be set to `done`
+      - Any coarse or non-falsifiable `decomp-*` item = reopen to `todo` with the specific failure
     - **Verifies test plan completion per work item:**
       - For each `test-assert-*` checklist item: confirm a corresponding vitest test exists and passes
       - For each `test-smoke-*` checklist item: run the command and confirm exit code / HTTP status

package/skills/handoff/SKILL.md

@@ -83,6 +83,27 @@ Template:
 Wave 1 (parallel): Package 1, Package 2
 Wave 2 (after Wave 1): Package 3
 
+## Checklist Decomposition Matrix
+
+| Work item | Atomic deliverable | Surface type | Route or file path | Preconditions / fixture data | Action | Expected result | Verification artifact | Owner package | Status |
+|-----------|-------------------|--------------|--------------------|------------------------------|--------|-----------------|-----------------------|---------------|--------|
+| WP-1 | decomp-<surface>-<slug> | screen | /route | seeded fixture | open / click / submit | observable result | Playwright screenshot / route probe / test name | Package 1 | todo |
+
+Rules:
+- One observable behavior per row.
+- Each row must be independently pass/fail.
+- Each implementation work item must have matching `decomp-*` checklist rows and `test-*` verification rows.
+- UI routes list state rows separately: empty, loading, loaded, error, create/edit/detail/mobile where applicable.
+- API and DB rows include success, failure/guard, and side-effect proof where applicable.
+
+## Checklist Quality Gate
+
+verdict: PASS | FAIL
+failures:
+- <missing/coarse row if any>
+deferred:
+- <explicitly out-of-scope row if any>
+
 ## Definition of Done
 
 - [ ] [specific acceptance criterion]
@@ -114,6 +135,9 @@ Where: <files>
 Agent type: <type>
 Guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
 Design doc: .rdc/plans/<topic-slug>.md (fallback: .rdc/plans/<topic-slug>.md)
+Checklist: include required rows from the plan matrix:
+- decomp-<surface>-<slug>: route/file=<path> | action=<action> | expect=<result> | evidence=<artifact>
+- test-<type>-<slug>: <verification command or artifact>
 Depends on: <other task if applicable>
 Est: <hours>',
   p_parent_id   := '<epic-uuid>'::uuid,
@@ -125,6 +149,8 @@ Est: <hours>',
 );
 ```
 
+Do not create build-ready tasks unless the plan has `## Checklist Decomposition Matrix` and `## Checklist Quality Gate` with `verdict: PASS`. If the matrix fails, save the plan as `Status: Needs checklist repair` and return the failure list instead of creating dispatchable implementation tasks.
+
 ### Step 4 — Register Prototype (if one was built)
 
 ```sql

package/skills/plan/SKILL.md

@@ -52,6 +52,66 @@ description: "No epic exists and you need architecture + task breakdown. Produce
    - Assign an agent type to each work package from the typed dispatch table in rdc:build. Include the guide file path (from `.rdc/guides/`, fallback `.rdc/guides/`) in each work package description.
    - Estimate: small (1 agent, <500 LOC), medium (1 agent, 500-1500 LOC), large (needs splitting)
 
+4b. **Build the checklist decomposition matrix (MANDATORY PRE-BUILD GATE):**
+
+   Before writing Supabase work items, create a `## Checklist Decomposition Matrix`
+   in the plan doc. This matrix is the source of truth for task checklists and
+   build verification.
+
+   Required columns:
+   - Work item ID or placeholder
+   - Atomic deliverable
+   - Surface type: `screen`, `state`, `action`, `api`, `db`, `migration`, `component`, `asset`, `tool`, `test`, `doc`
+   - Route or file path
+   - Preconditions / fixture data
+   - User or agent action
+   - Expected UI/API/DB result
+   - Verification artifact: test name, route probe, Playwright screenshot, SQL query, API response, type-check, migration proof, or CLI transcript
+   - Owner work package
+   - Status
+
+   Atomicity rubric:
+   - One observable behavior per row.
+   - Each row names a concrete route or file path.
+   - Each row names one concrete verification artifact.
+   - Each row can independently pass or fail.
+   - Each row is small enough for a worker to implement and tick without hidden intent.
+
+   Required decomposition by surface:
+   - UI screens: list empty, loading, loaded, error, create, edit, detail, delete/archive guard, mobile, and auth states where applicable.
+   - UI actions: open, search, filter, select, duplicate, save, assign, activate, archive, delete, import, apply, cancel where applicable.
+   - API routes: successful read/write, validation failure, unauthorized/forbidden, and side-effect verification where applicable.
+   - DB/migrations: table/column/index/policy/trigger/function, FK/guard, rollback or smoke query, and type exposure.
+   - CLI/sidebar/local tools: start, attach, enqueue, poll, reply, timeout/not-found, and live refresh where applicable.
+   - Visual work: each named screenshot and visual checkpoint gets its own row.
+   - Cross-system workflows: each handoff boundary gets its own row.
+
+   Minimum row-count heuristics:
+   - UI route: at least 4 rows.
+   - CRUD surface: at least 6 rows.
+   - API route: at least 3 rows.
+   - DB work package: at least 5 rows.
+   - Local editor/sidebar workflow: at least 5 rows.
+
+   Reject these checklist items as too coarse:
+   - "theme management works"
+   - "build all screens"
+   - "verify UI"
+   - "integration complete"
+   - "tests pass"
+
+   Replace them with rows like:
+   - `decomp-ui-theme-manager-loaded: /brands/[id]/theme shows owned theme rows with status, project usage, and actions; evidence: Playwright screenshot`
+   - `decomp-action-duplicate-theme: duplicate submits source brand_theme_id and creates a new editable brand-owned copy; evidence: vitest + DB query`
+   - `decomp-api-import-validation: POST /api/tools/theme-import rejects missing source URL with 400 JSON error; evidence: route probe`
+
+   Add a `## Checklist Quality Gate` section with:
+   - `verdict: PASS` only when every row passes the rubric.
+   - `failures:` list any coarse, missing, duplicate, or unverifiable rows.
+   - `deferred:` list any explicit out-of-scope rows.
+
+   Do not create build-ready work items unless this gate is `PASS`.
+
 5. **Write a test plan for each work package (MANDATORY):**
 
    Every work package MUST have a `test_plan` section with specific, concrete test items. Each item has a type:
@@ -65,6 +125,8 @@ description: "No epic exists and you need architecture + task breakdown. Produce
 
    **Rules for writing test plan items:**
    - Every item must be a specific, falsifiable assertion — not "write tests" or "verify it works"
+   - Every item must map to one or more rows in the Checklist Decomposition Matrix.
+   - A test plan item may summarize multiple checks only when the matrix still keeps those checks as separate atomic rows.
    - New functions/modules MUST have at least one `assert` item
    - API routes MUST have at least one `smoke` item
    - UI pages MUST have at least one `visual` item
@@ -91,6 +153,8 @@ description: "No epic exists and you need architecture + task breakdown. Produce
    ## Goal
    ## Design Decisions
    ## Work Packages (each with test plan)
+   ## Checklist Decomposition Matrix
+   ## Checklist Quality Gate
    ## Sequencing (what can parallelize, what depends on what)
    ## Risks & Mitigations
    ```
@@ -100,12 +164,16 @@ description: "No epic exists and you need architecture + task breakdown. Produce
    - Epic DoD MUST include: `{"id":"test-plan-verified","text":"All test plan items implemented and passing","required":true,"checked":false}`
    - Set `p_definition_of_done` on the epic — child tasks inserted under it will auto-inherit it as their checklist
    - One task per work package via `insert_work_item(p_parent_id := <epic_id>, ...)` — checklist auto-hydrated from epic's DoD
-   - **Additionally, write test plan items as checklist items** on each task, using id format `test-<type>-<slug>`:
+   - **Additionally, write decomposition rows as checklist items** on each task, using id format `decomp-<surface>-<slug>`.
+     The task checklist MUST include both the atomic `decomp-*` rows and the `test-*` verification rows.
+     The `decomp-*` row text must include the route/file, action, expected result, and evidence artifact.
+   - **Write test plan items as checklist items** on each task, using id format `test-<type>-<slug>`:
      ```sql
      SELECT insert_work_item(
        p_parent_id := '<epic_id>',
        p_title := 'WP-2: AST Scanner',
        p_checklist := '[
+         {"id":"decomp-api-scan-success","text":"api: GET /api/layout/scan?dir=apps/studio/src returns 200 JSON with roots[] and warnings[]; evidence: route probe output","required":true,"checked":false},
          {"id":"test-assert-scanner-filters","text":"assert: scanFile returns only container components","required":true,"checked":false},
          {"id":"test-assert-nesting-warn","text":"assert: invalid nesting produces warnings","required":true,"checked":false},
          {"id":"test-smoke-scan-api","text":"smoke: GET /api/layout/scan returns 200","required":true,"checked":false},
@@ -114,7 +182,7 @@ description: "No epic exists and you need architecture + task breakdown. Produce
        ]'::jsonb
      );
      ```
-   - Agents MUST tick each `test-*` checklist item as they implement/verify it (via `update_checklist_item`)
+   - Agents MUST tick each `decomp-*` and `test-*` checklist item as they implement/verify it (via `update_checklist_item`)
    - `update_work_item_status('done')` will REJECT if any `required: true` item is unchecked — this is the enforcement gate
    - Set priorities: urgent/high/normal based on sequencing
 

package/skills/review/SKILL.md

@@ -81,7 +81,8 @@ description: "Post-build quality gate: tsc, tests, stale docs, export conflicts
 
 9. **Verification gate — dispatch the verify agent:**
    After any fixes land, run the verify gate on every touched package. See `guides/agents/verify.md`.
-   **Iron Law: no CLEAN verdict without fresh evidence.** Quote the vitest + tsc output in the report.
+   **Iron Law: no CLEAN verdict without fresh evidence.** Quote the checklist decomposition verdict, vitest output, and tsc output in the report.
+   The verify agent must reject any work item that lacks passed `decomp-*` checklist rows or whose rows are too coarse to prove one observable behavior at a time.
    If verify fails → do NOT emit CLEAN. Loop back, fix, re-run verify.
 
 10. **Fix issues found:**

package/skills/terminal-config/SKILL.md

@@ -0,0 +1,217 @@
+---
+name: terminal-config
+description: "Read and safely modify Windows Terminal settings and cell startup sequencing. Contains the canonical file locations, profile GUIDs, keybinding map, and what NEVER to change."
+---
+
+> **⚠️ 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.
+
+# terminal-config — Windows Terminal & Cell Startup Reference
+
+## 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
+
+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).
+
+---
+
+## 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.cmd` | Launched by each cell profile. 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.
+
+| 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.cmd sv` |
+| `{190a2f39-f6ad-4638-8fef-e4c7aa58c349}` | Claude | `#B91C1C` (red) | Claude conversation cell, runs `cell-init.cmd sv` |
+| `{2d0248ef-7bb7-4b9e-b381-c4aa1f570f49}` | Codex | `#0F766E` (teal) | Codex AI cell — runs `powershell -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
+
+```
+SV / Claude:   cmd.exe /k "C:\Dev\regen-root\scripts\cell-init.cmd" sv
+Codex:         powershell.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"`.
+
+---
+
+## Keybinding Map
+
+### Critical: intentionally unbound keys (never restore these)
+
+```json
+{ "id": null, "keys": "shift+enter" }
+{ "id": null, "keys": "ctrl+enter" }
+{ "id": null, "keys": "enter" }
+```
+
+**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)
+
+```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
+```
+
+Font defaults (in `profiles.defaults`):
+```json
+"face": "Consolas"
+"size": 12
+"cellHeight": "1.2"
+"cellWidth": "0.6"
+"weight": "normal"
+```
+
+---
+
+## Cell Startup Sequencing
+
+`cell-init.cmd` is the 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_SCOPE` from a role table
+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. Opens VS Code for the project
+7. Launches: `claude --append-system-prompt "<PROMPT_SCOPE>"`
+
+### 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.cmd` — it's in the repo, so changes are tracked.
+- Adding a new role: add a new `if "%ROLE%"=="..."` block with all five vars
+- Changing scope: update `PATHS` and `PROMPT_SCOPE` only — don't touch banner/lockfile/git logic
+
+---
+
+## Validation Commands
+
+```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 `cmd.exe /k cell-init.cmd <role>`
+- Download: https://wezfurlong.org/wezterm/installation.html
+
+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.