aeoptimize 0.6.1 → 0.6.2

package/.claude-plugin/marketplace.json

@@ -5,7 +5,7 @@
   },
   "metadata": {
     "description": "Content-readiness lint with evidence-bounded AI discovery experiments",
-    "version": "0.6.1"
+    "version": "0.6.2"
   },
   "plugins": [
     {

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aeoptimize",
   "description": "Content-readiness lint and evidence-bounded discovery experiments",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "author": {
     "name": "Te-Shu Wang"
   },

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable user-visible changes will be documented here. The project follows Semantic Versioning after the v0.6 evidence baseline is released.
 
+## 0.6.2
+
+### Fixed
+
+- Added a fail-closed publish source gate that requires `HEAD` to match the fetched `origin/main` commit before npm publication.
+- Prepared a corrective release after npm 0.6.1 exposed the pre-squash PR commit as `gitHead`; the verified package contents were correct, but the release provenance did not match the merged commit.
+- Kept scoring rules, output contracts, and runtime behavior unchanged.
+
 ## 0.6.1
 
 ### Fixed

package/README.md

@@ -64,7 +64,7 @@ node -e "const r=require('./aeoptimize-report.json'); process.exit(r.overall.tot
 The v0.6 GitHub Action is advisory by default. It reports findings without blocking the workflow:
 
 ```yaml
-- uses: cucuwang/aeoptimize@v0.6.1
+- uses: cucuwang/aeoptimize@v0.6.2
   with:
     path: dist
 ```
@@ -72,7 +72,7 @@ The v0.6 GitHub Action is advisory by default. It reports findings without block
 Projects can explicitly choose blocking mode after accepting a baseline:
 
 ```yaml
-- uses: cucuwang/aeoptimize@v0.6.1
+- uses: cucuwang/aeoptimize@v0.6.2
   with:
     path: dist
     fail-on-low-score: 'true'

package/dist/cli/index.js

@@ -13,7 +13,7 @@ const program = new Command();
 program
     .name('aeoptimize')
     .description('Deterministic content-readiness lint for websites and documentation')
-    .version('0.6.1');
+    .version('0.6.2');
 // ── scan command ───────────────────────────────────────────────────
 program
     .command('scan <target>')

package/docs/release-v0.6.md

@@ -1,6 +1,6 @@
 # v0.6 release and rollback guide
 
-Version 0.6.1 hardens the v0.6 evidence-bounded scoring, packaging, and GitHub Action contracts. It is not released until npm, the Git tag, and the GitHub Release are each created and read back independently.
+Version 0.6.2 is the provenance-corrective release for the v0.6 evidence-bounded scoring, packaging, and GitHub Action contracts. npm 0.6.1 contained the verified candidate bytes but exposed the pre-squash PR commit as `gitHead`, so no v0.6.1 Git tag or GitHub Release was created. Version 0.6.2 is not released until npm, the Git tag, and the GitHub Release are each created and read back independently.
 
 ## Release acceptance
 
@@ -11,9 +11,9 @@ Before publication, run `npm ci` and `npm run release:check` from the intended r
 3. An actual `npm pack` candidate contains the required public files, its SHA-256 is recorded, and a clean consumer can invoke `aeoptimize`, `aeo`, and `aeo-cli` from that exact tarball.
 4. CI succeeds on Node.js 22 and 24 for the release commit.
 5. The JSON automation contract and Action sample tests pass.
-6. The npm account is verified immediately before publishing.
+6. The npm account is verified immediately before publishing, and the publish source gate confirms that `HEAD` is the exact fetched `origin/main` commit.
 
-CI runs the same candidate gate on Node.js 22 and 24 and compares version, filename, SHA-256, file count, and unpacked size. `prepublishOnly` invokes the candidate gate again and refuses a dirty worktree by default.
+CI runs the same candidate gate on Node.js 22 and 24 and compares version, filename, SHA-256, file count, and unpacked size. `prepublishOnly` invokes the candidate gate again, refuses a dirty worktree, and refuses publication unless `HEAD` matches `origin/main` exactly. Run `git fetch origin main` immediately before the authorized publish so the remote-tracking ref is current.
 
 Publishing, tagging, creating a GitHub Release, changing npm dist-tags, and deprecating a version are separate external mutations and require separate maintainer authorization.
 
@@ -25,6 +25,7 @@ Publishing, tagging, creating a GitHub Release, changing npm dist-tags, and depr
 - Require byte-identical candidate manifests from Node.js 22 and 24 before the release can proceed.
 - Bind the public verifier's CLI smoke checks to the downloaded, hash-verified npm tarball.
 - Fail closed when a CLI alias, tag target, repository identity, or GitHub Release state does not match.
+- Fail closed before publication when the checked-out commit differs from the fetched `origin/main` commit.
 - Exercise every v0.6 rule fixture through the real HTML parser boundary.
 
 No scoring rule, rule weight, JSON field, Action input, or Action output changes in this patch. No ranking, traffic, indexing, rich-result, AI Overview, or citation outcome is claimed by this release.
@@ -35,16 +36,16 @@ After an authorized npm publication:
 
 ```bash
 npm view aeoptimize version dist-tags --json
-npm view aeoptimize@0.6.1 version gitHead repository homepage bugs dist --json
-consumer_root=$(mktemp -d "${TMPDIR:-/tmp}/aeoptimize-v0.6.1-consumer.XXXXXX")
-npm install --prefix "$consumer_root" aeoptimize@0.6.1
+npm view aeoptimize@0.6.2 version gitHead repository homepage bugs dist --json
+consumer_root=$(mktemp -d "${TMPDIR:-/tmp}/aeoptimize-v0.6.2-consumer.XXXXXX")
+npm install --prefix "$consumer_root" aeoptimize@0.6.2
 "$consumer_root/node_modules/.bin/aeoptimize" --version
 "$consumer_root/node_modules/.bin/aeo" --version
 "$consumer_root/node_modules/.bin/aeo-cli" --version
 rm -rf -- "$consumer_root"
 ```
 
-After separately authorized tag and GitHub Release creation, verify that `v0.6.1` points to the tested release commit and that the Release is published rather than draft or prerelease.
+After separately authorized tag and GitHub Release creation, verify that `v0.6.2` points to the tested release commit and that the Release is published rather than draft or prerelease.
 
 The fail-closed public verifier checks npm `latest`, the exact version, public repository identity, the downloaded tarball SHA-256, all three installed CLI aliases, the tag target, and the published GitHub Release. The tarball hash is the required artifact-identity gate. If npm exposes `gitHead`, it must match the expected release commit; absence is reported as informational because npm's publish contract guarantees tarball integrity but does not guarantee that metadata field.
 
@@ -56,11 +57,11 @@ bash scripts/verify-release-v0.6.sh <verified-release-commit> <verified-package-
 
 An npm dist-tag rollback changes what `npm install aeoptimize` selects; it does not remove exact-version installs. Never silently move an existing Git tag to different code.
 
-If npm 0.6.1 is unsuitable before a corrective release is available, request separate authorization for each mutation, then:
+If npm 0.6.2 is unsuitable, request separate authorization for each mutation and restore `latest` to the last fully released version rather than the provenance-mismatched 0.6.1 artifact:
 
 ```bash
 npm dist-tag add aeoptimize@0.6.0 latest
-npm deprecate aeoptimize@0.6.1 "Use 0.6.0 until the corrective release is available."
+npm deprecate aeoptimize@0.6.2 "Use 0.6.0 until the corrective release is available."
 ```
 
-Mark the GitHub Release with the same warning. Preserve the `v0.6.1` tag as evidence of what was published, fix forward in 0.6.2, rerun the complete release acceptance suite, and only then move npm `latest` to the corrective version.
+Mark the GitHub Release with the same warning. Never create or retarget `v0.6.1` merely to mask its npm `gitHead` mismatch. Preserve immutable versions as evidence, fix forward in 0.6.3, rerun the complete release acceptance suite, and only then move npm `latest` to the corrective version.

package/examples/github-action-sample/.github/workflows/aeoptimize.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: cucuwang/aeoptimize@v0.6.1
+      - uses: cucuwang/aeoptimize@v0.6.2
         with:
           path: site
           fail-on-low-score: 'false'

package/examples/github-action-sample/README.md

@@ -6,4 +6,4 @@ This directory is a copyable end-to-end sample for the v0.6 Action contract.
 - `site/index.html` is a deterministic public input.
 - The Action is advisory by default. The sample does not block a pull request on an unreviewed score threshold.
 
-The workflow becomes reproducible only after both `aeoptimize@0.6.1` exists on npm and the immutable `v0.6.1` Git tag points to the matching release commit. Until both artifacts exist, use the local CLI or the release-candidate package during controlled verification.
+The workflow becomes reproducible only after both `aeoptimize@0.6.2` exists on npm and the immutable `v0.6.2` Git tag points to the matching release commit. Until both artifacts exist, use the local CLI or the release-candidate package during controlled verification.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aeoptimize",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "description": "Deterministic content-readiness lint for static websites and documentation",
   "type": "module",
   "main": "./dist/core/index.js",
@@ -21,6 +21,7 @@
     "fixtures/",
     "examples/github-action-sample/",
     "scripts/verify-release-candidate.sh",
+    "scripts/verify-publish-source.sh",
     "scripts/verify-release-v0.6.sh",
     ".claude-plugin/",
     "docs/methodology.md",
@@ -39,7 +40,7 @@
     "dev": "tsc --watch",
     "test": "vitest run",
     "test:watch": "vitest",
-    "prepublishOnly": "npm run release:check"
+    "prepublishOnly": "npm run release:check && bash scripts/verify-publish-source.sh"
   },
   "keywords": [
     "aeo",

package/scripts/verify-publish-source.sh

@@ -0,0 +1,25 @@
+#!/usr/bin/env bash
+set -u
+
+if ! command -v git >/dev/null 2>&1; then
+  echo "missing required command: git" >&2
+  exit 2
+fi
+
+if ! head_commit=$(git rev-parse --verify HEAD 2>/dev/null); then
+  echo "publish source gate: HEAD is unavailable" >&2
+  exit 1
+fi
+
+if ! main_commit=$(git rev-parse --verify refs/remotes/origin/main 2>/dev/null); then
+  echo "publish source gate: origin/main is unavailable; run git fetch origin main" >&2
+  exit 1
+fi
+
+if [ "$head_commit" != "$main_commit" ]; then
+  echo "publish source gate: HEAD is $head_commit; expected origin/main $main_commit" >&2
+  echo "fetch origin/main and publish from its exact commit" >&2
+  exit 1
+fi
+
+echo "Publish source gate passed: HEAD matches origin/main at $head_commit."