@research-engineering/agentic-proofkit 0.1.150 → 0.1.152

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/README.md CHANGED
@@ -12,8 +12,8 @@ packets without copying verifier logic between projects.
12
12
 
13
13
  | Surface | State |
14
14
  |---|---|
15
- | Source visibility | Public |
16
- | Current layer | Public source; release evidence is version-specific |
15
+ | Source repository | Declared in package metadata; provider visibility is a live GitHub fact |
16
+ | Current layer | Public-source workflow; release evidence is version-specific |
17
17
  | Runtime implementation | Go CLI with npm and Python wrapper packaging |
18
18
  | Package release | Scoped npm release channel configured; exact version and registry identity are owned by npm and GitHub Release artifacts |
19
19
  | Public-source provenance | Claimed only for a version whose release assets, registry identity, and checksum manifests are artifact-closed |
@@ -45,9 +45,11 @@ vulnerability absence, or consumer rollout safety by itself.
45
45
  inventory admission, command semantic routes without owner-declared proof
46
46
  identities, route-index-derived semantic proof identities, direct app
47
47
  semantic routes outside the command-scoped app test, package-level semantic
48
- routes outside the descriptor-owned command package, and missing matching
49
- semantic command evidence without claiming line coverage or exhaustive test
50
- semantic completeness.
48
+ routes outside the descriptor-owned command package, semantic command routes
49
+ whose parsed Go test body lacks the source-owned executable oracle marker for
50
+ the exact emitted command route fact, and missing matching semantic command
51
+ evidence without claiming line coverage or exhaustive test semantic
52
+ completeness.
51
53
  - `REQ-PROOFKIT-QUALITY-011`: CI separates the OS-independent full
52
54
  source/package gate from macOS platform smoke, uses explicit hosted runner
53
55
  labels instead of floating latest labels, and exposes one fail-closed
@@ -129,7 +129,7 @@
129
129
  {
130
130
  "requirementId": "REQ-PROOFKIT-QUALITY-010",
131
131
  "ownerId": "proofkit.supply-chain-quality",
132
- "invariant": "Coverage metrics report requirement, binding, witness, CLI inventory linkage, and descriptor-owned command semantic-route coverage from admitted test-evidence-inventory rows, failing closed on explicit requirement/proof linkage dead zones, failed command-route inventory admission, command semantic routes without owner-declared proof identities, route-index-derived semantic proof identities, direct app semantic routes outside the command-scoped app test, package-level semantic routes outside the descriptor-owned command package, or missing matching semantic command evidence without claiming line coverage or exhaustive test semantic completeness.",
132
+ "invariant": "Coverage metrics report requirement, binding, witness, CLI inventory linkage, and descriptor-owned command semantic-route coverage from admitted test-evidence-inventory rows, failing closed on explicit requirement/proof linkage dead zones, failed command-route inventory admission, command semantic routes without owner-declared proof identities, route-index-derived semantic proof identities, direct app semantic routes outside the command-scoped app test, package-level semantic routes outside the descriptor-owned command package, semantic command routes whose parsed Go test body lacks the source-owned executable oracle marker for the exact emitted command ref, selector, source path, falsifier ids, oracle id, and expected public outcome, or missing matching semantic command evidence without claiming line coverage or exhaustive test semantic completeness.",
133
133
  "claimLevel": "blocking",
134
134
  "riskClass": "medium",
135
135
  "proofBindingRefs": ["proofkit/requirement-bindings.json"],
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.150",
4
+ "version": "0.1.152",
5
5
  "type": "module",
6
6
  "license": "MIT",
7
7
  "sideEffects": false,
@@ -23,7 +23,6 @@
23
23
  "files": [
24
24
  "ADOPTION.md",
25
25
  "AGENTS.md",
26
- "BACKLOG.md",
27
26
  "CONTRIBUTING.md",
28
27
  "LICENSE",
29
28
  "NON_CLAIMS.md",
@@ -719,8 +719,12 @@
719
719
  "commandId": "proofkit.coverage-metrics",
720
720
  "inputSelectors": [
721
721
  "docs/specs",
722
+ "internal/app",
722
723
  "internal/app/command_coverage_routes.go",
724
+ "internal/app/command_coverage_source.go",
723
725
  "internal/app/command_registry.go",
726
+ "internal/command",
727
+ "internal/testsupport/commandcoverage",
724
728
  "internal/tools/coveragemetrics",
725
729
  "proofkit/cli-contract.v1.json",
726
730
  "proofkit/requirement-bindings.json",
package/BACKLOG.md DELETED
@@ -1,56 +0,0 @@
1
- # Proofkit Backlog
2
-
3
- This file is the canonical active-work ledger for
4
- `research-engineering/agentic-proofkit`.
5
-
6
- It tracks only current `NEXT`, `BLOCKED`, or `DEFERRED` work. It is not a
7
- roadmap, release log, proof registry, architecture document, CLI manual, or
8
- historical completion archive.
9
-
10
- ## Current State
11
-
12
- Active work is limited to the rows below.
13
-
14
- The public source cutover, scoped npm channel, optional PyPI channel, provider
15
- security setup, first-consumer proof, and second-consumer pilot have all been
16
- closed. Durable rules and reusable architecture now live in their owner
17
- surfaces:
18
-
19
- - `README.md` for human orientation;
20
- - `ADOPTION.md` for adoption, distribution, rendering, requirement, contract,
21
- test, and agent-guidance models;
22
- - `NON_CLAIMS.md` for boundary denials;
23
- - `docs/proofkit-contract-map.md` for command-family routing and agent
24
- decision procedure;
25
- - `docs/release-process.md` for release-channel evidence and publication
26
- process;
27
- - `docs/specs/**/requirements.v1.json` for durable machine requirements;
28
- - `proofkit/*.json` for shipped machine contracts and proof routes;
29
- - source, tests, package metadata, and workflows for executable behavior.
30
-
31
- ## Admission Rules
32
-
33
- Add a row only when new work is accepted and cannot be represented more
34
- precisely by an existing owner surface.
35
-
36
- Every row must be falsifiable and include:
37
-
38
- - `Status`: `NEXT`, `BLOCKED`, or `DEFERRED`;
39
- - `ID`: stable owner-scoped identifier;
40
- - `Scope`: one bounded reason to change;
41
- - `Completion condition`: objective proof or explicit retirement condition.
42
-
43
- When a row is completed, remove it from this active backlog after its durable
44
- rule, evidence, or behavior is represented by the owning source, test,
45
- contract, release artifact, provider record, or documentation surface. Do not
46
- retain completed rows here as history.
47
-
48
- Historical evidence belongs in pull requests, release artifacts, registry
49
- records, generated release manifests, or the owning docs named above.
50
-
51
- ## Open Rows
52
-
53
- | Status | ID | Scope | Completion condition |
54
- |---|---|---|---|
55
- | BLOCKED | RELEASE-01 | Decide whether normalized post-create GitHub Release facts need durable public evidence beyond retained workflow artifacts under immutable GitHub Releases. | Either keep `github-release.json` as retained workflow evidence with explicit non-claims, or design a provider-compatible public evidence channel that does not require post-create Release asset mutation. Completion requires a release-proof design and live provider proof; direct backfill/upload is blocked by immutable Release upload rejection. |
56
- | BLOCKED | RELEASE-02 | Resolve or explicitly retire the immutable historical GitHub Release asset-closure gap where release metadata references a notes asset that the published release does not contain. | Either attach the exact checksum-matching notes asset if provider policy allows, or record the provider-impossible closure in the release evidence model and prove future releases cannot repeat the gap. Completion requires live provider proof; direct backfill is currently blocked by immutable Release upload rejection. |