fix(release): bind package plan approval in publish

Author: rockyshi1993

.github/workflows/publish.yml

@@ -40,7 +40,14 @@ jobs:
         run: npm ci
 
       - name: Run package release checks
-        run: npm run test:package-release
+        shell: bash
+        run: |
+          set -euo pipefail
+          PLAN_DIGEST="$(
+            node scripts/run-validation.js --route package-release --plan --json |
+              node -e 'const fs = require("fs"); const envelope = JSON.parse(fs.readFileSync(0, "utf8")); const plan = envelope?.data?.plan; const digest = plan?.budgetCard?.digest; if (envelope?.ok !== true || plan?.routeResolved !== "package-release" || plan?.candidateStable !== true || !/^[a-f0-9]{64}$/.test(String(digest || ""))) process.exit(1); process.stdout.write(digest)'
+          )"
+          node scripts/run-validation.js --route package-release --approve-plan "${PLAN_DIGEST}"
 
       - name: Preview package contents
         run: npm pack --dry-run

changelogs/releases/v1.17.11.md

@@ -15,6 +15,7 @@ v1.17.11 修复“日常小改动也被推入完整发布验证”的控制面
 - `ValidationPlanV2` 通过类型化 runtime、qualification、release consumer 边构建影响图，保留 V1 兼容投影；未知输入失败关闭，不再静默升级成 full。
 - `fast` 改为动态影响选择；`profile-deploy` 与 `package-release` 固定为各自 V2 边界，不能吸收旧 full 清单或其他 dirty boundary。
 - `BudgetCardV1` 在执行前给出节点数、重节点和预计耗时；非发布重节点需要绑定精确计划摘要，发布 V3 则需要显式 release authority。
+- tag 触发的非交互 Publish 会先物化 `package-release` 计划，再把同一 `BudgetCardV1.digest` 绑定回执行；既避免自动发布卡在确认门禁，也不绕过候选 V3 或精确计划约束。
 - `ValidationEvidenceV2` 绑定 manifest、候选 dirty identity、节点合同/策略和上游 `nodeReceiptDigest`；只复用身份等价的节点证据，V3 永不复用缓存。
 - CLI 以 `--intent` 为正式参数，保留 `--purpose` 兼容别名；新增 `test:delivery` 与 `test:boundary`。
 

scripts/test-release-metadata.js

@@ -11,6 +11,7 @@ const plugin = JSON.parse(fs.readFileSync(path.join(ROOT, 'plugin.json'), 'utf8'
 const lock = JSON.parse(fs.readFileSync(path.join(ROOT, 'package-lock.json'), 'utf8'))
 const readme = fs.readFileSync(path.join(ROOT, 'README.md'), 'utf8')
 const publicCi = fs.readFileSync(path.join(ROOT, '.github', 'workflows', 'ci.yml'), 'utf8')
+const publishWorkflow = fs.readFileSync(path.join(ROOT, '.github', 'workflows', 'publish.yml'), 'utf8')
 
 const errors = []
 const publicReadmeContract = evaluatePublicReadmeContractV2(readme, { root: ROOT })
@@ -59,6 +60,17 @@ expect(publicCi.includes('route: test:windows-control-plane'), '公共 CI 必须
 expect(publicCi.includes('name: Full quality (Node 24.17)'), '公共 CI 全量质量门必须使用发布 Node 24.17')
 expect(publicCi.includes('name: Package boundary (Node 24.17)'), '公共 CI package job 必须只声明实际执行的 package boundary')
 expect(!publicCi.includes('Website and package'), '公共 CI 不得把条件缺席的网站构建表述为绿色证据')
+expect(publishWorkflow.includes('set -euo pipefail'), 'Publish workflow 必须让 package plan 管道失败关闭')
+expect(
+  publishWorkflow.includes('node scripts/run-validation.js --route package-release --plan --json'),
+  'Publish workflow 必须先物化 package-release 精确计划'
+)
+expect(publishWorkflow.includes('plan?.budgetCard?.digest'), 'Publish workflow 必须读取 BudgetCard 精确摘要')
+expect(
+  publishWorkflow.includes('--route package-release --approve-plan "${PLAN_DIGEST}"'),
+  'Publish workflow 必须把同一 BudgetCard 摘要绑定回 package-release 执行'
+)
+expect(!publishWorkflow.includes('run: npm run test:package-release'), 'Publish workflow 不得使用缺少非交互计划批准的旧入口')
 expect(nonEmptyString(pkg.publishConfig && pkg.publishConfig.registry), 'package.json publishConfig.registry 不能为空')
 expect(nonEmptyString(pkg.publishConfig && pkg.publishConfig.access), 'package.json publishConfig.access 不能为空')
 expect(files.length > 0, 'package.json files 不能为空')