fix: clarify ai validation entry guidance

Author: rockyshi1993

changelogs/unreleased.md

@@ -13,6 +13,7 @@
 
 - **本地候选修复 — 派生资产新鲜度与默认验证漏检**：刷新 `content/skills/portfolio.json`，并将 `skill-portfolio-current` 纳入 changed/iterative 默认验证不变量，使 clean-tree `npm test` 计划覆盖 portfolio freshness；同步 validation DAG 断言与 Windows 中文文件名负向测试夹具，避免默认验证对派生资产 stale false-green。本项仅为本地源码候选，未 tag、未 publish、未刷新 MCP。
 - **本地候选修复 — 提交后 Profile current truth 与 changed-route 防漏检**：新增轻量 `profile-current` validation node，并将其纳入 changed/iterative 默认验证不变量，使 clean-tree post-commit replay 也会检查 active Profile `ProfileCurrentTruthV1` 是否对齐当前源码 HEAD/source candidate；`profile-governance` 保持边界/综合验证，不被每次 clean changed-route 强制拉起。本项仅为本地源码候选，未 tag、未 publish、未刷新 MCP。
+- **本地候选修复 — AI 验证入口 authority 提示收敛**：`run-validation` 在 Codex/AI 环境缺少 ContextRead epoch 或 source-message digest 时继续 fail-closed，但 `Next` 提示改为明确分流到 `npm run test:changed:plan`、绑定 task/context/source-message 的 `test:changed:ai`，或真实人类交互式终端 `npm test`；新增 validation DAG 断言锁住该错误投影，避免把 authority fail-closed 误判为源码测试失败或诱导绕过执行权限。本项仅为本地源码候选，未 tag、未 publish、未刷新 MCP。
 - **本地候选修复 — 验证入口、产物状态投影与 Profile 当前真相刷新**：收紧 active-root 产物 stale CP 状态检测，避免把“待用户确认是否提交”等非 CP 文案误判为 CP1/CP2 阻断；默认 `test:fast/full/delivery/boundary/profile-deploy/package-release` 改为 `human-cli --plan` 入口并补充 `:ai` 严格变体，避免 Codex/AI 环境缺 `contextEpoch` 时本地 plan 命令误红；新增 `profile-current:refresh` 标准命令，用于更新 active Profile `ProfileCurrentTruthV1` 的当前源码 HEAD 与 source candidate 身份。本项仅为本地源码候选，未 tag、未 publish、未刷新 MCP。
 - **本地候选修复 — 验证入口派生资产与 Profile 边界**：将默认 `test` / `test:changed` / scoped route 入口恢复为执行型验证，新增显式 `test:plan` / `test:*:plan` 作为零执行预览入口，避免 plan-only 被误读为测试已执行；把 `scripts/refresh-profile-current-truth.js` 纳入 profile boundary 与 `profile-governance` 输入闭包，确保修改 Profile current truth refresh 脚本时触发 profile 验证；刷新 `content/skills/portfolio.json`。本项仅为本地源码候选，未 tag、未 publish、未刷新 MCP。
 - **本地候选修复 — 运行态可观测性与历史债务收敛**：`validate.js` 现在对每个 V 探针输出 start/done heartbeat，V7 改为有界 fast-path smoke，避免聚合校验无界卡死；visible reply evidence 绑定当前 promptCount，无 payload 时不再继承旧 precheck；`memory_status` 增加 `summaryCurrentProjection`，显式区分 append-only SUMMARY 历史与当前折叠状态；artifact checker 新增 digest-bound `HistoricalArtifactIssueDispositionV1`，用于精确处置历史 unknown/stale/conflict 产物噪声。本项仅为本地源码候选，未 tag、未 publish、未刷新 MCP。

scripts/run-validation.js

@@ -444,6 +444,14 @@ function detectedActorType(env = process.env) {
   return 'human-cli'
 }
 
+function aiAuthorityEvidenceNextStep(reason) {
+  const prefix = reason ? `${reason}; ` : ''
+  return prefix +
+    'choose the correct validation entry: for zero-execution local planning run `npm run test:changed:plan`; ' +
+    'for AI execution run `npm run test:changed:ai` from a bound task and pass the current --context-epoch, --task-recovery-key and --source-message-digest; ' +
+    'for direct local execution run `npm test` from a real interactive human terminal outside the AI host.'
+}
+
 function resolveActorType(requested, env = process.env, options = {}) {
   const detected = detectedActorType(env)
   if (options.allowPlanOnlyDowngrade && requested === 'human-cli' && detected === 'ai-hook') {
@@ -594,7 +602,7 @@ function resolveValidationAuthorityContext({ actorType, options, activeRoot, env
     throw new ValidationDagError(
       'VALIDATION_AI_CONTEXT_EPOCH_REQUIRED',
       'AI validation planning requires the current ContextRead epoch',
-      { nextStep: 'Rebuild ContextRead, then pass its exact context epoch before generating a BudgetCard.' }
+      { nextStep: aiAuthorityEvidenceNextStep('Rebuild ContextRead, then pass its exact context epoch before generating a BudgetCard') }
     )
   }
 
@@ -1851,7 +1859,7 @@ function createCliLease({ options, plan, candidate, actorType, authorityContext,
     throw new ValidationDagError(
       'VALIDATION_AI_CONFIRMATION_EVIDENCE_REQUIRED',
       'AI validation execution requires the exact current user-confirmation message digest',
-      { nextStep: 'Pass --source-message-digest for the message that confirmed this exact BudgetCard.' }
+      { nextStep: aiAuthorityEvidenceNextStep('Pass --source-message-digest for the message that confirmed this exact BudgetCard') }
     )
   }
   if (['trusted-ci', 'release-pipeline'].includes(actorType)) {
@@ -2640,6 +2648,7 @@ module.exports = {
   compactPlan,
   convergenceProjection,
   createCliLease,
+  aiAuthorityEvidenceNextStep,
   directActorIdentityEvidence,
   detectedActorType,
   envelope,

scripts/test-validation-dag.js

@@ -685,7 +685,14 @@ function run() {
       activeRoot: tempRoot,
       env: { CODEX_THREAD_ID: 'fixture-thread' },
       readTaskState: () => ({ status: 'fresh', identity: { taskId: aiAuthority.taskRecoveryKey } })
-    }), error => error instanceof ValidationDagError && error.code === 'VALIDATION_AI_CONTEXT_EPOCH_REQUIRED')
+    }), error => {
+      assert(error instanceof ValidationDagError)
+      assert.strictEqual(error.code, 'VALIDATION_AI_CONTEXT_EPOCH_REQUIRED')
+      assert.match(error.details.nextStep, /npm run test:changed:plan/)
+      assert.match(error.details.nextStep, /npm run test:changed:ai/)
+      assert.match(error.details.nextStep, /interactive human terminal/)
+      return true
+    })
     assert.throws(() => resolveValidationAuthorityContext({
       actorType: 'ai-hook',
       options: { contextEpoch: 'ctx-fixture-current', taskRecoveryKey: 'different-task' },