godpowers 2.3.0 → 2.4.0

package/routing/recipes/greenfield-fast.yaml

@@ -12,6 +12,9 @@ triggers:
     - "greenfield"
     - "new project"
     - "idea to production"
+    - "start a product"
+    - "start product"
+    - "build a product"
   state-conditions:
     - "no-godpowers-dir"
 

package/routing/recipes/production-broken.yaml

@@ -8,6 +8,10 @@ metadata:
 triggers:
   intent-keywords:
     - "production down"
+    - "production is broken"
+    - "production broken"
+    - "fix production"
+    - "prod is broken"
     - "urgent"
     - "p0"
     - "p1"

package/routing/recipes/release-maintenance.yaml

@@ -12,6 +12,9 @@ triggers:
     - "update readme badge"
     - "release notes"
     - "package release"
+    - "ship a release"
+    - "release the project"
+    - "prepare release"
 
 sequences:
   default:

package/routing/recipes/returning-after-break.yaml

@@ -11,6 +11,9 @@ triggers:
     - "after break"
     - "pick up where left"
     - "resume project"
+    - "coming back after a week"
+    - "back after a week"
+    - "coming back"
   state-conditions:
     - "file:.godpowers/PROGRESS.md"
 

package/routing/recipes/weekly-health-check.yaml

@@ -11,6 +11,8 @@ triggers:
     - "health check"
     - "hygiene"
     - "project health"
+    - "maintain project health"
+    - "maintain health"
   state-conditions:
     - "lifecycle-phase == steady-state-active"
 

package/schema/routing.v1.json

@@ -20,9 +20,29 @@
       "properties": {
         "command": {
           "type": "string",
-          "pattern": "^/god-[a-z-]+$"
+          "pattern": "^/god(?:-[a-z-]+)?$"
         },
         "description": { "type": "string" },
+        "family": {
+          "type": "string",
+          "enum": [
+            "start",
+            "continue",
+            "build",
+            "verify",
+            "operate",
+            "maintain",
+            "capture",
+            "recover",
+            "extend",
+            "collaborate",
+            "configure"
+          ]
+        },
+        "trigger-precedence": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/TriggerPrecedence" }
+        },
         "tier": {
           "type": "integer",
           "minimum": 0,
@@ -110,7 +130,10 @@
       "properties": {
         "next-recommended": {
           "type": "string",
-          "pattern": "^/god-[a-z-]+$"
+          "pattern": "^(?:/god(?:-[a-z-]+)?(?:\\s.*)?|varies|varies-by-verdict|steady-state|session-end)(?:\\sor\\s/god-[a-z-]+(?:\\s.*)?)*$"
+        },
+        "outcome": {
+          "$ref": "#/$defs/RouteOutcome"
         },
         "alternatives": {
           "type": "array",
@@ -162,7 +185,7 @@
         },
         "auto-complete": {
           "type": "string",
-          "pattern": "^/god-[a-z-]+$",
+          "pattern": "^/god(?:-[a-z-]+)?(?:\\s.*)?$",
           "description": "Command to run if prerequisite missing"
         },
         "human-required": {
@@ -175,9 +198,44 @@
       "type": "object",
       "required": ["command"],
       "properties": {
-        "command": { "type": "string", "pattern": "^/god-[a-z-]+$" },
+        "command": { "type": "string", "pattern": "^/god(?:-[a-z-]+)?(?:\\s.*)?$" },
         "when": { "type": "string", "description": "Condition for this recommendation" }
       }
+    },
+    "RouteOutcome": {
+      "type": "object",
+      "required": ["type", "label", "reason"],
+      "properties": {
+        "type": {
+          "type": "string",
+          "enum": [
+            "contextual",
+            "verdict-based",
+            "steady-state",
+            "session-end",
+            "requires-selection",
+            "no-next-command",
+            "explicit-command"
+          ]
+        },
+        "label": { "type": "string" },
+        "reason": { "type": "string" },
+        "allowed-next": {
+          "type": "array",
+          "items": { "type": "string" }
+        }
+      }
+    },
+    "TriggerPrecedence": {
+      "type": "object",
+      "required": ["trigger", "prefer"],
+      "properties": {
+        "trigger": { "type": "string" },
+        "prefer": { "type": "string" },
+        "when": { "type": "string" },
+        "fallback": { "type": "string" },
+        "reason": { "type": "string" }
+      }
     }
   }
 }

package/schema/workflow.v1.json

@@ -106,6 +106,20 @@
             ]
           }
         },
+        "local-helper-groups": {
+          "type": "array",
+          "description": "Named helper groups expanded by the workflow runner into explicit local-helpers in serialized plans.",
+          "items": {
+            "type": "string",
+            "enum": [
+              "standard-closeout",
+              "repo-maintenance-closeout",
+              "runtime-awareness-closeout",
+              "release-readiness-closeout",
+              "source-sync-closeout"
+            ]
+          }
+        },
         "per": { "type": "string", "enum": ["slice", "wave"] },
         "parallel-by": { "type": "string", "enum": ["slice", "wave"] },
         "on-pass": { "type": "string" },

package/skills/god-discuss.md

@@ -11,7 +11,7 @@ description: |
 
 # /god-discuss
 
-Pre-planning Socratic discussion with domain grilling.
+Pre-planning Socratic discussion with domain and plan grilling.
 
 ## When to use
 
@@ -31,10 +31,15 @@ The agent:
 4. Explores the codebase instead of asking when repo evidence can answer
 5. Challenges vague, overloaded, or conflicting terms against the glossary
 6. Stress-tests domain relationships with concrete scenarios and edge cases
-7. Surfaces 2-3 hidden assumptions
-8. Identifies what's [DECISION] vs [HYPOTHESIS] vs [OPEN QUESTION]
-9. Drafts a brief in `.godpowers/discussions/<topic>.md`
-10. Updates `.godpowers/domain/GLOSSARY.md` when a term or ambiguity is resolved
+7. Attempts to falsify the proposed plan before accepting it:
+   - What breaks if the smallest happy path is wrong?
+   - Which dependency, user behavior, or edge case could invalidate the plan?
+   - What would make this scope too broad for one safe slice?
+   - What evidence would change the recommended next command?
+8. Surfaces 2-3 hidden assumptions
+9. Identifies what's [DECISION] vs [HYPOTHESIS] vs [OPEN QUESTION]
+10. Drafts a brief in `.godpowers/discussions/<topic>.md`
+11. Updates `.godpowers/domain/GLOSSARY.md` when a term or ambiguity is resolved
 
 The brief and glossary get passed to the next planning command. The glossary is
 preparation context, not a replacement for PRD, ARCH, ROADMAP, STACK, or Pillars

package/skills/god-doctor.md

@@ -48,9 +48,9 @@ Plain-text report grouped by severity:
 GODPOWERS DOCTOR
 
 Install: claude (~/.claude/)
-  [OK] 111 skills installed
+  [OK] 112 skills installed
   [OK] 40 agents installed
-  [OK] VERSION matches (2.3.0)
+  [OK] VERSION matches (2.3.1)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 
 Project: /Users/.../my-project/.godpowers/
@@ -114,6 +114,12 @@ as a read-only diagnostic. It reports:
 `/god-doctor --fix` may call `lib/feature-awareness.run(projectRoot)` because
 that helper writes only safe state metadata and managed context fences.
 
+## Host Capability Reporting
+
+`/god-doctor` reports optional code intelligence when `ast-grep`, `sg`, or LSP
+tools are available. Missing code intelligence is diagnostic context only; it
+does not make the host degraded.
+
 ## Repo Documentation Sync
 
 For initialized projects, `/god-doctor` calls `lib/repo-doc-sync.detect` as a
@@ -151,7 +157,7 @@ Built-in, no spawned agent. Reads:
 - `lib/repo-surface-sync.detect(projectRoot)` for structural repo surface
   freshness
 - `lib/route-quality-sync.detect(projectRoot)` through repo surface sync for
-  atomic spawn and contextual route exit freshness
+  atomic spawn and typed route outcome freshness
 - `lib/recipe-coverage-sync.detect(projectRoot)` through repo surface sync for
   high-frequency intent recipe coverage freshness
 - `lib/release-surface-sync.detect(projectRoot)` through repo surface sync for

package/skills/god-extension-scaffold.md

@@ -0,0 +1,66 @@
+---
+name: god-extension-scaffold
+description: |
+  Create a publishable Godpowers extension pack skeleton from inside the
+  slash-command UX. Wraps the same extension authoring helper exposed by
+  `npx godpowers extension-scaffold`, then routes to contract testing.
+
+  Triggers on: "god extension scaffold", "/god-extension-scaffold",
+  "create extension pack", "author extension pack", "new extension pack",
+  "extend godpowers"
+---
+
+# /god-extension-scaffold
+
+Create a Godpowers extension pack skeleton.
+
+## Usage
+
+### `/god-extension-scaffold --name=@godpowers/my-pack --output=.`
+
+Optional arguments:
+
+- `--skill=custom-pack-command` sets the generated skill name.
+- `--agent=custom-pack-agent` creates a generated agent contract.
+- `--workflow=my-pack-workflow` creates a generated workflow YAML.
+- `--overwrite` allows replacing existing scaffold files.
+
+## Process
+
+1. Parse the requested package name, output root, optional skill, optional
+   agent, and optional workflow.
+2. Call `lib/extension-authoring.js scaffold(...)`.
+3. Validate the generated `manifest.yaml` against the extension manifest
+   contract.
+4. Report the created pack path and written files.
+5. Suggest `/god-test-extension <pack-dir>` before install or publish.
+
+## Output
+
+```
+Extension scaffold created: ./godpowers-my-pack
+
+Written:
+  manifest.yaml
+  package.json
+  README.md
+  skills/custom-pack-command.md
+
+Suggested next: /god-test-extension ./godpowers-my-pack
+```
+
+## Implementation
+
+Built-in. Calls `lib/extension-authoring.js scaffold(...)`.
+
+The terminal equivalent remains:
+
+```bash
+npx godpowers extension-scaffold --name=@godpowers/my-pack --output=.
+```
+
+## Related
+
+- `/god-test-extension <path>` - contract test the pack before install or publish
+- `/god-extension-add <path>` - install a passing pack
+- `/god-extension-list` - verify the pack is visible in the runtime

package/skills/god-help.md

@@ -12,7 +12,8 @@ description: |
 
 # /god-help
 
-List Godpowers commands organized by category. Show the catalog.
+List Godpowers commands organized by family first, then by full catalog
+category. Show the map without hiding any installed command.
 
 ## Output sections
 
@@ -23,11 +24,39 @@ One line summary of project state from `state.json`:
 ### 2. Suggested next
 The same suggestion `/god-next` would make. One command.
 
-### 3. Catalog
+### 3. Command families
+Load `<runtimeRoot>/lib/command-families.js` and render family cards before the
+full catalog:
+
+- Start: start or import a project.
+- Continue: understand state and choose the next move.
+- Build: plan, implement, test, and ship product work.
+- Verify: check artifacts, code, runtime behavior, and release readiness.
+- Operate: deploy, observe, harden, launch, and respond in production.
+- Maintain: keep artifacts, docs, dependencies, context, and repo surfaces current.
+- Capture: save thoughts, tasks, backlog items, seeds, and learnings.
+- Recover: undo, repair, restore, skip, or diagnose broken state.
+- Extend: install, inspect, test, remove, or author extension packs.
+- Collaborate: coordinate people, workstreams, suites, sprints, and pull requests.
+- Configure: tune settings, budgets, cache, profiles, help, and version info.
+
+### 4. Decision ladders
+Show the compact ladders when the user asks about capture, work size, or
+verification:
+
+- Capture ladder: `/god-note`, `/god-add-todo`, `/god-add-backlog`, `/god-plant-seed`.
+- Work size ladder: `/god-fast`, `/god-quick`, `/god-story`, `/god-feature`, `/god-build`, `/god-debug`, `/god-hotfix`.
+- Verification ladder: `/god-lint`, `/god-standards`, `/god-review`, `/god-test-runtime`, `/god-audit`, `/god-hygiene`, `/god-preflight`, `/god-dogfood`.
+
+### 5. Status views
+Present `/god-status` as the hub view and list the direct shortcuts:
+`/god-progress`, `/god-lifecycle`, `/god-locate`, and `/god-next`.
+
+### 6. Full catalog
 All installed skills grouped by category. Categories match
 `docs/reference.md` order.
 
-### 4. Where to go for more
+### 7. Where to go for more
 - Full reference: https://github.com/aihxp/godpowers/blob/main/docs/reference.md
 - Concepts: https://github.com/aihxp/godpowers/blob/main/docs/concepts.md
 - Roadmap: https://github.com/aihxp/godpowers/blob/main/docs/ROADMAP.md
@@ -44,6 +73,11 @@ Description of one specific command (reads the skill's frontmatter description).
 ### `/god-help search <keyword>`
 Filter the catalog by keyword match against descriptions.
 
+### `/god-help <family>`
+Show one family card plus its leaf commands. Valid families are start,
+continue, build, verify, operate, maintain, capture, recover, extend,
+collaborate, and configure.
+
 ### `/god-help --category=<name>`
 Show only one category (lifecycle, planning, building, shipping, etc.).
 
@@ -53,6 +87,7 @@ Built-in, no spawned agent. Reads:
 - `<runtime>/skills/*.md` frontmatter
 - `.godpowers/state.json` (for current state line)
 - `<runtimeRoot>/lib/recipes.js` (for suggested next)
+- `<runtimeRoot>/lib/command-families.js` (for family cards and ladders)
 
 Resolve `<runtimeRoot>` as `<projectRoot>` when `<projectRoot>/lib/recipes.js` exists. Otherwise use the installed bundle at `<tool-config-dir>/godpowers-runtime`, where `<tool-config-dir>` is the directory that contains this installed skill.
 

package/skills/god-next.md

@@ -22,10 +22,12 @@ Before reading routing data or calling runtime modules, resolve the Godpowers ru
 1. If `<projectRoot>/lib/router.js` exists, use the repository checkout runtime at `<projectRoot>`.
 2. Otherwise use the installed bundle at `<tool-config-dir>/godpowers-runtime`, where `<tool-config-dir>` is the directory that contains this installed skill, such as `~/.claude`, `~/.codex`, `~/.cursor`, `~/.windsurf`, or `~/.gemini`.
 3. Read routing definitions from `<runtimeRoot>/routing/*.yaml` and recipes from `<runtimeRoot>/routing/recipes/*.yaml`.
-4. For status output, load `<runtimeRoot>/lib/dashboard.js` and call
+4. Load `<runtimeRoot>/lib/command-families.js` for work size, verification,
+   capture, and trigger precedence hints.
+5. For status output, load `<runtimeRoot>/lib/dashboard.js` and call
    `dashboard.compute(projectRoot)`. Use `dashboard.render(result)` for the
    shared dashboard section before adding route-specific detail.
-5. If the checkout runtime and installed runtime differ, say which runtime root
+6. If the checkout runtime and installed runtime differ, say which runtime root
    was used. Only call the output a manual disk scan when `lib/dashboard.js`
    cannot be loaded at all.
 
@@ -72,6 +74,11 @@ Get success-path.next-recommended (e.g., "/god-arch"), then apply any
 conditional-next rule such as UI-detected -> "/god-design"
    |
    v
+Read success-path.outcome when present. Use it to label contextual,
+verdict-based, steady-state, session-end, and selection outcomes before
+showing allowed next commands.
+   |
+   v
 Display: "PRD complete: .godpowers/prd/PRD.md
           Suggested next: /god-arch (design the architecture)"
 ```
@@ -128,6 +135,16 @@ If prereqs missing and NOT auto-completable:
 
 ## Process for Mode 3 (standalone)
 
+When the user asks a broad next-step question, use the family helpers before
+falling back to raw route order:
+
+- Capture intent routes through the capture ladder.
+- Implementation intent routes through the work size ladder.
+- Check or audit intent routes through the verification ladder.
+- Duplicate trigger phrases use `resolveTrigger` so `continue`, `think through`,
+  `what happened`, `what's done`, and `where am i` pick the context-aware
+  command.
+
 ```
 User types: /god-next
    |

package/skills/god-status.md

@@ -11,6 +11,19 @@ description: |
 
 Re-derive state from disk. Your memory is not authoritative. The file system is.
 
+## Status family views
+
+`/god-status` is the hub for the continue family. It should render the overview
+first, then offer direct shortcuts when the user wants a narrower view:
+
+| View | Shortcut | Purpose |
+|------|----------|---------|
+| Overview | `/god-status` | Operational state, proactive checks, and blockers. |
+| Progress ledger | `/god-progress` | Requirement and roadmap increment completion. |
+| Lifecycle phase | `/god-lifecycle` | Project phase and fitting workflows. |
+| Resume location | `/god-locate` | Orientation from checkpoint, handoff, and disk state. |
+| Next action | `/god-next` | Single recommended command with reason. |
+
 ## Process
 
 1. Check if `.godpowers/PROGRESS.md` exists

package/skills/god-sync.md

@@ -93,7 +93,7 @@ Sync status:
     + source-sync: <written legacy planning/BMAD/Superpowers companion files, no-op, or skipped>
     + repo-doc-sync: <refreshed README badges/counts, recommended god-docs-writer, or no-op>
     + repo-surface-sync: <checked routes/package/agents/workflows/extensions, recommended scoped agents, or no-op>
-    + route-quality-sync: <checked atomic spawns and contextual exits, no-op, or recommended god-auditor>
+    + route-quality-sync: <checked atomic spawns and typed route outcomes, no-op, or recommended god-auditor>
     + recipe-coverage-sync: <checked high-frequency intent recipes, no-op, or recommended god-roadmap-reconciler>
     + release-surface-sync: <checked badges/changelog/release/package guards, no-op, or recommended god-docs-writer>
     + pillars-sync: <updated N pillar files, no-op, or proposed>

package/skills/god-version.md

@@ -14,9 +14,9 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v2.3.0
+Godpowers v2.3.1
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 111 skills, 40 agents, 13 workflows, 41 recipes
+Surface: 112 skills, 40 agents, 13 workflows, 42 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync, quick proof, request trace, release hardening, maintenance hardening

package/skills/god.md

@@ -22,7 +22,7 @@ Before calling runtime modules, resolve the Godpowers runtime root:
 
 1. If `<projectRoot>/lib/recipes.js` exists, use the repository checkout runtime at `<projectRoot>`.
 2. Otherwise use the installed bundle at `<tool-config-dir>/godpowers-runtime`, where `<tool-config-dir>` is the directory that contains this installed skill, such as `~/.claude`, `~/.codex`, `~/.cursor`, `~/.windsurf`, or `~/.gemini`.
-3. Load recipes from `<runtimeRoot>/lib/recipes.js`, routing from `<runtimeRoot>/lib/router.js`, and recipe YAML from `<runtimeRoot>/routing/recipes/`.
+3. Load recipes from `<runtimeRoot>/lib/recipes.js`, routing from `<runtimeRoot>/lib/router.js`, command families from `<runtimeRoot>/lib/command-families.js`, and recipe YAML from `<runtimeRoot>/routing/recipes/`.
 
 ## Why this exists
 
@@ -41,6 +41,57 @@ This skill complements `/god-next` rather than replacing it:
 | `/god-init` | "Start a project here" |
 | `/god-mode` | "Run the whole project run autonomously" |
 
+## Command family UX
+
+Before showing individual leaf commands, use the family map from
+`lib/command-families.js`:
+
+| Family | User question |
+|--------|---------------|
+| start | "How do I begin or import this project?" |
+| continue | "Where are we and what should happen next?" |
+| build | "How big is this work and how should it run?" |
+| verify | "What is the cheapest sufficient check?" |
+| operate | "How do we run, observe, harden, or fix production?" |
+| maintain | "How do we keep docs, deps, routes, and context current?" |
+| capture | "Where should this thought, task, backlog item, or seed go?" |
+| recover | "How do we repair or walk back state?" |
+| extend | "How do we install or author skill packs?" |
+| collaborate | "How do we coordinate people, workstreams, suites, or PRs?" |
+| configure | "How do we tune settings, budgets, cache, profiles, or help?" |
+
+Use the classifiers from `lib/command-families.js` when intent is about
+capture, work size, verification, or duplicate trigger phrases. Keep every
+leaf command available as a direct shortcut.
+
+### Capture ladder
+
+- Save only: `/god-note`
+- Actionable soon: `/god-add-todo`
+- Optional later: `/god-add-backlog`
+- Conditional future trigger: `/god-plant-seed`
+
+### Work size ladder
+
+- Trivial direct edit: `/god-fast`
+- Small TDD task: `/god-quick`
+- Fine-grained planned slice: `/god-story`
+- Existing-product feature: `/god-feature`
+- Current milestone work: `/god-build`
+- Non-urgent bug: `/god-debug`
+- Production outage: `/god-hotfix`
+
+### Verification ladder
+
+- Mechanical artifact check: `/god-lint`
+- Artifact quality gate: `/god-standards`
+- Code diff review: `/god-review`
+- Live behavior check: `/god-test-runtime`
+- Artifact set score: `/god-audit`
+- Ongoing health check: `/god-hygiene`
+- Existing repo intake: `/god-preflight`
+- Release fixture readiness: `/god-dogfood`
+
 ## Process
 
 ### Step 1: parse the user's intent
@@ -64,6 +115,7 @@ text empty?
          also call <runtimeRoot>/lib/router.js suggestNext(projectRoot) for structural next
 
   no  -> intent-driven: call <runtimeRoot>/lib/recipes.js matchIntent(text, projectRoot)
+         call <runtimeRoot>/lib/command-families.js classifiers for capture, work size, verification, and trigger precedence hints
          take top 1-3 matches by score
          if highest score >= 10 (exact phrase match): propose directly
          if highest score 5-9 (all-words match): propose with confirmation
@@ -160,13 +212,11 @@ any destructive sequence executes.
 ```
 User: /god production is broken
 
-Match: production-broken (score: 30)
-What this does: P0 incident response with rollback-first triage
+Match: production-broken (score: 20)
+What this does: Production is broken now
 
 Sequence:
-  1. /god-hotfix     Spawn god-debugger for fast triage
-  2. /god-deploy     Push the fix once green
-  3. /god-postmortem Schedule the incident review
+  1. /god-hotfix     Skip planning, debug, fix with TDD, expedited deploy, schedule postmortem
 
 Run this sequence? (yes / show others / cancel)
 ```
@@ -174,15 +224,14 @@ Run this sequence? (yes / show others / cancel)
 ### Example 2: ambiguous intent (multiple matches)
 
 ```
-User: /god add a new feature
+User: /god parallel feature during build
 
-Top matches for "add a new feature":
+Top matches for "parallel feature during build":
 
-  1. add-feature-mid-arc-pause       (15)   Pause /god-mode, run feature, resume
-  2. add-feature-small               (10)   Lightweight feature, no project-run context
-  3. add-feature-next-milestone      (10)   Defer to next milestone
+  1. add-feature-mid-arc-pause       (10)   Bigger feature during the current project run; reconcile with roadmap, pause, do feature, update roadmap, resume
+  2. add-feature-parallel            (10)   Parallel feature, do not disrupt main work
 
-Pick one (1/2/3) or describe more specifically.
+Pick one (1/2) or describe more specifically.
 ```
 
 ### Example 3: state-driven (no text)

package/workflows/audit-only.yaml

@@ -25,9 +25,9 @@ jobs:
     tier: 0
     needs: audit-score
     uses: god-orchestrator@^1.0.0
+    local-helper-groups:
+      - repo-maintenance-closeout
     local-helpers:
-      - repo-doc-sync
-      - repo-surface-sync
       - host-capabilities
     with:
       action: audit-closeout

package/workflows/bluefield-arc.yaml

@@ -133,13 +133,9 @@ jobs:
     tier: 0
     needs: launch
     uses: god-orchestrator@^1.0.0
-    local-helpers:
-      - feature-awareness
-      - repo-doc-sync
-      - repo-surface-sync
-      - host-capabilities
-      - checkpoint-sync
-      - pillars-sync-plan
+    local-helper-groups:
+      - runtime-awareness-closeout
+      - standard-closeout
     with:
       action: final-sync
       dashboard: action-brief

package/workflows/brownfield-arc.yaml

@@ -89,14 +89,10 @@ jobs:
     tier: 0
     needs: steady-state-handoff
     uses: god-orchestrator@^1.0.0
-    local-helpers:
-      - feature-awareness
-      - source-sync-back
-      - repo-doc-sync
-      - repo-surface-sync
-      - host-capabilities
-      - checkpoint-sync
-      - pillars-sync-plan
+    local-helper-groups:
+      - runtime-awareness-closeout
+      - source-sync-closeout
+      - standard-closeout
     with:
       action: final-sync
       dashboard: action-brief

package/workflows/deps-audit.yaml

@@ -59,11 +59,8 @@ jobs:
     tier: 0
     needs: [deps-patch-batch, deps-minor-per-package, deps-major-handoff]
     uses: god-orchestrator@^1.0.0
-    local-helpers:
-      - repo-doc-sync
-      - repo-surface-sync
-      - checkpoint-sync
-      - pillars-sync-plan
+    local-helper-groups:
+      - standard-closeout
     with:
       action: final-sync
       dashboard: action-brief

package/workflows/docs-arc.yaml

@@ -18,9 +18,9 @@ jobs:
   mechanical-doc-sync:
     tier: 0
     uses: god-orchestrator@^1.0.0
+    local-helper-groups:
+      - repo-maintenance-closeout
     local-helpers:
-      - repo-doc-sync
-      - repo-surface-sync
       - host-capabilities
     with:
       action: local-helper-sync