@jtf19/vibecoding-kit 0.1.0

package/tools/vibe-runtime/state-extension-paths.mjs

@@ -0,0 +1,198 @@
+import path from 'node:path';
+import { stateDirectory } from './runtime-state-directory-model.mjs';
+
+export const hookIntentsDirectoryName = 'hook-intents';
+export const subagentEligibilityDirectoryName = 'subagent-eligibility';
+export const subagentDispatchesDirectoryName = 'subagent-dispatches';
+export const subagentAdapterDispatchesDirectoryName = 'subagent-adapter-dispatches';
+export const subagentRunLeasesDirectoryName = 'subagent-run-leases';
+export const subagentRunResultsDirectoryName = 'subagent-run-results';
+export const subagentResultsDirectoryName = 'subagent-results';
+export const subagentReviewsDirectoryName = 'subagent-reviews';
+export const hookRunsDirectoryName = 'hook-runs';
+export const hookHeartbeatsDirectoryName = 'hook-heartbeats';
+export const platformCapabilitiesDirectoryName = 'platform-capabilities';
+export const platformSessionApprovalsDirectoryName = 'platform-session-approvals';
+export const platformSessionsDirectoryName = 'platform-sessions';
+export const platformSessionLeasesDirectoryName = 'platform-session-leases';
+export const platformSessionResultsDirectoryName = 'platform-session-results';
+export const platformSessionCancellationsDirectoryName = 'platform-session-cancellations';
+export const platformSessionIntakeDirectoryName = 'platform-session-intake';
+export const platformSessionReviewsDirectoryName = 'platform-session-reviews';
+export const sourceChangeCandidatesDirectoryName = 'source-change-candidates';
+export const sourceSandboxRunsDirectoryName = 'source-sandbox-runs';
+export const sourceVerificationsDirectoryName = 'source-verifications';
+export const mergeReadinessDirectoryName = 'merge-readiness';
+export const mergeApprovalsDirectoryName = 'merge-approvals';
+export const mergeAppliesDirectoryName = 'merge-applies';
+export const plannerRoutesDirectoryName = 'planner-routes';
+export const plannerPlansDirectoryName = 'planner-plans';
+export const plannerBriefsDirectoryName = 'planner-briefs';
+export const routerPlansDirectoryName = 'router-plans';
+export const routerApprovalsDirectoryName = 'router-approvals';
+export const orchestratorPlansDirectoryName = 'orchestrator-plans';
+export const orchestratorDispatchPlansDirectoryName = 'orchestrator-dispatch-plans';
+export const evalSuitesDirectoryName = 'eval-suites';
+export const evalRunsDirectoryName = 'eval-runs';
+export const evalReportsDirectoryName = 'eval-reports';
+export const releaseGatesDirectoryName = 'release-gates';
+export const releaseNotesDirectoryName = 'release-notes';
+export const feedbackLedgersDirectoryName = 'feedback-ledgers';
+export const learningDirectoryName = 'learning';
+export const tokenEconomyDirectoryName = 'token-economy';
+
+export function hookIntentsDirectory(root) {
+  return path.join(stateDirectory(root), hookIntentsDirectoryName);
+}
+
+export function subagentEligibilityDirectory(root) {
+  return path.join(stateDirectory(root), subagentEligibilityDirectoryName);
+}
+
+export function subagentDispatchesDirectory(root) {
+  return path.join(stateDirectory(root), subagentDispatchesDirectoryName);
+}
+
+export function subagentAdapterDispatchesDirectory(root) {
+  return path.join(stateDirectory(root), subagentAdapterDispatchesDirectoryName);
+}
+
+export function subagentRunLeasesDirectory(root) {
+  return path.join(stateDirectory(root), subagentRunLeasesDirectoryName);
+}
+
+export function subagentRunResultsDirectory(root) {
+  return path.join(stateDirectory(root), subagentRunResultsDirectoryName);
+}
+
+export function subagentResultsDirectory(root) {
+  return path.join(stateDirectory(root), subagentResultsDirectoryName);
+}
+
+export function subagentReviewsDirectory(root) {
+  return path.join(stateDirectory(root), subagentReviewsDirectoryName);
+}
+
+export function hookRunsDirectory(root) {
+  return path.join(stateDirectory(root), hookRunsDirectoryName);
+}
+
+export function hookHeartbeatsDirectory(root) {
+  return path.join(stateDirectory(root), hookHeartbeatsDirectoryName);
+}
+
+export function platformCapabilitiesDirectory(root) {
+  return path.join(stateDirectory(root), platformCapabilitiesDirectoryName);
+}
+
+export function platformSessionApprovalsDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionApprovalsDirectoryName);
+}
+
+export function platformSessionsDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionsDirectoryName);
+}
+
+export function platformSessionLeasesDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionLeasesDirectoryName);
+}
+
+export function platformSessionResultsDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionResultsDirectoryName);
+}
+
+export function platformSessionCancellationsDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionCancellationsDirectoryName);
+}
+
+export function platformSessionIntakeDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionIntakeDirectoryName);
+}
+
+export function platformSessionReviewsDirectory(root) {
+  return path.join(stateDirectory(root), platformSessionReviewsDirectoryName);
+}
+
+export function sourceChangeCandidatesDirectory(root) {
+  return path.join(stateDirectory(root), sourceChangeCandidatesDirectoryName);
+}
+
+export function sourceSandboxRunsDirectory(root) {
+  return path.join(stateDirectory(root), sourceSandboxRunsDirectoryName);
+}
+
+export function sourceVerificationsDirectory(root) {
+  return path.join(stateDirectory(root), sourceVerificationsDirectoryName);
+}
+
+export function mergeReadinessDirectory(root) {
+  return path.join(stateDirectory(root), mergeReadinessDirectoryName);
+}
+
+export function mergeApprovalsDirectory(root) {
+  return path.join(stateDirectory(root), mergeApprovalsDirectoryName);
+}
+
+export function mergeAppliesDirectory(root) {
+  return path.join(stateDirectory(root), mergeAppliesDirectoryName);
+}
+
+export function plannerRoutesDirectory(root) {
+  return path.join(stateDirectory(root), plannerRoutesDirectoryName);
+}
+
+export function plannerPlansDirectory(root) {
+  return path.join(stateDirectory(root), plannerPlansDirectoryName);
+}
+
+export function plannerBriefsDirectory(root) {
+  return path.join(stateDirectory(root), plannerBriefsDirectoryName);
+}
+
+export function routerPlansDirectory(root) {
+  return path.join(stateDirectory(root), routerPlansDirectoryName);
+}
+
+export function routerApprovalsDirectory(root) {
+  return path.join(stateDirectory(root), routerApprovalsDirectoryName);
+}
+
+export function orchestratorPlansDirectory(root) {
+  return path.join(stateDirectory(root), orchestratorPlansDirectoryName);
+}
+
+export function orchestratorDispatchPlansDirectory(root) {
+  return path.join(stateDirectory(root), orchestratorDispatchPlansDirectoryName);
+}
+
+export function evalSuitesDirectory(root) {
+  return path.join(stateDirectory(root), evalSuitesDirectoryName);
+}
+
+export function evalRunsDirectory(root) {
+  return path.join(stateDirectory(root), evalRunsDirectoryName);
+}
+
+export function evalReportsDirectory(root) {
+  return path.join(stateDirectory(root), evalReportsDirectoryName);
+}
+
+export function releaseGatesDirectory(root) {
+  return path.join(stateDirectory(root), releaseGatesDirectoryName);
+}
+
+export function releaseNotesDirectory(root) {
+  return path.join(stateDirectory(root), releaseNotesDirectoryName);
+}
+
+export function feedbackLedgersDirectory(root) {
+  return path.join(stateDirectory(root), feedbackLedgersDirectoryName);
+}
+
+export function learningDirectory(root) {
+  return path.join(stateDirectory(root), learningDirectoryName);
+}
+
+export function tokenEconomyDirectory(root) {
+  return path.join(stateDirectory(root), tokenEconomyDirectoryName);
+}

package/tools/vibe-runtime/state-safe-paths.mjs

@@ -0,0 +1,2 @@
+export * from './state-core-paths.mjs';
+export * from './state-extension-paths.mjs';

package/tools/vibe-runtime-check/README.md

@@ -0,0 +1,110 @@
+# Vibe Runtime Check
+
+`vibe-runtime-check` 是只读 workflow contract 检查器。
+
+它检查 Vibecoding workflow skills 是否具备未来 runtime 可读取的 handoff 结构，但不写状态、不自动执行下一步、不调用 subagent。
+
+## 使用
+
+在仓库根目录运行：
+
+```bash
+node tools/vibe-runtime-check/index.mjs
+```
+
+指定检查根目录：
+
+```bash
+node tools/vibe-runtime-check/index.mjs --root /path/to/vibe-coading
+```
+
+## 检查内容
+
+当前检查：
+
+- `tools/vibe-runtime-check/index.mjs` 只保留 runner、结果输出和 domain check 调用；通用 marker helper 由 `marker-contract-core.mjs` 拥有。
+- runtime-check marker owner 按 domain 分布在 `runtime-doc-contracts.mjs`、`runtime-cli-surface-contracts.mjs`、`runtime-control-plane-contracts.mjs`、`workflow-ux-contracts.mjs`、`runtime-governance-learning-token-contracts.mjs`、`runtime-experience-contracts.mjs`、`runtime-automation-readiness-contracts.mjs`、`runtime-doc-marker-contracts.mjs`、`runtime-tool-readme-contracts.mjs` 和 `product-artifact-contracts.mjs`。
+- `product-artifact-contracts.mjs` 负责 Stage 151-156 product/UI/delivery/implementation completion evidence markers，并检查拆分后的 completion owner modules：`runtime-completion-evidence-descriptors.mjs`、`runtime-completion-chain-assembly.mjs`、`runtime-completion-readiness-summary.mjs` 和 `runtime-completion-bundle-contract.mjs`。
+- `docs/runtime-roadmap.md` 是否存在并说明分阶段 runtime 边界。
+- `docs/runtime-contract.md` 是否存在并说明 skill contract、handoff contract、execution policy 和 failure semantics。
+- `docs/runtime-contract.md` 是否声明 Stage 3 `JSON handoff`、`JSON-first`、`legacy fallback` 和 no automatic next_skill execution。
+- `docs/runtime-contract.md` 是否声明 Stage 4 `artifacts --dry-run` / `artifacts --write`、`tasks --dry-run` / `tasks --write`、生成文件边界、task id 路径安全与唯一性（含 Windows 保留设备名、重复 id 和尾随点边界）、`depends_on` dependency contract、cyclic task dependency 负路径、`Task readiness` 只读摘要、`review_status` 状态边界，以及可选 `goal` / `key_decisions` / `tasks` 上下文字段。
+- `docs/runtime-contract.md` 是否声明 Stage 4.7 `status --json`、`validate-handoff --json`、`next --dry-run --json` 和 `tasks --dry-run --json` 只读 JSON envelope，包括 `schema_version`、`state_present`、`selected_count` 和 `artifact_paths` marker；`tasks --dry-run --task <task-id> --json` 只过滤输出任务，但 readiness / blocked_by 以完整 ledger dependency graph 为准；写入类 `record-handoff --json`、`artifacts --json`、`tasks --write --json` 和 `reset --json` 必须明确失败。
+- `docs/runtime-contract.md` 是否声明 Stage 5.x `next --dry-run --dispatch-intent` 只读 adapter bridge intent，包含 `runtimeBridge` manual mode、`platform_hints`、gate preview、`dispatch_event=false` 和 no auto execution 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 6.x `next --confirm --dispatch` confirm-dispatch gate，成功只写 `.vibecoding-state/dispatches/<timestamp>.json`，失败 gate 不写 dispatch event，并保持 no git / worktree / subagent / MCP / daemon / business source write 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 6.5 `dispatches --list`、`dispatches --show` 和 `dispatches --verify` read-only dispatch audit，包含 confirm-dispatch event verification、路径边界、损坏 event 失败和 no skill execution / platform API / subagent / MCP / daemon / git / worktree / business source write 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 7 `dispatches --claim`、`dispatches --ack` 和 `dispatches --claims` Dispatch Claim / Ack Gate，包含 Stage 7.1 claim input hardening、Stage 7.2 ack lifecycle hardening、Stage 7.3 claims audit hardening、`.vibecoding-state/dispatch-claims/` claim state、actor gate、重复 claim 失败、ack actor mismatch 失败、`picked` / `skipped` / `failed` 状态边界、原始 dispatch event 不变性和 no auto execution 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 8 `dispatches --pickup` Adapter Pickup Package Gate，包含 Stage 8.1 pickup package manifest、Stage 8.2 pickup readiness gates、Stage 8.3 pickup read-only audit、pickup package、platform entry、manual instruction、event verification、session / auto claim 边界、未 claim warning、claim 非 picked 不暗示 execution readiness、只读 no-write、no platform API / subagent / MCP / daemon / git / worktree / business source write 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 9 `execute --from-dispatch` Supervised Executor Gate，包含 Stage 9.1-9.11：dry-run execution plan、confirm planned envelope、claim picked gate、no execution boundary、execution envelope safety、immutability、execution preflight audit、planned envelope verify、stable `idempotency_key`、execution policy snapshot、write boundary preview；兼容 Stage 9.1 execution preflight gates、Stage 9.2 execution preflight audit / planned execution envelope、Stage 9.3 immutability guarantees、Stage 9.5 idempotency / policy snapshot marker，并保持 dry-run 只读预览、confirm execution envelope、claim actor gate、`picked` claim 状态要求、`runtime_action=false`、只写 `.vibecoding-state/executions/`，以及 no skill execution / platform API / subagent / MCP / daemon / git / worktree / business source write 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 10 `daemon --dry-run`、`daemon --scan --dry-run` 和 `daemon --once --confirm` Daemon / Continuous Runtime Gate，包含 Stage 10.1 daemon command gate、Stage 10.2 once-run envelope、Stage 10.3-10.6 scheduler scan dry-run / scheduler policy dry-run / stale claim and stale running audit / retry policy preview、Stage 10.8 once scan no-op envelope、Stage 10.11-10.13 lock / watcher / lease heartbeat contract、default-off daemon、no-op once-run envelope、只写 `.vibecoding-state/daemon-runs/`，以及 no dispatch scan execution / execute call / skill execution / platform API / subagent / MCP / git / worktree / business source write 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 11 Supervised Real Executor v1，包含 `execute --confirm --run`、`supervised-run`、`runtime_action=true`、allowlist、execution lifecycle、`executions --list` / `executions --show` / `executions --verify` read-only execution audit，以及 no platform API / subagent / MCP / daemon / git / worktree / business source write 边界。
+- `docs/runtime-contract.md` 是否声明 Stage 151 Product/UI Methodology Artifact Gate，包含 `methodology --gate --kind product-spec --from-file`、`product_methodology_gate`、`gate_digest`、`source_bindings.artifact_digest`、`browser_execution=false`、`skill_execution=false`、`git=false`、`subagent=false`。
+- `docs/runtime-contract.md` 是否声明 Stage 152 Product Completion Evidence Bundle，包含 `completion --evidence-bundle --from-product-discovery`、`requirements_chain`、`product_readiness`、`ui_readiness`、`engineering_readiness`、`bundle_digest`、`verification_execution=false`、`command_execution=false`、`git=false`。
+- `docs/runtime-contract.md` 是否声明 Stage 153 Architecture Design Artifact Gate，包含 `methodology --gate --kind architecture-design --from-file`、`delivery-methodology-gate`、`gate_digest`、`source_bindings.artifact_digest`、`Boundary`、`Evidence`、`git_write=false`。
+- `docs/runtime-contract.md` 是否声明 Stage 154 Delivery Traceability Artifact Gate，包含 `methodology --gate --kind delivery-traceability --from-file`、`delivery_methodology_gate`、`summary.link_count`、`summary.statuses`、`blocked_reasons`、`boundary_assertions`、`git_write=false`。
+- `docs/runtime-contract.md` 是否声明 Stage 155 Full-chain Product Completion Evidence Bundle，包含 `--from-architecture`、`--from-traceability`、`--from-test-evidence`、`--from-diff-coverage`、`--from-commit-readiness`、`architecture_chain`、`traceability_chain`、`implementation_chain`、`release_readiness_chain`、`cross_artifact_ref_validation_ok`、`test_evidence_gate_ok`、`diff_coverage_gate_ok`、`commit_boundary_ok`、`implementation_alignment_ok`、`test_evidence_digest`、`diff_coverage_digest`、`commit_readiness_digest`，并保持 `commit_execution_authorized=false`、`git_write=false`、`commit=false`、`push=false`、`pr=false`、`merge=false`。
+- `docs/runtime-contract.md` 是否声明 Stage 156 Implementation Task Completion Alignment，包含 `methodology --gate --kind implementation-plan --from-file`、`Implementation Task Registry`、`implementation_task_registry_digest`、`task_coverage`、`task_refs`、`implementation_alignment_gate`、`implementation_changed_file_unexplained`、`implementation_task_uncovered`、`implementation_operation_mismatch` 和 `implementation_task_missing_test_evidence`。
+- `examples/runtime-fixtures/negative/` 是否包含 negative release smoke 输入，覆盖 `traceability_ref_missing`、缺 `output_digest`、`unexpected_files` 非空、`commit_execution_authorized=true` / `git_write=true` 扩权阻断、changed file 缺 task_ref、required task 未覆盖、operation mismatch 和 risky task 缺测试证据。
+- `docs/workflow-chaining.md` 是否覆盖现有 workflow skill marker。
+- `skills/*/SKILL.md` 是否自动纳入 workflow handoff 检查；新增产品发现、产品规格、UI 设计和产品体验验收 skill 必须具备相同 `下一步调用` / `Workflow Handoff` 契约。
+- `templates/` 和 `examples/runtime-fixtures/` 是否包含产品发现、产品规格、UI contract、产品验收、场景验收 DSL、架构设计、交付追踪矩阵、实现计划、测试证据、diff coverage、commit readiness 和工程证据 fixture。
+- `tools/vibe-runtime/index.mjs` 和 `tools/vibe-runtime/README.md` 是否存在。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 56 `governance --compatibility --report` 只读兼容性检查，基于当前 `policy_catalog_digest`、`eval_catalog_digest` 和已识别 `known_trace_source_types` 报告 `compatible` / `manual-migration-required` / `untrusted`，且不创建 `.vibecoding-state/`、不迁移旧 artifact、不重签 digest。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 57 `governance --pr-readiness` optional governance sidecar，验证 `optional`、`sidecar-only`、`default_enabled=false`、`release_chain_required=false`、human approval、existing PR search evidence、`pr=false`、`push=false`、`merge=false` 边界；该检查只要求合约和命令存在，不要求默认生成 Stage 57 sidecar。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 58 `governance --pr-review-intake --from-file <local-evidence-file>` optional governance sidecar，验证本地 evidence digest、可选 Stage 57 readiness digest、`policy_catalog_digest`、`allowed_followup` 只建议不派发，以及 `platform_api=false`、`external_network=false`、`git=false`、`worktree=false`、`runtime_action=false` 边界；该检查只要求合约和命令存在，不要求默认生成 Stage 58 sidecar。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 59 `governance --convergence --report` 只读能力收敛差距报告，覆盖 `workflow-experience`、`learning-model`、`deterministic-token-economy`、`stream-distillation` 与 `runtime-governance`，并保持不写状态、不改 skill、不注册 hook、不拦截 shell、不联网、不调用模型或平台 API。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 60 `methodology --route --intent <kind>` 只读 workflow route，输出 `selected_workflow`、`first_skill`、`gate_kinds`、`trigger_discipline` 与 `route_digest`，并保持不写状态、不执行 workflow skill、不调用 subagent、不触发 runtime action。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 61 `learning --observe --from-file <session-evidence-file>` 本地 learning observation ledger，验证 `source_digest`、`evidence_excerpt_digest`、`signals_digest`、`learning_observation_digest`、`candidate_only=true`、`promotion_required=true`，并保持不写正式 skill、不改 prompt、不注册 hook、不拦截 shell、不联网、不调用模型/平台/subagent。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 62 `learning --instincts --from-observations <learning-observation-file...>` 与 `learning --promote --instinct <candidate-instinct-file>` 候选 instinct / promotion gate，验证 `.candidate-instinct.json` 与 `.learning-promotion.json` 的 observation/candidate digest 绑定、atomic trigger/action、manual skill authoring handoff、`vibe-writing-skills` 后续边界，并保持不自动写正式 skill、AGENTS.md、CLAUDE.md、prompt、hook、不拦截 shell、不联网、不调用模型/平台/subagent。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 63 `tokens --catalog`、`tokens --compact-output --command <cmd-name> --from-file <output-file>` 与 `tokens --verify <token-compaction-file>` 确定性 token output compactor，验证 `.token-compaction.json` 的 `source_digest`、`full_output_digest`、`compacted_digest`、`token_compaction_digest`、metrics、dropped categories 和 root-relative output file 边界，并保持不拦截 shell、不执行命令、不隐藏原始输出、不调用模型/平台/subagent、不自动 rewrite 用户命令。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 64 `tokens --profile --name minimal|balanced|full`、`tokens --metrics --from-compactions <token-compaction-file...>` 与 `tokens --rewrite-preview --command <cmd>` token economy 治理能力，验证 `.token-metrics.json` 的 source compaction digest、totals、command families、`token_metrics_digest`，并保持 profile/rewrite-preview 只读、不拦截 shell、不执行命令、不自动改写用户命令。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 65 `release --gate --from-evals <eval-report-file...> --with-convergence` 可选 convergence evidence 绑定，验证 `convergence_evidence_bound`、`convergence_digest`、`boundary_assertions_digest`、`evidence_digest`、`release_chain_required=false`、convergence report/evidence digest drift 负例，并保持 Stage 52 required suites 不变、不接平台/git/PR/subagent/MCP/daemon。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 68 `release --notes --from-file <local-evidence-file>` 与 `release --verify-notes <release-notes-file>` release notes evidence sidecar，验证 `.vibecoding-state/release-notes/*.release-notes.json` 的 `source_digest`、`range_hint`、`commit_hygiene_findings`、`release_notes_digest`、source digest drift 和 release notes digest mismatch，并保持不 amend、不 rebase、不 reset、不 force push、不 tag、不创建 PR、不调用平台/网络/模型，也不接入 release gate required chain。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 151 `methodology --gate --kind product-discovery|product-spec|ui-design|product-acceptance|scenario-acceptance --from-file <artifact>` 产品/UI artifact gate，验证 `product_methodology_gate`、`gate_digest`、source binding、required sections/fields、scenario DSL、boundary assertions，并保持 no write/no execution/no browser/no git/no subagent。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 152 `completion --evidence-bundle --from-product-discovery ... --from-evidence ...` 产品完成证据包，验证 `requirements_chain`、`product_readiness`、`ui_readiness`、`engineering_readiness`、`evidence_gaps`、`blocked_reasons`、`bundle_digest`，并保持 no verification execution/no git/no platform/no subagent。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 153 `methodology --gate --kind architecture-design --from-file <artifact>` 架构设计 artifact gate，验证 architecture decision frame、module ownership、dependency direction、data flow、state lifecycle、contract sync、Evidence、Boundary 和 `delivery-methodology-gate` digest。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 154 `methodology --gate --kind delivery-traceability --from-file <artifact>` 交付追踪矩阵 gate，验证 links、status enum、需求/产品/UI/架构/任务/测试/场景/验收 refs、boundary assertions 和 `delivery_methodology_gate` digest。
+- `tools/vibe-runtime/index.mjs` 是否提供 Stage 155 `completion --evidence-bundle --from-product-discovery ... --from-architecture ... --from-traceability ... --from-commit-readiness ...` full-chain completion evidence bundle，验证 `architecture_chain`、`traceability_chain`、`implementation_chain`、`release_readiness_chain`、`test_evidence_digest`、`diff_coverage_digest`、`commit_readiness_digest`，并保持 `commit_execution_authorized=false`、`git_write=false`、`commit=false`、`push=false`、`pr=false`、`merge=false`。
+- `tools/vibe-runtime/index.mjs` 是否保留 Stage 2 边界：显式 `record-handoff`、`.vibecoding-state/`、`next --dry-run`、`reset --confirm`。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 3 JSON-first handoff parser、`status` ledger 摘要、`record-handoff` quality hint 和 `next --dry-run` 文本建议 marker。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 4 artifacts dry-run/write、tasks dry-run/write、`validate-handoff` 只读校验和 `tasks --task` 单任务选择 marker，并保持只写 `.vibecoding-state/*.md` 与 `.vibecoding-state/tasks/<task-id>/*.md`，同时展示 `Goal`、`Key decisions`、`Review focus`、`Risk gate`、`Evidence gate`、`Evidence gaps to fill`、`Spec compliance gate`、`review_status` / `Review state` 和 evidence 决策证据 marker。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 4.7 只读 JSON 输出 marker：`jsonSchemaVersion`、`writeJsonEnvelope`、`status --json`、`validate-handoff --json`、`next --dry-run --json`、`tasks --dry-run --json`、`state_present`、`selected_count` 和 `artifact_paths`。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 5.x dispatch intent marker：`Vibecoding Runtime Dispatch Intent`、`next --dispatch-intent requires --dry-run`、`platform_hints`、manual `runtimeBridge` 和 `dispatch_event=false`。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 6.x confirm-dispatch marker：`next --confirm --dispatch`、`confirm-dispatch`、`Vibecoding Runtime Confirm Dispatch`、dispatch envelope、allowed transition、review gate、task readiness gate、`dispatches` 和 forbidden action boundary。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 6.5 read-only dispatch audit marker：`dispatches --list`、`dispatches --show`、`dispatches --verify`、`Vibecoding Runtime Dispatch Audit`、`dispatchAuditEnvelope`、`verifyDispatchEvent`、read-only dispatch audit 和 confirm-dispatch event verification。
+- `tools/vibe-runtime/index.mjs` 是否包含 Stage 11 supervised-run marker：`execute --confirm --run`、`supervised-run`、`runtime_action`、`generate-supervised-handoff-package`、`stage11AllowedExecutionSkills`、`Vibecoding Runtime Execution Audit`、`executions-audit-list`、`executions-audit-show`、`executions-audit-verify`、`validateExecutionEnvelope` 和 `execute --run requires --confirm`。
+- `.gitignore` 是否忽略 `.vibecoding-state/`。
+- `skills/*/SKILL.md` 是否包含：
+  - `## 下一步调用`
+  - `## Workflow Handoff`
+  - `current_skill:`
+  - `next_skill:`
+  - `handoff:`
+  - `stop_condition:`
+
+## 输出语义
+
+```text
+ok     contract 可被读取
+warn   contract 可读但存在未来 runtime 风险
+fail   缺少当前只读检查要求的必要结构
+```
+
+存在 `fail` 时返回非零退出码。
+
+## 与其他工具关系
+
+- `vibe-doctor`：检查安装布局、分发资产和入口文件一致性。
+- `vibe-runtime-check`：检查 workflow contract 是否可被 runtime 消费。
+- `vibe-release-check`：发布前聚合检查，可运行 runtime check。
+
+## 边界
+
+该工具只读，不做：
+
+- 写入 `.vibecoding-state/`。
+- 修改 skill、docs、入口文件或业务项目文件。
+- 自动选择或进入 `next_skill`。
+- 调用 subagent。
+- 执行 git、worktree、依赖安装或清理动作。
+- 启动 MCP、agent graph、daemon 或后台 worker。

package/tools/vibe-runtime-check/architecture-tool-contracts.mjs

@@ -0,0 +1,150 @@
+import process from 'node:process';
+import { spawnSync } from 'node:child_process';
+
+const architectureBaselineWarningCeiling = 0;
+export const architectureBaselineWarningCeilingsByRule = Object.freeze({
+  'contract-sync': 0,
+  'dependency-direction': 0,
+  'entry-like-domain-logic': 0,
+  'evolution-pressure': 0,
+  'factory-pressure': 0,
+  'file-role-budget': 0,
+  'function-density': 0,
+  'io-purity': 0,
+  'long-function': 0,
+  'owner-drift': 0,
+  'risk-zone-touch': 0,
+  'state-boundary': 0,
+});
+const requiredBaselinedWarningRuleFamilies = Object.freeze(
+  Object.entries(architectureBaselineWarningCeilingsByRule)
+    .filter(([, count]) => count > 0)
+    .map(([rule]) => rule),
+);
+
+function architectureBaselineFailureFix() {
+  return 'Owner: runtime/check governance. Risk: hidden architecture debt growth. Burn-down plan: locate the new file/rule via npm run check:arch JSON output, then split owner, narrow wording, or document an explicit burn-down entry before raising any baseline.';
+}
+
+export function evaluateArchitectureCheckReport(
+  report,
+  {
+    ceiling = architectureBaselineWarningCeiling,
+    requiredRuleFamilies = requiredBaselinedWarningRuleFamilies,
+    ruleCeilings = architectureBaselineWarningCeilingsByRule,
+  } = {},
+) {
+  const failures = [];
+  const warningCount = Number(report?.warning_count ?? 0);
+  const baselinedWarningCount = Number(report?.baselined_warning_count ?? 0);
+  const byRule = report?.baselined_warning_breakdown?.by_rule || {};
+  const missingRuleFamilies = [];
+  const unknownRuleFamilies = Object.keys(byRule).filter((rule) => !Object.prototype.hasOwnProperty.call(ruleCeilings, rule));
+  const exceededRuleFamilies = Object.entries(ruleCeilings)
+    .map(([rule, ruleCeiling]) => ({ rule, count: Number(byRule[rule] ?? 0), ceiling: ruleCeiling }))
+    .filter((item) => item.count > item.ceiling);
+
+  if (report?.result !== 'passed') failures.push(`architecture check result must remain passed; result=${report?.result || 'unknown'}`);
+  if (warningCount !== 0) failures.push(`architecture active warning count must be 0; warning_count=${warningCount}`);
+  if (baselinedWarningCount > ceiling) failures.push(`architecture baselined warning count exceeded ceiling; baselined_warning_count=${baselinedWarningCount}; ceiling=${ceiling}`);
+  if (missingRuleFamilies.length > 0) failures.push(`architecture baseline breakdown missing rule family key(s): ${missingRuleFamilies.join(', ')}`);
+  if (unknownRuleFamilies.length > 0) failures.push(`architecture baseline breakdown has unregistered rule family key(s): ${unknownRuleFamilies.join(', ')}`);
+  for (const item of exceededRuleFamilies) {
+    failures.push(`architecture baseline rule family exceeded ceiling; rule=${item.rule}; count=${item.count}; ceiling=${item.ceiling}`);
+  }
+
+  return {
+    ok: failures.length === 0,
+    failures,
+    warningCount,
+    baselinedWarningCount,
+    ceiling,
+    ruleCeilings,
+    ruleFamilyCount: Object.keys(byRule).length,
+    missingRuleFamilies,
+    unknownRuleFamilies,
+    exceededRuleFamilies,
+  };
+}
+
+function architectureBaselineCeilingContractFixtures() {
+  const by_rule = { ...architectureBaselineWarningCeilingsByRule };
+  return {
+    acceptedCurrentCeiling: { result: 'passed', warning_count: 0, baselined_warning_count: architectureBaselineWarningCeiling, baselined_warning_breakdown: { by_rule } },
+    rejectedBaselineGrowth: { result: 'passed', warning_count: 0, baselined_warning_count: architectureBaselineWarningCeiling + 1, baselined_warning_breakdown: { by_rule } },
+    rejectedRuleFamilyShift: { result: 'passed', warning_count: 0, baselined_warning_count: architectureBaselineWarningCeiling, baselined_warning_breakdown: { by_rule: shiftedRuleFamilyFixture() } },
+    rejectedUnknownRuleFamily: { result: 'passed', warning_count: 0, baselined_warning_count: architectureBaselineWarningCeiling, baselined_warning_breakdown: { by_rule: unknownRuleFamilyFixture() } },
+  };
+}
+
+function shiftedRuleFamilyFixture() {
+  return {
+    ...architectureBaselineWarningCeilingsByRule,
+    'risk-zone-touch': architectureBaselineWarningCeilingsByRule['risk-zone-touch'] - 1,
+    'dependency-direction': architectureBaselineWarningCeilingsByRule['dependency-direction'] + 1,
+  };
+}
+
+function unknownRuleFamilyFixture() {
+  return {
+    ...architectureBaselineWarningCeilingsByRule,
+    'risk-zone-touch': architectureBaselineWarningCeilingsByRule['risk-zone-touch'] - 1,
+    'not-registered-rule': 1,
+  };
+}
+
+function checkArchitectureBaselineCeilingFixture(api) {
+  const fixtures = architectureBaselineCeilingContractFixtures();
+  const accepted = evaluateArchitectureCheckReport(fixtures.acceptedCurrentCeiling);
+  const rejected = evaluateArchitectureCheckReport(fixtures.rejectedBaselineGrowth);
+  const rejectedRuleShift = evaluateArchitectureCheckReport(fixtures.rejectedRuleFamilyShift);
+  const rejectedUnknownRule = evaluateArchitectureCheckReport(fixtures.rejectedUnknownRuleFamily);
+  if (
+    accepted.ok
+    && !rejected.ok
+    && rejected.failures.some((failure) => failure.includes(`baselined_warning_count=${architectureBaselineWarningCeiling + 1}`))
+    && !rejectedRuleShift.ok
+    && rejectedRuleShift.failures.some((failure) => failure.includes('rule=dependency-direction; count=1; ceiling=0'))
+    && !rejectedUnknownRule.ok
+    && rejectedUnknownRule.failures.some((failure) => failure.includes('not-registered-rule'))
+  ) {
+    api.ok('architecture baseline ceiling fixtures reject total growth, rule migration, and unknown rule family', `ceiling=${architectureBaselineWarningCeiling}; dependency-direction ceiling=0`);
+  } else {
+    api.fail(
+      'architecture baseline ceiling fixture regressed',
+      `accepted=${accepted.ok}; rejected=${rejected.ok}; ruleShift=${rejectedRuleShift.ok}; unknownRule=${rejectedUnknownRule.ok}; failures=${[
+        ...rejected.failures,
+        ...rejectedRuleShift.failures,
+        ...rejectedUnknownRule.failures,
+      ].join('; ') || 'none'}`,
+      architectureBaselineFailureFix(),
+    );
+  }
+}
+
+export function checkArchitectureCheckTool(root, api) {
+  const tool = 'tools/vibe-architecture-check/index.mjs';
+  if (!api.exists(root, tool)) {
+    api.warn(`${tool} missing`, 'Architecture-first coding warnings are unavailable.', 'Restore the project-level architecture check tool.');
+    return;
+  }
+
+  const result = spawnSync(process.execPath, [tool, '--root', root, '--json'], { cwd: root, encoding: 'utf8', timeout: 30000, maxBuffer: 5 * 1024 * 1024 });
+  if (result.status !== 0) {
+    api.warn('architecture check could not run', (result.stderr || result.stdout || '').trim(), 'Keep tools/vibe-architecture-check/index.mjs runnable and warning-only.');
+    return;
+  }
+
+  try {
+    const report = JSON.parse(result.stdout);
+    const evaluation = evaluateArchitectureCheckReport(report);
+    if (evaluation.ok) {
+      api.ok('architecture check is runnable and warning-only', `${evaluation.warningCount} active warning(s); baselined=${evaluation.baselinedWarningCount}; ceiling=${evaluation.ceiling}; ruleFamilies=${evaluation.ruleFamilyCount}`);
+    } else {
+      api.fail('architecture warning baseline ceiling regressed', evaluation.failures.join('; '), architectureBaselineFailureFix());
+    }
+    checkArchitectureBaselineCeilingFixture(api);
+  } catch (error) {
+    api.warn('architecture check JSON output invalid', error.message, 'Keep architecture check --json machine-readable.');
+  }
+}