@lifeaitools/rdc-skills 0.24.38 → 0.24.41

package/commands/collab.md

@@ -1,180 +1,180 @@
----
-name: rdc:collab
-description: >-
-  Usage `rdc:collab --session <id>` — bidirectional relay with claude.ai. Read inbox, do work, write outbox, loop. Dave watches terminal and can interject.
----
-
-> **⚠️ 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:collab — Claude Code Collab Session Listener
-> Invoked as: `/rdc:collab --session <session_id>`
-> You are the build/execute half of a live collab session with claude.ai.
-> Transport: file relay via `.rdc/relay/sessions/<id>/inbox/` + `outbox/`
-> Dave is watching this terminal and can interject at any time.
-
----
-
-## What This Is
-
-claude.ai writes tasks into your inbox. You read, act, commit, write the response
-to outbox, and loop. clauth relays messages between claude.ai and this session via
-the `chitchat_*` MCP tools. Dave can watch everything in this terminal and interject
-by typing — treat anything Dave types as a high-priority override.
-
----
-
-## Step 1 — Parse session ID
-
-Extract `--session <uuid>` from args.
-
-If no `--session`, list `.rdc/relay/sessions/` and show available sessions.
-
----
-
-## Step 2 — Initialize
-
-```
-sessionDir = .rdc/relay/sessions/<session_id>/
-inbox      = sessionDir/inbox/
-outbox     = sessionDir/outbox/
-```
-
-Verify both dirs exist. If not:
-```
-Session directory not found. Run chitchat_start from claude.ai first.
-```
-
-Update `sessionDir/status.json`:
-```json
-{ "status": "active", "cli_connected_at": "<iso>", "session_id": "<id>" }
-```
-
-Write a ready signal to outbox so claude.ai knows the CLI is connected:
-
-```
-outbox/<iso-ts>-ready.md
----
-from: claude-code
-to: claude-ai
-session_id: <id>
-type: ready
-responded_at: <iso>
----
-Claude Code connected. Ready to receive tasks.
-cwd: <rootPath>
-```
-
-Print to terminal:
-```
-[rdc:collab] Session <id> active.
-Inbox:  .rdc/relay/sessions/<id>/inbox/
-Outbox: .rdc/relay/sessions/<id>/outbox/
-Waiting for messages from claude.ai... (Ctrl+C to end)
-```
-
----
-
-## Step 3 — Poll inbox
-
-Scan `inbox/` for `.md` files that do NOT end in `.processed`. Sort ascending by name.
-
-- **No files:** wait 5 seconds, poll again.
-- **After 10 min idle:** print `[rdc:collab] Still listening...` heartbeat, keep waiting.
-- **Files found:** process the oldest one first (Step 4).
-
----
-
-## Step 4 — Process message
-
-Read the file. Parse frontmatter `type` field.
-
-**`type: stop`** → go to Step 6.
-
-**Anything else (default: task/message):**
-
-Print to terminal:
-```
-[rdc:collab] Turn <N> from claude.ai:
-──────────────────────────────────────
-<message body>
-──────────────────────────────────────
-```
-
-Rename the inbox file to `<filename>.processed`.
-
----
-
-## Step 5 — Do the work
-
-Act on the message. Full Claude Code capabilities:
-- File edits, git commits to `develop`
-- Supabase RPC queries
-- Type-checks: `npx tsc --noEmit` (never `pnpm build`)
-- Run skills: `/rdc:plan`, `/rdc:fixit`, etc.
-- Answer questions directly
-
-Follow `.rdc/guides/agent-bootstrap.md` rules throughout.
-
-When done, write response to outbox:
-```
-outbox/<iso-ts>-turn<N>.md
----
-from: claude-code
-to: claude-ai
-session_id: <session_id>
-turn: <N>
-responded_at: <iso>
-commits: <sha1, sha2 or none>
----
-
-<what you did, what you found, any questions or decisions needed from claude.ai>
-```
-
-Print to terminal:
-```
-[rdc:collab] Turn <N> done. Response written to outbox.
-Waiting for next message...
-```
-
-Return to Step 3.
-
----
-
-## Step 6 — End session
-
-Received `type: stop` in inbox, or Dave pressed Ctrl+C.
-
-Write final summary to outbox:
-```
-outbox/<iso-ts>-final.md
----
-from: claude-code
-to: claude-ai
-session_id: <session_id>
-type: final
-responded_at: <iso>
----
-Session complete.
-Turns: <N>
-Commits: <list or none>
-Open items: <anything unresolved>
-```
-
-Update `status.json` → `{ "status": "done", "ended_at": "<iso>" }`
-
-Print:
-```
-[rdc:collab] Session ended.
-```
-
----
-
-## Dave Interjections
-
-If Dave types in this terminal during a turn:
-- Treat it as an override injected into the current task
-- Acknowledge it in your outbox response
-- If it changes direction mid-task, note what you stopped and why
+---
+name: rdc:collab
+description: >-
+  Usage `rdc:collab --session <id>` — bidirectional relay with claude.ai. Read inbox, do work, write outbox, loop. Dave watches terminal and can interject.
+---
+
+> **⚠️ 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:collab — Claude Code Collab Session Listener
+> Invoked as: `/rdc:collab --session <session_id>`
+> You are the build/execute half of a live collab session with claude.ai.
+> Transport: file relay via `.rdc/relay/sessions/<id>/inbox/` + `outbox/`
+> Dave is watching this terminal and can interject at any time.
+
+---
+
+## What This Is
+
+claude.ai writes tasks into your inbox. You read, act, commit, write the response
+to outbox, and loop. clauth relays messages between claude.ai and this session via
+the `chitchat_*` MCP tools. Dave can watch everything in this terminal and interject
+by typing — treat anything Dave types as a high-priority override.
+
+---
+
+## Step 1 — Parse session ID
+
+Extract `--session <uuid>` from args.
+
+If no `--session`, list `.rdc/relay/sessions/` and show available sessions.
+
+---
+
+## Step 2 — Initialize
+
+```
+sessionDir = .rdc/relay/sessions/<session_id>/
+inbox      = sessionDir/inbox/
+outbox     = sessionDir/outbox/
+```
+
+Verify both dirs exist. If not:
+```
+Session directory not found. Run chitchat_start from claude.ai first.
+```
+
+Update `sessionDir/status.json`:
+```json
+{ "status": "active", "cli_connected_at": "<iso>", "session_id": "<id>" }
+```
+
+Write a ready signal to outbox so claude.ai knows the CLI is connected:
+
+```
+outbox/<iso-ts>-ready.md
+---
+from: claude-code
+to: claude-ai
+session_id: <id>
+type: ready
+responded_at: <iso>
+---
+Claude Code connected. Ready to receive tasks.
+cwd: <rootPath>
+```
+
+Print to terminal:
+```
+[rdc:collab] Session <id> active.
+Inbox:  .rdc/relay/sessions/<id>/inbox/
+Outbox: .rdc/relay/sessions/<id>/outbox/
+Waiting for messages from claude.ai... (Ctrl+C to end)
+```
+
+---
+
+## Step 3 — Poll inbox
+
+Scan `inbox/` for `.md` files that do NOT end in `.processed`. Sort ascending by name.
+
+- **No files:** wait 5 seconds, poll again.
+- **After 10 min idle:** print `[rdc:collab] Still listening...` heartbeat, keep waiting.
+- **Files found:** process the oldest one first (Step 4).
+
+---
+
+## Step 4 — Process message
+
+Read the file. Parse frontmatter `type` field.
+
+**`type: stop`** → go to Step 6.
+
+**Anything else (default: task/message):**
+
+Print to terminal:
+```
+[rdc:collab] Turn <N> from claude.ai:
+──────────────────────────────────────
+<message body>
+──────────────────────────────────────
+```
+
+Rename the inbox file to `<filename>.processed`.
+
+---
+
+## Step 5 — Do the work
+
+Act on the message. Full Claude Code capabilities:
+- File edits, git commits to `develop`
+- Supabase RPC queries
+- Type-checks: `npx tsc --noEmit` (never `pnpm build`)
+- Run skills: `/rdc:plan`, `/rdc:fixit`, etc.
+- Answer questions directly
+
+Follow `.rdc/guides/agent-bootstrap.md` rules throughout.
+
+When done, write response to outbox:
+```
+outbox/<iso-ts>-turn<N>.md
+---
+from: claude-code
+to: claude-ai
+session_id: <session_id>
+turn: <N>
+responded_at: <iso>
+commits: <sha1, sha2 or none>
+---
+
+<what you did, what you found, any questions or decisions needed from claude.ai>
+```
+
+Print to terminal:
+```
+[rdc:collab] Turn <N> done. Response written to outbox.
+Waiting for next message...
+```
+
+Return to Step 3.
+
+---
+
+## Step 6 — End session
+
+Received `type: stop` in inbox, or Dave pressed Ctrl+C.
+
+Write final summary to outbox:
+```
+outbox/<iso-ts>-final.md
+---
+from: claude-code
+to: claude-ai
+session_id: <session_id>
+type: final
+responded_at: <iso>
+---
+Session complete.
+Turns: <N>
+Commits: <list or none>
+Open items: <anything unresolved>
+```
+
+Update `status.json` → `{ "status": "done", "ended_at": "<iso>" }`
+
+Print:
+```
+[rdc:collab] Session ended.
+```
+
+---
+
+## Dave Interjections
+
+If Dave types in this terminal during a turn:
+- Treat it as an override injected into the current task
+- Acknowledge it in your outbox response
+- If it changes direction mid-task, note what you stopped and why

package/commands/deploy.md

@@ -1,152 +1,152 @@
----
-name: rdc:deploy
-description: >-
-  Coolify ops. Usage `rdc:deploy <slug> [build-id]` or `rdc:deploy new <slug>` or `rdc:deploy diagnose <slug>` or `rdc:deploy audit [--fix]` — type checklists, DNS decision tree, mandatory post-deploy gate. Checklist-only output.
----
-
-> **⚠️ 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:deploy — Coolify Operations
-
-**READ FIRST:** `guides/output-contract.md`. Checklist-only output. No narration.
-No raw MCP dumps. No UUIDs unless asked.
-
-> **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.
->
-> *Under `$RDC_TEST=1`:* Modes 1 (deploy) and 2 (new) are **entirely skipped** — echo `[RDC_TEST] skipping Coolify deploy/create` and mark every `[ ]` line in those checklists as `[~]`. Modes 3 (diagnose) and 4 (audit without `--fix`) are **read-only and run normally**. Mode 4 with `--fix` skips all remediation — echo `[RDC_TEST] skipping audit --fix remediation` and report findings only. Registry SELECTs, Coolify status reads, HTTP gate probes, TLS checks, and DNS lookups are NOT destructive and run normally. Anything that writes (create app, set watch_paths, deploy trigger, env var write, DNS write, CF cache purge, registry UPDATE/INSERT) is gated.
-
-## Arguments
-
-- `rdc:deploy <slug>` — deploy existing app (latest commit on its watched branch)
-- `rdc:deploy <slug> <build-id>` — deploy specific commit/tag
-- `rdc:deploy new <slug>` — create a new Coolify app from registry
-- `rdc:deploy diagnose <slug>` — debug why an app is broken
-- `rdc:deploy audit` — fleet-wide scan for missed failures
-- `rdc:deploy audit --fix` — fleet scan + auto-remediate safe issues
-- `rdc:deploy` (no args) — print mode menu, ask which
-
-## Modes
-
-### Mode 1 — deploy <slug> [build-id]
-
-```
-rdc:deploy: <slug> → <domain>
-[ ] Registry lookup (slug, uuid, branch, type, env_vars_needed)
-[ ] Git state verified (branch matches Coolify, commit pushed)
-[ ] Build-id resolved (default: HEAD of watched branch)
-[ ] Env vars present in Coolify (compare to registry)
-[ ] Type-specific preflight (see docs/runbooks/coolify-deploy-checklist.md)
-[ ] Deploy triggered
-[ ] Deployment reached "finished" state
-[ ] Gate: HTTP 200
-[ ] Gate: TLS valid (no SSL cipher mismatch)
-[ ] Gate: cache headers correct on HTML
-[ ] Gate: container running on declared port
-[ ] Cloudflare cache purged (if proxied)
-[ ] deployment_registry updated (last_deploy_at, status)
-✅ rdc:deploy: <slug> deployed in Nm Ns
-```
-
-### Mode 2 — new <slug>
-
-```
-rdc:deploy new: <slug>
-[ ] Registry entry loaded (or interactive create)
-[ ] DNS path chosen (A: staging wildcard  B: apex  C: other zone)
-[ ] DNS record verified or wildcard confirmed
-[ ] Cloudflare proxy setting correct for DNS path
-[ ] server_uuid, project_uuid, environment_uuid, github_app_uuid resolved
-[ ] Build type chosen (Next.js / Vite / static / standalone)
-[ ] Type-specific fields filled (ports, build cmd, install cmd, start cmd)
-[ ] Application created via /applications/private-github-app
-[ ] watch_paths set and verified
-[ ] Env vars set in Coolify
-[ ] First deploy triggered
-[ ] Gate passed (5 checks)
-[ ] deployment_registry row inserted
-✅ rdc:deploy new: <slug> live at <domain>
-```
-
-### Mode 3 — diagnose <slug>
-
-```
-rdc:deploy diagnose: <slug>
-[ ] App located (uuid, domain, last deploy)
-[ ] Container state (running / restarting / stopped)
-[ ] Last 100 log lines scanned for known error patterns
-[ ] Port mismatch check (declared vs actual)
-[ ] Env var drift check (registry vs Coolify)
-[ ] watch_paths sanity check
-[ ] HTTP / TLS reachability
-[ ] Cloudflare proxy state check
-[ ] Disk space on server
-[ ] Branch mismatch check (Coolify git_branch vs expected)
-⚠️ rdc:deploy diagnose: <root cause in one sentence> — fix: <one command>
-```
-
-### Mode 4 — audit
-
-```
-rdc:deploy audit: fleet scan
-[ ] Inventory join: Coolify apps ⋈ deployment_registry
-[ ] Orphans (in one but not the other)
-[ ] Monorepo apps missing watch_paths
-[ ] Stale deploys (>14 days since last success)
-[ ] Registry rows with status='broken'
-[ ] Failed deployments in last 7 days
-[ ] HTTP gate sweep (non-200 per domain)
-[ ] TLS cert expiry <30 days
-[ ] Port mismatches (ports_exposes vs actual container port)
-[ ] Env var drift (registry.env_vars_needed vs Coolify env)
-[ ] Branch mismatches (Coolify git_branch ≠ expected)
-[ ] Disk space on 64.237.54.189
-[ ] DNS/proxy misconfigs on configured staging wildcard
-[ ] Duplicate apps (same repo, multiple UUIDs)
-
-Findings:
-| Severity | App | Issue | Fix |
-|----------|-----|-------|-----|
-| HIGH     | ... | ...   | ... |
-⚠️ rdc:deploy audit: N HIGH · M MED · K LOW — run `rdc:deploy audit --fix` to auto-remediate safe issues
-```
-
-Severity rules:
-- **HIGH** — user-facing down (HTTP non-200, TLS invalid, container not running)
-- **MED** — degraded or drifting (watch_paths missing, env var drift, stale deploy, branch mismatch)
-- **LOW** — cleanup (orphans, duplicates, registry status stale)
-
-`--fix` auto-remediates only: missing watch_paths, registry row updates, CF cache purges. Never touches env vars, DNS, or container config without explicit confirmation.
-
-## Coolify Access — clauth + REST API
-
-All Coolify operations use the clauth daemon and the Coolify REST API directly.
-There is no Coolify MCP server — do not reference `@masonator/coolify-mcp`.
-
-```bash
-_COOLIFY=$(curl -s http://127.0.0.1:52437/v/coolify-api)
-curl -s -H "Authorization: Bearer $_COOLIFY" "$DEPLOY_API_BASE/api/v1/applications"
-```
-
-If clauth daemon is not responding:
-```
-BLOCKED: clauth daemon not responding. Run scripts\restart-clauth.bat, unlock at http://127.0.0.1:52437
-```
-
-## References
-
-- Type-specific checklists + DNS tree + gate commands: `docs/runbooks/coolify-deploy-checklist.md`
-- Rules / registry RPCs / hard limits: `.claude/rules/coolify-deployment.md`
-- Infrastructure constants:
-  ```
-  Server UUID:     ih386anenvvvn6fy1umtyow0
-  Server IP:       64.237.54.189
-  Dashboard:       <deployment-dashboard-url>
-  GitHub App UUID: xdmcy60putp5h9j7k4kwg9c3
-  ```
-
-## Supersedes
-
-`coolify-deploy` standalone skill (kept for back-compat; new work uses `rdc:deploy`).
+---
+name: rdc:deploy
+description: >-
+  Coolify ops. Usage `rdc:deploy <slug> [build-id]` or `rdc:deploy new <slug>` or `rdc:deploy diagnose <slug>` or `rdc:deploy audit [--fix]` — type checklists, DNS decision tree, mandatory post-deploy gate. Checklist-only output.
+---
+
+> **⚠️ 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:deploy — Coolify Operations
+
+**READ FIRST:** `guides/output-contract.md`. Checklist-only output. No narration.
+No raw MCP dumps. No UUIDs unless asked.
+
+> **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.
+>
+> *Under `$RDC_TEST=1`:* Modes 1 (deploy) and 2 (new) are **entirely skipped** — echo `[RDC_TEST] skipping Coolify deploy/create` and mark every `[ ]` line in those checklists as `[~]`. Modes 3 (diagnose) and 4 (audit without `--fix`) are **read-only and run normally**. Mode 4 with `--fix` skips all remediation — echo `[RDC_TEST] skipping audit --fix remediation` and report findings only. Registry SELECTs, Coolify status reads, HTTP gate probes, TLS checks, and DNS lookups are NOT destructive and run normally. Anything that writes (create app, set watch_paths, deploy trigger, env var write, DNS write, CF cache purge, registry UPDATE/INSERT) is gated.
+
+## Arguments
+
+- `rdc:deploy <slug>` — deploy existing app (latest commit on its watched branch)
+- `rdc:deploy <slug> <build-id>` — deploy specific commit/tag
+- `rdc:deploy new <slug>` — create a new Coolify app from registry
+- `rdc:deploy diagnose <slug>` — debug why an app is broken
+- `rdc:deploy audit` — fleet-wide scan for missed failures
+- `rdc:deploy audit --fix` — fleet scan + auto-remediate safe issues
+- `rdc:deploy` (no args) — print mode menu, ask which
+
+## Modes
+
+### Mode 1 — deploy <slug> [build-id]
+
+```
+rdc:deploy: <slug> → <domain>
+[ ] Registry lookup (slug, uuid, branch, type, env_vars_needed)
+[ ] Git state verified (branch matches Coolify, commit pushed)
+[ ] Build-id resolved (default: HEAD of watched branch)
+[ ] Env vars present in Coolify (compare to registry)
+[ ] Type-specific preflight (see docs/runbooks/coolify-deploy-checklist.md)
+[ ] Deploy triggered
+[ ] Deployment reached "finished" state
+[ ] Gate: HTTP 200
+[ ] Gate: TLS valid (no SSL cipher mismatch)
+[ ] Gate: cache headers correct on HTML
+[ ] Gate: container running on declared port
+[ ] Cloudflare cache purged (if proxied)
+[ ] deployment_registry updated (last_deploy_at, status)
+✅ rdc:deploy: <slug> deployed in Nm Ns
+```
+
+### Mode 2 — new <slug>
+
+```
+rdc:deploy new: <slug>
+[ ] Registry entry loaded (or interactive create)
+[ ] DNS path chosen (A: staging wildcard  B: apex  C: other zone)
+[ ] DNS record verified or wildcard confirmed
+[ ] Cloudflare proxy setting correct for DNS path
+[ ] server_uuid, project_uuid, environment_uuid, github_app_uuid resolved
+[ ] Build type chosen (Next.js / Vite / static / standalone)
+[ ] Type-specific fields filled (ports, build cmd, install cmd, start cmd)
+[ ] Application created via /applications/private-github-app
+[ ] watch_paths set and verified
+[ ] Env vars set in Coolify
+[ ] First deploy triggered
+[ ] Gate passed (5 checks)
+[ ] deployment_registry row inserted
+✅ rdc:deploy new: <slug> live at <domain>
+```
+
+### Mode 3 — diagnose <slug>
+
+```
+rdc:deploy diagnose: <slug>
+[ ] App located (uuid, domain, last deploy)
+[ ] Container state (running / restarting / stopped)
+[ ] Last 100 log lines scanned for known error patterns
+[ ] Port mismatch check (declared vs actual)
+[ ] Env var drift check (registry vs Coolify)
+[ ] watch_paths sanity check
+[ ] HTTP / TLS reachability
+[ ] Cloudflare proxy state check
+[ ] Disk space on server
+[ ] Branch mismatch check (Coolify git_branch vs expected)
+⚠️ rdc:deploy diagnose: <root cause in one sentence> — fix: <one command>
+```
+
+### Mode 4 — audit
+
+```
+rdc:deploy audit: fleet scan
+[ ] Inventory join: Coolify apps ⋈ deployment_registry
+[ ] Orphans (in one but not the other)
+[ ] Monorepo apps missing watch_paths
+[ ] Stale deploys (>14 days since last success)
+[ ] Registry rows with status='broken'
+[ ] Failed deployments in last 7 days
+[ ] HTTP gate sweep (non-200 per domain)
+[ ] TLS cert expiry <30 days
+[ ] Port mismatches (ports_exposes vs actual container port)
+[ ] Env var drift (registry.env_vars_needed vs Coolify env)
+[ ] Branch mismatches (Coolify git_branch ≠ expected)
+[ ] Disk space on 64.237.54.189
+[ ] DNS/proxy misconfigs on configured staging wildcard
+[ ] Duplicate apps (same repo, multiple UUIDs)
+
+Findings:
+| Severity | App | Issue | Fix |
+|----------|-----|-------|-----|
+| HIGH     | ... | ...   | ... |
+⚠️ rdc:deploy audit: N HIGH · M MED · K LOW — run `rdc:deploy audit --fix` to auto-remediate safe issues
+```
+
+Severity rules:
+- **HIGH** — user-facing down (HTTP non-200, TLS invalid, container not running)
+- **MED** — degraded or drifting (watch_paths missing, env var drift, stale deploy, branch mismatch)
+- **LOW** — cleanup (orphans, duplicates, registry status stale)
+
+`--fix` auto-remediates only: missing watch_paths, registry row updates, CF cache purges. Never touches env vars, DNS, or container config without explicit confirmation.
+
+## Coolify Access — clauth + REST API
+
+All Coolify operations use the clauth daemon and the Coolify REST API directly.
+There is no Coolify MCP server — do not reference `@masonator/coolify-mcp`.
+
+```bash
+_COOLIFY=$(curl -s http://127.0.0.1:52437/v/coolify-api)
+curl -s -H "Authorization: Bearer $_COOLIFY" "$DEPLOY_API_BASE/api/v1/applications"
+```
+
+If clauth daemon is not responding:
+```
+BLOCKED: clauth daemon not responding. Run scripts\restart-clauth.bat, unlock at http://127.0.0.1:52437
+```
+
+## References
+
+- Type-specific checklists + DNS tree + gate commands: `docs/runbooks/coolify-deploy-checklist.md`
+- Rules / registry RPCs / hard limits: `.claude/rules/coolify-deployment.md`
+- Infrastructure constants:
+  ```
+  Server UUID:     ih386anenvvvn6fy1umtyow0
+  Server IP:       64.237.54.189
+  Dashboard:       <deployment-dashboard-url>
+  GitHub App UUID: xdmcy60putp5h9j7k4kwg9c3
+  ```
+
+## Supersedes
+
+`coolify-deploy` standalone skill (kept for back-compat; new work uses `rdc:deploy`).