@research-engineering/agentic-proofkit 0.1.136 → 0.1.137

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/BACKLOG.md CHANGED
@@ -66,7 +66,7 @@ only when these criteria are satisfied or explicitly retired by owner decision:
66
66
  | DONE | IMPORT-05 | Historical design and plan cleanup | Durable claims from pre-cutover design and implementation-plan work are represented by deterministic specs, proof bindings, tests, package-public docs, or open backlog rows. No source-repository design documents or implementation plans are retained as current authority. |
67
67
  | DONE | IMPORT-06 | Remaining source-local code delta audit | Non-document source comparison found no old source file missing from the public source tree. Old source bytes remain candidate evidence only and are not imported over current hardening. |
68
68
  | DONE | RELEASE-01 | Public source release | `v0.1.135` was published from this public repository through npm Trusted Publisher, post-publish npm registry identity was captured, root-only installed-package proof passed, and GitHub Release assets were published. PyPI publication and GitHub artifact attestations were skipped by explicit optional-channel policy and are not claimed. |
69
- | OPEN | RELEASE-02 | Scoped npm package identity | Source is staged for `@research-engineering/agentic-proofkit@0.1.136` while preserving the `agentic-proofkit` CLI binary and Python package identities. Completion requires scoped npm Trusted Publisher configuration, a `v0.1.136` release from public source, post-publish scoped npm registry identity, root-only installed-package JSON CLI ABI proof, and an explicit compatibility or deprecation disposition for the unscoped npm package. |
69
+ | OPEN | RELEASE-02 | Scoped npm package identity | `@research-engineering/agentic-proofkit@0.1.136` created the scoped public package namespace and Trusted Publisher settings without claiming workflow release provenance. Source is staged for `@research-engineering/agentic-proofkit@0.1.137` while preserving the `agentic-proofkit` CLI binary and Python package identities. Completion requires a `v0.1.137` release from public source through the scoped Trusted Publisher path, post-publish scoped npm registry identity, root-only installed-package JSON CLI ABI proof, and an explicit compatibility or deprecation disposition for the unscoped npm package. |
70
70
  | DONE | SECURITY-01 | Provider security settings | Repository is public with collaborator-only PR creation, public issues, squash-only merges, branch protection on `main`, strict required CI, CodeQL, OSV source advisory scanning, Scorecard, Dependabot security updates, secret scanning, and push protection. Non-provider secret patterns and validity checks remain unavailable or disabled under the current provider plan and are not claimed. |
71
71
  | DONE | CONSUMER-01 | Public-package consumer proof | A private first consumer repository consumed exact public npm `agentic-proofkit@0.1.134` through its repository-owned external-consumer gate. The proof installed the package into an isolated temporary consumer, matched the admitted tarball integrity and shasum, proved lockfile resolution was not workspace based, ran installed CLI `self-check`, `witness-plan`, and `release-authority`, proved rollback by removing the dependency from the temporary lockfile, and preserved consumer-owned native witness authority. |
72
72
  | DONE | CONSUMER-02 | Second-consumer pilot | A private topology-distinct Python/FastAPI consumer module was run through explicit-input warn-mode `gradual-adoption-guidance` and `--agent-envelope` pilot records. Proofkit admitted the caller-owned route, reported one advisory candidate boundary, reported two missing proof-binding rule IDs as warnings, emitted route/bind/modernize/verify/promote agent actions, and kept enforcement blocked until consumer owners admit stable requirements and proof bindings. No generic Proofkit blocker was confirmed. |
package/README.md CHANGED
@@ -13,10 +13,10 @@ packets without copying verifier logic between projects.
13
13
  | Surface | State |
14
14
  |---|---|
15
15
  | Source visibility | Public |
16
- | Current layer | Public source with admitted unscoped npm release evidence; scoped npm identity is staged for the next release |
16
+ | Current layer | Public source with admitted unscoped npm release evidence; scoped npm identity has a bootstrap namespace release and is staged for Trusted Publisher release evidence |
17
17
  | Runtime implementation | Go CLI with npm and Python wrapper packaging |
18
- | Package release | `agentic-proofkit@0.1.135` is admitted; `@research-engineering/agentic-proofkit@0.1.136` is pending release evidence |
19
- | Public-source provenance | Admitted for `v0.1.135`; scoped package provenance is pending a reviewed scoped release |
18
+ | Package release | `agentic-proofkit@0.1.135` is admitted; `@research-engineering/agentic-proofkit@0.1.136` is bootstrap-published; `@research-engineering/agentic-proofkit@0.1.137` is pending release evidence |
19
+ | Public-source provenance | Admitted for `v0.1.135`; scoped package Trusted Publisher provenance is pending a reviewed scoped release |
20
20
  | License | MIT |
21
21
 
22
22
  ## Project Boundary
@@ -121,11 +121,12 @@ The `release` workflow must:
121
121
 
122
122
  1. verify source package identity;
123
123
  2. run the package gate;
124
- 3. build publish dry-run evidence;
124
+ 3. build publish candidate evidence through either npm publish dry-run or
125
+ exact existing-byte-match validation for an already published version;
125
126
  4. build Python wheel candidates for the same embedded Go CLI;
126
127
  5. prove publish readiness before any registry side effect: the tag must equal
127
128
  `v<package.json version>`, target a commit reachable from `main`, and have
128
- npm dry-run evidence plus PyPI wheel candidates;
129
+ npm publish candidate evidence plus PyPI wheel candidates;
129
130
  6. publish to public npm through the admitted trusted path, or record
130
131
  `existing_byte_match` when the same version already exists with exact
131
132
  candidate bytes;
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@research-engineering/agentic-proofkit",
3
3
  "description": "Reusable proof profile, report, graph, and witness-planning primitives.",
4
- "version": "0.1.136",
4
+ "version": "0.1.137",
5
5
  "type": "module",
6
6
  "license": "MIT",
7
7
  "sideEffects": false,