@pieai/pro-gov 0.4.3 → 0.4.5

package/assets/profiles/engineering-runtime/profile.md

@@ -9,9 +9,6 @@ Use for code-heavy projects: apps, games, runtimes, services, browser products,
 - `docs/governance/ssot-v0.9.md`
 - external AI-in-the-Loop policy linked by target projects under `docs/policy/shared-rules/ai-in-the-loop.md`
 - `docs/governance/agents-routing/engineering-runtime-v0.9.md`
-- `integrations/superpowers.md`
-- `integrations/compound-engineering.md`
-- `integrations/directed-development.md`
 - `integrations/mattpocock-skills.md`
 - starter `docs/governance/` and `docs/policy/` templates
 
@@ -30,8 +27,7 @@ Each project must define:
 - product canon
 - stack-specific rules
 - game/app-specific lane wording
-- Superpowers plugin body
-- Compound Engineering plugin body
+- external workflow plugin bodies
 - mattpocock/skills body
 
 ## Automation Boundary
@@ -44,14 +40,7 @@ content under the target project's ownership. Optional Lefthook and CI
 guardrails are also consumer-owned when installed; `doc-gov doctor` checks that
 their required governance commands remain present.
 
-Engineering-runtime starters also include Codex, Claude Code, and Antigravity
-Stop hooks that call `pro-gov host-hook`. Use `pro-gov doctor --strict-hooks`
-after sync to confirm the host configs are wired. The starter default is
-`--compound-gate-mode off`, so the hook does not interrupt the main session
-unless the project explicitly switches to `lite` or `strict`. Even when enabled,
-the hook does not replace verification, tests, or `ce-compound` itself.
-
 For non-trivial engineering work, run `pro-gov learn recall --query "<task
 summary>"` before changing files so existing `docs/solutions/**` and
-`CONCEPTS.md` lessons can shape the work without enabling a second default
-workflow.
+`CONCEPTS.md` lessons can shape the work. After verified work, use the
+`capture-learning` skill only when a reusable lesson exists.

package/assets/starter/AGENTS.template.md

@@ -40,13 +40,9 @@
 
 - Name this project's adopted profile: `engineering-runtime` or `doc-only`.
 - Point to the chosen agents-routing file from `docs/governance/agents-routing/`.
-- Engineering projects may use Superpowers, Directed Development, GStack, or other external workflows only inside the selected lane; do not copy upstream integration guides into the target project by default.
-- For engineering projects, Superpowers is the default engineering workflow. Compound Engineering is used by default only as the post-work Compound Gate through `ce-compound`; full CE workflows require an explicit user request.
-- For engineering projects, PGS Learning Recall is the pre-work companion to that post-work gate: recall existing lessons first, then do the work, then decide whether a new lesson should be compounded.
-- Engineering projects should have PGS Stop hooks wired for Codex, Claude Code, and Antigravity. Starter hooks default to `--compound-gate-mode off`; opt into `lite` or `strict` only when this project wants runtime exit-gate reminders. Before final reporting after completed engineering work, report `Compound Gate: ran ce-compound -> <path>`, `Compound Gate: ran fallback capture -> <path>`, or `Compound Gate: skipped -> <reason>`.
-- Use fallback capture only when the current host cannot load Compound Engineering; run `pro-gov learn capture --title "<learning title>" --summary "<reusable lesson>"` so Learning Recall can find the lesson later.
-- Doc-only projects should say that Superpowers TDD and Directed Development are not enabled by default.
-- External workflow systems such as Superpowers or GStack run inside the lane selected by this router. They must not replace this project router.
+- Before non-trivial work, use Learning Recall. After verified work, use `capture-learning` only when a non-obvious reusable lesson exists.
+- Do not install Stop/SubagentStop workflow reminder hooks.
+- Doc-only projects should say that engineering test workflows are not enabled by default.
 
 <!-- PGS-ROUTER:END -->
 

package/assets/starter/docs/governance/agents-routing/doc-only-v0.9.md

@@ -24,7 +24,7 @@ superseded_by: null
 
 Shared routing algorithm for non-runtime projects such as AI media, IP development, research, and asset governance workspaces.
 
-This route does not use Superpowers TDD or Directed Development by default.
+This route does not use engineering test workflows by default.
 
 ## Core Flow
 
@@ -52,7 +52,6 @@ flowchart TD
 ## Rules
 
 - Do not ask whether the task needs TDD unless the project has actual runtime code.
-- Do not trigger Directed Development unless the project explicitly opts in.
 - Prefer SSOT, provenance, and approval clarity over engineering ceremonies.
 - Use AI-in-the-Loop for evidence: inspect source, change one thing, verify the target document or asset path.
 
@@ -76,8 +75,7 @@ written as Markdown. Governed docs record decisions, plans, references, policies
 and workspace truth. Product artifacts stay in the project package or workbench
 unless the project explicitly opts them into doc-gov.
 
-## External Workflow Boundary
+## Host Adapter Boundary
 
-This route runs before external workflow systems such as Superpowers or GStack.
 Host-specific adapters such as `CLAUDE.md` may adapt the route for a specific AI
 client, but they must not replace the project `AGENTS.md` route.

package/assets/starter/docs/governance/agents-routing/engineering-runtime-v0.9.md

@@ -32,12 +32,8 @@ This file decides **how to choose a workflow**, not what the project is currentl
 flowchart TD
   A["Task arrives"] --> B["Read project router and current work"]
   B --> C["Classify with local lane profile"]
-  C --> D{"Mixed / cross-domain / interdependent product work?"}
-  D -- "yes" --> E["Use Directed Development to split ordered DD Blocks"]
-  E --> C
-  D -- "no" --> F["Enter local lane"]
-  F --> G["Use matching Superpowers workflow if applicable"]
-  G --> H["Use AI-in-the-Loop evidence cycle"]
+  C --> F["Enter local lane"]
+  F --> H["Use AI-in-the-Loop evidence cycle"]
   H --> I["Record evidence in doc-gov"]
 ```
 
@@ -45,16 +41,6 @@ flowchart TD
 
 Use this router only to pick depth and workflow. Do not use it as a project roadmap.
 
-## DD Trigger
-
-Use Directed Development only when all are true:
-
-- the task is product work
-- it crosses local lanes or shared contracts
-- sequencing risk makes a flat plan unsafe
-
-Do not trigger DD for broad mechanical edits, renames, formatting, or ordinary docs migration.
-
 ## Project-Local Lane Profile
 
 Every engineering project must define its own lane profile in `AGENTS.md` or `docs/policy/best-practice-for-this-project.md`.
@@ -68,11 +54,7 @@ Typical lanes:
 
 But the shared router must not define project-specific lanes.
 
-## External Workflow Boundary
-
-This route runs before external workflow systems such as Superpowers or GStack.
-Those systems may provide skills, reviews, browser workflows, or shipping gates,
-but they execute **inside** the lane selected by this route.
+## Host Adapter Boundary
 
 Host-specific adapters such as `CLAUDE.md` may adapt the route for a specific AI
 client, but they must not replace the project `AGENTS.md` route.

package/assets/starter/docs/governance/boundary.md

@@ -45,8 +45,7 @@ project-specific AI development habits live.
 - Product canon, runtime truth, or content truth.
 - Product prompts, generated media notes, or project-package workbench files.
 - Current project plans or active specs.
-- Superpowers plugin content.
-- Compound Engineering plugin content.
+- External workflow plugin content.
 
 ## Put Those Elsewhere
 
@@ -60,7 +59,7 @@ project-specific AI development habits live.
 | Product or world truth | `docs/canon/` |
 | Active implementation work | `docs/plans/active/` |
 | Completed proof records | `docs/plans/completed/` |
-| Compound Engineering learnings | `docs/solutions/**` as CE-owned external artifacts |
+| Reusable project learnings | `docs/solutions/**` as learning artifacts |
 | Product artifacts outside governed docs | Project package, workbench, assets, runtime config, or source tree |
 
 When unsure, ask this question: is this rule about how the document system works,
@@ -77,7 +76,5 @@ product packages, workbenches, prompt libraries, source folders, or asset
 folders can be product artifacts. Keep those files where the product package
 expects them unless a project explicitly opts them into doc-gov.
 
-Compound Engineering external artifacts under `docs/solutions/**`,
-`docs/brainstorms/**`, `docs/pulse-reports/**`, and CE-native root files under
-`docs/plans/*` are not governed docs by default. They remain valid project
-artifacts, but their frontmatter belongs to Compound Engineering, not Doc Gov.
+Learning artifacts under `docs/solutions/**` are not governed docs by default.
+They remain searchable project artifacts with their own lightweight metadata.

package/assets/starter/docs/governance/ssot-v0.9.md

@@ -50,13 +50,12 @@ Markdown.
 
 Extra governed roots are allowed only when a project explicitly opts in.
 
-Compound Engineering external artifacts are explicitly outside the default Doc
-Gov schema:
+Learning and optional-tool artifacts are explicitly outside the default Doc Gov
+schema:
 
 - `docs/solutions/**`
 - `docs/brainstorms/**`
 - `docs/pulse-reports/**`
-- CE-native root artifacts under `docs/plans/*`
 
 PGS plans remain under `docs/plans/active/**` and
 `docs/plans/completed/**`.
@@ -117,7 +116,7 @@ works for governed docs:
 | Project AI/development policy | `docs/policy/` |
 | Product or feature requirement | `docs/specs/` |
 | Step-by-step implementation work | `docs/plans/` |
-| Compound Engineering learning records | `docs/solutions/**`, governed by CE schema |
+| Reusable learning records | `docs/solutions/**`, outside Doc Gov schema |
 | Durable workspace/system truth | `docs/canon/` |
 | How-to guides, architecture maps, tool notes | `docs/reference/` |
 | Retired governed history | `docs/archive/` |

package/assets/starter/docs/reference/documentation-map.md

@@ -40,7 +40,7 @@ Use `AGENTS.md` for startup reading. It should point agents to:
 | `docs/specs/completed/` | Completed specs |
 | `docs/plans/active/` | Active implementation plans |
 | `docs/plans/completed/` | Completed execution records |
-| `docs/solutions/` | Compound Engineering learning records, governed by CE schema |
+| `docs/solutions/` | Reusable learning records, outside Doc Gov schema |
 | `docs/canon/` | Durable project truth |
 | `docs/reference/` | Guides and references |
 | `docs/archive/` | Retired history |
@@ -51,6 +51,6 @@ project-package canon, generated media notes, and source-package files stay in
 their product/workbench structure unless this project explicitly opts them into
 doc-gov.
 
-Compound Engineering may create `docs/solutions/**`, `docs/brainstorms/**`,
-`docs/pulse-reports/**`, and CE-native root artifacts under `docs/plans/*`.
-Those are external workflow artifacts, not Doc Gov canonical documents.
+Optional skills may create `docs/solutions/**`, `docs/brainstorms/**`, or
+`docs/pulse-reports/**`. Those are external artifacts, not Doc Gov canonical
+documents.

package/cli-guide.md

@@ -21,17 +21,15 @@ pro-gov portfolio plan --config /path/to/portfolio.json --target web-app --json
 pro-gov portfolio assets-check --config /path/to/portfolio.json --json
 pro-gov portfolio doctor --config /path/to/portfolio.json --json
 pro-gov learn recall --query "release downstream sync" --target .
-pro-gov learn capture --title "Fallback learning" --summary "Reusable lesson..." --target .
+pro-gov learn capture --title "Reusable learning" --summary "Reusable lesson..." --target .
 pro-gov lens inspect --target .
 pro-gov lens report --target . --out .pro-gov/lens-report.md
 pro-gov lens audit init --target /path/to/project --out audits/project/2026-07-01
 pro-gov lens audit check --dir audits/project/2026-07-01
-pro-gov host-hook --host codex --event Stop --compound-gate-mode off|lite|strict
 pro-gov init --profile engineering-runtime --dry-run
 pro-gov init --profile engineering-runtime --apply
 pro-gov init --profile doc-only --dry-run
 pro-gov sync --check [--profile engineering-runtime|doc-only]
-pro-gov sync --apply-host-hooks --profile engineering-runtime
 pro-gov doctor
 ```
 
@@ -45,47 +43,26 @@ Actions references stay packaged but are not installed by default.
 but checks project-local seeds such as `AGENTS.md`, project policy, and current
 work for presence only. Optional `lefthook.yml` and CI guardrails remain
 consumer-owned when installed; `doc-gov doctor` validates their required PGS
-commands without requiring byte-for-byte template equality. Host configs are
-compared by PGS-owned entries, so consumer hooks do not create false drift. It
-infers the installed profile when exactly one route exists; `--profile` resolves
-an empty or temporarily ambiguous target.
-
-`sync --apply-host-hooks` is the bounded write path for engineering-runtime
-host configs. It updates only PGS Compound Gate entries and preserves consumer
-`PreToolUse`, other events, other top-level keys, and non-PGS entries inside
-Stop/SubagentStop arrays. All three files are parsed before any write.
-
-`learn recall` is the pre-work companion to Compound Engineering's post-work
-`ce-compound` learning records. It searches `docs/solutions/**` and
+commands without requiring byte-for-byte template equality. It infers the
+installed profile when exactly one route exists; `--profile` resolves an empty
+or temporarily ambiguous target. PGS does not install or modify AI-host hooks.
+
+`learn recall` searches `docs/solutions/**` and
 `CONCEPTS.md` in the target repository and returns the most relevant prior
 lessons for the current task. Use it before non-trivial implementation,
 debugging, release, architecture, or portfolio-sync work. It is read-only and
 does not require a full local PGS checkout.
 
-`learn capture` is the fallback capture path for hosts where the Compound
-Engineering plugin or `ce-compound` skill is unavailable. Prefer CE when it is
-installed. Use fallback capture only after verified completed work produced a
-reusable lesson that is not already covered by an existing `docs/solutions/**`
-record:
+`learn capture` is the small native capture path. Use it only after verified
+work produced a reusable lesson that is not already covered by an existing
+`docs/solutions/**` record:
 
 ```bash
 pro-gov learn capture \
-  --title "Use fallback capture when CE is unavailable" \
-  --summary "Capture the reusable lesson through PGS fallback capture so Learning Recall can find it later."
+  --title "Keep the reusable lesson searchable" \
+  --summary "Capture the lesson so Learning Recall can find it later."
 ```
 
-Then report:
-
-```text
-Compound Gate: ran fallback capture -> docs/solutions/<category>/<file>.md
-```
-
-`host-hook` is the cross-host Compound Gate adapter for Codex, Claude Code, and
-Antigravity. `--compound-gate-mode off` is the default and does not interrupt
-the main session. `lite` emits a short continuation prompt when completed
-engineering work lacks a Compound Gate marker. `strict` emits the fuller legacy
-prompt. The same value can be supplied through `PGS_COMPOUND_GATE_MODE`.
-
 Full upstream-checkout commands:
 
 ```bash
@@ -123,7 +100,7 @@ maintainer checks.
 `portfolio assets-check` verifies that the currently recorded lock and managed
 links are healthy. `portfolio doctor` additionally compares each target with the
 current portfolio `assetBundles`, registry hashes, package versions, target-local
-router/hook checks, and optional `hostTooling` requirements. The doctor is
+router checks, and optional `hostTooling` requirements. The doctor is
 offline and read-only by default. A dirty product worktree is reported as
 evidence but is not itself a governance failure.
 
@@ -141,14 +118,14 @@ The native tools own fetching and installation. PGS reviews resulting asset
 changes, regenerates plans, and verifies the fleet; it does not implement a
 second plugin marketplace or silently accept upstream changes.
 
-`lens audit init` creates a raw-first audit package for Project Lens plus
-Ponytail reviews. For a "read-only project audit", the target repository remains
+`lens audit init` creates a raw-first audit package for Project Lens reviews.
+For a "read-only project audit", the target repository remains
 read-only, but the audit package is still the required output record. `lens
 audit check` fails when the package is missing required artifacts, when
 artifacts are still marked pending, or when generated template text was not
 replaced with real audit output. It also requires method records for the
-read-only boundary, agent execution, subagent trace, Project Lens/Ponytail
-sources, target status, and audit package status. Use
+read-only boundary, agent execution, subagent trace, Project Lens and simplicity
+review sources, target status, and audit package status. Use
 `lens audit check --mode fresh` when this session must prove it created the raw
 passes; use `--mode reuse` when it only verifies an existing audit package.
 
@@ -163,7 +140,6 @@ pnpm pro-gov init --profile engineering-runtime --dry-run
 pnpm pro-gov init --profile engineering-runtime --apply
 pnpm doc-gov scan
 pnpm pro-gov sync --check --profile engineering-runtime
-pnpm pro-gov sync --apply-host-hooks --profile engineering-runtime
 pnpm doc-gov migrate --profile engineering-runtime --check
 pnpm doc-gov doctor
 ```