@lifeaitools/rdc-skills 0.8.8 → 0.9.0

package/guides/agent-bootstrap.md

@@ -183,6 +183,47 @@ If you discover that fixing your assigned task would also require changing files
 
 ---
 
+## ⛔ Implementation Report Contract
+
+Every agent MUST follow this protocol before closing any work item as `done`.
+
+### Step 1 — Tick checklist items as you complete them
+
+```sql
+SELECT update_checklist_item('<work-item-id>'::uuid, 'item-id', true);
+```
+
+Call this for each item AS you complete it — not all at once at the end.
+
+### Step 2 — Submit implementation report BEFORE marking done
+
+```sql
+SELECT submit_implementation_report(
+  '<work-item-id>'::uuid,
+  '{"tldr":"...","assumptions":[],"deviations":[],"uncertainty":[],"detail":"...","flags":[]}'::jsonb
+);
+```
+
+Returns `{ flags_count, deviations_count, has_deviations }`. Include this signal in your `AGENT_COMPLETE` report.
+
+### Step 3 — Mark done
+
+```sql
+SELECT update_work_item_status('<work-item-id>'::uuid, 'done');
+```
+
+If any `required: true` checklist item is still unchecked, the DB raises EXCEPTION — fix it first.
+
+### Supervisor workflow
+
+- All zeros → clean run, proceed
+- `flags_count > 0` or `deviations_count > 0` → pull full report:
+  ```sql
+  SELECT implementation_report FROM work_items WHERE id = '<id>';
+  ```
+
+---
+
 ## Now read your role-specific guide
 
 Path: `{PROJECT_ROOT}/.rdc/guides/<type>.md` (e.g., `frontend.md`, `backend.md`, `data.md`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.8.8",
+  "version": "0.9.0",
   "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.8.7",
+    "version": "0.9.0",
     "commands": "commands/"
   },
   "scripts": {

package/rules/work-items-rpc.md

@@ -122,6 +122,8 @@ const { data } = await supabase.rpc('insert_work_item', {
 | `p_session_id` | text | NULL | Session UUID (for audit trail) |
 | `p_package` | text | NULL | Package/module name (e.g., '@regen/ui') |
 | `p_source` | text | `'manual'` | How was this created: `manual`, `agent`, `api`, `import` |
+| `p_checklist` | jsonb | `NULL` | Checklist items. If NULL and parent has `definition_of_done`, auto-inherited with all `checked: false` |
+| `p_definition_of_done` | jsonb | `NULL` | DoD template (epics only). Child tasks inherit this as their checklist at insert time |
 
 **Returns:**
 - Full inserted work_item row as JSONB
@@ -171,6 +173,7 @@ const { data } = await supabase.rpc('update_work_item_status', {
 
 **Behavior:**
 - Setting `done` auto-sets `completed_at = now()`
+- Setting `done` raises EXCEPTION if any `required: true` checklist item has `checked: false` — DoD gate
 - Setting `todo`, `in_progress`, `blocked`, or `review` clears `completed_at`
 - `updated_at` always refreshed to current timestamp
 - Raises exception if ID not found
@@ -180,7 +183,76 @@ const { data } = await supabase.rpc('update_work_item_status', {
 
 ---
 
-### 4. get_work_items_by_epic — Fetch epic + children
+### 4. update_checklist_item — Tick off a checklist item
+
+**Supabase SQL:**
+```sql
+SELECT update_checklist_item(
+  'work-item-uuid'::uuid,
+  'tsc-clean',   -- string id of the checklist item
+  true           -- checked state
+);
+```
+
+**Parameters:**
+
+| Name | Type | Required | Notes |
+|------|------|----------|-------|
+| `p_work_item_id` | uuid | yes | the work item ID |
+| `p_item_id` | text | yes | the `id` field of the checklist item |
+| `p_checked` | boolean | yes | `true` = checked, `false` = unchecked |
+
+Call this as each checklist item is completed — not all at once at the end.
+
+**Returns:** updated checklist JSONB array.
+
+---
+
+### 5. submit_implementation_report — File agent completion narrative
+
+MUST be called BEFORE `update_work_item_status('done')`.
+
+**Supabase SQL:**
+```sql
+SELECT submit_implementation_report(
+  'work-item-uuid'::uuid,
+  '{
+    "tldr": "One-sentence summary",
+    "assumptions": [],
+    "deviations": [],
+    "uncertainty": [],
+    "detail": "Full narrative",
+    "flags": []
+  }'::jsonb
+);
+```
+
+**Parameters:**
+
+| Name | Type | Required | Notes |
+|------|------|----------|-------|
+| `p_work_item_id` | uuid | yes | the work item ID |
+| `p_report` | jsonb | yes | implementation report (shape below) |
+
+**Returns:** `{ "flags_count": N, "deviations_count": N, "has_deviations": bool }` — signal only.
+
+**`implementation_report` shape:**
+```json
+{
+  "tldr": "string",
+  "assumptions": ["string", "..."],
+  "deviations": ["string — deviation from plan", "..."],
+  "uncertainty": ["string — anything unclear", "..."],
+  "detail": "string — full narrative",
+  "flags": ["string — supervisor attention needed", "..."]
+}
+```
+
+If `has_deviations` is true or `flags_count > 0`, supervisor pulls full report from DB.
+
+---
+
+### 6. get_work_items_by_epic — Fetch epic + children
 
 Get an epic and all its child tasks/subtasks, sorted by priority.
 
@@ -216,7 +288,7 @@ const { data } = await supabase.rpc('get_work_items_by_epic', {
 
 ---
 
-### 5. bump_epic_version — Version with history
+### 7. bump_epic_version — Version with history
 
 Snapshot an epic's current state and assign a version number.
 

package/skills/fixit/SKILL.md

@@ -89,7 +89,13 @@ fi
 
 ### 6. Close and clean up
 
+Submit implementation report first, then mark done:
+
 ```sql
+SELECT submit_implementation_report('<id>'::uuid,
+  '{"tldr":"<one sentence>","assumptions":[],"deviations":[],"uncertainty":[],"detail":"<what was fixed>","flags":[]}'::jsonb
+);
+
 SELECT update_work_item_status('<id>'::uuid, 'done',
   '["Fixed via rdc:fixit"]'::jsonb
 );

package/skills/plan/SKILL.md

@@ -66,8 +66,9 @@ description: >-
    ```
 
 6. **Create Supabase epic + child tasks:**
-   - Epic via `insert_work_item(p_item_type := 'epic', ...)`
-   - One task per work package via `insert_work_item(p_parent_id := <epic_id>, ...)`
+   - Epic via `insert_work_item(p_item_type := 'epic', p_definition_of_done := '[{"id":"...", "text":"...", "required":true, "checked":false}]'::jsonb, ...)`
+   - 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
    - Set priorities: urgent/high/normal based on sequencing
 
 7. **Report results:**

package/skills/release/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: rdc:release
 description: >-
-  Atomic release for ANY LIFEAI repo. Usage `rdc:release <repo> [version]` — one skill, all repos. Known repos: clauth, rdc-skills, regen-root, regen-media, gws. Handles npm publish, monorepo develop→main promotion, and MCP server restarts. No user handoff.
+  Atomic release for ANY LIFEAI repo. Usage `rdc:release <repo> [version]` — one skill, all repos. Known repos: clauth, rdc-skills, regen-root, regen-media, gws. Also promotes individual deployed apps from staging to production: `rdc:release promote <slug>`. Handles npm publish, monorepo develop→main promotion, per-app Coolify gate checks, and MCP server restarts. No user handoff.
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
@@ -25,6 +25,9 @@ Dave has Bash access. He should never be asked to run commands. This skill runs
 - A package, plugin, or app needs to be versioned and pushed to its distribution channel
 - After landing significant changes that must be published (clauth, rdc-skills, regen-media, gws)
 - After develop is verified and staging passes — promoting to main
+- User says "promote studio", "release studio to production", "ship the app" — use `promote <slug>` mode
+
+**Never release autonomously.** This skill ONLY runs when the user explicitly invokes it. Never push to main on your own initiative.
 
 ## Arguments
 
@@ -32,6 +35,8 @@ Dave has Bash access. He should never be asked to run commands. This skill runs
 - `rdc:release <repo> <version>` — explicit version (e.g. `1.6.0`)
 - `rdc:release <repo> --minor` | `--major` | `--patch` — semver bump
 - `rdc:release <repo> --dry-run` — show checklist and planned version, do nothing
+- `rdc:release promote <slug>` — promote a specific deployed app from staging → production
+- `rdc:release promote <slug> --dry-run` — show what would happen, do nothing
 - `rdc:release` (no args) — list known repos, ask which
 
 ## Known Repos — The Single Lookup Table
@@ -74,6 +79,30 @@ rdc:release: <repo> vX.Y.Z → vA.B.C
 ✅ rdc:release <repo>: vA.B.C live
 ```
 
+### App promote checklist (promote <slug>)
+
+This mode promotes a single deployed app. It does NOT push `git push origin main` directly — it uses the GitHub PR merge API, which bypasses the `block-main-push` hook by design. The hook blocks autonomous pushes; explicit promotion via this skill is authorized by the user invoking it.
+
+```
+rdc:release promote: <slug> → <domain>
+[ ] Registry lookup (slug, coolify_uuid, domain, staging_slug, staging_domain, app_version)
+[ ] Staging health gate (HTTP 200 on staging_domain)
+[ ] Staging TLS valid
+[ ] develop branch clean and pushed
+[ ] Commits ahead of main: <N> commits
+[ ] Dry-run gate (if --dry-run, stop here and print planned commands)
+[ ] app package.json version bumped on develop
+[ ] Version bump committed + pushed to develop
+[ ] GitHub PR develop→main: created or located
+[ ] PR merged via GitHub API (merge method: merge)
+[ ] Coolify auto-deploy confirmed started (polling <slug> deployments)
+[ ] Deployment reached "finished" state
+[ ] Gate: HTTP 200 on <domain>
+[ ] Gate: TLS valid on <domain>
+[ ] deployment_registry updated (last_deploy_at, status='active')
+✅ rdc:release promote <slug>: <domain> live
+```
+
 ### Monorepo release checklist (regen-root)
 
 ```
@@ -147,6 +176,71 @@ npm view @lifeaitools/clauth version
 
 ---
 
+### App promote (promote <slug>)
+
+#### 1. Registry lookup
+```sql
+SELECT slug, display_name, domain, staging_slug, staging_domain, coolify_uuid, monorepo_path, environment
+FROM deployment_registry
+WHERE slug = '<slug>';
+```
+If no `staging_slug` or `staging_domain`, ask Dave before proceeding — don't assume.
+
+#### 2. Staging health gate
+```bash
+curl -s -o /dev/null -w "%{http_code}" https://<staging_domain>/
+# Must return 200. TLS must be valid (no -k flag).
+```
+If staging is not healthy, STOP with `[!]` — don't promote a broken staging.
+
+#### 3. Git state check
+```bash
+cd C:/Dev/regen-root
+git status          # must be clean on develop
+git push origin develop
+git log origin/main..develop --oneline   # show what's going to main
+```
+
+#### 4. Version bump
+- Read `apps/<app>/package.json` (use `monorepo_path` from registry), parse `version`
+- Apply patch bump (default) or use explicit version if provided
+- Commit: `chore(release): <slug> vA.B.C`
+- Push to develop
+
+#### 5. GitHub PR merge
+```
+# Check for existing open PR develop→main
+mcp__claude_ai_Github_Proxy_MCP__list_pull_requests (base: main, head: develop)
+
+# If none: create one
+mcp__claude_ai_Github_Proxy_MCP__create_pull_request (base: main, head: develop, title: "chore(release): <slug> vA.B.C")
+
+# Merge it
+mcp__claude_ai_Github_Proxy_MCP__merge_pull_request (merge_method: merge)
+```
+**Note:** This uses the GitHub API — it does NOT run `git push origin main`. The `block-main-push` hook only blocks direct git push, not API merges.
+
+#### 6. Coolify deploy poll
+```bash
+# Use clauth to get Coolify token, then poll the app's deployments
+# Wait for status = "finished" — poll every 15s, 15min timeout
+curl -s -H "Authorization: Bearer $COOLIFY_TOKEN" \
+  "https://deploy.regendevcorp.com/api/v1/applications/<coolify_uuid>/deployments?per_page=1"
+```
+
+#### 7. Gate checks
+```bash
+curl -s -o /dev/null -w "%{http_code}" https://<domain>/   # must return 200
+curl -s -I https://<domain>/ | grep -i "strict-transport"   # TLS
+```
+
+#### 8. Update registry
+```sql
+UPDATE deployment_registry SET last_deploy_at = now(), status = 'active' WHERE slug = '<slug>';
+```
+
+---
+
 ### Monorepo release (regen-root)
 
 #### 1. Git state check