Skip to content

Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.

docs: record verified npm 0.1.0 publication

David Zhang209ddc1610f2
diff --git a/README.md b/README.md
index 34aae9a..deff3ac 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,8 @@ configuration changes only when the user explicitly installs or exports it.
The npm package is `@dzhng/jevgrep`; its executable is `jg`. The project uses the
[MIT license](LICENSE). [Release guidance](scripts/RELEASING.md) describes the
-verified tarball and GitHub tag workflow. Publication requires the repository's
-`NPM_TOKEN` secret and a deliberate release tag. The user authorized `0.1.0`
-publication after the completed repeat and final release checks; the frozen benchmark archive
-remains `0.0.0` and is not a publication candidate.
+verified tarball and GitHub tag workflow. Version [0.1.0](https://www.npmjs.com/package/@dzhng/jevgrep/v/0.1.0) is published:
+`npm install --global @dzhng/jevgrep`. The
+[release record](specs/done/jevgrep/assets/release-0.1.0.md) owns artifact identity
+and verification. The frozen benchmark archive remains `0.0.0`; publication does
+not replace either measured cohort.
diff --git a/specs/done/jevgrep/README.md b/specs/done/jevgrep/README.md
index 85ee94f..787f170 100644
--- a/specs/done/jevgrep/README.md
+++ b/specs/done/jevgrep/README.md
@@ -23,8 +23,8 @@ finished with seven solves, seven of eight baseline solves preserved, four
successful cost wins and 40.70% lower full Sol cost. Its original gate also remains
failed. Both cohorts retain every attempt; neither best-cell pooling nor baseline
reruns contribute to either result. No further repeat was authorized or run.
-The user authorized publication of `0.1.0` after closeout. The
-[release evidence](assets/release-0.1.0.md) distinguishes local validation from
+The user explicitly authorized publication, and `0.1.0` is published on npm.
+The [release evidence](assets/release-0.1.0.md) records local validation,
CI publication and registry verification. Both measured cohorts retain the frozen
`0.0.0` archive; release preparation changes version identity, not their evidence.
diff --git a/specs/done/jevgrep/assets/release-0.1.0.md b/specs/done/jevgrep/assets/release-0.1.0.md
index a145ff9..35b5f3e 100644
--- a/specs/done/jevgrep/assets/release-0.1.0.md
+++ b/specs/done/jevgrep/assets/release-0.1.0.md
@@ -1,9 +1,20 @@
# 0.1.0 release evidence
-The user explicitly authorized publishing `0.1.0` after the variance repeat and
-closeout finish. Publication is pending; preparing an archive is not publication.
+Published `@dzhng/[email protected]` to npm as `latest`, with provenance, on
+2026-09-26 under the user's explicit authorization. Both jobs in the
+[release workflow](https://github.com/dzhng/jevgrep/actions/runs/36253715874)
+passed: publication and independent registry verification. The
+[GitHub release](https://github.com/dzhng/jevgrep/releases/tag/v0.1.0)
+links the tag at commit `c6842af31d4442791c0769b5b65899693e114a6c`.
-The final local release candidate is
+Published tarball SHA-256:
+`0909f05dbabf74feaa6358e182b6e7743e8f5f16a791ebfd53367b3974d01f6d`.
+Registry and candidate integrity:
+`sha512-ISmf+ujNstQ5spvxkwJ43Dk3ZTjAfEvEPsY67IUoWpR/t06Fuqn/W+xHTYKKny8xok5jVLjEtVZ0BvkkjdCXNw==`.
+The workflow artifact `jevgrep-0.1.0` retains the archive and manifest. Registry
+metadata confirms version `0.1.0`, `latest`, and an SLSA provenance attestation.
+
+The locally verified release candidate is
`/tmp/jg-010-final-release/dzhng-jevgrep-0.1.0.tgz`, SHA-256
`447cdeb88695b6851efb7fbe4bfd628a69e1c83b2f1651e7ed3f3453fe747523`.
It passed the release identity/content/license validator. Compared with the
@@ -22,7 +33,20 @@ Logs: `/tmp/jg-010-{native,installed}.log` and
Full deterministic verification of the unchanged
implementation is retained in [freshness verification](source-freshness.md).
-The tag workflow still has to run its own full verification, pack and validate
-its candidate, test those exact bytes, publish them, and verify the registry
-archive's integrity and installed behavior. The local hash above is local proof;
-the workflow's retained manifest owns the published artifact identity.
+A final documentation-only commit removes stale pre-publication wording from
+the packaged README. It does not change executable or runtime assets. The first
+workflow was canceled before packing or publication (publish step skipped), then
+the unpublished tag was moved to that documentation commit. The canceled run
+is retained at https://github.com/dzhng/jevgrep/actions/runs/36253611769.
+
+The successful workflow ran full deterministic verification, release validation,
+exact-tarball Docker journeys, dry-run publication, and provenance publication.
+Its separate registry job fetched `@dzhng/[email protected]`, verified identical
+integrity and passed all 24 installed journeys from those public bytes. Full log:
+`/tmp/jg-010-ci.log` and the linked workflow.
+
+The downloaded CI archive also passed both native macOS arm64 smoke journeys on
+Node 24.14.0 (`/tmp/jg-010-ci-native.log`). A member-by-member comparison with the
+locally verified candidate found only the expected README wording difference;
+all executable and runtime assets are byte-identical (`/tmp/jg-010-ci-parity.json`).
+No further paid model evaluations or baseline executions accompanied publication.