principal-pi-skills 3.1.0 → 3.2.0

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.
package/AGENTS.md CHANGED
@@ -119,11 +119,11 @@ to every output.
119
119
 
120
120
  ## Setup (pi)
121
121
 
122
- 1. `pi install git:github.com/mojomanyana/principal-pi-skills@v3.1.0` — the immutable install
123
- coordinate for source version `3.1.0`. Publication status is external to these package bytes:
122
+ 1. `pi install git:github.com/mojomanyana/principal-pi-skills@v3.2.0` — the immutable install
123
+ coordinate for source version `3.2.0`. Publication status is external to these package bytes:
124
124
  run `npm view principal-pi-skills version dist-tags --json` and check the
125
- [GitHub release](https://github.com/mojomanyana/principal-pi-skills/releases/tag/v3.1.0) before
126
- installing. Preparation evidence (2026-09-11): `v3.1.0` was pending and npm `latest` was `3.0.1`;
125
+ [GitHub release](https://github.com/mojomanyana/principal-pi-skills/releases/tag/v3.2.0) before
126
+ installing. Preparation evidence (2026-09-11): `v3.2.0` was pending and npm `latest` was `3.1.0`;
127
127
  this dated fact is not current registry guidance. `standard` is the default assurance
128
128
  profile, so a v2 invocation keeps working unchanged. It registers the
129
129
  skills and the `/principal-feature` + `/principal-bugfix` commands via the `pi`
package/CHANGELOG.md CHANGED
@@ -6,6 +6,14 @@ Where review revealed a prior claim or design decision didn't hold up under clos
6
6
 
7
7
  ---
8
8
 
9
+ ## [3.2.0] — 2026-09-11
10
+
11
+ **Changed — ordinary assurance status is current by default.** `report --format human` and the no-format default now render the existing `current-v1` applicability semantics for current, stale and superseded task/check evidence. The original all-history report remains byte-preserved as `--format human-legacy`; explicit `current-v1` JSON and in-toto machine formats are unchanged.
12
+
13
+ **Compatibility — presentation default only.** Native assurance gates, event replay, acceptance semantics, generated skill/agent/prompt text, external compatibility adapters and the 28-file npm package boundary are unchanged. A current status is not retrospective truth or human acceptance.
14
+
15
+ **Changed — release evidence remains static and model-free.** No skill, prompt or agent text changed from 3.1.0, and no 3.2.0 model score is claimed. Deterministic unit, generated-contract, clean-install, pack and lint checks are the release evidence. Preparation evidence (2026-09-11): `v3.2.0` was pending and npm `latest` was `3.1.0`; check live status with `npm view principal-pi-skills version dist-tags --json` and the [GitHub release](https://github.com/mojomanyana/principal-pi-skills/releases/tag/v3.2.0).
16
+
9
17
  ## [3.1.0] — 2026-09-11
10
18
 
11
19
  **Added — opt-in current evidence applicability projection.** The shipped assurance CLI now supports
package/README.md CHANGED
@@ -8,15 +8,15 @@ to isolated contexts (`plan`, `review`, `debug` — single-shot variants in `age
8
8
  generated from the same contract as the skill). The files follow the [Agent Skills](https://agentskills.io/specification)
9
9
  standard, so other harnesses can consume the skills, but pi is the supported target.
10
10
 
11
- **Source version:** `3.1.0`. Release coordinates are npm `principal-pi-skills@3.1.0` and the
12
- immutable git tag `v3.1.0`. Publication status lives outside these immutable package bytes: run
11
+ **Source version:** `3.2.0`. Release coordinates are npm `principal-pi-skills@3.2.0` and the
12
+ immutable git tag `v3.2.0`. Publication status lives outside these immutable package bytes: run
13
13
  `npm view principal-pi-skills version dist-tags --json` and check the
14
- [GitHub release](https://github.com/mojomanyana/principal-pi-skills/releases/tag/v3.1.0) before
15
- installing. Preparation evidence (2026-09-11): the `v3.1.0` tag was pending and npm `latest` was
16
- `3.0.1`; this dated fact is not a claim about current registry state. This version adds the opt-in
17
- `current-v1` assurance evidence projection and validates cross-repository compatibility without
18
- shipping the source-only host adapters. It carries no new model score; the committed board remains
19
- a historical v2.4 baseline.
14
+ [GitHub release](https://github.com/mojomanyana/principal-pi-skills/releases/tag/v3.2.0) before
15
+ installing. Preparation evidence (2026-09-11): the `v3.2.0` tag was pending and npm `latest` was
16
+ `3.1.0`; this dated fact is not a claim about current registry state. The ordinary assurance human
17
+ report now uses current applicability semantics. `--format human-legacy` retains the original
18
+ all-history bytes; explicit `current-v1` and in-toto formats are unchanged. It carries no new model
19
+ score; the committed board remains a historical v2.4 baseline.
20
20
 
21
21
  The set is built for **one principal engineer steering at a high level while skills and
22
22
  subagents do the work.** Two properties follow, and every design choice below serves them:
@@ -105,10 +105,10 @@ docs/demos/ the chains running end to end, repo-verifi
105
105
  1. **Skills + prompts** — install an immutable tag, not a branch:
106
106
 
107
107
  ```
108
- pi install git:github.com/mojomanyana/principal-pi-skills@v3.1.0
108
+ pi install git:github.com/mojomanyana/principal-pi-skills@v3.2.0
109
109
  ```
110
110
 
111
- This source tree represents `3.1.0`. Before installing, use the live npm and GitHub checks above
111
+ This source tree represents `3.2.0`. Before installing, use the live npm and GitHub checks above
112
112
  to confirm publication; do not infer registry state from immutable README text. v3 adds the
113
113
  risk-adaptive assurance profiles; `standard` is the default and preserves v2 invocation,
114
114
  so upgrading from `2.4.0` changes no command you already type.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "principal-pi-skills",
3
- "version": "3.1.0",
3
+ "version": "3.2.0",
4
4
  "description": "Skill framework for principal-level software engineering: seven dual-use skills (decide, architect, plan, build, review, debug, git-ops) that work unedited as loaded skills or as subagent system prompts.",
5
5
  "license": "MIT",
6
6
  "author": "Nemanja Alavanja",
@@ -1933,6 +1933,33 @@ export function buildCurrentApplicabilityProjection(state) {
1933
1933
  };
1934
1934
  }
1935
1935
 
1936
+ export function renderCurrentApplicabilityReport(state) {
1937
+ const projection = buildCurrentApplicabilityProjection(state);
1938
+ const lines = [
1939
+ `# Current assurance: ${projection.ledger.runId}`,
1940
+ "",
1941
+ `Result: ${projection.result}`,
1942
+ `Candidate: head=${projection.candidate.head_sha ?? "UNKNOWN"}; tree=${projection.candidate.tree_sha ?? "UNKNOWN"}`,
1943
+ `Freshness floor: seq ${projection.authority.freshness_floor}`,
1944
+ "",
1945
+ "## Current tasks",
1946
+ ...(projection.tasks.length ? projection.tasks.map(task =>
1947
+ `- ${task.task_id}: ${task.applicability}; status=${task.status}` + (task.reasons.length ? `; ${task.reasons.join(",")}` : "")) : ["- None declared."]),
1948
+ "",
1949
+ "## Current checks",
1950
+ ...(projection.checks.length ? projection.checks.map(check =>
1951
+ `- ${check.status}: ${check.kind}; task=${check.task_id ?? "run"}; command=${quoted(check.command)}`) : ["- None recorded."]),
1952
+ "",
1953
+ "## Required evidence",
1954
+ ...projection.requirements.map(requirement =>
1955
+ `- ${requirement.status}: ${requirement.kind}; task=${requirement.task_id ?? "run"}` + (requirement.command ? `; command=${quoted(requirement.command)}` : "")),
1956
+ "",
1957
+ "Historical/stale/superseded receipts remain in --format current-v1. Use --format human-legacy for the original all-history report.",
1958
+ projection.notice,
1959
+ ];
1960
+ return lines.join("\n");
1961
+ }
1962
+
1936
1963
  /** Project validated ledger events into an unsigned in-toto test-result Statement (legacy semantics). */
1937
1964
  export function buildAssuranceStatement(events) {
1938
1965
  const evidence = events.filter((event) => event.type === "evidence_recorded");
@@ -2091,9 +2118,11 @@ export function runCli(argv, { cwd = process.cwd(), env = process.env, out = con
2091
2118
  const { state, events } = store.load(runId, { withEvents: true });
2092
2119
  out(format === "current-v1"
2093
2120
  ? JSON.stringify(buildCurrentApplicabilityProjection(state), null, 2)
2094
- : ["in-toto", "in-toto-legacy"].includes(format)
2095
- ? JSON.stringify(buildAssuranceStatement(events), null, 2)
2096
- : renderAssuranceReport(state, events));
2121
+ : format === "human"
2122
+ ? renderCurrentApplicabilityReport(state)
2123
+ : ["in-toto", "in-toto-legacy"].includes(format)
2124
+ ? JSON.stringify(buildAssuranceStatement(events), null, 2)
2125
+ : renderAssuranceReport(state, events));
2097
2126
  return 0;
2098
2127
  }
2099
2128
  if (command === "event") {