@pieai/pro-gov 0.4.5 → 0.4.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,16 @@
1
+ <!doctype html>
2
+ <html lang="zh-CN">
3
+ <head>
4
+ <meta charset="utf-8" />
5
+ <meta name="viewport" content="width=device-width, initial-scale=1" />
6
+ <meta name="color-scheme" content="light" />
7
+ <title>ProjectLens · AI 产品线健康看板</title>
8
+ <link rel="stylesheet" href="./app.css" />
9
+ </head>
10
+ <body>
11
+ <div id="root"></div>
12
+ <noscript>此看板需要 JavaScript 才能读取本地扫描数据。</noscript>
13
+ <script src="./data.js"></script>
14
+ <script src="./app.js"></script>
15
+ </body>
16
+ </html>
@@ -4,48 +4,32 @@
4
4
 
5
5
  <!-- PGS-ROUTER:BEGIN v0.9 -->
6
6
 
7
- ## Startup Reading
8
-
9
- `README.md` is the human-facing project introduction. Do not use it as the default AI startup path unless the task is about project positioning, public explanation, or the README itself.
10
-
11
- 1. All Markdown files under `docs/policy/**/*.md`, including files in
12
- subdirectories and symlinked shared-rule files.
13
- 2. `docs/governance/boundary.md`
14
- 3. `docs/governance/ssot-v0.9.md`
15
- 4. `docs/governance/doc-agent-rules.md`
16
- 5. `docs/governance/doc-types.md`
17
- 6. The selected agents routing file:
18
- - `docs/governance/agents-routing/engineering-runtime-v0.9.md`, or
19
- - `docs/governance/agents-routing/doc-only-v0.9.md`
20
- 7. `docs/reference/execution/current-work.md`
21
- 8. Before non-trivial implementation, debugging, release, architecture, or
22
- migration work, run `pro-gov learn recall --query "<task summary>"` and read
23
- any relevant prior-learning hits before changing files.
24
-
25
- ## Governance
26
-
27
- - Use doc-gov for governed Markdown.
28
- - Governed Markdown lives under `docs/**` by default.
7
+ ## Boundary
8
+
9
+ - PGS governs this `AGENTS.md` entry and governed Markdown under `docs/**`.
29
10
  - Product artifacts outside `docs/**` are not governed docs unless this project explicitly opts them in.
30
- - Before creating docs: `pnpm doc-gov find <topic>`.
31
- - Before claiming doc work complete:
32
- - `pnpm doc-gov router-check`
33
- - `pnpm doc-gov check`
34
- - `pnpm doc-gov scan --check`
35
- - `pnpm doc-gov links`
36
- - `pnpm doc-gov audit`
37
- - `pnpm doc-gov doctor`
38
-
39
- ## Routing
40
-
41
- - Name this project's adopted profile: `engineering-runtime` or `doc-only`.
42
- - Point to the chosen agents-routing file from `docs/governance/agents-routing/`.
43
- - Before non-trivial work, use Learning Recall. After verified work, use `capture-learning` only when a non-obvious reusable lesson exists.
44
- - Do not install Stop/SubagentStop workflow reminder hooks.
45
- - Doc-only projects should say that engineering test workflows are not enabled by default.
11
+ - `README.md` is the human-facing introduction; read it only for positioning,
12
+ public explanation, or README work.
13
+ - `docs/reference/execution/current-work.md` is the active-work index; read it
14
+ when the task depends on current priorities or in-flight work.
15
+ - This project's adopted profile is `PROFILE_NAME`.
16
+ - Its selected agents routing file is `PROFILE_ROUTE` under
17
+ `docs/governance/agents-routing/`.
18
+
19
+ ## Documentation Tasks
20
+
21
+ When the task creates, edits, moves, deletes, or governs documentation, read
22
+ `docs/governance/boundary.md`, `docs/governance/ssot-v0.9.md`,
23
+ `docs/governance/doc-agent-rules.md`, `docs/governance/doc-types.md`, the
24
+ selected agents routing file, and all Markdown under `docs/policy/**/*.md`.
25
+ That policy set includes subdirectories and symlinked shared-rule files; keep
26
+ project AI development policy in `docs/policy/`.
46
27
 
47
28
  <!-- PGS-ROUTER:END -->
48
29
 
49
30
  ## Upstream Rule
50
31
 
51
- Do not locally invent doc-gov core changes such as new document statuses, frontmatter schema, lifecycle rules, shared agents-routing rules, or external shared-rule placement contracts. If such a change seems necessary, propose it upstream in the Project Governance System upstream repository first.
32
+ Do not locally invent doc-gov core changes such as new document statuses,
33
+ frontmatter schema, lifecycle rules, shared agents-routing rules, or external
34
+ shared-rule placement contracts. Propose them in the Project Governance System
35
+ upstream repository first.
@@ -6,7 +6,7 @@ status: stable
6
6
  canonical: true
7
7
  owner: human
8
8
  created: 2026-05-09
9
- last_reviewed: 2026-05-09
9
+ last_reviewed: 2026-07-12
10
10
  domain: agents-routing
11
11
  tags:
12
12
  - agents-routing
@@ -51,7 +51,6 @@ flowchart TD
51
51
 
52
52
  ## Rules
53
53
 
54
- - Do not ask whether the task needs TDD unless the project has actual runtime code.
55
54
  - Prefer SSOT, provenance, and approval clarity over engineering ceremonies.
56
55
  - Use AI-in-the-Loop for evidence: inspect source, change one thing, verify the target document or asset path.
57
56
 
package/cli-guide.md CHANGED
@@ -20,6 +20,7 @@ pro-gov portfolio check --config /path/to/portfolio.json
20
20
  pro-gov portfolio plan --config /path/to/portfolio.json --target web-app --json
21
21
  pro-gov portfolio assets-check --config /path/to/portfolio.json --json
22
22
  pro-gov portfolio doctor --config /path/to/portfolio.json --json
23
+ pro-gov portfolio ai-health --config /path/to/portfolio.json --out audits/portfolio-ai-health/2026-07-12
23
24
  pro-gov learn recall --query "release downstream sync" --target .
24
25
  pro-gov learn capture --title "Reusable learning" --summary "Reusable lesson..." --target .
25
26
  pro-gov lens inspect --target .
@@ -71,6 +72,7 @@ pro-gov portfolio check --config /path/to/control-repo/.pro-gov/portfolio.json -
71
72
  pro-gov portfolio plan --config /path/to/control-repo/.pro-gov/portfolio.json --target web-app --json
72
73
  pro-gov portfolio assets-check --config /path/to/control-repo/.pro-gov/portfolio.json --json
73
74
  pro-gov portfolio doctor --config /path/to/control-repo/.pro-gov/portfolio.json --json
75
+ pro-gov portfolio ai-health --config /path/to/control-repo/.pro-gov/portfolio.json --out audits/portfolio-ai-health/2026-07-12
74
76
  pro-gov assets plan --bundle base-governance --target . --out .pro-gov/asset-plan.json
75
77
  pro-gov assets plan --bundle project-lens --target /path/to/project --host codex --placement manual --out /tmp/project-lens-plan.json
76
78
  pro-gov assets apply --plan .pro-gov/asset-plan.json
@@ -89,6 +91,12 @@ Skill placement normally comes from the asset registry. Use `--placement
89
91
  auto|manual` only as a migration override when deliberately moving an existing
90
92
  target.
91
93
 
94
+ `portfolio ai-health` performs a read-only structural inventory of the control
95
+ plane, execution engine, and registered targets, then writes a fixed local HTML
96
+ dashboard plus JSON evidence to the explicit `--out` directory. It records MCP
97
+ server names and environment filenames, but never reads or emits secret values,
98
+ environment values, MCP commands, arguments, or MCP environment maps.
99
+
92
100
  Portfolio manifests are external configuration files owned by a user or
93
101
  organization. PGS provides the format and commands; it does not publish a real
94
102
  user's private downstream project list. A normal npm user can omit