godpowers 0.15.14 → 0.15.15

package/CHANGELOG.md

@@ -5,6 +5,20 @@ 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).
 
+## [0.15.15] - 2026-05-11
+
+Transcript hygiene release. Keeps God Mode orchestration scaffolding out of the
+normal user-visible transcript.
+
+### Changed
+- Added a User-Visible Transcript Contract to `/god-mode` and
+  `god-orchestrator`.
+- God Mode now explicitly hides raw Task input, "Hard instructions", spawned
+  agent prompts, complete file loadout lists, and internal routing metadata from
+  the user-facing transcript.
+- Private rules that affect a pause must be translated into the smallest
+  user-facing question instead of exposing the underlying prompt.
+
 ## [0.15.14] - 2026-05-11
 
 Origin evidence release. Prevents `/god-mode --yolo` from inventing staging,

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-0.15.14-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-0.15.15-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.**

package/agents/god-orchestrator.md

@@ -632,6 +632,32 @@ Options:
 Default: If you say "go", I'll pick [X] because [Y].
 ```
 
+## User-Visible Transcript Contract
+
+The user-facing God Mode transcript is an operator console, not a prompt
+debugger. Keep orchestration scaffolding private.
+
+Show:
+- concise phase status
+- durable state detected from disk
+- commands being run and whether they passed or failed
+- scoped file changes
+- final validation summary
+- `Arc complete` or `PAUSE: external access required`
+
+Hide:
+- raw Task input
+- "Hard instructions" sections
+- spawned-agent prompt text
+- system, developer, AGENTS.md, or internal policy recitations
+- complete file loadout lists
+- routing metadata unless it changes a user decision
+
+When a private rule affects a pause, translate it into the smallest
+user-facing question. Do not expose the rule itself. Example: ask for
+`STAGING_APP_URL=<deployed staging origin>` rather than showing the Shipping
+Closure Protocol.
+
 ## Resume Protocol
 
 On every invocation:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "0.15.14",
+  "version": "0.15.15",
   "description": "AI-powered development system: 104 slash commands and 38 specialist agents that take a project from raw idea to hardened production. Runs inside Claude Code, Codex, Cursor, Windsurf, Gemini, and 10+ other AI coding tools.",
   "bin": {
     "godpowers": "./bin/install.js"

package/skills/god-mode.md

@@ -95,17 +95,49 @@ You are receiving a /god-mode invocation. Your job is to spawn the
      name, repo name, README title, or brand name. If no deployed origin is
      evidenced, pause for `STAGING_APP_URL=<deployed staging origin>`.
 
-6. Orchestrator runs the appropriate workflow:
+6. Keep the spawn payload private. Do not echo or summarize raw Task input,
+   "Hard instructions", hidden orchestration rules, agent prompts, file
+   loadout lists, or internal routing payloads into the user-visible transcript.
+   The visible transcript may say only what phase is running, what durable state
+   was detected, what commands are running, what changed, and the final
+   `Arc complete` or `PAUSE: external access required` block.
+
+7. Orchestrator runs the appropriate workflow:
    - Greenfield -> full-arc
    - Brownfield -> brownfield-arc (archaeology -> reconstruct -> debt-assess -> proceed)
    - Bluefield -> bluefield-arc (org-context -> arc with constraints)
 
-7. Relay the orchestrator's output to the user.
+8. Relay only the orchestrator's user-facing output to the user. If the
+   platform displays raw spawn details automatically, immediately follow with a
+   clean public summary and never repeat the leaked payload.
 
-8. When the orchestrator pauses, present the question to the user using the
+9. When the orchestrator pauses, present the question to the user using the
    pause format (What / Why / Options / Default).
 
-9. When the user answers, re-spawn god-orchestrator with the answer.
+10. When the user answers, re-spawn god-orchestrator with the answer.
+
+## User-Visible Transcript Contract
+
+The God Mode transcript is an operator console, not a prompt debugger.
+
+Show:
+- detected resume or project mode in plain language
+- short progress updates for phases, commands, validations, and file edits
+- concise validation summaries instead of full command noise when possible
+- final changed paths, validation results, and completion or pause status
+
+Hide:
+- raw Task input
+- "Hard instructions" sections
+- spawned-agent prompt text
+- system, developer, or AGENTS.md rule recitations
+- complete file loadout lists
+- internal routing metadata unless it directly affects a user decision
+
+If an internal instruction must influence a pause, translate it into the
+smallest user-facing question. For example, ask for
+`STAGING_APP_URL=<deployed staging origin>` instead of exposing the full
+Shipping Closure Protocol.
 
 ## Pause Format (relay from orchestrator)