@lifeaitools/rdc-skills 0.9.4 → 0.9.6

package/.github/workflows/publish.yml

@@ -31,4 +31,4 @@ jobs:
           STATUS="${{ job.status }}"
           curl -s -X POST "${{ secrets.CLAUTH_CHANNEL_URL }}" \
             -H "Content-Type: application/json" \
-            -d "{\"text\":\"rdc-skills v${VERSION} npm publish: ${STATUS}\",\"source\":\"github-actions\"}"
+            -d "{\"event\":\"npm-publish\",\"package\":\"rdc-skills\",\"version\":\"${VERSION}\",\"status\":\"${STATUS}\",\"source\":\"github-actions\"}"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.9.4",
+  "version": "0.9.6",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight builds",
   "keywords": [
     "claude-code",
@@ -19,7 +19,7 @@
     "type": "plugin",
     "skills": "skills/",
     "guides": "guides/",
-    "version": "0.9.4",
+    "version": "0.9.6",
     "commands": "commands/"
   },
   "scripts": {

package/skills/plan/SKILL.md

@@ -96,3 +96,41 @@ choose the most conservative/reversible approach and document the decision.
 - Reference affected CLAUDE.md files in each work package description
 - Reference the relevant guide file from `.rdc/guides/` (fallback: `.rdc/guides/`) for agent context
 - **If a work package involves creating a new deployed app:** the task description MUST say "Use `rdc:deploy new <slug>` — do NOT create the Coolify app manually. Read `docs/runbooks/coolify-app-templates.json` first." Assign it to an `infra` agent. This is a hard rule — manually created apps have consistently been misconfigured.
+
+## New App Q&A (mandatory before writing any infra task that creates a Coolify app)
+
+If the plan includes deploying a new app, these questions MUST be answered — in interactive mode, ask the user; in unattended mode, escalate via advisor. Do NOT write the infra task until all answers are locked in. Record answers in the plan doc and embed them directly in the task description.
+
+**Never guess. Wrong project = delete and recreate. There is no move operation in Coolify.**
+
+```
+Q1. Which Coolify project does this app belong to?
+    → Read docs/runbooks/coolify-app-templates.json → _infrastructure.projects
+    → Match by area: design-system / prt / rdc / rdc-marketing / zoen / lifeai / place-fund / infrastructure / ai-platform
+    → If unsure: ASK. Do not infer from app name alone.
+    → Record: project_uuid + environment_uuid (staging or production)
+
+Q2. What is the domain?
+    → *.dev.place.fund subdomain? (staging / internal tools)
+    → Custom subdomain on an existing zone? (e.g. app.regendevcorp.com)
+    → Apex domain? (e.g. place.fund itself)
+    → Domain on a different zone entirely? (e.g. skymesasouth.com)
+
+Q3. Is this domain already in our Cloudflare account?
+    → Yes, zone exists → which zone?
+    → No → who controls the nameservers? Does the registrar point NS to Cloudflare?
+    → If NS not delegated to Cloudflare: A record in Cloudflare does nothing — must go to registrar
+
+Q4. Does this app need Cloudflare proxy (orange cloud)?
+    → *.dev.place.fund: NEVER proxy — breaks Traefik Let's Encrypt HTTP-01 cert provisioning
+    → Custom domain needing DDoS/CDN: proxy OK only if SSL mode = Full (strict) + origin cert provisioned
+    → Any doubt: start unproxied, add proxy after confirming SSL works
+
+Q5. What SSL path?
+    → Traefik + Let's Encrypt (default for all unproxied): automatic, no action needed
+    → Cloudflare proxy + Full (strict): need origin cert from Cloudflare dashboard first
+    → Nixpacks build pack: DO NOT USE for any app that needs custom SSL setup — nixpacks
+      containers have incompatible SSL configuration requirements. Use dockerfile build pack only.
+```
+
+Embed all five answers into the infra task description verbatim before handing to the agent.

package/skills/release/SKILL.md

@@ -126,6 +126,10 @@ rdc:release: regen-root — develop → main
 
 ## Execution Details
 
+> **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
@@ -277,10 +281,22 @@ git push origin develop
 - Merge via `mcp__claude_ai_Github_Proxy_MCP__merge_pull_request` with `merge_method: merge`
 
 #### 4. Confirm Coolify auto-deploy
-- Coolify watches `main` for all production apps
-- Poll the deployment for each affected app (identified by which `watch_paths` match changed files)
-- Use clauth daemon + Coolify REST to poll: `GET /api/v1/applications/<uuid>/deployments?per_page=1`
-- Wait for `status = finished`
+
+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:
+
+```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"
+```
 
 #### 5. Gate checks
 For each affected app, verify: HTTP 200, TLS valid, container running.