godpowers 0.15.17 → 1.0.0

package/CHANGELOG.md

@@ -5,6 +5,59 @@ 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).
 
+## [1.0.0] - 2026-05-14
+
+Public adoption freeze release. Promotes the shipped Godpowers surface to the
+stable 1.0 line so real users can adopt it without the project moving under
+them.
+
+### Added
+- Added 1.0 release notes and public adoption language.
+- Added greenfield Pillars seeding so new Godpowers projects write the project
+  name into `agents/context.md` during initialization.
+
+### Changed
+- Bumped the package and public documentation version to 1.0.0.
+- Generated `AGENTS.md` now names Godpowers first, then explains that Pillars is
+  the native project context layer and `.godpowers/` remains the workflow state
+  and artifact layer.
+- Release documentation now frames the project as stable for public adoption
+  freeze rather than pre-launch expansion.
+- The release script now checks the installer version through `package.json`,
+  matching the dynamic installer implementation.
+
+### Frozen
+- Public slash-command, agent, workflow, routing, recipe, and schema surfaces are
+  frozen except for critical fixes and adoption feedback.
+- New command families, schema churn, and Pillars format changes are deferred
+  until adoption produces evidence.
+
+## [0.15.18] - 2026-05-14
+
+Native Pillars context release. Makes Pillars the default project context
+layer for Godpowers projects and keeps existing `.godpowers` artifacts aligned
+with portable `agents/*.md` pillar files.
+
+### Added
+- Added `lib/pillars.js` for Pillars detection, initialization, load-set
+  routing, existing-project Pillar-ization, artifact sync planning, and
+  semantic signal extraction from labeled Godpowers artifacts.
+- Added `scripts/test-pillars.js` and `npm run test:pillars` to cover the
+  `agents/` collision risk, Pillars initialization, routed load sets,
+  existing `.godpowers` conversion, artifact-to-pillar sync, `--yolo`
+  auto-apply behavior, and restricted-character sanitization.
+
+### Changed
+- `/god-init`, `/god-mode`, `/god-context`, and `/god-sync` now treat every
+  Godpowers project as a Pillars project by default.
+- Existing `.godpowers` projects are Pillar-ized on resume or sync, with PRD,
+  ARCH, STACK, ROADMAP, BUILD, DEPLOY, OBSERVE, HARDEN, DESIGN, and PRODUCT
+  artifacts linked into relevant pillar files.
+- `/god-feature`, `/god-build`, `/god-review`, PRD, architecture, roadmap,
+  orchestrator, and updater flows now document Pillars-first context loading.
+- Under `/god-mode --yolo`, durable artifact changes auto-apply managed
+  pillar sync sections and log the decision.
+
 ## [0.15.17] - 2026-05-12
 
 Greenfieldification release. Turns the brownfield and bluefield simulation

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.17-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-1.0.0-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,8 +12,15 @@ 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.0.0 is the public adoption freeze: the command, agent, workflow,
+schema, artifact, and native Pillars context surfaces are stable while real
+projects shape the next release train.
+
 It fuses four disciplines into one unified workflow:
 
+- **Native project context** - every Godpowers project is a Pillars project:
+  root `AGENTS.md` plus task-routed `agents/*.md` files carry durable project
+  truth before commands touch code.
 - **Artifact discipline** - every sentence in every document is a labeled
   decision, hypothesis, or open question. Mechanically verified failure modes.
 - **Execution engine** - fresh-context agents in parallel waves with atomic
@@ -156,6 +163,10 @@ reported as the final result.
 If `.godpowers` state already exists, `/god-mode --yolo` resumes from disk
 instead of asking for the project description again.
 
+Under `--yolo`, Godpowers also auto-applies Pillars sync proposals when
+durable `.godpowers` artifacts change project truth. The decision is logged to
+`.godpowers/YOLO-DECISIONS.md`.
+
 For existing codebases and org-constrained new projects, God Mode now runs a
 greenfield simulation audit and then actions it through a greenfieldification
 plan. It pauses before risky artifact rewrites because that process can change
@@ -206,6 +217,20 @@ Skill updates:   PROGRESS.md
 .godpowers/harden/FINDINGS.md  Security Findings
 ```
 
+Godpowers projects also include native Pillars context:
+
+```
+AGENTS.md              Pillars loading protocol plus Godpowers managed fence
+agents/context.md      Always-loaded project identity and invariants
+agents/repo.md         Always-loaded repository layout and naming
+agents/*.md            Task-routed domain pillars
+```
+
+Existing `.godpowers` projects are Pillar-ized on resume or sync. Current PRD,
+ARCH, STACK, ROADMAP, BUILD, DEPLOY, OBSERVE, HARDEN, DESIGN, and PRODUCT
+artifacts become managed source references in the relevant pillar files, with
+labeled decisions, hypotheses, and open questions extracted when available.
+
 ## Quality Guardrails
 
 Every artifact passes these mechanical checks before it is treated as complete:
@@ -265,6 +290,7 @@ Pi. T3 Code inherits from the underlying agent (Codex / Claude / OpenCode).
 - [Concepts](docs/concepts.md)
 - [Command reference (all 105 skills + 39 agents)](docs/reference.md)
 - [Roadmap](docs/ROADMAP.md)
+- [1.0 Release Notes](RELEASE.md)
 - [Changelog](CHANGELOG.md)
 - [Inspiration](INSPIRATION.md)
 

package/RELEASE.md

@@ -0,0 +1,61 @@
+# Godpowers 1.0.0 Release
+
+Date: 2026-05-14
+
+Godpowers 1.0.0 is the public adoption freeze. The goal of this release is not
+to add another layer of capability, but to stop the ground from moving so real
+projects can try the system, report friction, and shape the next cycle from
+evidence.
+
+## What is stable
+
+- 105 slash commands
+- 39 specialist agents
+- 13 executable workflows
+- 36 intent recipes
+- 15-runtime installer
+- Native Pillars project context through `AGENTS.md` and `agents/*.md`
+- `.godpowers/` workflow state and artifact layout
+- Core schemas: intent, state, events, workflow, routing, recipes, extension
+  manifests
+- Extension pack compatibility range for the 1.x line
+
+## What 1.0 means
+
+Godpowers is the product users invoke. Pillars is the native project context
+layer Godpowers installs, reads, and keeps current.
+
+New projects get Godpowers-branded `AGENTS.md` protocol text, always-loaded
+`agents/context.md` and `agents/repo.md`, and routed pillar files for stack,
+architecture, data, API, UI, auth, quality, deploy, and observe concerns.
+
+Existing `.godpowers` projects are Pillar-ized on resume or sync. Durable
+signals from PRD, architecture, stack, roadmap, build, deploy, observe, harden,
+design, and product artifacts are linked back into relevant pillars.
+
+## Freeze policy
+
+During the adoption freeze, do not add new command families, change schema
+formats, or rename public artifacts without evidence from real use.
+
+Allowed changes:
+
+- Critical bug fixes
+- Documentation clarity
+- Test coverage for frozen behavior
+- Compatibility fixes for supported AI coding tools
+- Small fixes that make existing 1.0 behavior work as documented
+
+Deferred changes:
+
+- New lifecycle phases
+- New schema versions
+- Pillars format changes
+- Major routing semantics
+- Large extension API changes
+
+## Adoption ask
+
+Use Godpowers on real projects and report what breaks, what feels too heavy,
+what feels magical, and what needs sharper defaults. The next release train
+should be shaped by those reports rather than by more speculative surface area.

package/agents/god-architect.md

@@ -29,6 +29,11 @@ Before starting:
 
 ## Imported Preparation Context
 
+Before drafting, compute the Pillars load set for the architecture task with
+`lib/pillars.computeLoadSet(projectRoot, taskText)`. Read `agents/context.md`
+and `agents/repo.md` first, then routed pillars such as `arch`, `stack`,
+`data`, `api`, `auth`, `deploy`, or `observe` when relevant.
+
 If `.godpowers/prep/INITIAL-FINDINGS.md` exists, read it first for direct
 Godpowers observations about framework, tooling, deploy, tests, docs, and
 codebase risks.
@@ -50,6 +55,9 @@ Rules:
   descriptions, or open questions.
 - If imported context conflicts with the PRD, the PRD wins and the conflict
   becomes an `[OPEN QUESTION]`.
+- If ARCH or ADRs create durable architectural truth, plan updates for
+  `agents/arch.md` and related pillars. In `--yolo`, apply those updates and
+  log them to `.godpowers/YOLO-DECISIONS.md`.
 
 ## Output
 

package/agents/god-orchestrator.md

@@ -146,6 +146,31 @@ During `/god-init`, scan for adjacent methodology artifacts from GSD,
 Superpowers, BMAD, and similar systems. Treat them as preparation context,
 not as source of truth.
 
+## Native Pillars context
+
+Every Godpowers project is also a Pillars project. During `/god-init` and
+`/god-mode`, call `lib/pillars.detect(projectRoot)`. If Pillars is absent or
+partial, call `lib/pillars.init(projectRoot)` before planning or build work
+continues.
+
+If `.godpowers/` already exists, call
+`lib/pillars.pillarizeExisting(projectRoot)` before resume work continues.
+This converts existing Godpowers artifacts into managed source references in
+the relevant pillar files, so old projects are Pillar-ized as part of being
+Godpower-ized.
+
+Before each major command, compute the task-specific Pillars load set with
+`lib/pillars.computeLoadSet(projectRoot, taskText)`. Load `agents/context.md`
+and `agents/repo.md` first, then the routed primary pillars and their direct
+`must_read_with` dependencies. Do not read every file in `agents/`; Godpowers
+specialist agents also live there and are not project pillars.
+
+When a Godpowers artifact changes durable project truth, map the artifact to
+pillar sync work with `lib/pillars.planArtifactSync(projectRoot, artifacts,
+{ yolo })`. Default mode proposes pillar updates for review. Under `--yolo`,
+apply the pillar updates immediately and log the action to
+`.godpowers/YOLO-DECISIONS.md`.
+
 Before or alongside that import, write `.godpowers/prep/INITIAL-FINDINGS.md`
 using `templates/INITIAL-FINDINGS.md`. This artifact records what Godpowers
 observed directly during init:
@@ -407,6 +432,7 @@ for `STAGING_APP_URL=<deployed staging origin>` before deployed staging smoke.
 | Drift (breaking) | Pause | Pause anyway |
 | Impeccable critical at /god-launch | Pause | Pause anyway |
 | Impeccable warnings at launch | Pause to ack | Auto-ack with justification |
+| Pillars durable context sync | Propose updates | Auto-apply and log |
 | REVIEW-REQUIRED.md auto-clear | No | No anyway |
 | Reverse-sync between tiers | Yes | Yes |
 | Mandatory final /god-sync | Always | Always |

package/agents/god-pm.md

@@ -31,6 +31,11 @@ required sections:
 
 ## Imported Preparation Context
 
+Before drafting, compute the Pillars load set for the PRD task with
+`lib/pillars.computeLoadSet(projectRoot, taskText)`. Read `agents/context.md`
+and `agents/repo.md` first, then any task-routed pillars. Pillars is native
+project truth for Godpowers; use it before broader repo archaeology.
+
 If `.godpowers/prep/INITIAL-FINDINGS.md` exists, read it first so the PRD
 reflects what Godpowers observed during init: codebase shape, tests, docs,
 risks, and methodology systems detected.
@@ -48,6 +53,9 @@ Rules:
   preserve the Godpowers state and add an `[OPEN QUESTION]`.
 - In PRD rationale, mention the source only when it materially changes a
   requirement.
+- If the PRD creates durable product truth, plan corresponding updates for
+  `agents/context.md`. In `--yolo`, apply those updates and log them to
+  `.godpowers/YOLO-DECISIONS.md`.
 
 ## Quality Gates
 

package/agents/god-roadmapper.md

@@ -25,6 +25,11 @@ may exist as early product-experience preparation.
 
 ## Imported Preparation Context
 
+Before sequencing, compute the Pillars load set for the roadmap task with
+`lib/pillars.computeLoadSet(projectRoot, taskText)`. Read `agents/context.md`
+and `agents/repo.md` first, then routed pillars that affect delivery,
+quality, deploy, or observability.
+
 If `.godpowers/prep/INITIAL-FINDINGS.md` exists, read it first for repo risks,
 existing tests, docs, CI, deploy, and suggested sequencing implications.
 
@@ -47,6 +52,9 @@ Rules:
 - Mark any imported sequencing assumption as `[HYPOTHESIS]` until confirmed by
   Godpowers artifacts or the user.
 - Keep design-derived delivery increments grounded in the PRD and ARCH.
+- If ROADMAP creates durable delivery or sequencing truth, plan updates for
+  relevant pillars. In `--yolo`, apply those updates and log them to
+  `.godpowers/YOLO-DECISIONS.md`.
 
 ## Process
 

package/agents/god-updater.md

@@ -112,6 +112,17 @@ After feature work, every artifact that was impacted needs to reflect reality.
 - Emit events: `linkage.snapshot`, `drift.detected` (per finding),
   `review-required.populated`
 
+### Pillars sync (native context)
+- Call `lib/pillars.pillarizeExisting(projectRoot)` if Pillars is absent or
+  partial.
+- For every durable Godpowers artifact changed during this sync, call
+  `lib/pillars.applyArtifactSync(projectRoot, changedArtifacts, { yolo })`.
+- Default mode may report the pillar updates as proposed review items when the
+  change is interpretive. Under `--yolo`, apply the managed source sections
+  immediately and log the decision to `.godpowers/YOLO-DECISIONS.md`.
+- Never read every file in `agents/` as project context. Only files with
+  `pillar:` frontmatter are Pillars files.
+
 ### AI-tool context refresh (always, unless never-ask)
 - Read `state.json` for `project.context-prompt-answered`
   - If `never-ask`: skip; do not touch AGENTS.md / CLAUDE.md / others