godpowers 1.6.22 → 1.6.24

package/AGENTS.md

@@ -15,10 +15,14 @@ projects from raw idea to hardened production.
 
 - `SKILL.md` is the main entry point, loaded by AI coding tools
 - `skills/` contains individual command skills (one per file)
+- `routing/` contains command routing metadata and intent recipes
+- `workflows/` contains executable workflow YAML
 - `references/` contains per-tier reference material (antipatterns, examples)
 - `bin/` contains the CLI installer and `god` command
+- `lib/` contains executable runtime helpers, sync checks, dogfood, dashboard, and release logic
 - `scripts/` contains validation and testing scripts
 - `templates/` contains artifact templates
+- `fixtures/dogfood/` contains messy-repo release dogfood scenarios
 
 ## Conventions
 
@@ -27,6 +31,8 @@ projects from raw idea to hardened production.
 - Every tier skill documents its have-nots (failure modes)
 - Artifacts are written to `.godpowers/<tier>/` paths
 - State is tracked in `.godpowers/PROGRESS.md`
+- Dashboard state is computed by `lib/dashboard.js`
+- Repo docs, repo surface, route quality, recipe coverage, release surface, host capability, and dogfood checks are executable release gates
 - Disk state is authoritative; conversation memory is not
 
 ## Quality Rules

package/CHANGELOG.md

@@ -7,6 +7,80 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.6.24] - 2026-05-16
+
+Strict background release readiness.
+
+### Added
+- Added the `strict-release-readiness` automation template so delegated or
+  scheduled release checks fail closed when any required release surface is
+  unchecked, stale, missing, untested, or inconsistent with the intended
+  version.
+- Added a required release-surface manifest for root docs, docs, agents,
+  skills, routing, workflows, schema, templates, references, hooks, lib,
+  scripts, tests, fixtures, GitHub workflows, package metadata, npm latest,
+  git tag state, GitHub release state, CI, publish workflow, and local install
+  state.
+
+### Changed
+- `/god-automation-setup` now recommends `strict-release-readiness` for
+  background release checks and keeps the narrower `release-readiness`
+  template reserved for quick manual checks.
+- The release maintenance recipe now routes background-release setup through
+  `/god-automation-setup` with an explicit no-publish guardrail.
+- Auto-invoke visibility docs now classify strict release readiness as a
+  read-only, fail-closed Level 2 automation candidate.
+- The release checklist now names every folder and published surface that must
+  be checked before packaging, tagging, pushing, releasing, or publishing.
+
+### Guardrails
+- Added behavioral coverage that verifies the strict release readiness
+  template exists, is fail-closed, refuses file mutation, and names every
+  required release surface.
+- The strict readiness template may report blockers and exact next commands,
+  but it must not modify files, stage, commit, tag, push, create a GitHub
+  release, publish to npm, delete files, clear caches, or change installs.
+
+## [1.6.23] - 2026-05-16
+
+Full repository audit, release gate hardening, and documentation repair.
+
+### Added
+- Added `.planning/2026-05-16-surface-sync-status.md` to record the current
+  `.github/workflows`, `.planning`, and `agents` sync status without rewriting
+  historical planning evidence.
+- Expanded `god-reconciler` and `god-updater` contracts so repo docs, repo
+  surface, runtime feature awareness, source-system sync-back, host capability,
+  and dashboard refresh are checked and reported as part of the same loop.
+- Documented the audited source scan across root docs, `.github`, `.godpowers`,
+  `.planning`, agents, docs, examples, extensions, fixtures, hooks, lib,
+  references, routing, schema, scripts, skills, templates, tests, and workflows.
+
+### Changed
+- Release workflows now run `npm run release:check` before publishing the root
+  package or first-party extension packs.
+- `prepublishOnly` now runs the full release gate instead of only `npm test`.
+- `/god-reconcile`, `/god-mode`, the orchestrator, agent specs, and roadmap
+  now describe the expanded local sync surfaces consistently.
+- Version, badge, roadmap, architecture, user-support, and reference surfaces
+  now align to 1.6.23.
+
+### Fixed
+- Repaired stale 1.6.19 and 1.6.22 current-version claims in runtime docs.
+- Removed literal forbidden dash and emoji characters from primary source
+  files while preserving validator coverage through Unicode escape sequences.
+- Repaired release documentation drift around package contents, route quality,
+  recipe coverage, release-surface checks, dogfood, host guarantees, extension
+  authoring, and Mode D suite release dry-runs.
+
+### Guardrails
+- Primary source scan now covers 639 tracked plus untracked source files and
+  verifies zero forbidden dash characters, zero emoji characters, zero invalid
+  JSON files, zero CRLF files, zero missing final newlines, and zero zero-byte
+  files.
+- `npm run release:check` remains the one-command release gate before commit,
+  tag, npm publish, and GitHub release creation.
+
 ## [1.6.22] - 2026-05-16
 
 Dogfooding, host guarantees, extension authoring, and suite release dry-runs.

package/INSPIRATION.md

@@ -33,6 +33,12 @@ Beyond what was inherited, godpowers added:
   for the case where Impeccable is not installed
 - **AI-tool context writer** that maintains fenced sections in
   AGENTS.md / CLAUDE.md / GEMINI.md and 11 other tool-specific paths
+- **Feature awareness and host guarantee reporting** so existing projects and
+  AI coding hosts can state what Godpowers capabilities are actually available
+- **Messy-repo dogfood fixtures** for GSD migration, sync-back, extension
+  authoring, host capability, and Mode D suite release dry-run behavior
+- **Autonomous repo documentation and surface sync** for badges, route
+  metadata, recipes, package payloads, release gates, and extension packs
 
 ## Why this is the only mention
 

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.22-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-1.6.24-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,10 +12,12 @@ 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.22 turns the last "needs more outside use" gaps into executable
-surface area. Godpowers now ships a messy-repo dogfood runner, dashboard host
-guarantee reporting, compact dashboard output, extension scaffolding, and
-Mode D suite release dry-run planning.
+Version 1.6.24 makes background release readiness strict and fail-closed.
+Godpowers now requires delegated release checks to cover root docs, docs,
+agents, skills, routing, workflows, schema, templates, references, hooks, lib,
+scripts, tests, fixtures, GitHub workflows, package metadata, npm, GitHub
+release, CI, publish workflow, and local install state before a human-approved
+release executor can run.
 
 The dashboard now starts with an action brief and a host guarantee line: the
 next command, why it is recommended, whether the project is ready, the first

package/RELEASE.md

@@ -1,11 +1,12 @@
-# Godpowers 1.6.22 Release
+# Godpowers 1.6.24 Release
 
 Date: 2026-05-16
 
-Godpowers 1.6.22 turns the remaining "needs more real use" risks into
-executable surfaces. It adds deterministic messy-repo dogfooding, dashboard
-host guarantees, compact status output, extension authoring scaffolds, and
-Mode D suite release dry-run planning.
+Godpowers 1.6.24 turns release readiness automation into a strict,
+fail-closed background check. It packages the lesson from the 1.6.23 release:
+release readiness cannot be inferred from README, package metadata, and
+changelog alone. Every owned repo surface must be checked or the release is
+blocked.
 
 ## What is stable
 
@@ -34,79 +35,51 @@ Mode D suite release dry-run planning.
 - Messy-repo dogfood scenarios
 - Extension authoring scaffold helper
 - Mode D suite release dry-run planner
+- Release gate enforcement through `npm run release:check`
 
 ## What is new
 
-- Added `lib/dogfood-runner.js`, `/god-dogfood`, and CLI `dogfood`.
-- Added dogfood fixtures for half-migrated GSD import and sync-back, full and
-  degraded host guarantees, extension scaffold validation, and suite release
-  dry-run planning.
-- Added `lib/host-capabilities.js` and dashboard host guarantee reporting.
-- Added compact dashboard output through `--brief`.
-- Added `lib/extension-authoring.js` and CLI `extension-scaffold`.
-- Added `suiteState.planRelease` for Mode D dependent impact planning before
-  mutation.
-
-## 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 agent-spawning route declares `agent.start` and `agent.end`
-- 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
-- release gates include dogfood, extension publish, Mode D suite, and installer
-  smoke checks
-- dogfood fixtures cover migration, host guarantees, extension authoring, and
-  suite release dry-runs
-- host guarantees are visible in dashboard and compact dashboard output
-
-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 surface sync is local runtime work and must be reported as:
-
-```text
-Agent: none, local runtime only
-```
-
-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
-- `god-greenfieldifier` for dogfood migration failures
-- `god-context-writer` for host capability failures
+- Added `strict-release-readiness` to the safe automation templates.
+- Added a strict release-surface manifest that covers root docs, docs, agents,
+  skills, routing, workflows, schema, templates, references, hooks, lib,
+  scripts, tests, fixtures, GitHub workflows, package metadata, npm latest, git
+  tag state, GitHub release state, CI status, publish workflow status, and
+  local install state.
+- Updated `/god-automation-setup` so background release checks use the strict
+  template by default.
+- Updated the release maintenance recipe so background release setup goes
+  through `/god-automation-setup` and keeps publishing behind explicit human
+  approval.
+- Updated auto-invoke visibility docs so strict release readiness is a Level 2
+  read-only local automation candidate.
+
+## Guardrails
+
+- Strict release readiness fails closed when any required surface is unchecked,
+  stale, missing, untested, or inconsistent with the intended version.
+- Strict release readiness reports blockers and exact next commands only.
+- Strict release readiness must not modify files, stage, commit, tag, push,
+  create a GitHub release, publish to npm, delete files, clear caches, or
+  change runtime installs.
+- Behavioral tests verify that the strict template is fail-closed, read-only,
+  and names every required release surface.
 
 ## Validation
 
 Release validation includes:
 
-- `node scripts/test-dogfood-runner.js`
-- `node scripts/test-host-capabilities.js`
-- `node scripts/test-extension-authoring.js`
-- `node scripts/test-repo-surface-sync.js`
+- `node scripts/test-automation-providers.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-mode-d.js`
-- `node scripts/test-extensions-publish.js`
-- `node scripts/test-install-smoke.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`
+- `node scripts/test-recipes.js`
+- source scan for forbidden dash characters in edited files
 - `npm run release:check`
-
-The `v1.6.22` tag should point to the release commit that matches the npm
-`godpowers@1.6.22` package.
+- `npm pack --json`
+- npm cache clear before local install
+- local uninstall and reinstall from the generated tarball
+- tag-triggered npm publish workflow with provenance
+- npm registry verification after publish
+- local uninstall and reinstall from `godpowers@1.6.24`
+- all-runtime `godpowers --all` refresh after published install
+
+The `v1.6.24` tag should point to the release commit that matches the npm
+`godpowers@1.6.24` package.

package/SKILL.md

@@ -120,9 +120,9 @@ When the runtime bundle is available, compute this with
 `lib/dashboard.compute(projectRoot)` and render it with
 `lib/dashboard.render(result)`. The executable dashboard engine is the shared
 source for phase, tier, step, progress, PRD and roadmap visibility, proactive
-checks, open items, and the next route. If the runtime module is unavailable,
-fall back to a manual disk scan and say `Dashboard engine: unavailable, manual
-scan used`.
+checks, host guarantees, open items, and the next route. If the runtime module
+is unavailable, fall back to a manual disk scan and say `Dashboard engine:
+unavailable, manual scan used`.
 
 Use this shape:
 
@@ -137,6 +137,13 @@ Current status:
   Worktree: <clean | modified files unstaged | staged changes | mixed>
   Index: <untouched | staged files listed>
 
+Action brief:
+  Next: <recommended command or user decision>
+  Why: <route reason tied to disk state>
+  Readiness: <ready | needs attention>
+  Attention: <top blockers or none>
+  Host guarantees: <full | degraded | unknown with host and first gap>
+
 Planning visibility:
   PRD: <done | pending | missing | deferred> <artifact path when present>
   Roadmap: <done | pending | missing | deferred> <artifact path when present>
@@ -156,6 +163,7 @@ Proactive checks:
   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>
+  Host: <full | degraded | unknown with host and first gap>
   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>
@@ -215,7 +223,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 | repo-surface-sync | route-quality-sync | recipe-coverage-sync | release-surface-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 | host-capabilities | dogfood-runner | 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>
 ```
@@ -250,6 +258,10 @@ Automatic steps that especially need visible reporting:
 - 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`
+- host capability detection during `/god-status`, `/god-next`, and closeout
+  dashboards
+- dogfood runner execution during `/god-dogfood`, release checks, or explicit
+  dogfood requests
 
 ### 13. Proactive Auto-Invoke Policy
 Godpowers should be proactive from disk evidence, not from guesswork. Before
@@ -297,6 +309,10 @@ Run these local runtime helpers automatically when their trigger is present:
 - `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.
+- `lib/host-capabilities.detect` during dashboard computation so runtime
+  guarantees are visible before Godpowers claims autonomy.
+- `lib/dogfood-runner.runAll` during explicit `/god-dogfood`, release checks,
+  or user-requested dogfood verification.
 - Context refresh dry-run after `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`,
   `.cursor/rules/`, `.windsurfrules`, `.github/copilot-instructions.md`,
   `.clinerules`, `.roo/`, or `.continue/` changes.
@@ -332,6 +348,10 @@ Spawn these agents only when the trigger is direct and scope is bounded:
   artifacts after local import.
 - `god-greenfieldifier` when feature-awareness detects unimported or imported
   source-system context that is low confidence or conflicting.
+- `god-greenfieldifier` when dogfood migration scenarios fail.
+- `god-context-writer` when host capability dogfood scenarios fail.
+- `god-coordinator` when extension authoring or suite release dogfood
+  scenarios fail.
 
 #### Level 4: Explicit approval required
 Never auto-run these from inference alone:

package/agents/god-orchestrator.md

@@ -643,10 +643,13 @@ ecosystem.
 Before declaring the project run complete, ALWAYS run /god-sync:
 
 1. Spawn god-updater in fresh context
-2. Verify final consistency across all 14 artifact categories:
+2. Verify final consistency across all 14 core artifact categories and local
+   sync surfaces:
    - All Tier 1-3 artifacts written and pass have-nots
    - Capture artifacts (BACKLOG, SEEDS, TODOS, THREADS) noted as
      "not-yet-created" if absent (graceful, not a failure)
+   - Repo docs, repo surface, feature awareness, source sync-back, host
+     capability, checkpoint, Pillars, and context refresh statuses reported
 3. Update SYNC-LOG.md with the project-run completion entry
 4. Update state.json with all final tier statuses
 
@@ -685,19 +688,28 @@ Godpowers project run complete.
 
 Godpowers Dashboard
 
+Source: runtime dashboard (lib/dashboard.js)
+
 Current status:
   State: complete
   Phase: <plain-language phase> (tier <human ordinal> of <human total>)
   Step: <sub-step label> (step <n> of <total steps>)
-  Progress: <pct>% (<done> of <total> steps complete)
+  Progress: <pct>% workflow progress (<done> of <total> tracked steps complete)
   Worktree: <clean | modified files unstaged | staged changes | mixed>
   Index: <untouched | staged files listed>
 
+Action brief:
+  Next: <one command or user decision>
+  Why: <one sentence tied to disk state>
+  Readiness: <ready | needs attention>
+  Attention: <none or top blockers>
+  Host guarantees: <full | degraded | unknown>
+
 Planning visibility:
   PRD: <done | pending | missing | deferred> <artifact path when present>
   Roadmap: <done | pending | missing | deferred> <artifact path when present>
   Current milestone: <roadmap milestone, tier, or next planning gate when known>
-  Completion: <pct>% <brief basis, for example done steps over total tracked steps>
+  Completion basis: <state.json, PROGRESS.md, artifacts, or audit score source>
 
 What changed:
   1. <highest-signal user-visible change>
@@ -711,6 +723,9 @@ Proactive checks:
   Reviews: <none | N pending, suggest /god-review-changes>
   Sync: <fresh | suggested | local helper ran>
   Docs: <fresh | suggested | drift-check spawned>
+  Repo surface: <fresh | stale, suggest /god-doctor>
+  Host: <full | degraded | unknown>
+  Dogfood: <not-run | pass | fail | suggest /god-dogfood>
   Runtime: <not-applicable | suggested | browser test spawned>
   Security: <clear | suggested | harden spawned>
   Dependencies: <clear | suggested | deps audit spawned>

package/agents/god-reconciler.md

@@ -3,9 +3,10 @@ name: god-reconciler
 description: |
   Comprehensive reconciliation across ALL impacted artifacts before feature
   work. Checks PRD, ARCH, ROADMAP, STACK, REPO, DEPLOY, OBSERVE, HARDEN,
-  LAUNCH, BACKLOG, SEEDS, TODOS, THREADS in parallel. Returns multi-
-  dimensional verdict so user knows every place the work intersects with
-  existing artifacts.
+  LAUNCH, BACKLOG, SEEDS, TODOS, THREADS, repository documentation,
+  repository surface, feature awareness, host capability, and source-system
+  sync-back in parallel. Returns multi-dimensional verdict so user knows every
+  place the work intersects with existing artifacts.
 
   Spawned by: /god-reconcile, recipe execution (feature-addition category)
 tools: Read, Bash, Grep, Glob, Task
@@ -25,6 +26,8 @@ A feature addition often impacts multiple artifacts:
 - STACK may need a new dependency
 - BACKLOG may already capture the intent
 - SEEDS may trigger a planted seed
+- README, release notes, schemas, workflows, recipes, and installed-project
+  feature awareness may need mechanical sync
 
 If we don't check all of these, we get drift. Roadmap says one thing, PRD
 says another, code does a third.
@@ -120,6 +123,38 @@ For each artifact below, check (in parallel where possible):
 - Is there an active thread about this topic?
 - Verdict: no-thread / active-thread (with thread name)
 
+### Runtime and repository surface artifacts
+
+#### REPO DOCS (`README.md`, `CHANGELOG.md`, `RELEASE.md`, docs, support files)
+- Does this work change public counts, badges, release status, install
+  guidance, contributor guidance, or support policy?
+- Verdict: fresh / needs-mechanical-sync / needs-docs-writer
+- If narrative release or support docs need judgment: recommend
+  `god-docs-writer`.
+
+#### REPO SURFACE (`skills/`, `agents/`, `routing/`, `workflows/`, `schema/`, `package.json`)
+- Did the work add, rename, remove, or change a command, agent, workflow,
+  recipe, schema, package file entry, extension, or release helper?
+- Verdict: fresh / needs-surface-sync / needs-safe-fix / needs-human-review
+- If stale checks are mechanical: recommend `lib/repo-surface-sync.run`.
+
+#### FEATURE AWARENESS (`.godpowers/state.json`, context fences)
+- Does an existing Godpowers project need to learn about new runtime features?
+- Verdict: fresh / needs-awareness-refresh / needs-migration-judgment
+- If imported planning systems have low confidence or conflicts: recommend
+  `god-greenfieldifier`.
+
+#### SOURCE SYSTEM SYNC-BACK (GSD, BMAD, Superpowers)
+- Did migrated source-system summaries need managed sync-back?
+- Verdict: not-applicable / fresh / needs-sync-back / blocked-by-conflict
+- If conflicts exist: recommend greenfieldifier review before writes.
+
+#### HOST CAPABILITY (`lib/host-capabilities.js`)
+- Does the work depend on a host feature such as fresh-context spawning,
+  local shell, GitHub CLI, npm, or extension authoring?
+- Verdict: full / degraded / unknown
+- If degraded: include the missing guarantee in the recommendation.
+
 ## Output
 
 Return structured JSON to the orchestrating skill:
@@ -141,6 +176,11 @@ Return structured JSON to the orchestrating skill:
   "seeds": { "status": "no-seeds" },
   "todos": { "status": "supersedes-todo", "match": "P1: refactor auth middleware" },
   "threads": { "status": "active-thread", "match": "auth migration" },
+  "repo_docs": { "status": "needs-mechanical-sync", "action": "run repo-doc-sync" },
+  "repo_surface": { "status": "needs-surface-sync", "action": "run repo-surface-sync" },
+  "feature_awareness": { "status": "needs-awareness-refresh", "action": "run feature-awareness" },
+  "source_sync_back": { "status": "not-applicable" },
+  "host_capability": { "status": "degraded", "gap": "fresh-context agent spawn not detected" },
   "recommendation": {
     "primary-action": "/god-feature scoped to Milestone 2",
     "preflight": [
@@ -148,7 +188,7 @@ Return structured JSON to the orchestrating skill:
       "/god-arch with mode=delta-only (add component + ADR)"
     ],
     "post-work": [
-      "/god-sync (update all affected artifacts)"
+      "/god-sync (update all affected artifacts and local sync surfaces)"
     ]
   }
 }
@@ -175,12 +215,17 @@ Where this intersects existing artifacts:
   SEEDS:      no triggers
   TODOS:      supersedes "refactor auth middleware"
   THREADS:    relates to active thread "auth migration"
+  REPO DOCS:  needs mechanical sync
+  SURFACE:    needs repo-surface sync
+  FEATURES:   awareness refresh needed
+  SOURCE:     no sync-back needed
+  HOST:       degraded - fresh-context agent spawn not detected
 
 Recommended sequence:
   1. /god-redo prd            (add requirement)
   2. /god-arch delta-only     (architecture delta)
   3. /god-feature             (build it, scoped to Milestone 2)
-  4. /god-sync                (update all touched artifacts)
+  4. /god-sync                (update all touched artifacts and local sync surfaces)
 
 Run this sequence? (yes / show alternatives / cancel)
 ```
@@ -224,6 +269,8 @@ For feature-addition category recipes: ALWAYS reconcile.
 Reconciliation FAILS if:
 - Returns "all covered" without checking each artifact
 - Skips an artifact silently (must report status for each)
+- Skips repo docs, repo surface, feature awareness, source sync-back, or host
+  capability when the work affects them
 - Recommends bypass without justification
 - Missing prerequisite check
 - Doesn't surface ambiguous cases

package/agents/god-updater.md

@@ -4,8 +4,9 @@ description: |
   After feature work, syncs all affected artifacts: PRD (add requirement),
   ARCH (add ADR/delta), ROADMAP (mark progress, append entries), STACK
   (add deps), DEPLOY/OBSERVE/HARDEN/LAUNCH (note new surface), TODOS
-  (resolve superseded), THREADS (update). Re-validates have-nots after
-  each update.
+  (resolve superseded), THREADS (update), repository documentation, runtime
+  feature awareness, source-system sync-back, host capability notes, and
+  repository surface checks. Re-validates have-nots after each update.
 
   Spawned by: /god-sync, end of feature-addition recipe execution
 tools: Read, Write, Edit, Bash, Grep, Glob, Task
@@ -20,6 +21,9 @@ After feature work, every artifact that was impacted needs to reflect reality.
 - The reconciliation verdict (from god-reconciler) showing which artifacts changed
 - Description of what was just done (commits, slice plans, etc.)
 - Project root
+- Changed files, when the caller can provide them
+- Trigger type: manual `/god-sync`, closeout from `/god-mode`, release work,
+  migration import, hotfix, or docs-only sync
 
 ## Operations (per artifact, conditional)
 
@@ -118,6 +122,74 @@ After feature work, every artifact that was impacted needs to reflect reality.
   - drift findings
   - REVIEW-REQUIRED.md items created
 
+### Repository documentation sync
+- Call `lib/repo-doc-sync.run(projectRoot, { changedFiles })` when the runtime
+  is available. Use detect-only mode when the caller is in read-only audit mode.
+- Safe mechanical fixes may update version badges, package description counts,
+  README command counts, reference counts, and shipped-version markers.
+- Narrative drift in release notes, changelog, contribution policy, security
+  policy, or support docs must spawn or recommend `god-docs-writer`.
+- Emit or preserve the local log at `.godpowers/docs/REPO-DOC-SYNC.md`.
+- Report:
+  - status: fresh, stale, applied, or skipped
+  - safe fixes applied
+  - narrative paths requiring a docs writer
+  - Pillars sync plan count when touched docs affect portable context
+
+### Repository surface sync
+- Call `lib/repo-surface-sync.run(projectRoot, { changedFiles })` when the
+  runtime is available.
+- This checks routing, package file entries, package content checks, agent
+  contracts, workflow metadata, recipe coverage, extension publish readiness,
+  route quality, release surface, and repository documentation drift.
+- Safe local fixes may write missing routing stubs only when explicitly allowed
+  by the caller.
+- Emit or preserve the local log at `.godpowers/surface/REPO-SURFACE-SYNC.md`.
+- Report:
+  - status: fresh, stale, applied, or skipped
+  - stale checks by area
+  - spawn recommendations
+  - whether route, recipe, release, and documentation sub-checks were fresh
+
+### Runtime feature awareness
+- Call `lib/feature-awareness.run(projectRoot)` for existing `.godpowers`
+  projects when the runtime is available.
+- Record the installed runtime version, the current feature-set version, and
+  known feature IDs into `.godpowers/state.json`.
+- Refresh AI-tool context fences only through `god-context-writer` or
+  `lib/context-writer.js`; do not hand-edit outside managed fences.
+- If low-confidence imported planning systems or sync-back conflicts are
+  detected, spawn or recommend `god-greenfieldifier`.
+- Report:
+  - runtime version
+  - missing features before refresh
+  - whether state changed
+  - context files refreshed or skipped
+
+### Source-system sync-back
+- Call `lib/source-sync.run(projectRoot)` when `.godpowers/state.json`
+  declares GSD, BMAD, Superpowers, or other source-system records.
+- Write only managed Godpowers summary sections back to source systems.
+- Preserve user-authored source-system content outside managed sections.
+- If source-system confidence is low or conflicts are present, recommend
+  `god-greenfieldifier` before writing.
+- Report:
+  - source systems found
+  - summaries written, unchanged, skipped, or blocked
+  - conflict count
+
+### Host capability and dashboard refresh
+- Call `lib/host-capabilities.detect(projectRoot)` when available and include
+  the guarantee level in closeouts.
+- Call `lib/dashboard.compute(projectRoot)` and `lib/dashboard.render(result)`
+  for user-facing status when available.
+- Treat host guarantee gaps as visible runtime facts, not fatal failures.
+- Report:
+  - host name
+  - guarantee level: full, degraded, or unknown
+  - top gap, when present
+  - dashboard readiness and attention line
+
 ### Pillars sync (native context)
 - Call `lib/pillars.pillarizeExisting(projectRoot)` if Pillars is absent or
   partial.
@@ -171,6 +243,11 @@ Sync status:
 - Pillars sync: [applied/proposed/no-op/skipped], [N] pillar files
 - Checkpoint sync: [created/updated/no-op/skipped] .godpowers/CHECKPOINT.md
 - Context refresh: [spawned god-context-writer/no-op/skipped], [N] files
+- Repo docs sync: [fresh/applied/stale/skipped], [N] safe fixes, [N] docs-writer paths
+- Repo surface sync: [fresh/applied/stale/skipped], [N] stale checks, [N] spawn recommendations
+- Feature awareness: [fresh/applied/skipped], runtime [version], [N] new features recorded
+- Source sync-back: [written/unchanged/blocked/skipped], [N] source systems
+- Host capabilities: [full/degraded/unknown], [top gap or none]
 
 Updated:
 - prd/PRD.md: added requirement P-MUST-12
@@ -201,8 +278,13 @@ Sync status:
   Local syncs:
     + reverse-sync: <counts and result>
     + pillars-sync: <counts and result>
+    + repo-doc-sync: <fresh, applied, stale, or skipped>
+    + repo-surface-sync: <fresh, applied, stale, or skipped>
+    + feature-awareness: <fresh, applied, or skipped>
+    + source-sync-back: <written, unchanged, blocked, or skipped>
     + checkpoint-sync: <created, updated, no-op, or skipped>
     + context-refresh: <spawned, no-op, or skipped>
+    + host-capabilities: <full, degraded, or unknown>
   Artifacts: <changed files or no-op>
   Log: .godpowers/SYNC-LOG.md