@pieai/pro-gov 0.9.2 → 0.9.4

package/README.md

@@ -65,6 +65,7 @@ What these commands do:
 | `assets list` | Shows packaged assets and public registry metadata. | No |
 | `assets discover` | Detects local project signals. | No |
 | `assets recommend` | Suggests relevant asset bundles with reasons. | No |
+| `assets catalog build|check` | Builds or verifies the full-checkout portable asset catalog; optional native links are local cache only. | Only `build` writes the explicit catalog output |
 | `portfolio check` | Validates an external portfolio manifest owned by the user or organization. | No |
 | `portfolio plan` | Builds dry-run asset plans for manifest targets, using packaged public assets unless a full checkout is supplied. | No |
 | `portfolio assets-check` | Checks the integrity of each target's current managed asset lock and symlinks. | No |
@@ -93,6 +94,8 @@ pro-gov assets apply --plan .pro-gov/asset-plan.json
 pro-gov assets check --target .
 pro-gov assets public-check --json
 pro-gov assets npx update --plan
+pro-gov assets catalog build --native-links
+pro-gov assets catalog check
 ```
 
 Skill placement normally comes from the asset registry. Use `--placement
@@ -120,6 +123,14 @@ package use `public-agent-assets/` as the reviewed promotion surface.
 `assets public-check` verifies that every publishable public asset still matches
 the private-source and public-copy hashes recorded during promotion.
 
+`assets catalog build` leaves every canonical asset in place and generates one
+discovery surface directly under `agent-assets/#catalogs`: a local search page,
+Markdown/JSON indexes, and purpose-based topic folders. Source, author, type,
+and bundle remain searchable attributes instead of duplicate folder trees.
+`--native-links` adds ignored machine-local shortcuts beside each topic README;
+`assets catalog check` verifies the portable output and fails closed on
+uncovered or uncategorized sources.
+
 ## Package Boundary
 
 - `pro-gov` distributes starter, profile, integration, and adoption assets.

package/cli-guide.md

@@ -87,6 +87,8 @@ pro-gov assets check --target .
 pro-gov assets public-check --json
 pro-gov assets npx add <source> --plan
 pro-gov assets npx update --plan
+pro-gov assets catalog build --native-links
+pro-gov assets catalog check
 ```
 
 These commands use a maintainer-local `agent-assets/` registry when local-only
@@ -98,6 +100,17 @@ Skill placement normally comes from the asset registry. Use `--placement
 auto|manual` only as a migration override when deliberately moving an existing
 target.
 
+`assets catalog` is a full-checkout discovery layer. `build` creates the local
+search page, Markdown/JSON indexes, and purpose-based folders directly under
+`agent-assets/#catalogs`; source, author, type, and bundle stay available as
+search attributes instead of duplicate folder trees. `--native-links` places
+ignored shortcuts beside each topic README. On macOS and Linux those links are
+relative symlinks. On Windows directory links use junctions and file links are
+best-effort because they may require Developer Mode or elevated permission.
+`check` is read-only and fails when generated files are stale, a source is not
+represented, or an asset has no topic. The catalog never moves canonical assets
+and does not change installation plans.
+
 `portfolio ai-health` performs a read-only structural inventory of the control
 plane, execution engine, registered targets, user/project AI-host configuration,
 exact technology-version policy, the four verification-gate scripts, bounded