@lifeaitools/rdc-skills 0.25.1 → 0.25.2

package/skills/self-test/SKILL.md

@@ -1,100 +1,100 @@
----
-name: rdc:self-test
-description: "Usage `rdc:self-test [--strict]` — Validate all rdc:* skills, plugin manifest, and tooling consistency. Use after editing skills, upgrading the plugin, or when a skill behaves unexpectedly."
----
-
-> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No tool-call narration. No raw runner dumps — summarize.
-> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
-
-> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Tier 2 behavioral runs and any git push are skipped under `RDC_TEST=1`; Tier 1 static lint runs normally.
-
-
-# rdc:self-test — Skill Library Self-Test (Tier 1)
-
-## When to Use
-- Before every `rdc:release rdc-skills` tag push
-- After editing any skill description or frontmatter
-- When a skill mysteriously disappears from the menu (backtick bug repro)
-- In CI on every rdc-skills PR (once wired)
-
-## Tiers
-
-| Tier | What it checks | Status |
-|------|----------------|--------|
-| Tier 1 | Static lint — frontmatter, Usage line, referenced files, name match | ✅ live |
+---
+name: rdc:self-test
+description: "Usage `rdc:self-test [--strict]` — Validate all rdc:* skills, plugin manifest, and tooling consistency. Use after editing skills, upgrading the plugin, or when a skill behaves unexpectedly."
+---
+
+> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
+> Checklist-only output. No tool-call narration. No raw runner dumps — summarize.
+> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
+
+> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Tier 2 behavioral runs and any git push are skipped under `RDC_TEST=1`; Tier 1 static lint runs normally.
+
+
+# rdc:self-test — Skill Library Self-Test (Tier 1)
+
+## When to Use
+- Before every `rdc:release rdc-skills` tag push
+- After editing any skill description or frontmatter
+- When a skill mysteriously disappears from the menu (backtick bug repro)
+- In CI on every rdc-skills PR (once wired)
+
+## Tiers
+
+| Tier | What it checks | Status |
+|------|----------------|--------|
+| Tier 1 | Static lint — frontmatter, Usage line, referenced files, name match | ✅ live |
 | Tier 2 | Behavioral — headless Claude or Codex runs each skill in sandbox, asserts artifacts | ✅ live — 30 manifests; acceptance harness records transcripts, tool calls, artifacts, and lessons learned |
-| Tier 3 | Golden checklists — snapshot output format, regress on drift | 🔒 future |
-
-## Interactive UI
-
-Launch the interactive menu — pick tier, pick skill, see live output:
-
-```bash
+| Tier 3 | Golden checklists — snapshot output format, regress on drift | 🔒 future |
+
+## Interactive UI
+
+Launch the interactive menu — pick tier, pick skill, see live output:
+
+```bash
 node {RDC_SKILLS_ROOT}/scripts/self-test-ui.mjs
-```
-
-Menu options:
-- **1** — Full Tier 1 test (all skills)
-- **2** — Pick a specific skill from a numbered list
-- **3** — Choose tier (Tier 1 static lint | Tier 2 behavioral | Tier 3 🔒 future)
-
-Test output streams live to the terminal. No server, no extra processes.
-
-## Procedure (Tier 1)
-
-1. **Run the linter (direct or via UI):**
-   ```bash
+```
+
+Menu options:
+- **1** — Full Tier 1 test (all skills)
+- **2** — Pick a specific skill from a numbered list
+- **3** — Choose tier (Tier 1 static lint | Tier 2 behavioral | Tier 3 🔒 future)
+
+Test output streams live to the terminal. No server, no extra processes.
+
+## Procedure (Tier 1)
+
+1. **Run the linter (direct or via UI):**
+   ```bash
    node {RDC_SKILLS_ROOT}/scripts/self-test.mjs
-   # or interactively:
+   # or interactively:
    node {RDC_SKILLS_ROOT}/scripts/self-test-ui.mjs
-   ```
-
-2. **Interpret exit codes:**
-   - `0` = all skills pass
-   - `1` = at least one FAIL or (in `--strict` mode) at least one WARN
-   - `2` = runner itself crashed (e.g., skills dir unreadable)
-   - `3` = `.claude-plugin/plugin.json` missing entirely (distinct from skill failures)
-
-3. **Common findings and fixes:**
-
-   | Finding code | Cause | Fix |
-   |---|---|---|
-   | `description-backtick-leading` | Folded YAML starts with `` ` `` — parser drops skill | Rewrite description to start with a word |
-   | `usage-marker-missing` | No `` Usage `rdc:name <args>` `` in description | Front-load arg contract |
-   | `usage-marker-mismatch` | `Usage` line references a different skill's name (copy-paste drift) | Fix the skill name in the Usage marker |
-   | `name-filename-mismatch` | frontmatter `name:` ≠ filename | `--fix` auto-renames; or rewrite name |
-   | `guide-not-found` / `rule-not-found` / `hook-not-found` | Dead reference in skill body | Create file or fix link |
-   | `banner-missing` | Skill missing OUTPUT CONTRACT banner | `--fix` auto-inserts |
-   | `manifest-missing` / `manifest-version-mismatch` | `.claude-plugin/plugin.json` missing or out-of-sync with `package.json` | Create/update manifest |
-   | `duplicate-skill-name` / `skill-guide-filename-collision` | Two skills claim same name, or skill collides with agent guide | Rename one |
-   | `orphan-hook` | File under `hooks/` isn't referenced by any skill, settings.json, or plugin.json | Wire it up or delete |
-
-4. **Flags:**
-   - `--strict` — promotes warnings to failures (use in CI and before release)
-   - `--skill <name>` — run against a single skill (e.g. `--skill rdc:build`)
-   - `--json` — machine-readable schema v2 (per-skill `findings[]` with `code` + `level`, plugin_manifest block, global_findings, summary.exit_code). Consumed by Tier 2 runner as pre-gate.
-   - `--fix` — auto-repair fixable findings: insert missing OUTPUT CONTRACT banner, rename files to match frontmatter name. Prints `FIXED:` lines + touched file list so you can git diff + commit. Backtick-leading descriptions are NOT auto-fixed (need human rewrite).
-
-5. **Report to the project lead:**
-   ```
-   Self-test: X/Y pass, Z warnings, W failures
-   Failures: <list>
-   Verdict: PASS | FAIL
-   ```
-
-## Procedure (Tier 2)
-
+   ```
+
+2. **Interpret exit codes:**
+   - `0` = all skills pass
+   - `1` = at least one FAIL or (in `--strict` mode) at least one WARN
+   - `2` = runner itself crashed (e.g., skills dir unreadable)
+   - `3` = `.claude-plugin/plugin.json` missing entirely (distinct from skill failures)
+
+3. **Common findings and fixes:**
+
+   | Finding code | Cause | Fix |
+   |---|---|---|
+   | `description-backtick-leading` | Folded YAML starts with `` ` `` — parser drops skill | Rewrite description to start with a word |
+   | `usage-marker-missing` | No `` Usage `rdc:name <args>` `` in description | Front-load arg contract |
+   | `usage-marker-mismatch` | `Usage` line references a different skill's name (copy-paste drift) | Fix the skill name in the Usage marker |
+   | `name-filename-mismatch` | frontmatter `name:` ≠ filename | `--fix` auto-renames; or rewrite name |
+   | `guide-not-found` / `rule-not-found` / `hook-not-found` | Dead reference in skill body | Create file or fix link |
+   | `banner-missing` | Skill missing OUTPUT CONTRACT banner | `--fix` auto-inserts |
+   | `manifest-missing` / `manifest-version-mismatch` | `.claude-plugin/plugin.json` missing or out-of-sync with `package.json` | Create/update manifest |
+   | `duplicate-skill-name` / `skill-guide-filename-collision` | Two skills claim same name, or skill collides with agent guide | Rename one |
+   | `orphan-hook` | File under `hooks/` isn't referenced by any skill, settings.json, or plugin.json | Wire it up or delete |
+
+4. **Flags:**
+   - `--strict` — promotes warnings to failures (use in CI and before release)
+   - `--skill <name>` — run against a single skill (e.g. `--skill rdc:build`)
+   - `--json` — machine-readable schema v2 (per-skill `findings[]` with `code` + `level`, plugin_manifest block, global_findings, summary.exit_code). Consumed by Tier 2 runner as pre-gate.
+   - `--fix` — auto-repair fixable findings: insert missing OUTPUT CONTRACT banner, rename files to match frontmatter name. Prints `FIXED:` lines + touched file list so you can git diff + commit. Backtick-leading descriptions are NOT auto-fixed (need human rewrite).
+
+5. **Report to the project lead:**
+   ```
+   Self-test: X/Y pass, Z warnings, W failures
+   Failures: <list>
+   Verdict: PASS | FAIL
+   ```
+
+## Procedure (Tier 2)
+
 Tier 2 runs each skill end-to-end in an isolated sandbox and asserts on observed state (files touched, commits made, work items, exit code). Build acceptance additionally records all observable engine events/tool calls, assistant output, stdout/stderr artifacts, lessons learned, and next build optimizations. It supports `--engine claude` and `--engine codex`; both engines use the same manifests, worktree sandbox, JSONL evidence, and Markdown report. Use it before shipping behavioral changes — Tier 1 alone can't catch runtime drift.
-
-1. **Prerequisites:**
+
+1. **Prerequisites:**
    - `claude` CLI on PATH for Claude runs (headless mode: `claude --print`)
    - `codex` CLI on PATH for Codex runs (headless mode: `codex exec --json`)
-   - clauth daemon unlocked (`curl -s http://127.0.0.1:52437/ping`)
-   - Supabase MCP reachable (runner creates a throwaway test branch)
-   - Clean git tree in `rdc-skills` (worktrees are added under `.rdc/sandbox/<run-id>/`)
-
-2. **Run:**
+   - clauth daemon unlocked (`curl -s http://127.0.0.1:52437/ping`)
+   - Supabase MCP reachable (runner creates a throwaway test branch)
+   - Clean git tree in `rdc-skills` (worktrees are added under `.rdc/sandbox/<run-id>/`)
+
+2. **Run:**
    ```bash
    node scripts/self-test.mjs --tier2                    # all skills with manifests
    node scripts/self-test.mjs --tier2 --skill rdc:build  # single skill
@@ -103,30 +103,30 @@ Tier 2 runs each skill end-to-end in an isolated sandbox and asserts on observed
    node scripts/acceptance.mjs --skill rdc:build         # build acceptance with JSONL/tool-call evidence
    node scripts/acceptance.mjs --engine codex --skill rdc:build
    ```
-
-3. **What it does:**
-   - Runs Tier 1 as a pre-gate (fails fast if static lint fails)
-   - Creates one Supabase test branch for the run
+
+3. **What it does:**
+   - Runs Tier 1 as a pre-gate (fails fast if static lint fails)
+   - Creates one Supabase test branch for the run
    - For each skill: `git worktree add` into `.rdc/sandbox/<run-id>/<skill>/`, sets `RDC_TEST=1`, invokes the selected headless engine with the skill prompt, waits for exit
    - Asserts per the skill's manifest: exit code, files touched, commits made, stdout patterns
    - Build acceptance writes JSONL evidence and extracts tool calls from the engine stream
    - Cleans up worktrees + deletes the Supabase branch at the end (even on failure)
-
-4. **Reports:**
+
+4. **Reports:**
    - `.rdc/reports/self-test-tier2-<iso>.json` — full per-skill result, findings, timings
    - `.rdc/reports/acceptance-*.jsonl` and `.rdc/reports/acceptance-*.md` — build acceptance evidence, transcript artifact pointers, lessons learned, and next build optimizations
    - Exit codes: `0` pass, `1` fail (one or more skills failed assertions), `2` runner error (couldn't set up sandbox / branch)
-
-5. **Adding a new manifest:**
-   - Create `skills/tests/<skill>.test.json` (one per skill, colocated)
-   - Validate the shape against the schema at `scripts/lib/manifest-schema.mjs`
-   - Test it in isolation: `node scripts/self-test.mjs --tier2 --skill rdc:name`
-   - Commit the manifest alongside any skill body changes
-
-## Rules
-- Run Tier 1 **before every `rdc:release rdc-skills`** — it catches the backtick-drift class of bugs that break the skill menu silently.
-- Use `--strict` in CI. Warnings matter in the release path.
-- Do NOT skip findings by relaxing the linter. Fix the skill.
-- Run Tier 2 before tagging a release. Gate the tag if any manifested skill fails.
+
+5. **Adding a new manifest:**
+   - Create `skills/tests/<skill>.test.json` (one per skill, colocated)
+   - Validate the shape against the schema at `scripts/lib/manifest-schema.mjs`
+   - Test it in isolation: `node scripts/self-test.mjs --tier2 --skill rdc:name`
+   - Commit the manifest alongside any skill body changes
+
+## Rules
+- Run Tier 1 **before every `rdc:release rdc-skills`** — it catches the backtick-drift class of bugs that break the skill menu silently.
+- Use `--strict` in CI. Warnings matter in the release path.
+- Do NOT skip findings by relaxing the linter. Fix the skill.
+- Run Tier 2 before tagging a release. Gate the tag if any manifested skill fails.
 - Headless sessions must not steal focus. The runner uses hidden process launch options where supported; if windows flash or focus is grabbed, inspect `scripts/lib/runner.mjs` before changing skill behavior.
 - If Tier 2 tests fail with `exit_code: -1`, verify the runner still passes `--dangerously-skip-permissions` and sets `RDC_TEST=1`.

package/skills/status/SKILL.md

@@ -1,99 +1,99 @@
----
-name: rdc:status
-description: "Usage `rdc:status` — Read-only snapshot of open epics, work items, Coolify health, blockers, and next recommended action. Safe to call anytime. Start here when disoriented or resuming a session."
----
-
-> **⚠️ 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.
-
-> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
-
-
-# rdc:status — Project Dashboard
-
-## When to Use
-- Start of any session
-- Project lead asks "what's the status", "where are we", "what's open"
-- Before deciding what to work on next
-
-## Procedure
-
-1. **Open epics:**
-   ```sql
-   SELECT get_open_epics();
-   ```
-
-2. **Work item counts by status:**
-   ```sql
-   SELECT status, count(*) FROM work_items 
-   WHERE status != 'archived' 
-   GROUP BY status ORDER BY status;
-   ```
-
-3. **Items by label/project (top 10 labels):**
-   ```sql
-   SELECT unnest(labels) as label, count(*), 
-          count(*) FILTER (WHERE status = 'done') as done,
-          count(*) FILTER (WHERE status = 'todo') as todo,
-          count(*) FILTER (WHERE status = 'in_progress') as wip
-   FROM work_items 
-   GROUP BY label ORDER BY count DESC LIMIT 10;
-   ```
-
-4. **Recent activity (last 48 hours):**
-   ```sql
-   SELECT title, status, updated_at 
-   FROM work_items 
-   WHERE updated_at > now() - interval '48 hours'
-   ORDER BY updated_at DESC LIMIT 15;
-   ```
-
-5. **Git status:**
-   ```bash
-   git log --oneline -10
-   git status
-   git branch -v
-   ```
-
-6. **Dev server health (PM2):**
-   SSH into the Coolify server and check PM2 process state:
-   ```bash
-   # Note: clauth key name for the SSH key may vary by project. Common names: ssh-key-path, vultr-ssh-key, dev-ssh-key.
-   # Check available keys with: curl -s http://127.0.0.1:52437/list-services
-   SSH_KEY=$(curl -s http://127.0.0.1:52437/v/ssh-key-path)
-   ssh -i "$SSH_KEY" -o StrictHostKeyChecking=no root@64.237.54.189 "pm2 jlist 2>/dev/null"
-   ```
-   Parse the JSON array — for each process note `name`, `pm2_env.status` (online/stopped/errored), and `pm2_env.pm_uptime`.
-   If SSH fails or PM2 returns nothing, note "PM2 unreachable" and continue.
-
-7. **Infrastructure health** (if MCP available):
-   - Get infrastructure overview or diagnose issues
-   - Report any apps with failed builds or down containers
-
-8. **Present as a compact dashboard:**
-   ```
-   ## Open Epics (N)
-   <table>
-   
-   ## Work Items: X done | Y todo | Z in_progress
-   
-   ## Recent (48h)
-   <list>
-   
-   ## Dev Servers (PM2)
-   online: studio canvas lifeai ...   stopped: issho-invest
-   
-   ## Deployments
-   <green/red/yellow status>
-   
-   ## Recommended Next
-   <highest priority unstarted epic>
-   ```
-
-## Rules
-- Keep output concise — this is a glance, not a deep dive
-- Always end with a recommendation for what to work on next
-- After the Recommended Next section, suggest which guide file from `.rdc/guides/` (fallback: `.rdc/guides/`) the recommended work would need
-- Use database MCP for queries (not raw curl)
-- If infrastructure MCP is unavailable, skip deployment status and note it
+---
+name: rdc:status
+description: "Usage `rdc:status` — Read-only snapshot of open epics, work items, Coolify health, blockers, and next recommended action. Safe to call anytime. Start here when disoriented or resuming a session."
+---
+
+> **⚠️ 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.
+
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
+
+
+# rdc:status — Project Dashboard
+
+## When to Use
+- Start of any session
+- Project lead asks "what's the status", "where are we", "what's open"
+- Before deciding what to work on next
+
+## Procedure
+
+1. **Open epics:**
+   ```sql
+   SELECT get_open_epics();
+   ```
+
+2. **Work item counts by status:**
+   ```sql
+   SELECT status, count(*) FROM work_items 
+   WHERE status != 'archived' 
+   GROUP BY status ORDER BY status;
+   ```
+
+3. **Items by label/project (top 10 labels):**
+   ```sql
+   SELECT unnest(labels) as label, count(*), 
+          count(*) FILTER (WHERE status = 'done') as done,
+          count(*) FILTER (WHERE status = 'todo') as todo,
+          count(*) FILTER (WHERE status = 'in_progress') as wip
+   FROM work_items 
+   GROUP BY label ORDER BY count DESC LIMIT 10;
+   ```
+
+4. **Recent activity (last 48 hours):**
+   ```sql
+   SELECT title, status, updated_at 
+   FROM work_items 
+   WHERE updated_at > now() - interval '48 hours'
+   ORDER BY updated_at DESC LIMIT 15;
+   ```
+
+5. **Git status:**
+   ```bash
+   git log --oneline -10
+   git status
+   git branch -v
+   ```
+
+6. **Dev server health (PM2):**
+   SSH into the Coolify server and check PM2 process state:
+   ```bash
+   # Note: clauth key name for the SSH key may vary by project. Common names: ssh-key-path, vultr-ssh-key, dev-ssh-key.
+   # Check available keys with: curl -s http://127.0.0.1:52437/list-services
+   SSH_KEY=$(curl -s http://127.0.0.1:52437/v/ssh-key-path)
+   ssh -i "$SSH_KEY" -o StrictHostKeyChecking=no root@64.237.54.189 "pm2 jlist 2>/dev/null"
+   ```
+   Parse the JSON array — for each process note `name`, `pm2_env.status` (online/stopped/errored), and `pm2_env.pm_uptime`.
+   If SSH fails or PM2 returns nothing, note "PM2 unreachable" and continue.
+
+7. **Infrastructure health** (if MCP available):
+   - Get infrastructure overview or diagnose issues
+   - Report any apps with failed builds or down containers
+
+8. **Present as a compact dashboard:**
+   ```
+   ## Open Epics (N)
+   <table>
+   
+   ## Work Items: X done | Y todo | Z in_progress
+   
+   ## Recent (48h)
+   <list>
+   
+   ## Dev Servers (PM2)
+   online: studio canvas lifeai ...   stopped: issho-invest
+   
+   ## Deployments
+   <green/red/yellow status>
+   
+   ## Recommended Next
+   <highest priority unstarted epic>
+   ```
+
+## Rules
+- Keep output concise — this is a glance, not a deep dive
+- Always end with a recommendation for what to work on next
+- After the Recommended Next section, suggest which guide file from `.rdc/guides/` (fallback: `.rdc/guides/`) the recommended work would need
+- Use database MCP for queries (not raw curl)
+- If infrastructure MCP is unavailable, skip deployment status and note it

package/skills/tests/MATRIX.md

@@ -1,55 +1,55 @@
-# RDC Skill Test Suite Matrix
-
-Current coverage: 31 manifests for 31 skill directories.
-
-The manifest layer verifies each skill can be started from a realistic caller prompt in an isolated `RDC_TEST=1` sandbox. The acceptance harness can run either Claude (`--engine claude`) or Codex (`--engine codex`) against the same manifests and records the engine stream, extracted tool calls, stdout/stderr artifacts, rendered assistant output, failures, lessons learned, and next build optimizations under `.rdc/reports/`.
-
-`rdc:channel-formatter` currently has the strongest content acceptance fixture: it asserts source-grounded social-pack output, forbidden-claim absence, and observable corpus or web-search tool routing. `rdc:help` asserts the public MCP/curl caller surface and structured `format:"json"` discovery path. `rdc:self-test` validates the test-tier/evidence language. Planning/reporting skills (`rdc:preplan`, `rdc:plan`, `rdc:handoff`, `rdc:prototype`, `rdc:review`, `rdc:report`) assert their required artifacts and safety boundaries. Operational/content skills (`rdc:brochure`, `rdc:convert`, `lifeai-brochure-author`, `rdc:build`, `rdc:fixit`, `rdc:fs-mcp`, `rdc:workitems`) assert artifact paths, dispatch gates, scoped commits, filesystem boundaries, and sandboxed work-item behavior. Coordination/design/maintenance skills (`rdc:co-develop`, `rdc:collab`, `rdc:design`, `rdc:extract-verifier-rules`, `rdc:housekeeping`, `rdc:overnight`, `rdc:rpms-filemap`) assert relay safety, token/reference use, verifier corpus safety, maintenance/reporting, unattended sentinel behavior, and canonical file-map rules. All manifests now include a deeper acceptance block beyond the basic executable smoke fixture.
-
-| Skill | Manifest | Fixture prompt class | Assertions | Acceptance depth |
-|---|---|---|---|---|
-| `rdc:brochure` | `rdc-brochure.test.json` | HTML-to-PDF brochure fixture | `exit_code`, `stdout_contains` | PDF artifact, page/size/source output, and no upload/deploy/source-modification checks |
-| `rdc:build` | `rdc-build.test.json` | Unattended build from sandbox label | `commits_made`, `exit_code`, `stdout_contains` | Dispatch guide, code-review, validator, sandbox, and no-push/no-skip checks |
-| `rdc:channel-formatter` | `rdc-channel-formatter.test.json` | Long article to social content pack | `exit_code`, `stdout_contains` | Output contains, output not contains, tool-call routing |
-| `rdc:co-develop` | `rdc-co-develop.test.json` | Coordination status | `commits_made`, `exit_code`, `stdout_contains` | codevelop status, sandbox skip, no chitchat/live-send negative checks |
-| `rdc:collab` | `rdc-collab.test.json` | Claude session relay fixture | `commits_made`, `exit_code`, `stdout_contains` | chitchat/SSE session handling, sandbox skip, and no-reply/no-push negative checks |
-| `rdc:convert` | `rdc-convert.test.json` | Markdown-to-Word conversion fixture | `exit_code`, `stdout_contains` | build-corpus command surface, Word/Markdown flags, and no-GUI/global-install/commit checks |
-| `rdc:deploy` | `rdc-deploy.test.json` | Deployment diagnosis | `commits_made`, `exit_code`, `stdout_contains` | Read-only diagnose output and destructive deploy/DNS negative checks |
-| `rdc:edit` | `rdc-edit.test.json` | Local editor launch | `exit_code`, `stdout_contains` | Resolved target, editor host URL, and no-unknown-target negative checks |
-| `rdc:design` | `rdc-design.test.json` | Studio palette audit | `exit_code`, `stdout_contains` | Studio/token/Rampa references and external-write negative checks |
-| `rdc:fixit` | `rdc-fixit.test.json` | Tiny sandbox typo fix | `commits_made`, `exit_code`, `stdout_contains` | Scope, code-review, specific-file staging, and broad-add negative checks |
-| `rdc:fs-mcp` | `rdc-fs-mcp.test.json` | File-system bridge read fixture | `commits_made`, `exit_code`, `stdout_contains` | Local-vs-MCP access boundary, live FS, no-preview/no-overwrite checks, and read-tool routing |
-| `rdc:handoff` | `rdc-handoff.test.json` | Stub work handoff | `exit_code`, `stdout_contains` | Plan path, DoD, work-item handoff, and placeholder negative checks |
-| `rdc:help` | `rdc-help.test.json` | Help menu rendering | `commits_made`, `exit_code`, `stdout_contains` | MCP/curl output, structured JSON fetch, dev-endpoint negative checks |
-| `rdc:housekeeping` | `rdc-housekeeping.test.json` | Read-only housekeeping audit | `commits_made`, `exit_code`, `stdout_contains` | PUBLISH/CLAUDE/orphan/report checks and no-fix/no-Coolify-write negative checks |
-| `lifeai-brochure-author` | `rdc-lifeai-brochure-author.test.json` | JSX compliance review fixture | `exit_code`, `stdout_contains` | brochure-kit component guidance and raw HTML/style/token negative checks |
-| `rdc:overnight` | `rdc-overnight.test.json` | Label-based overnight queue drain | `exit_code`, `stdout_contains` | overnight sentinel, clauth preflight, full chain, and no-wide-add/no-lock-left negative checks |
-| `rdc:plan` | `rdc-plan.test.json` | Health-endpoint planning prompt | `exit_code`, `stdout_contains` | Design-decision, decomposition-matrix, work-package, and coarse-check negative checks |
-| `rdc:preplan` | `rdc-preplan.test.json` | Rate-limiter research prompt | `commits_made`, `exit_code`, `stdout_contains` | Research artifact, comparison, unknowns, recommendation, and research-tool routing checks |
-| `rdc:prototype` | `rdc-prototype.test.json` | Tiny component prototype prompt | `exit_code`, `stdout_contains` | Local TSX prototype artifact, registry, test-mode, and production-write negative checks |
-| `rdc:brochurify` | `rdc-rdc-brochurify.test.json` | Read-only markdown Brochurify fixture | `exit_code`, `stdout_contains` | Sandbox output and no-follow-up negative checks |
-| `rdc:extract-verifier-rules` | `rdc-rdc-extract-verifier-rules.test.json` | Enhancement-log verifier fixture | `exit_code`, `stdout_contains` | Candidate, false-positive, known-good, recall, and no-auto-merge/PR negative checks |
-| `rdc:release` | `rdc-release.test.json` | Dry-run package release | `commits_made`, `exit_code`, `stdout_contains` | Dry-run release checklist and force/bypass negative checks |
-| `rdc:regen-media` | `rdc-regen-media.test.json` | Image generation path selection | `commits_made`, `exit_code`, `stdout_contains` | Local keyless Codex gpt-image-2 default, test-mode no-generation, and server-side fallback negative checks |
-| `rdc:report` | `rdc-report.test.json` | Unattended report generation | `exit_code`, `stdout_contains` | Report status block, counts, next recommendation, and dump/push negative checks |
-| `rdc:review` | `rdc-review.test.json` | Unattended review gate | `exit_code`, `stdout_contains` | Code-review, verify, fresh-evidence, tsc, and forbidden-build negative checks |
-| `rdc:rpms-filemap` | `rdc-rpms-filemap.test.json` | Canonical location lookup | `commits_made`, `exit_code`, `stdout_contains` | Rule #1, context door, one-home rules, and no-hand-edit/second-home negative checks |
-| `rdc:self-test` | `rdc-self-test.test.json` | Strict self-test prompt | `commits_made`, `exit_code`, `stdout_contains` | Strict validation evidence, hook/guide checks, and no-relaxed-linter negative check |
-| `rdc:status` | `rdc-status.test.json` | Read-only status snapshot | `commits_made`, `exit_code`, `stdout_contains` | Read-only status output and raw-MCP/write negative checks |
-| `rdc:terminal-config` | `rdc-terminal-config.test.json` | Hidden-window launch policy audit | `commits_made`, `exit_code`, `stdout_contains` | Hidden-window output and focus/collapse API negative checks |
-| `rdc:watch` | `rdc-watch.test.json` | Watcher initialization prompt | `exit_code`, `stdout_contains` | Test-mode no-open output, tool-call routing, and focus-event negative checks |
-| `rdc:workitems` | `rdc-workitems.test.json` | Work-item epic listing | `commits_made`, `exit_code`, `stdout_contains` | Read-only epics query, sandbox, and work-item write negative checks |
-
-## What The Tests Accomplish
-
-- Verify every installed RDC skill has at least one executable caller-facing prompt.
-- Exercise the `RDC_TEST=1` sandbox contract so build tests do not publish, deploy, or mutate production services.
-- Capture observed engine events and extracted tool calls for periodic inspection.
-- Preserve stdout, stderr, and rendered assistant output as report artifacts.
-- Make content-producing skills eligible for deeper source-fidelity checks through the optional `acceptance` block.
-
-## Next Coverage Upgrades
-
-- Run full scheduled Claude and Codex sweeps regularly, not only changed-skill acceptance, so transcripts and lessons stay fresh.
-- Add richer artifact-content checks for output-producing skills (`rdc:brochure`, `rdc:convert`, `rdc:prototype`, `rdc:report`).
-- Promote recurring transcript review findings into manifest assertions instead of relying on human inspection.
+# RDC Skill Test Suite Matrix
+
+Current coverage: 31 manifests for 31 skill directories.
+
+The manifest layer verifies each skill can be started from a realistic caller prompt in an isolated `RDC_TEST=1` sandbox. The acceptance harness can run either Claude (`--engine claude`) or Codex (`--engine codex`) against the same manifests and records the engine stream, extracted tool calls, stdout/stderr artifacts, rendered assistant output, failures, lessons learned, and next build optimizations under `.rdc/reports/`.
+
+`rdc:channel-formatter` currently has the strongest content acceptance fixture: it asserts source-grounded social-pack output, forbidden-claim absence, and observable corpus or web-search tool routing. `rdc:help` asserts the public MCP/curl caller surface and structured `format:"json"` discovery path. `rdc:self-test` validates the test-tier/evidence language. Planning/reporting skills (`rdc:preplan`, `rdc:plan`, `rdc:handoff`, `rdc:prototype`, `rdc:review`, `rdc:report`) assert their required artifacts and safety boundaries. Operational/content skills (`rdc:brochure`, `rdc:convert`, `lifeai-brochure-author`, `rdc:build`, `rdc:fixit`, `rdc:fs-mcp`, `rdc:workitems`) assert artifact paths, dispatch gates, scoped commits, filesystem boundaries, and sandboxed work-item behavior. Coordination/design/maintenance skills (`rdc:co-develop`, `rdc:collab`, `rdc:design`, `rdc:extract-verifier-rules`, `rdc:housekeeping`, `rdc:overnight`, `rdc:rpms-filemap`) assert relay safety, token/reference use, verifier corpus safety, maintenance/reporting, unattended sentinel behavior, and canonical file-map rules. All manifests now include a deeper acceptance block beyond the basic executable smoke fixture.
+
+| Skill | Manifest | Fixture prompt class | Assertions | Acceptance depth |
+|---|---|---|---|---|
+| `rdc:brochure` | `rdc-brochure.test.json` | HTML-to-PDF brochure fixture | `exit_code`, `stdout_contains` | PDF artifact, page/size/source output, and no upload/deploy/source-modification checks |
+| `rdc:build` | `rdc-build.test.json` | Unattended build from sandbox label | `commits_made`, `exit_code`, `stdout_contains` | Dispatch guide, code-review, validator, sandbox, and no-push/no-skip checks |
+| `rdc:channel-formatter` | `rdc-channel-formatter.test.json` | Long article to social content pack | `exit_code`, `stdout_contains` | Output contains, output not contains, tool-call routing |
+| `rdc:co-develop` | `rdc-co-develop.test.json` | Coordination status | `commits_made`, `exit_code`, `stdout_contains` | codevelop status, sandbox skip, no chitchat/live-send negative checks |
+| `rdc:collab` | `rdc-collab.test.json` | Claude session relay fixture | `commits_made`, `exit_code`, `stdout_contains` | chitchat/SSE session handling, sandbox skip, and no-reply/no-push negative checks |
+| `rdc:convert` | `rdc-convert.test.json` | Markdown-to-Word conversion fixture | `exit_code`, `stdout_contains` | build-corpus command surface, Word/Markdown flags, and no-GUI/global-install/commit checks |
+| `rdc:deploy` | `rdc-deploy.test.json` | Deployment diagnosis | `commits_made`, `exit_code`, `stdout_contains` | Read-only diagnose output and destructive deploy/DNS negative checks |
+| `rdc:edit` | `rdc-edit.test.json` | Local editor launch | `exit_code`, `stdout_contains` | Resolved target, editor host URL, and no-unknown-target negative checks |
+| `rdc:design` | `rdc-design.test.json` | Studio palette audit | `exit_code`, `stdout_contains` | Studio/token/Rampa references and external-write negative checks |
+| `rdc:fixit` | `rdc-fixit.test.json` | Tiny sandbox typo fix | `commits_made`, `exit_code`, `stdout_contains` | Scope, code-review, specific-file staging, and broad-add negative checks |
+| `rdc:fs-mcp` | `rdc-fs-mcp.test.json` | File-system bridge read fixture | `commits_made`, `exit_code`, `stdout_contains` | Local-vs-MCP access boundary, live FS, no-preview/no-overwrite checks, and read-tool routing |
+| `rdc:handoff` | `rdc-handoff.test.json` | Stub work handoff | `exit_code`, `stdout_contains` | Plan path, DoD, work-item handoff, and placeholder negative checks |
+| `rdc:help` | `rdc-help.test.json` | Help menu rendering | `commits_made`, `exit_code`, `stdout_contains` | MCP/curl output, structured JSON fetch, dev-endpoint negative checks |
+| `rdc:housekeeping` | `rdc-housekeeping.test.json` | Read-only housekeeping audit | `commits_made`, `exit_code`, `stdout_contains` | PUBLISH/CLAUDE/orphan/report checks and no-fix/no-Coolify-write negative checks |
+| `lifeai-brochure-author` | `rdc-lifeai-brochure-author.test.json` | JSX compliance review fixture | `exit_code`, `stdout_contains` | brochure-kit component guidance and raw HTML/style/token negative checks |
+| `rdc:overnight` | `rdc-overnight.test.json` | Label-based overnight queue drain | `exit_code`, `stdout_contains` | overnight sentinel, clauth preflight, full chain, and no-wide-add/no-lock-left negative checks |
+| `rdc:plan` | `rdc-plan.test.json` | Health-endpoint planning prompt | `exit_code`, `stdout_contains` | Design-decision, decomposition-matrix, work-package, and coarse-check negative checks |
+| `rdc:preplan` | `rdc-preplan.test.json` | Rate-limiter research prompt | `commits_made`, `exit_code`, `stdout_contains` | Research artifact, comparison, unknowns, recommendation, and research-tool routing checks |
+| `rdc:prototype` | `rdc-prototype.test.json` | Tiny component prototype prompt | `exit_code`, `stdout_contains` | Local TSX prototype artifact, registry, test-mode, and production-write negative checks |
+| `rdc:brochurify` | `rdc-rdc-brochurify.test.json` | Read-only markdown Brochurify fixture | `exit_code`, `stdout_contains` | Sandbox output and no-follow-up negative checks |
+| `rdc:extract-verifier-rules` | `rdc-rdc-extract-verifier-rules.test.json` | Enhancement-log verifier fixture | `exit_code`, `stdout_contains` | Candidate, false-positive, known-good, recall, and no-auto-merge/PR negative checks |
+| `rdc:release` | `rdc-release.test.json` | Dry-run package release | `commits_made`, `exit_code`, `stdout_contains` | Dry-run release checklist and force/bypass negative checks |
+| `rdc:regen-media` | `rdc-regen-media.test.json` | Image generation path selection | `commits_made`, `exit_code`, `stdout_contains` | Local keyless Codex gpt-image-2 default, test-mode no-generation, and server-side fallback negative checks |
+| `rdc:report` | `rdc-report.test.json` | Unattended report generation | `exit_code`, `stdout_contains` | Report status block, counts, next recommendation, and dump/push negative checks |
+| `rdc:review` | `rdc-review.test.json` | Unattended review gate | `exit_code`, `stdout_contains` | Code-review, verify, fresh-evidence, tsc, and forbidden-build negative checks |
+| `rdc:rpms-filemap` | `rdc-rpms-filemap.test.json` | Canonical location lookup | `commits_made`, `exit_code`, `stdout_contains` | Rule #1, context door, one-home rules, and no-hand-edit/second-home negative checks |
+| `rdc:self-test` | `rdc-self-test.test.json` | Strict self-test prompt | `commits_made`, `exit_code`, `stdout_contains` | Strict validation evidence, hook/guide checks, and no-relaxed-linter negative check |
+| `rdc:status` | `rdc-status.test.json` | Read-only status snapshot | `commits_made`, `exit_code`, `stdout_contains` | Read-only status output and raw-MCP/write negative checks |
+| `rdc:terminal-config` | `rdc-terminal-config.test.json` | Hidden-window launch policy audit | `commits_made`, `exit_code`, `stdout_contains` | Hidden-window output and focus/collapse API negative checks |
+| `rdc:watch` | `rdc-watch.test.json` | Watcher initialization prompt | `exit_code`, `stdout_contains` | Test-mode no-open output, tool-call routing, and focus-event negative checks |
+| `rdc:workitems` | `rdc-workitems.test.json` | Work-item epic listing | `commits_made`, `exit_code`, `stdout_contains` | Read-only epics query, sandbox, and work-item write negative checks |
+
+## What The Tests Accomplish
+
+- Verify every installed RDC skill has at least one executable caller-facing prompt.
+- Exercise the `RDC_TEST=1` sandbox contract so build tests do not publish, deploy, or mutate production services.
+- Capture observed engine events and extracted tool calls for periodic inspection.
+- Preserve stdout, stderr, and rendered assistant output as report artifacts.
+- Make content-producing skills eligible for deeper source-fidelity checks through the optional `acceptance` block.
+
+## Next Coverage Upgrades
+
+- Run full scheduled Claude and Codex sweeps regularly, not only changed-skill acceptance, so transcripts and lessons stay fresh.
+- Add richer artifact-content checks for output-producing skills (`rdc:brochure`, `rdc:convert`, `rdc:prototype`, `rdc:report`).
+- Promote recurring transcript review findings into manifest assertions instead of relying on human inspection.