hamzahskafi · Oct 13, 2026 · Oct 13, 2026
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -4,6 +4,14 @@ All notable changes to this project are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and releases follow
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+### Changed
+
+- Recorded the independent inspection of npm `@augmentworks/cli@0.3.9`.
+  The published tarball is unchanged and still embeds the prior 0.3.8
+  `LAST_VERIFIED` snapshot.
+
 ## [0.3.9] - 2026-10-13
 
 Immutable patch. Customers can install the hosted run-scope lookup hardening

diff --git a/docs/discovery-handoff.md b/docs/discovery-handoff.md
@@ -15,7 +15,7 @@ constants. Packaged identity versus post-publication inspection is defined in
 | `capabilities.localDemo` | `true` |
 | Demo invocation | `node dist/index.js demo` |
 | Provenance | `sourceCommit: null`, `verifiedAt: null` |
-| Last independently inspected npm | `@augmentworks/cli@0.3.8` (tag `v0.3.8` commit `f36d9086bad1ac109a7670e8acc9bf14a5d15047`, published 2026-10-08T01:42:45.969Z, integrity `sha512-T+e1VWQ8plx0jJMdkOHxocpH8SjCr9BSeRLMsCnCHAO0Z3z9bhgIf0um9x6eyWJfwPz01YOL7CZvM6sLTiSLIA==`, tarball SHA-256 `2849ceb6c3c9b18d02a4cb2aa7f0ad470ec74cb7846a8eadf91d83147965f36e`, 74 files). The registry document omitted `gitHead`. That artifact stays `lastIndependentlyInspected`. `thisPackageIdentity` for this 0.3.9 checkout is `pending-protected-publish`. The published 0.3.8 tarball still embeds the prior `LAST_VERIFIED` 0.3.7 snapshot; that inspection commit is not inside that artifact. |
+| Last independently inspected npm | `@augmentworks/cli@0.3.9` (tag `v0.3.9` commit `9e7919cbfe583cc15701904580be9d36da3bcaf4`, published 2026-10-13T20:31:53.099Z, integrity `sha512-ZDXMg5etb3UNGGrakJ5Iz+oYAkAOHqOt2DIVn41MvFnLjmlz/AIUL05pYGJHnDISo1At5Cik6Kjkses4hB4CYA==`, tarball SHA-256 `176e0b6e1ae6e68b98e1ee363568241ac6534ceb5317ebd9f618980ef0efe72b`, 74 files). The registry document omitted `gitHead`. `thisPackageIdentity` is `independently-inspected`. The published 0.3.9 tarball still embeds the prior `LAST_VERIFIED` 0.3.8 snapshot; this inspection commit is not inside that artifact. |
 | Immutable prior npm | `@augmentworks/cli@0.3.8`, `@augmentworks/cli@0.3.7`, `@augmentworks/cli@0.3.6`, `@augmentworks/cli@0.3.5`, `@augmentworks/cli@0.3.4`, and `@augmentworks/cli@0.3.3` (gitHead `4a08ea0d352f2515e725cb9ca946807112422436`). Do not overwrite or relabel. |
 
 The committed discovery manifest stays `development` for a source checkout. A
@@ -31,9 +31,9 @@ node scripts/verify-published-discovery.mjs --version 0.3.7
 ```
 
 `verify-published-discovery` emits metadata and does not replace executable
-inspection. Independently inspected 0.3.8 registry evidence stays
-`lastIndependentlyInspected`. `thisPackageIdentity` for this checkout is
-`0.3.9` / `pending-protected-publish` in
+inspection. Independently inspected 0.3.9 registry evidence is
+`lastIndependentlyInspected` and `thisPackageIdentity`
+(`independently-inspected`) in
 `docs/feature-readiness/published-registry-evidence.json`. Independently
 inspected 0.3.6 remains historical (capabilities, no saved-suite `/2`).
 Independently inspected 0.3.5 remains historical (it omits suite-selection
@@ -91,8 +91,7 @@ npm test
 
 ## Changed resources in this source revision
 
-- `lastIndependentlyInspected` remains independently inspected `@augmentworks/cli@0.3.8`
-- `thisPackageIdentity` is `@augmentworks/cli@0.3.9` with status `pending-protected-publish`
+- `lastIndependentlyInspected` and `thisPackageIdentity` record independently inspected `@augmentworks/cli@0.3.9`
 - Immutable 0.3.8, 0.3.7, 0.3.6, 0.3.5, 0.3.4, and 0.3.3 records stay unchanged
 - Source discovery stays `development`
 

diff --git a/docs/distribution-runbook.md b/docs/distribution-runbook.md
@@ -28,17 +28,15 @@ accurate extra term.
 
 ## npm
 
-Do not run `npm publish` ad hoc. `@augmentworks/cli@0.3.8` is published from
-GitHub tag `v0.3.8` (`f36d9086bad1ac109a7670e8acc9bf14a5d15047`) and
+Do not run `npm publish` ad hoc. `@augmentworks/cli@0.3.9` is published from
+GitHub tag `v0.3.9` (`9e7919cbfe583cc15701904580be9d36da3bcaf4`) and
 independently inspected. The trusted workflow's OIDC publish returned 404
 after the repository moved to `augmentworks-org`; the same tag bytes were
 published by the package owner and have no SLSA provenance attestation. Do not
-republish 0.3.8. `@augmentworks/cli@0.3.9` is the next immutable artifact:
-publish it only from GitHub release `v0.3.9` through
-`.github/workflows/release.yml`, then inspect that new tarball. Do not
-overwrite or relabel `@augmentworks/cli@0.3.8`, `0.3.7`, `0.3.6`, `0.3.5`,
-`0.3.4`, or `0.3.3`. The npm trusted publisher must allow
-`augmentworks-org/augmentworks-cli`.
+republish 0.3.9. Do not overwrite or relabel `@augmentworks/cli@0.3.8`,
+`0.3.7`, `0.3.6`, `0.3.5`, `0.3.4`, or `0.3.3`. The next release still needs a
+new tag and `.github/workflows/release.yml`, after the npm trusted publisher
+allows `augmentworks-org/augmentworks-cli`.
 
 ## Website
 

diff --git a/docs/feature-readiness/published-registry-evidence.json b/docs/feature-readiness/published-registry-evidence.json
@@ -1,34 +1,37 @@
 {
   "schemaVersion": "aw-cli-registry-evidence/1",
-  "semantics": "Post-publication independent inspection of npm tarballs. Packaged cli-release.json is this artifact's identity, not a live registry probe of this version. Do not overwrite or relabel existing npm versions. The published 0.3.8 tarball embeds the prior LAST_VERIFIED 0.3.7 snapshot; this file records the later inspection and is not inside that tarball. thisPackageIdentity for 0.3.9 stays pending-protected-publish until the trusted publish is inspected.",
+  "semantics": "Post-publication independent inspection of npm tarballs. Packaged cli-release.json is this artifact's identity, not a live registry probe of this version. Do not overwrite or relabel existing npm versions. The published 0.3.9 tarball embeds the prior LAST_VERIFIED 0.3.8 snapshot; this file records the later inspection and is not inside that tarball.",
   "lastIndependentlyInspected": {
     "packageName": "@augmentworks/cli",
-    "version": "0.3.8",
-    "gitHead": "f36d9086bad1ac109a7670e8acc9bf14a5d15047",
-    "integrity": "sha512-T+e1VWQ8plx0jJMdkOHxocpH8SjCr9BSeRLMsCnCHAO0Z3z9bhgIf0um9x6eyWJfwPz01YOL7CZvM6sLTiSLIA==",
-    "verifiedAt": "2026-10-08T01:42:45.969Z",
-    "githubRelease": "v0.3.8",
-    "githubReleasePublishedAt": "2026-10-08T01:28:38Z",
-    "githubReleaseUrl": "https://github.com/augmentworks-org/augmentworks-cli/releases/tag/v0.3.8",
-    "registryUrl": "https://registry.npmjs.org/@augmentworks/cli/0.3.8",
-    "tarballUrl": "https://registry.npmjs.org/@augmentworks/cli/-/cli-0.3.8.tgz",
-    "shasum": "009bc1739654c704b75967214ef9604374bd9a92",
-    "tarballSha256": "2849ceb6c3c9b18d02a4cb2aa7f0ad470ec74cb7846a8eadf91d83147965f36e",
+    "version": "0.3.9",
+    "gitHead": "9e7919cbfe583cc15701904580be9d36da3bcaf4",
+    "integrity": "sha512-ZDXMg5etb3UNGGrakJ5Iz+oYAkAOHqOt2DIVn41MvFnLjmlz/AIUL05pYGJHnDISo1At5Cik6Kjkses4hB4CYA==",
+    "verifiedAt": "2026-10-13T20:31:53.099Z",
+    "githubRelease": "v0.3.9",
+    "githubReleasePublishedAt": "2026-10-13T20:16:25Z",
+    "githubReleaseUrl": "https://github.com/augmentworks-org/augmentworks-cli/releases/tag/v0.3.9",
+    "registryUrl": "https://registry.npmjs.org/@augmentworks/cli/0.3.9",
+    "tarballUrl": "https://registry.npmjs.org/@augmentworks/cli/-/cli-0.3.9.tgz",
+    "shasum": "196d1c0eaa59a6c7a89166cdd0991ff1debbb82d",
+    "tarballSha256": "176e0b6e1ae6e68b98e1ee363568241ac6534ceb5317ebd9f618980ef0efe72b",
     "fileCount": 74,
-    "notes": "Downloaded registry tarball. GitHub tag v0.3.8 is f36d9086bad1ac109a7670e8acc9bf14a5d15047. The npm version document omitted gitHead. The tarball shasum matches the pack of that tag. No SLSA provenance attestation: trusted publishing from augmentworks-org returned 404 because the publisher was still bound to jeffskafi/augmentworks-cli. The same bytes were published by the package owner. Installed binary passed the AUG-272 packed report fixture, including exit 11 for a claimed pass with a required fail. Do not republish 0.3.8 or 0.3.7. Do not use @latest."
+    "notes": "Downloaded registry tarball. GitHub tag v0.3.9 is 9e7919cbfe583cc15701904580be9d36da3bcaf4. The npm version document omitted gitHead. The tarball shasum matches the pack of that tag. No SLSA provenance attestation: the trusted workflow's OIDC publish returned 404 after the repository moved to augmentworks-org, and the registry version document has no attestations. The same tag bytes were published by the package owner. Do not republish 0.3.9 or 0.3.8. Do not use @latest."
   },
   "thisPackageIdentity": {
     "packageName": "@augmentworks/cli",
     "version": "0.3.9",
     "publishedPackageVerifiedMeaning": "published-line identity, not inspection of this tarball",
-    "gitHead": null,
-    "integrity": null,
-    "verifiedAt": null,
-    "status": "pending-protected-publish",
-    "githubRelease": null,
-    "githubReleasePublishedAt": null,
+    "gitHead": "9e7919cbfe583cc15701904580be9d36da3bcaf4",
+    "integrity": "sha512-ZDXMg5etb3UNGGrakJ5Iz+oYAkAOHqOt2DIVn41MvFnLjmlz/AIUL05pYGJHnDISo1At5Cik6Kjkses4hB4CYA==",
+    "verifiedAt": "2026-10-13T20:31:53.099Z",
+    "status": "independently-inspected",
+    "githubRelease": "v0.3.9",
+    "githubReleasePublishedAt": "2026-10-13T20:16:25Z",
     "registryUrl": "https://registry.npmjs.org/@augmentworks/cli/0.3.9",
-    "notes": "Source 0.3.9 ships the AUG-335 hosted run-scope lookup hardening. Fill gitHead, integrity, and verifiedAt after the protected v0.3.9 GitHub release and npm trusted publish. Do not overwrite 0.3.8, 0.3.7, 0.3.6, 0.3.5, 0.3.4, or 0.3.3."
+    "shasum": "196d1c0eaa59a6c7a89166cdd0991ff1debbb82d",
+    "tarballSha256": "176e0b6e1ae6e68b98e1ee363568241ac6534ceb5317ebd9f618980ef0efe72b",
+    "fileCount": 74,
+    "notes": "Same immutable artifact as lastIndependentlyInspected. The inspection commit is later than the tag and is not inside the tarball. The registry document omitted gitHead. Do not overwrite 0.3.9, 0.3.8, 0.3.7, 0.3.6, 0.3.5, 0.3.4, or 0.3.3."
   },
   "immutableArtifacts": [
     {
@@ -84,6 +87,16 @@
       "tarballSha256": "2849ceb6c3c9b18d02a4cb2aa7f0ad470ec74cb7846a8eadf91d83147965f36e",
       "fileCount": 74,
       "notes": "Independently inspected report-consistency patch. Registry metadata omitted gitHead. No SLSA provenance attestation. Do not republish or relabel."
+    },
+    {
+      "version": "0.3.9",
+      "gitHead": "9e7919cbfe583cc15701904580be9d36da3bcaf4",
+      "integrity": "sha512-ZDXMg5etb3UNGGrakJ5Iz+oYAkAOHqOt2DIVn41MvFnLjmlz/AIUL05pYGJHnDISo1At5Cik6Kjkses4hB4CYA==",
+      "verifiedAt": "2026-10-13T20:31:53.099Z",
+      "shasum": "196d1c0eaa59a6c7a89166cdd0991ff1debbb82d",
+      "tarballSha256": "176e0b6e1ae6e68b98e1ee363568241ac6534ceb5317ebd9f618980ef0efe72b",
+      "fileCount": 74,
+      "notes": "Independently inspected hosted run-scope lookup patch. Registry metadata omitted gitHead. No SLSA provenance attestation. Do not republish or relabel."
     }
   ]
 }
diff --git a/docs/feature-readiness/release-state.md b/docs/feature-readiness/release-state.md
@@ -12,26 +12,25 @@ honestly live inside that same tarball.
 | Package identity | `package.json`, `src/version.ts`, `CLI_RELEASE` / `schemas/v1/cli-release.json` | This artifact's version, protocol, and whether it is a **published-line release** versus a candidate snapshot. |
 | Source discovery | `contracts/discovery-manifest.json` | This git checkout. Stays `releaseStatus: development` with `node dist/index.js` commands. Not a live registry status. |
 | Independently inspected tarball | `LAST_VERIFIED_*` and `docs/feature-readiness/published-registry-evidence.json` | A **prior** (or separately inspected) registry version, keyed by version, gitHead, integrity, and `verifiedAt`. |
-| Website pin | Main repository discovery snapshot | Adopted only after independent review of **this** patch. This CLI does not self-adopt. Independently inspected 0.3.8 remains the website pin until 0.3.9 is inspected. Website adoption of that pin is separate. Independently inspected 0.3.7 remains historical and omits the AUG-272 consistency check. Independently inspected 0.3.6 remains historical (capabilities, no saved-suite `/2`). Independently inspected 0.3.5 remains historical and omits suite-selection `capabilities`. Source 0.3.9 is not a registry probe until the protected `v0.3.9` release. Do not fetch `latest`. |
+| Website pin | Main repository discovery snapshot | Adopted only after independent review of **this** patch. This CLI does not self-adopt. Independently inspected 0.3.9 is the current registry pin. Website adoption of that pin is separate. Independently inspected 0.3.8 remains historical and includes the AUG-272 consistency check. Independently inspected 0.3.7 remains historical and omits the AUG-272 consistency check. Independently inspected 0.3.6 remains historical (capabilities, no saved-suite `/2`). Independently inspected 0.3.5 remains historical and omits suite-selection `capabilities`. Do not fetch `latest`. |
 
 ## `published_package_verified` (`aw-cli-release/0.1`)
 
 `true` means this packaged identity is a published release line, not a
 candidate. It is **not** proof that this exact tarball was downloaded from npm
 and inspected.
 
-Independent inspection of `@augmentworks/cli@0.3.8` remains
-`lastIndependentlyInspected`. Packaged `LAST_VERIFIED_*` in this checkout names
-that artifact (tag `v0.3.8` commit `f36d9086bad1ac109a7670e8acc9bf14a5d15047`,
-published `2026-10-08T01:42:45.969Z`). The registry version document omitted
-`gitHead`. `thisPackageIdentity` for 0.3.9 stays
-`pending-protected-publish` until the trusted npm workflow runs and a later
-commit records the downloaded tarball. The immutable 0.3.8 tarball still embeds
-the prior 0.3.7 `LAST_VERIFIED_*` snapshot. Do not republish 0.3.8 to bake a
-newer receipt in.
-
-Do not overwrite or relabel existing npm versions, including 0.3.8, 0.3.7, and
-0.3.6.
+Independent inspection of `@augmentworks/cli@0.3.9` is
+`lastIndependentlyInspected` and `thisPackageIdentity`
+(`independently-inspected`). Packaged `LAST_VERIFIED_*` in this checkout names
+that artifact (tag `v0.3.9` commit `9e7919cbfe583cc15701904580be9d36da3bcaf4`,
+published `2026-10-13T20:31:53.099Z`). The registry version document omitted
+`gitHead`. The immutable 0.3.9 tarball still embeds the prior 0.3.8
+`LAST_VERIFIED_*` snapshot; this inspection commit is not inside that tarball.
+Do not republish 0.3.9 to bake the receipt in.
+
+Do not overwrite or relabel existing npm versions, including 0.3.9, 0.3.8, and
+0.3.7.
 
 ## Help and documented pins
 

diff --git a/docs/qa/README.md b/docs/qa/README.md
@@ -24,9 +24,9 @@ coordinator) should link here. This file does not replace
 
 Package identity of a checkout is `package.json` (currently `0.3.9`). That
 version string alone is not registry proof. The last independently inspected
-npm tarball recorded in-tree is `@augmentworks/cli@0.3.8` in
-`docs/feature-readiness/published-registry-evidence.json` (tag `v0.3.8`
-commit `f36d9086bad1ac109a7670e8acc9bf14a5d15047`; the registry document
+npm tarball recorded in-tree is `@augmentworks/cli@0.3.9` in
+`docs/feature-readiness/published-registry-evidence.json` (tag `v0.3.9`
+commit `9e7919cbfe583cc15701904580be9d36da3bcaf4`; the registry document
 omitted `gitHead`). Confirm with `npm view` before
 treating a pin as installed. Never run `npx @augmentworks/cli@latest`.
 `npx --yes` only skips the npm prompt; it is not a spending ceiling.
@@ -196,10 +196,9 @@ is not a normal offline check).
 
 Independently inspect registry identity with `npm view` and compare
 `gitHead` / `dist.integrity` / tarball SHA-256 to
-`docs/feature-readiness/published-registry-evidence.json`. npm `0.3.8`
-is independently inspected. Source `0.3.9` stays `pending-protected-publish`
-until the `v0.3.9` tarball is inspected. That gap is not a local-runner
-pass, and the 0.3.8 receipt is not inside the published tarball.
+`docs/feature-readiness/published-registry-evidence.json`. npm `0.3.9`
+is independently inspected. That receipt is not a substitute for a local-runner
+pass, and it is not inside the published tarball.
 Customer-facing `init` next steps on an npm install must not tell the user to
 run `node dist/index.js` from an empty project.