@pieai/pro-gov 0.8.0 → 0.9.0

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

@@ -38,7 +38,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.
 
-For non-trivial engineering work, run `pro-gov learn recall --query "<task
+For non-trivial engineering work, run `pnpm pro-gov learn recall --query "<task
 summary>"` before changing files so existing `docs/reference/learnings/**` and
 `CONCEPTS.md` lessons can shape the work. After completed, verified, non-trivial
 work, let `capture-learning` make a visible soft closeout decision. Capture only

package/assets/public-agent-assets/registry.json

@@ -25,11 +25,11 @@
       "notes": "Public rule for choosing evidence lanes and requiring fresh verification before completion.",
       "promotion": {
         "privateSourcePath": "rules/pie-rules/ai-in-the-loop.md",
-        "privateSourceHash": "sha256:045f9dcd0b1425155a89c863d24ba1509dee4e1e572f23f27fb7fe6f201874ec",
+        "privateSourceHash": "sha256:71f487152123491a2c110ad839a90780b08e04ae3a133d59bbe977bf8b2f64e4",
         "publicHash": "sha256:911702baf6ea1d724e41ea1876d23d80f4de8dfaaadbf1399a40c982c810224c",
         "sanitized": true,
-        "lastReviewed": "2026-06-25",
-        "reviewNotes": "Public copy keeps the evidence-loop method while removing private wording and local-only assumptions."
+        "lastReviewed": "2026-08-17",
+        "reviewNotes": "Reviewed after the private source gained governed front matter and normalized formatting. The public copy intentionally keeps the portable evidence-loop method without the private Grok compatibility lane or project governance metadata."
       }
     },
     {

package/assets/starter/AGENTS.template.md

@@ -20,14 +20,28 @@
 - Its selected agents routing file is `PROFILE_ROUTE` under
   `docs/governance/agents-routing/`.
 
+## Policy Discovery
+
+All Markdown under `docs/policy/**/*.md`, including subdirectories and any
+symlinked shared-rule files, belongs to the discoverable policy index. This is
+not a command to load every policy at startup. Read the project-local baseline
+and only the shared rules whose task surface actually matches.
+
+## Skill Availability
+
+An asset manifest or lock records desired state; it does not prove that an
+optional skill is installed, host-discoverable, loaded, or invoked. Use a skill
+only when its SKILL.md actually exists and can be read. Centrally managed
+project links may need the portfolio control plane to materialize them after a
+fresh clone; their absence must not hide or replace the portable policy rules.
+
 ## Documentation Tasks
 
 When the task creates, edits, moves, deletes, or governs documentation, read
 `docs/governance/boundary.md`, `docs/governance/ssot-v1.1.md`,
 `docs/governance/doc-agent-rules.md`, `docs/governance/doc-types.md`, the
-selected agents routing file, and all Markdown under `docs/policy/**/*.md`.
-That policy set includes subdirectories and symlinked shared-rule files; keep
-project AI development policy in `docs/policy/`.
+selected agents routing file, and the policy files that govern the changed
+surface. Keep project AI development policy in `docs/policy/`.
 
 <!-- PGS-ROUTER:END -->
 

package/assets/starter/docs/governance/agents-routing/engineering-runtime-v1.1.md

@@ -6,7 +6,7 @@ status: stable
 canonical: true
 owner: human
 created: 2026-07-13
-last_reviewed: 2026-07-16
+last_reviewed: 2026-08-17
 domain: agents-routing
 tags:
   - agents-routing
@@ -30,13 +30,22 @@ This file decides **how to choose a workflow**, not what the project is currentl
 
 ```mermaid
 flowchart TD
-  A["Task arrives"] --> B["Read project router and current work"]
-  B --> C["Classify with local lane profile"]
-  C --> F["Enter local lane"]
-  F --> H["Use AI-in-the-Loop evidence cycle"]
-  H --> I["Record evidence in doc-gov"]
+  A["Task arrives"] --> B["Read project router and local baseline"]
+  B --> C{"Does the task depend on current priorities or in-flight work?"}
+  C -->|"yes"| D["Read current work"]
+  C -->|"no"| E["Skip current work"]
+  D --> F["Classify with local lane profile"]
+  E --> F
+  F --> G["Enter local lane"]
+  G --> H["Use the relevant verification cycle"]
+  H --> I["Record durable evidence only when its document role requires it"]
 ```
 
+`current-work` is a conditional state surface, not universal startup context.
+Likewise, AI-in-the-Loop applies when implementation or runtime verification
+needs it; a documentation-only or read-only routing task does not load that
+policy by default.
+
 ## Keep It Small
 
 Use this router only to pick depth and workflow. Do not use it as a project roadmap.

package/cli-guide.md

@@ -34,9 +34,12 @@ 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 doctor
+pro-gov package-doctor
 ```
 
+`package-doctor` checks the installed package itself; it is not a target-project
+health claim. The older `doctor` command remains a compatibility alias.
+
 `init --apply` is safe for a fresh target: it preflights every destination and
 refuses the entire operation if any target file already exists. It never merges
 or overwrites an existing router or project-local policy. Existing projects