godpowers 1.6.17 → 1.6.20

package/AGENTS.md

@@ -37,11 +37,34 @@ projects from raw idea to hardened production.
 - Every claim must fail the substitution test (swap in a competitor, sentence must break)
 
 <!-- pillars:begin -->
-## Godpowers Pillars Protocol
+# Godpowers Project Context
 
-- [DECISION] Load `agents/context.md` and `agents/repo.md` before Godpowers commands make durable project decisions.
-- [DECISION] Load additional `agents/*.md` pillar files only when their frontmatter matches the task.
-- [DECISION] Treat `.godpowers/state.json`, `.godpowers/PROGRESS.md`, and `.godpowers/CHECKPOINT.md` as workflow state.
-- [DECISION] Treat Pillars files as portable project context for any coding agent that opens this repository.
-- [DECISION] Disk state wins over conversation memory when these sources disagree.
+This is a Godpowers project. Godpowers uses the Pillars standard as its native project context layer.
+Coding agents read project context from `./agents/*.md` before changing code, while `.godpowers/` remains the Godpowers workflow state and artifact layer.
+
+## At the start of any task
+
+1. Load every pillar whose frontmatter has `always_load: true`.
+2. Scan remaining pillar frontmatter and select task-relevant primaries from `triggers` and `covers`.
+3. Add each primary pillar direct `must_read_with` dependencies, depth 1 only.
+4. Read every pillar body in the computed load set.
+5. Read `see_also` pillars only when the task explicitly touches that area.
+6. Follow Rules, apply Workflows, heed Watchouts, and ask before deciding open Gaps.
+
+## Handling missing pillars
+
+| State | Action |
+|---|---|
+| `status: present` | Load and comply. |
+| `status: stub` | Treat the concern as acknowledged but undecided. Ask before making domain decisions. |
+| Name in `excluded:` | Treat as intentionally not applicable. |
+| Relevant but absent | Infer from code, state the assumption, and recommend authoring the pillar. |
+
+If `context.md` or `repo.md` is missing, pause and create stubs before continuing.
+
+## Excluded pillars
+
+```yaml
+excluded: []
+```
 <!-- pillars:end -->

package/CHANGELOG.md

@@ -5,6 +5,72 @@ All notable changes to Godpowers will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+## [1.6.20] - 2026-05-16
+
+Automation surface closeout and release guardrails.
+
+### Added
+- Added `lib/route-quality-sync.js` to detect symbolic route spawns,
+  unresolved agent targets, and unapproved contextual route exits.
+- Added `lib/recipe-coverage-sync.js` to detect missing high-frequency intent
+  recipes for release maintenance, docs drift, context refresh, story work, and
+  automation setup.
+- Added `lib/release-surface-sync.js` to detect release-facing drift across
+  badges, changelog, release notes, package guards, release checklist policy,
+  and package lock version.
+- Added recipe routes for release maintenance, context refresh, story work, and
+  automation setup.
+
+### Changed
+- `/god-party` routing now uses `built-in` as the primary owner and declares
+  selectable specialist personas under `parallel-spawns`.
+- `/god-story-build` routing now uses `god-planner` as primary and declares
+  executor plus reviewer agents as secondary spawns.
+- `lib/router.js` now includes conditional `parallel-spawns` in spawned-agent
+  resolution.
+- Repo surface sync now includes route-quality, recipe-coverage, and
+  release-surface checks.
+
+### Guardrails
+- Route quality checks now block symbolic spawn tokens, unresolved specialist
+  targets, unapproved contextual exits, and durable-writing routes without
+  standards coverage.
+- Release surface checks now require package, lockfile, README badge,
+  changelog, release notes, release checklist, and package payload guards to
+  agree before publish.
+
+## [1.6.19] - 2026-05-16
+
+Repository surface sync and status truth closeout.
+
+### Added
+- Added `lib/repo-surface-sync.js` to detect structural drift across command
+  routing, package payload rules, agent handoffs, workflow metadata, recipe
+  routes, extension packs, and release policy checks.
+- Added `docs/repo-surface-sync.md` with auto-invoke, auto-spawn, and guardrail
+  behavior.
+- Added behavioral tests for missing route detection, explicit route stub
+  creation, sync logging, package checks, agent handoff checks, and current
+  repo freshness.
+
+### Changed
+- `/god-sync`, `/god-docs`, `/god-doctor`, `/god-status`, and `/god-mode` now
+  document repo surface sync behavior.
+- Dashboard proactive checks now include a repo surface status line.
+- Feature awareness now records `repo-surface-sync` as a known runtime feature.
+- Package contents checks now require `lib/repo-surface-sync.js`.
+- README, release notes, command flows, release checklist, command reference,
+  and runtime docs now describe repo surface sync.
+
+### Guardrails
+- Detection is read-only by default.
+- Safe apply can create missing routing stubs only when `fixRouting` is
+  explicitly enabled.
+- Agent, workflow, recipe, extension, and release-policy ambiguity routes to
+  scoped specialists instead of being rewritten blindly.
+
 ## [1.6.17] - 2026-05-16
 
 Autonomous repository documentation sync.

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-1.6.17-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-1.6.20-blue)](CHANGELOG.md)
 [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
 
 **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -12,11 +12,11 @@ idea to hardened production. It runs as **slash commands inside your AI coding
 tool** (Claude Code, Codex, Cursor, etc.) that orchestrate **specialist agents**
 in fresh contexts to do the work.
 
-Version 1.6.17 adds autonomous repository documentation sync. `/god-sync`,
-`/god-docs`, `/god-doctor`, `/god-status`, and `/god-mode` can now detect stale
-README badges, public surface counts, release docs, contribution guidance,
-security policy, and Pillars context planning needs before a project run is
-declared complete.
+Version 1.6.20 closes the automation surface gaps around route quality, recipe
+coverage, and release readiness. Godpowers now checks symbolic route spawns,
+unresolved agent targets, standards coverage for durable-writing routes, missing
+high-frequency recipes, package payload guards, and release-facing version drift
+before closeout.
 
 It fuses four disciplines into one unified workflow:
 
@@ -194,12 +194,13 @@ durable `.godpowers` artifacts change project truth. The decision is logged to
 `.godpowers/YOLO-DECISIONS.md`.
 
 Every completing command now ends with a **Godpowers Dashboard**. It shows the
-current phase, tier, step count, percent complete, PRD and roadmap visibility,
+current phase, tier, step count, workflow progress, PRD and roadmap visibility,
 recent work, proactive checks, open items, and the single recommended next
 action. `/god-status` and `/god-next` use the same shape so the project never
 ends in a vague "done" state. The dashboard is backed by
-`lib/dashboard.js`, so status and next-step commands share one executable
-source of disk truth instead of parallel Markdown-only contracts.
+`lib/dashboard.js`, and the rendered output names that source when the runtime
+engine is available. Audit, hygiene, and remediation scores are reported as
+separate scores rather than being reused as workflow progress.
 
 Godpowers can also inspect automation support:
 
@@ -361,6 +362,7 @@ Pi. T3 Code inherits from the underlying agent (Codex / Claude / OpenCode).
 - [Command reference (all 109 skills + 40 agents)](docs/reference.md)
 - [Feature awareness](docs/feature-awareness.md)
 - [Repository documentation sync](docs/repo-doc-sync.md)
+- [Repository surface sync](docs/repo-surface-sync.md)
 - [Roadmap](docs/ROADMAP.md)
 - [Release Notes](RELEASE.md)
 - [Changelog](CHANGELOG.md)

package/RELEASE.md

@@ -1,19 +1,19 @@
-# Godpowers 1.6.17 Release
+# Godpowers 1.6.20 Release
 
 Date: 2026-05-16
 
-Godpowers 1.6.17 adds autonomous repository documentation sync for release
-surfaces and project-run closeout. Godpowers can now detect stale README badges,
-public surface counts, release notes, changelog entries, contribution guidance,
-security policy, and Pillars context planning needs before a sync, docs, doctor,
-status, or god-mode closeout declares the repository current.
+Godpowers 1.6.20 closes the automation gaps found after repository surface
+sync. It adds dedicated route-quality, recipe-coverage, and release-surface
+checks so Godpowers detects disconnected route spawns, missing intent recipes,
+and stale release-facing documentation before declaring a project or release
+current.
 
 ## What is stable
 
 - 109 slash commands
 - 40 specialist agents
 - 13 executable workflows
-- 36 intent recipes
+- 40 intent recipes
 - 15-runtime installer
 - Codex installs with generated `god-*.toml` agent metadata files
 - Markdown specialist agent contracts at `<runtime>/agents/god-*.md`
@@ -25,57 +25,71 @@ status, or god-mode closeout declares the repository current.
 - Planning-system migration for GSD, BMAD, and Superpowers
 - Managed sync-back companion files for imported source systems
 - Feature awareness for existing Godpowers projects
+- Repository documentation sync checks
+- Repository surface sync checks
+- Route quality, recipe coverage, and release surface sync checks
 
 ## What is new
 
-- Added `lib/repo-doc-sync.js`.
-- Added `docs/repo-doc-sync.md`.
-- Added `scripts/test-repo-doc-sync.js`.
-- Added missing `/god-export-otel` routing metadata.
-- `/god-sync`, `/god-docs`, `/god-doctor`, `/god-status`, and `/god-mode` now
-  document repo documentation sync integration.
-- The dashboard proactive docs check now reads repo documentation sync status.
-- Package contents checks now require the repo documentation sync helper and
-  `/god-export-otel` routing metadata.
-
-## Sync behavior
-
-For a Godpowers repository, the helper:
-
-- reads package version and repository surface counts
-- detects stale mechanical claims in README, user docs, architecture docs,
-  roadmap docs, command reference docs, `/god-version`, and `/god-doctor`
-- applies safe mechanical badge, version, and count refreshes when requested
-- plans Pillars sync for changed repo documentation paths
-- recommends `god-docs-writer` for release notes, changelog, contribution,
-  support, or security policy prose
-
-Detection is read-only by default. Applying sync does not invent narrative
-release notes, changelog entries, contribution policy, support policy, or
-security support policy.
+- Added `lib/route-quality-sync.js`.
+- Added `lib/recipe-coverage-sync.js`.
+- Added `lib/release-surface-sync.js`.
+- Added `scripts/test-automation-surface-sync.js`.
+- Added release maintenance, context refresh, story work, and automation setup
+  recipes.
+- `/god-party` now declares concrete parallel specialist personas.
+- `/god-story-build` now declares planner, executor, and reviewer handoffs
+  without symbolic spawn tokens.
+- Feature awareness now records route quality, recipe coverage, and release
+  surface sync as known runtime features.
+- Package contents checks now require all three new sync helpers.
+
+## Automation surface behavior
+
+For a Godpowers repository, the helper checks:
+
+- every routed specialist spawn resolves to a real agent or built-in runtime
+  owner
+- every durable-writing route declares standards coverage or an approved
+  exemption
+- high-frequency work has discoverable intent recipes
+- release-facing version surfaces agree with `package.json`
+- package content checks require load-bearing runtime helper files
+- release checklist policy names the current sync guards
+
+Detection is read-only by default. Applying sync writes logs and leaves
+judgment-heavy rewrites to scoped specialists.
 
 ## Auto-invoke and auto-spawn policy
 
-Safe repo documentation sync is local runtime work and must be reported as:
+Safe repo surface sync is local runtime work and must be reported as:
 
 ```text
 Agent: none, local runtime only
 ```
 
-Godpowers recommends or spawns `god-docs-writer` only when narrative docs need
-claim verification or policy judgment after local mechanical sync has finished.
+Godpowers recommends scoped specialists only when judgment is needed:
+
+- `god-auditor` for agent contract or handoff drift
+- `god-roadmap-reconciler` for workflow or recipe lifecycle drift
+- `god-coordinator` for extension pack drift
+- `god-docs-writer` for release prose drift
 
 ## Validation
 
 Release validation includes:
 
+- `node scripts/test-repo-surface-sync.js`
+- `node scripts/test-automation-surface-sync.js`
 - `node scripts/test-repo-doc-sync.js`
 - `node scripts/test-feature-awareness.js`
+- `node scripts/test-dashboard.js`
 - `node scripts/test-context-writer.js`
 - `node scripts/test-planning-systems.js`
 - `node scripts/test-doc-surface-counts.js`
 - `node scripts/validate-skills.js`
 - `git diff --check`
+- `npm run release:check`
 
-The `v1.6.17` tag should point to the release commit that matches the npm
-`godpowers@1.6.17` package.
+The `v1.6.20` tag should point to the release commit that matches the npm
+`godpowers@1.6.20` package.

package/SKILL.md

@@ -155,6 +155,7 @@ Proactive checks:
   Reviews: <none | N pending, suggest /god-review-changes>
   Sync: <fresh | missing | stale | local helper ran | suggest /god-sync>
   Docs: <fresh | N stale, suggest /god-docs | repo-doc-sync ran>
+  Repo surface: <fresh | N stale, suggest /god-doctor | repo-surface-sync ran>
   Runtime: <not-applicable | known URL, suggest /god-test-runtime | no known URL, defer deployed verification>
   Automation: <not configured | N active | available via provider, suggest /god-automation-setup>
   Security: <clear | sensitive files changed, suggest /god-harden>
@@ -214,7 +215,7 @@ Auto-invoked:
   Trigger: <what caused this automatic step>
   Agent: <god-updater | god-context-writer | none, local runtime only>
   Local syncs:
-    + <feature-awareness | planning-system-import | reverse-sync | source-sync | repo-doc-sync | pillars-sync | checkpoint-sync | context-refresh>: <result or skipped reason>
+    + <feature-awareness | planning-system-import | reverse-sync | source-sync | repo-doc-sync | repo-surface-sync | route-quality-sync | recipe-coverage-sync | release-surface-sync | pillars-sync | checkpoint-sync | context-refresh>: <result or skipped reason>
   Artifacts: <changed files, no-op, or deferred>
   Log: <SYNC-LOG.md, CHECKPOINT.md, REVIEW-REQUIRED.md, or none>
 ```
@@ -244,6 +245,11 @@ Automatic steps that especially need visible reporting:
   `/god-sync`, or `/god-mode`
 - repo documentation sync during `/god-sync`, `/god-docs`, `/god-doctor`,
   `/god-status`, or `/god-mode`
+- repo surface sync during `/god-sync`, `/god-docs`, `/god-doctor`,
+  `/god-status`, or `/god-mode`
+- route-quality sync, recipe-coverage sync, and release-surface sync through
+  repo-surface sync during `/god-sync`, `/god-docs`, `/god-doctor`,
+  `/god-status`, or `/god-mode`
 
 ### 13. Proactive Auto-Invoke Policy
 Godpowers should be proactive from disk evidence, not from guesswork. Before
@@ -284,6 +290,13 @@ Run these local runtime helpers automatically when their trigger is present:
   `lib/repo-doc-sync.run` during `/god-sync`, `/god-docs`, or `/god-mode`
   when README badges, public surface counts, release docs, contribution docs,
   or security policy may have drifted.
+- `lib/repo-surface-sync.detect` during `/god-status` and `/god-doctor`, and
+  `lib/repo-surface-sync.run` during `/god-sync`, `/god-docs`, or
+  `/god-mode` when command routing, package payload, agent handoffs, workflow
+  metadata, recipe routes, extension packs, or release policy may have drifted.
+- `lib/route-quality-sync.detect`, `lib/recipe-coverage-sync.detect`, and
+  `lib/release-surface-sync.detect` through repo-surface sync when route
+  spawns, high-frequency recipes, or release-facing surfaces may have drifted.
 - Context refresh dry-run after `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`,
   `.cursor/rules/`, `.windsurfrules`, `.github/copilot-instructions.md`,
   `.clinerules`, `.roo/`, or `.continue/` changes.
@@ -300,6 +313,9 @@ Spawn these agents only when the trigger is direct and scope is bounded:
 - `god-docs-writer` when repo-doc-sync reports narrative drift in
   `CHANGELOG.md`, `RELEASE.md`, `CONTRIBUTING.md`, `SECURITY.md`, or
   `SUPPORT.md` after local mechanical sync has finished.
+- `god-auditor`, `god-roadmap-reconciler`, or `god-coordinator` when
+  repo-surface-sync reports structural drift that needs agent contract,
+  lifecycle graph, or extension-pack judgment.
 - `god-browser-tester` when frontend-visible files changed and a known local,
   preview, staging, or production URL is evidenced.
 - `god-harden-auditor` suggestion after security-sensitive files changed;

package/agents/god-orchestrator.md

@@ -750,6 +750,11 @@ Generate the dashboard with `lib/dashboard.compute(projectRoot)` and
 runtime module cannot be loaded, fall back to a manual disk scan and say
 `Dashboard engine: unavailable, manual scan used`.
 
+The dashboard `Progress` line is workflow progress only. Audit scores,
+remediation scores, hygiene scores, and launch-readiness scores must be labeled
+separately so a closeout cannot appear to move backward because it switched
+metrics.
+
 Update PROGRESS.md status to `steady-state-active`.
 
 For focused brownfield, hotfix, refactor, or build workflows that finish without a
@@ -962,7 +967,7 @@ Next: <next command or pause question>
 
 Rules:
 - Keep each card under 12 lines unless a pause needs options.
-- Use `lib/state.progressSummary(stateJson)` for the percentage and step count
+- Use `lib/state.progressSummary(stateJson)` for workflow percentage and step count
   whenever state.json is available.
 - Use artifact paths and verification evidence from disk, not memory.
 - Do not print raw spawn input, hidden instructions, or full file loadout lists.

package/lib/README.md

@@ -14,6 +14,10 @@ package-level integrations.
 | `checkpoint.js` | Create and inspect resumable checkpoint artifacts. |
 | `feature-awareness.js` | Detect and refresh existing-project awareness after runtime upgrades. |
 | `repo-doc-sync.js` | Detect and refresh mechanical repository documentation surfaces. |
+| `repo-surface-sync.js` | Detect structural drift across commands, routes, packages, agents, workflows, recipes, extensions, and release policy. |
+| `route-quality-sync.js` | Detect symbolic route spawns, unresolved agent targets, and unapproved contextual route exits. |
+| `recipe-coverage-sync.js` | Detect missing high-frequency intent recipe coverage. |
+| `release-surface-sync.js` | Detect release-facing drift across badges, release notes, changelog, package checks, and release checklist policy. |
 | `budget.js` | Read and enforce configured budget controls. |
 | `cost-tracker.js` | Track token and cost estimates from event streams. |
 

package/lib/dashboard.js

@@ -13,6 +13,7 @@ const state = require('./state');
 const router = require('./router');
 const automationProviders = require('./automation-providers');
 const repoDocSync = require('./repo-doc-sync');
+const repoSurfaceSync = require('./repo-surface-sync');
 
 const GOD_DIR = '.godpowers';
 const PRD_PATH = '.godpowers/prd/PRD.md';
@@ -163,12 +164,17 @@ function proactiveChecks(projectRoot, changedFiles = []) {
   const repoDocsStatus = repoDocs.status === 'fresh'
     ? 'fresh'
     : `${repoDocs.stale.length} stale, suggest /god-docs`;
+  const repoSurface = repoSurfaceSync.detect(projectRoot);
+  const repoSurfaceStatus = repoSurface.status === 'fresh'
+    ? 'fresh'
+    : `${repoSurface.stale.length} stale, suggest /god-doctor`;
 
   return {
     checkpoint,
     reviews: reviews > 0 ? `${reviews} pending, suggest /god-review-changes` : 'none',
     sync,
     docs: repoDocsStatus,
+    repoSurface: repoSurfaceStatus,
     runtime: 'not-applicable',
     automation: automationSummary(projectRoot),
     security: sensitiveChanged ? 'sensitive files changed, suggest /god-harden' : 'clear',
@@ -200,7 +206,8 @@ function planningVisibility(projectRoot, progress) {
     prd: { status: prd, path: prd === 'done' ? PRD_PATH : null },
     roadmap: { status: roadmap, path: roadmap === 'done' ? ROADMAP_PATH : null },
     currentMilestone: phase.stepLabel ? `${phase.phase} / ${phase.stepLabel}` : phase.phase,
-    completion: `${progress.percent}% based on state.json tracked steps`
+    completion: `${progress.percent}% workflow progress from .godpowers/state.json tracked steps`,
+    completionBasis: '.godpowers/state.json workflow steps'
   };
 }
 
@@ -211,6 +218,7 @@ function compute(projectRoot, opts = {}) {
   if (!s) {
     const next = { command: '/god-init', reason: 'No Godpowers project initialized' };
     return {
+      source: 'runtime dashboard (lib/dashboard.js)',
       state: 'not initialized',
       mode: null,
       lifecycle: 'pre-init',
@@ -222,7 +230,8 @@ function compute(projectRoot, opts = {}) {
         prd: { status: 'missing', path: null },
         roadmap: { status: 'missing', path: null },
         currentMilestone: 'Project initialization',
-        completion: '0% based on missing state.json'
+        completion: '0% workflow progress because .godpowers/state.json is missing',
+        completionBasis: 'missing .godpowers/state.json'
       },
       proactive: proactiveChecks(projectRoot, git.entries.map(statusPath)),
       next,
@@ -242,6 +251,7 @@ function compute(projectRoot, opts = {}) {
   if (openItems.length === 0) openItems.push('none');
 
   return {
+    source: 'runtime dashboard (lib/dashboard.js)',
     state: progress.remaining === 0 ? 'complete' : 'in progress',
     mode: s.mode || s['mode-announced-as'] || null,
     lifecycle: s['lifecycle-phase'] || 'in-arc',
@@ -271,11 +281,13 @@ function render(dashboard) {
   return [
     'Godpowers Dashboard',
     '',
+    `Source: ${dashboard.source || 'manual disk scan'}`,
+    '',
     'Current status:',
     `  State: ${dashboard.state}`,
     `  Phase: ${current.phase || 'unknown'}${current.tierNumber !== null && current.tierNumber !== undefined ? ` (tier ${current.tierOrdinal} of ${current.tierCount}, internal ${current.tierKey || `tier-${current.tierNumber}`})` : ''}`,
     `  Step: ${current.stepLabel || 'unknown'}${current.stepNumber ? ` (step ${current.stepNumber} of ${current.totalSteps})` : ''}`,
-    `  Progress: ${progress.percent || 0}% (${progress.completed || 0} of ${progress.total || 0} steps complete)`,
+    `  Progress: ${progress.percent || 0}% workflow progress (${progress.completed || 0} of ${progress.total || 0} tracked steps complete)`,
     `  Worktree: ${dashboard.worktree}`,
     `  Index: ${dashboard.index}`,
     '',
@@ -283,13 +295,14 @@ function render(dashboard) {
     `  PRD: ${prd.status || 'missing'}${prd.path ? ` ${prd.path}` : ''}`,
     `  Roadmap: ${roadmap.status || 'missing'}${roadmap.path ? ` ${roadmap.path}` : ''}`,
     `  Current milestone: ${planning.currentMilestone || 'unknown'}`,
-    `  Completion: ${planning.completion || 'unknown'}`,
+    `  Completion basis: ${planning.completionBasis || planning.completion || 'unknown'}`,
     '',
     'Proactive checks:',
     `  Checkpoint: ${proactive.checkpoint || 'unknown'}`,
     `  Reviews: ${proactive.reviews || 'unknown'}`,
     `  Sync: ${proactive.sync || 'unknown'}`,
     `  Docs: ${proactive.docs || 'unknown'}`,
+    `  Repo surface: ${proactive.repoSurface || 'unknown'}`,
     `  Runtime: ${proactive.runtime || 'unknown'}`,
     `  Automation: ${proactive.automation || 'unknown'}`,
     `  Security: ${proactive.security || 'unknown'}`,

package/lib/feature-awareness.js

@@ -40,6 +40,30 @@ const FEATURES = [
     since: '1.6.17',
     commands: ['/god-sync', '/god-docs', '/god-doctor', '/god-status', '/god-mode'],
     description: 'Detect and refresh repository documentation surfaces, release docs, and Pillars planning signals.'
+  },
+  {
+    id: 'repo-surface-sync',
+    since: '1.6.19',
+    commands: ['/god-sync', '/god-docs', '/god-doctor', '/god-status', '/god-mode'],
+    description: 'Detect structural drift across routing, packages, agents, workflows, recipes, extensions, and release policy.'
+  },
+  {
+    id: 'route-quality-sync',
+    since: '1.6.19',
+    commands: ['/god-sync', '/god-doctor', '/god-status', '/god-mode'],
+    description: 'Detect symbolic route spawns, unresolved agent targets, and unapproved contextual route exits.'
+  },
+  {
+    id: 'recipe-coverage-sync',
+    since: '1.6.19',
+    commands: ['/god-sync', '/god-doctor', '/god-status', '/god-mode'],
+    description: 'Detect missing intent recipes for release, docs, context refresh, story work, and automation setup.'
+  },
+  {
+    id: 'release-surface-sync',
+    since: '1.6.19',
+    commands: ['/god-sync', '/god-docs', '/god-doctor', '/god-status', '/god-mode'],
+    description: 'Detect release-facing drift across badges, release notes, changelog, package checks, and release checklist policy.'
   }
 ];
 

package/lib/recipe-coverage-sync.js

@@ -0,0 +1,149 @@
+/**
+ * Recipe coverage sync.
+ *
+ * Keeps fuzzy user intent connected to shipped command routes for the
+ * high-frequency areas that users naturally ask for in prose.
+ */
+
+const fs = require('fs');
+const path = require('path');
+
+const recipes = require('./recipes');
+
+const LOG_PATH = '.godpowers/surface/RECIPE-COVERAGE-SYNC.md';
+
+const REQUIRED_COVERAGE = [
+  {
+    id: 'release-maintenance',
+    description: 'release maintenance',
+    commands: ['/god-sync', '/god-docs', '/god-version']
+  },
+  {
+    id: 'docs-drift',
+    description: 'documentation drift',
+    commands: ['/god-docs']
+  },
+  {
+    id: 'context-refresh',
+    description: 'context refresh and feature awareness',
+    commands: ['/god-context', '/god-sync', '/god-status']
+  },
+  {
+    id: 'story-work',
+    description: 'story creation, build, verify, and close',
+    commands: ['/god-story', '/god-story-build', '/god-story-verify', '/god-story-close']
+  },
+  {
+    id: 'automation-setup',
+    description: 'automation setup and status',
+    commands: ['/god-automation-setup', '/god-automation-status']
+  }
+];
+
+function read(projectRoot, relPath) {
+  const file = path.join(projectRoot, relPath);
+  if (!fs.existsSync(file)) return '';
+  return fs.readFileSync(file, 'utf8');
+}
+
+function write(projectRoot, relPath, content) {
+  const file = path.join(projectRoot, relPath);
+  fs.mkdirSync(path.dirname(file), { recursive: true });
+  fs.writeFileSync(file, content);
+}
+
+function addCheck(checks, id, status, relPath, message, opts = {}) {
+  checks.push({
+    area: 'recipe-coverage',
+    id,
+    status,
+    path: relPath,
+    message,
+    severity: opts.severity || (status === 'fresh' ? 'info' : 'warning'),
+    spawn: opts.spawn || null
+  });
+}
+
+function recipePath(projectRoot, name) {
+  const rel = `routing/recipes/${name}.yaml`;
+  return fs.existsSync(path.join(projectRoot, rel)) ? rel : 'routing/recipes/';
+}
+
+function detect(projectRoot) {
+  recipes.clearCache();
+  const checks = [];
+  const all = recipes.loadAll();
+  const recipeTexts = new Map();
+  for (const recipe of all) {
+    const name = recipe.metadata && recipe.metadata.name;
+    if (!name) continue;
+    recipeTexts.set(name, read(projectRoot, `routing/recipes/${name}.yaml`));
+  }
+
+  for (const required of REQUIRED_COVERAGE) {
+    const matched = [...recipeTexts.entries()].filter(([, text]) =>
+      required.commands.every((command) => text.includes(command))
+    );
+    addCheck(
+      checks,
+      `coverage-${required.id}`,
+      matched.length > 0 ? 'fresh' : 'stale',
+      matched.length > 0 ? `routing/recipes/${matched[0][0]}.yaml` : recipePath(projectRoot, required.id),
+      matched.length > 0
+        ? `Recipe coverage exists for ${required.description}.`
+        : `No recipe covers ${required.description} with ${required.commands.join(', ')}.`,
+      { spawn: matched.length > 0 ? null : 'god-roadmap-reconciler' }
+    );
+  }
+
+  const stale = checks.filter((check) => check.status !== 'fresh');
+  return {
+    status: stale.length === 0 ? 'fresh' : 'stale',
+    checks,
+    stale
+  };
+}
+
+function appendLog(projectRoot, before, after) {
+  const now = new Date().toISOString();
+  const lines = [];
+  if (fs.existsSync(path.join(projectRoot, LOG_PATH))) {
+    lines.push(read(projectRoot, LOG_PATH).replace(/\s*$/, ''));
+    lines.push('');
+  } else {
+    lines.push('# Recipe Coverage Sync Log');
+    lines.push('');
+    lines.push('- [DECISION] This file records recipe-coverage sync checks run by Godpowers.');
+    lines.push('');
+  }
+  lines.push(`## ${now}`);
+  lines.push('');
+  lines.push(`- [DECISION] Recipe coverage status before apply was ${before.status}.`);
+  lines.push(`- [DECISION] Recipe coverage status after apply is ${after.status}.`);
+  lines.push('');
+  write(projectRoot, LOG_PATH, lines.join('\n'));
+}
+
+function run(projectRoot, opts = {}) {
+  const before = detect(projectRoot);
+  const after = detect(projectRoot);
+  if (opts.log !== false) appendLog(projectRoot, before, after);
+  return {
+    before,
+    after,
+    applied: [],
+    logPath: opts.log === false ? null : LOG_PATH
+  };
+}
+
+function summary(report) {
+  return report.status === 'fresh' ? 'fresh' : `${report.stale.length} stale`;
+}
+
+module.exports = {
+  LOG_PATH,
+  REQUIRED_COVERAGE,
+  detect,
+  run,
+  summary
+};