@pieai/pro-gov 0.4.3 → 0.4.4

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
 ```