@jtf19/vibecoding-kit 0.1.0

package/examples/full-chain/delivery-traceability.yaml

@@ -0,0 +1,32 @@
+version: 1
+artifact_kind: delivery-traceability
+source_skill: vibe-writing-plans
+status: accepted
+next_skill: vibe-test-driven-development
+
+# Evidence
+evidence_sources:
+  - examples/full-chain/evidence.json
+
+# Boundary
+boundary:
+  writes: false
+  state_directory_created: false
+  command_execution: false
+  test_execution: false
+  skill_execution: false
+  subagent: false
+  mcp: false
+  git: false
+links:
+  - id: trace-product-ui-architecture-gate
+    requirement_ref: req-product-ui-delivery-chain
+    product_story_ref: story-maintainer-validates-delivery-chain
+    ui_flow_ref: flow-runtime-artifact-gate-review
+    architecture_decision_ref: adr-delivery-methodology-gate
+    implementation_task_ref: task-extend-completion-bundle
+    test_evidence_ref: test-release-fast-delivery-chain
+    scenario_ref: product-gate-happy-path
+    product_acceptance_ref: acceptance-product-ui-delivery-chain
+    commit_readiness_ref: commit-readiness-local
+    status: verified

package/examples/full-chain/diff-coverage.json

@@ -0,0 +1,73 @@
+{
+  "version": 1,
+  "artifact_kind": "diff-coverage-evidence",
+  "status": "provided",
+  "diff_coverage_ref": "diff-delivery-chain-fixture",
+  "planned_files": [
+    "templates/architecture-design.md",
+    "templates/delivery-traceability.yaml",
+    "tools/vibe-runtime/runtime-delivery-methodology-gates.mjs",
+    "tools/vibe-runtime/runtime-completion-evidence-bundle.mjs",
+    "examples/full-chain/architecture-design.md",
+    "examples/full-chain/delivery-traceability.yaml"
+  ],
+  "changed_files": [
+    "templates/architecture-design.md",
+    "templates/delivery-traceability.yaml",
+    "tools/vibe-runtime/runtime-delivery-methodology-gates.mjs",
+    "tools/vibe-runtime/runtime-completion-evidence-bundle.mjs",
+    "examples/full-chain/architecture-design.md",
+    "examples/full-chain/delivery-traceability.yaml"
+  ],
+  "unexpected_files": [],
+  "missing_files": [],
+  "task_coverage": [
+    {
+      "task_ref": "task-extend-completion-bundle",
+      "status": "covered",
+      "changed_files": [
+        {
+          "path": "templates/architecture-design.md",
+          "operation": "modify",
+          "digest": "sha256:templates-architecture-design-fixture"
+        },
+        {
+          "path": "templates/delivery-traceability.yaml",
+          "operation": "modify",
+          "digest": "sha256:templates-delivery-traceability-fixture"
+        },
+        {
+          "path": "tools/vibe-runtime/runtime-delivery-methodology-gates.mjs",
+          "operation": "modify",
+          "digest": "sha256:runtime-delivery-methodology-gates-fixture"
+        },
+        {
+          "path": "tools/vibe-runtime/runtime-completion-evidence-bundle.mjs",
+          "operation": "modify",
+          "digest": "sha256:runtime-completion-evidence-bundle-fixture"
+        },
+        {
+          "path": "examples/full-chain/architecture-design.md",
+          "operation": "modify",
+          "digest": "sha256:examples-full-chain-architecture-design-fixture"
+        },
+        {
+          "path": "examples/full-chain/delivery-traceability.yaml",
+          "operation": "modify",
+          "digest": "sha256:examples-full-chain-delivery-traceability-fixture"
+        }
+      ]
+    }
+  ],
+  "boundary_assertions": {
+    "runtime_read_git_diff": false,
+    "command_execution": false,
+    "test_execution": false,
+    "git": false,
+    "git_write": false,
+    "commit": false,
+    "push": false,
+    "pr": false,
+    "merge": false
+  }
+}

package/examples/full-chain/evidence.json

@@ -0,0 +1,20 @@
+{
+  "version": 1,
+  "artifact_kind": "engineering-evidence",
+  "status": "provided",
+  "checks": [
+    {
+      "command": "node tools/vibe-runtime/index.mjs methodology --gate --kind product-spec --from-file examples/full-chain/product-spec.md --json",
+      "status": "pass",
+      "summary": "product methodology gate returned ok true"
+    },
+    {
+      "command": "node tools/vibe-runtime/index.mjs methodology --gate --kind scenario-acceptance --from-file examples/full-chain/scenario-acceptance.yaml --json",
+      "status": "pass",
+      "summary": "scenario acceptance gate returned ok true"
+    }
+  ],
+  "not_verified": [
+    "No browser, git, subagent, MCP, platform API, or external network action was executed by this evidence example."
+  ]
+}

package/examples/full-chain/implementation-plan.md

@@ -0,0 +1,54 @@
+# Full-Chain Implementation Plan Example
+
+## Goal
+
+Implement the delivery methodology evidence chain without adding runtime execution or git automation.
+
+## Architecture Binding
+
+- architecture_artifact: examples/full-chain/architecture-design.md
+- architecture_gate: methodology --gate --kind architecture-design
+
+## Implementation Task Registry
+
+- task_id: task-extend-completion-bundle
+  required: true
+  status: planned
+  source_refs: req-product-ui-delivery-chain, story-maintainer-validates-delivery-chain, adr-delivery-methodology-gate
+  expected_files: tools/vibe-runtime/runtime-completion-evidence-bundle.mjs, tools/vibe-runtime/runtime-delivery-methodology-gates.mjs, templates/architecture-design.md, templates/delivery-traceability.yaml, examples/full-chain/architecture-design.md, examples/full-chain/delivery-traceability.yaml
+  allowed_paths: tools/vibe-runtime/**, templates/**, examples/full-chain/**
+  expected_operations: add, modify, docs
+  required_scenario_refs: product-gate-happy-path
+  test_required: true
+  risk: medium
+  rollback: revert delivery chain runtime, fixture, and template changes only
+
+## Tasks
+
+- id: task-extend-completion-bundle
+  owner: tools/vibe-runtime/runtime-completion-evidence-bundle.mjs
+  layer: runtime read-only aggregation
+  dependency_direction: command wrapper -> bundle core -> local artifact readers
+  acceptance: expanded completion bundle binds architecture, traceability, plan, test, diff coverage, and commit readiness digests.
+  verification: full-chain demo smoke checks deterministic JSON markers.
+
+## Delivery Traceability
+
+- traceability_artifact: examples/full-chain/delivery-traceability.yaml
+- traceability_ref: trace-product-ui-architecture-gate
+
+## Evidence
+
+- evidence_sources: examples/full-chain/evidence.json, examples/full-chain/test-evidence.json, examples/full-chain/diff-coverage.json
+- not_verified: runtime does not execute tests or read git diff
+
+## Boundary
+
+- writes: false
+- state_directory_created: false
+- command_execution: false
+- test_execution: false
+- skill_execution: false
+- subagent: false
+- mcp: false
+- git: false

package/examples/full-chain/product-acceptance.md

@@ -0,0 +1,86 @@
+---
+artifact_kind: product-acceptance
+version: 1
+source_skill: vibe-product-acceptance
+status: accepted
+next_skill: vibe-verification-before-completion
+---
+
+# Full-Chain Product Acceptance Example
+
+## Goal
+
+- product_claim: Product/UI artifact gates are ready as local read-only completion evidence.
+- acceptance_scope: Product spec, UI contract, scenario DSL, and boundary claims.
+- ship_decision: pass
+
+## Input
+
+- product_spec_artifact: examples/full-chain/product-spec.md
+- ui_design_contract_artifact: examples/full-chain/ui-design-contract.md
+- scenario_acceptance_artifact: examples/full-chain/scenario-acceptance.yaml
+- engineering_evidence: examples/full-chain/evidence.json
+
+## Output Fields
+
+- product_claim: Artifact gates validate product/UI workflow contracts before completion.
+- scenario_coverage: Happy-path runtime gate scenario is covered by scenario-acceptance.yaml.
+- user_flow_evidence: CLI and JSON flows are represented by examples and smoke commands.
+- ui_state_evidence: Success and blocked states are represented by gate outcome and blockers.
+- accessibility_evidence: Text output uses labels rather than color-only status.
+- metric_readiness: Gate pass/block and digest are observable local signals.
+- experience_gaps: Visual quality and browser behavior are intentionally not verified.
+- not_verified: Browser rendering, screenshots, external platform behavior.
+- ship_decision: pass
+- next_skill: vibe-verification-before-completion
+
+## Non Goals
+
+- not_in_scope: Replacing engineering verification or commit readiness.
+
+## Risks
+
+- experience_risks: Product acceptance may be mistaken for test execution.
+- release_risks: Release docs must say smoke checks are read-only.
+- unresolved_decisions: none
+
+## Acceptance
+
+- pass_conditions: Product spec, UI design, scenario DSL, and product acceptance gates pass.
+- fail_conditions: Missing scenario evidence or unsafe boundary assertions.
+- blocked_conditions: Product or UI artifact lacks source binding, evidence, or handoff.
+
+## Reference Registry
+
+reference_registry:
+  product_acceptance_refs:
+    - acceptance-product-ui-delivery-chain
+
+## Evidence
+
+- evidence_sources: Static example and full-chain demo smoke commands.
+- not_verified: No browser, test runner, git, subagent, MCP, or platform API was run by this artifact.
+
+## Boundary
+
+- writes: false
+- state_directory_created: false
+- command_execution: false
+- skill_execution: false
+- subagent: false
+- mcp: false
+- git: false
+
+## Handoff
+
+current_skill: vibe-product-acceptance
+next_skill: vibe-verification-before-completion
+reason: Product acceptance evidence is present and can feed completion verification.
+handoff:
+  goal: Verify completion evidence before reporting done.
+  scope: Local evidence bundle only.
+  key_decisions: Keep git and release actions manual.
+  files: examples/full-chain/evidence.json
+  risks: Engineering verification still needs separate evidence.
+  acceptance: completion --evidence-bundle summarizes product and engineering readiness.
+stop_condition: none

package/examples/full-chain/product-discovery.md

@@ -0,0 +1,84 @@
+---
+artifact_kind: product-discovery
+version: 1
+source_skill: vibe-product-discovery
+status: accepted
+next_skill: vibe-product-spec
+---
+
+# Full-Chain Product Discovery Example
+
+## Goal
+
+- problem: Users need a visible way to confirm runtime product artifact checks before implementation.
+- target_users: maintainers using Vibecoding workflow skills
+- value_hypothesis: Standard artifacts reduce ambiguous handoffs between product, UI, and engineering workflows.
+- mvp_slice: Validate one product artifact locally through a read-only gate.
+
+## Input
+
+- original_request: Add product and UI artifact gates.
+- context: Runtime commands already support read-only methodology checks.
+- constraints: Do not execute workflows, tests, git, browser, subagents, MCP, or platform APIs.
+
+## Output Fields
+
+- scenarios: Maintainer runs a local gate against a product spec fixture.
+- current_alternatives: Free-form markdown that cannot be checked deterministically.
+- success_metrics: Gate returns a deterministic digest and actionable gaps.
+- anti_metrics: Gate mutates state or runs implementation commands.
+- mvp_slice: One local artifact and one read-only gate command.
+- non_goals: No automated implementation, browser validation, or git action.
+- risks: Artifact fields may drift unless checked by runtime-check.
+- decision: continue
+- next_skill: vibe-product-spec
+
+## Non Goals
+
+- not_in_scope: Visual regression, browser automation, or code generation.
+
+## Risks
+
+- product_risks: Users may confuse contract completeness with product quality.
+- assumptions: Local artifact content is user-provided evidence.
+- open_questions: none
+
+## Acceptance
+
+- discovery_complete_when: Required fields and handoff are present.
+- blocked_when: Problem, users, MVP slice, or evidence is missing.
+
+## Reference Registry
+
+reference_registry:
+  requirement_refs:
+    - req-product-ui-delivery-chain
+
+## Evidence
+
+- evidence_sources: This example is static local evidence for full-chain readiness demonstration.
+- not_verified: No user research was run.
+
+## Boundary
+
+- writes: false
+- state_directory_created: false
+- command_execution: false
+- skill_execution: false
+- subagent: false
+- mcp: false
+- git: false
+
+## Handoff
+
+current_skill: vibe-product-discovery
+next_skill: vibe-product-spec
+reason: Discovery is bounded and ready for product specification.
+handoff:
+  goal: Define checkable product/UI workflow artifacts.
+  scope: Local artifact contract only.
+  key_decisions: Keep gates read-only.
+  files: examples/full-chain/product-spec.md
+  risks: Contract completeness does not prove runtime behavior.
+  acceptance: Product spec artifact passes methodology gate.
+stop_condition: none

package/examples/full-chain/product-spec.md

@@ -0,0 +1,88 @@
+---
+artifact_kind: product-spec
+version: 1
+source_skill: vibe-product-spec
+status: accepted
+next_skill: vibe-ui-design
+---
+
+# Full-Chain Product Spec Example
+
+## Goal
+
+- product_goal: Provide a read-only product artifact gate that validates a local spec before planning.
+- release_slice: Add standard artifact contract checks for product spec and UI handoff.
+- priority: P1 because product workflow output must become reusable runtime evidence.
+
+## Input
+
+- discovery_artifact: examples/full-chain/product-discovery.md
+- users_and_scenarios: Maintainer checks product spec completeness before implementation planning.
+- constraints: Local-only, deterministic, no writes, no command execution, no git.
+
+## Output Fields
+
+- product_goal: Validate product spec artifacts as workflow contracts.
+- users_and_scenarios: Maintainers and assistant sessions using product/UI workflow skills.
+- user_stories: As a maintainer, I can gate a product spec file and see missing fields before planning.
+- functional_requirements: Gate checks frontmatter, sections, required fields, evidence, boundary, and handoff.
+- non_functional_requirements: Deterministic digest, root-relative file binding, and no runtime state writes.
+- acceptance_criteria: Passing artifact returns ok true, gate_outcome pass, and a gate digest.
+- priority: P1 product workflow contract.
+- release_slice: Product spec and UI design gate smoke fixtures.
+- out_of_scope: Running tests, writing state, browser validation, git automation.
+- open_questions: none
+- next_skill: vibe-ui-design
+
+## Non Goals
+
+- out_of_scope: Product quality scoring and automated implementation.
+
+## Risks
+
+- product_risks: Empty but syntactically present sections could still be weak evidence.
+- delivery_risks: CLI help and validation tools may drift from command behavior.
+- unresolved_decisions: none
+
+## Acceptance
+
+- acceptance_criteria: Runtime methodology gate passes this example.
+- fail_conditions: Missing evidence, boundary, next_skill, or required requirement fields.
+- release_readiness_signal: full-chain demo smoke can validate this example.
+
+## Reference Registry
+
+reference_registry:
+  requirement_refs:
+    - req-product-ui-delivery-chain
+  product_story_refs:
+    - story-maintainer-validates-delivery-chain
+
+## Evidence
+
+- evidence_sources: Static example for full-chain readiness demonstration.
+- not_verified: No implementation test was executed by this artifact.
+
+## Boundary
+
+- writes: false
+- state_directory_created: false
+- command_execution: false
+- skill_execution: false
+- subagent: false
+- mcp: false
+- git: false
+
+## Handoff
+
+current_skill: vibe-product-spec
+next_skill: vibe-ui-design
+reason: Product requirements are checkable and UI contract is needed.
+handoff:
+  goal: Define UI states and interaction contract for artifact gates.
+  scope: UI contract example and gate evidence.
+  key_decisions: Keep validation deterministic and read-only.
+  files: examples/full-chain/ui-design-contract.md
+  risks: UI quality is not visually judged by this gate.
+  acceptance: UI design artifact passes methodology gate.
+stop_condition: none

package/examples/full-chain/scenario-acceptance.yaml

@@ -0,0 +1,32 @@
+version: 1
+artifact_kind: scenario-acceptance
+source_skill: vibe-product-acceptance
+status: accepted
+next_skill: vibe-product-acceptance
+boundary:
+  writes: false
+  state_directory_created: false
+  command_execution: false
+  skill_execution: false
+  subagent: false
+  mcp: false
+  git: false
+scenarios:
+  - id: product-gate-happy-path
+    user: Vibecoding maintainer
+    given:
+      - product spec and UI contract artifacts exist under the project root
+    when:
+      - user runs methodology --gate with a product artifact file
+    then:
+      - runtime returns a deterministic gate digest and no writes
+    ui_states:
+      - success
+      - blocked
+    evidence:
+      required:
+        - release_smoke_output
+        - json_envelope
+      optional:
+        - manual_observation
+    status: pass

package/examples/full-chain/test-evidence.json

@@ -0,0 +1,29 @@
+{
+  "version": 1,
+  "artifact_kind": "test-evidence",
+  "status": "provided",
+  "test_evidence_ref": "test-release-fast-delivery-chain",
+  "runs": [
+    {
+      "id": "test-release-fast-delivery-chain",
+      "command": "node tools/vibe-release-check/index.mjs --suite fast --quiet",
+      "exit_code": 0,
+      "timestamp": "2026-03-14T00:00:00.000Z",
+      "output_digest": "sha256:release-fast-delivery-chain-fixture",
+      "task_refs": ["task-extend-completion-bundle"],
+      "scenario_refs": ["product-gate-happy-path"],
+      "status": "pass"
+    }
+  ],
+  "boundary_assertions": {
+    "runtime_executed_command": false,
+    "command_execution": false,
+    "test_execution": false,
+    "git": false,
+    "git_write": false,
+    "commit": false,
+    "push": false,
+    "pr": false,
+    "merge": false
+  }
+}

package/examples/full-chain/ui-design-contract.md

@@ -0,0 +1,87 @@
+---
+artifact_kind: ui-design-contract
+version: 1
+source_skill: vibe-ui-design
+status: accepted
+next_skill: vibe-planning
+---
+
+# Full-Chain UI Design Contract Example
+
+## Goal
+
+- design_goal: Make product artifact gate results understandable in one terminal or JSON envelope.
+- primary_user_flow: User runs methodology gate, reads pass/block result, then fixes artifact gaps manually.
+- target_surfaces: CLI text output and JSON envelope.
+
+## Input
+
+- product_spec_artifact: examples/full-chain/product-spec.md
+- user_stories: Maintainer checks contract gaps before planning.
+- design_constraints: No browser, no screenshots, no visual scoring.
+
+## Output Fields
+
+- screens: CLI result screen and JSON envelope consumer.
+- user_flow: Run command, inspect checks, fix artifact, rerun gate.
+- information_architecture: Stage, kind, artifact, source skill, next skill, check count, blockers, digest, boundary.
+- components: Summary header, source binding block, checks list, boundary line, manual action.
+- ui_states: loading is not applicable; success, blocked, and invalid input states are represented.
+- copy_rules: Text must say read-only and never imply workflow execution.
+- interaction_rules: User manually reruns command after editing local artifact.
+- responsive_rules: Terminal output stays line-oriented and JSON stays machine-readable.
+- accessibility: Plain text output preserves semantic labels and does not rely on color.
+- design_acceptance: Text and JSON expose blockers and boundary assertions.
+- open_questions: none
+- next_skill: vibe-planning
+
+## Non Goals
+
+- not_in_scope: Browser UI, screenshot comparison, generated design mockups.
+
+## Risks
+
+- usability_risks: Too many checks may be noisy unless blockers are concise.
+- accessibility_risks: Color-only status must not be introduced.
+- open_questions: none
+
+## Acceptance
+
+- design_acceptance: CLI text includes outcome, blockers, digest, and manual action.
+- ui_state_acceptance: Pass and blocked states are both representable.
+- accessibility_acceptance: Plain labels are available in text and JSON.
+
+## Reference Registry
+
+reference_registry:
+  ui_flow_refs:
+    - flow-runtime-artifact-gate-review
+
+## Evidence
+
+- evidence_sources: Static example for UI methodology gate smoke.
+- not_verified: No browser rendering or visual review was run.
+
+## Boundary
+
+- writes: false
+- state_directory_created: false
+- command_execution: false
+- skill_execution: false
+- subagent: false
+- mcp: false
+- git: false
+
+## Handoff
+
+current_skill: vibe-ui-design
+next_skill: vibe-planning
+reason: UI contract is defined and ready for implementation planning.
+handoff:
+  goal: Plan runtime gate implementation without expanding execution paths.
+  scope: CLI wrapper and read-only envelope.
+  key_decisions: Text output stays deterministic and no visual scoring is performed.
+  files: examples/full-chain/architecture-design.md
+  risks: CLI usage docs can drift.
+  acceptance: Runtime smoke validates the UI design example.
+stop_condition: none

package/examples/golden-path/README.md

@@ -0,0 +1,84 @@
+# Golden Path Demo
+
+这个目录是 Vibecoding Kit 的最小 `team mode` 交付闭环。它刻意小于 `examples/runtime-fixtures/` 下的 full-chain fixture，用来验证团队常规交付最需要的四类产物是否能对齐。
+
+## 它证明什么
+
+- `product-spec.md` 可以通过 product methodology gate。
+- `implementation-plan.md` 声明了 `Implementation Task Registry`。
+- `test-evidence.json` 和 `diff-coverage.json` 绑定到同一个 `task_ref`。
+- runtime 只验证本地 evidence envelope；它不运行测试、不读取 git diff、不提交。
+- 最小 team-mode 省略 full compliance artifact 时，completion readiness 顶层 `ok=false` 是预期边界；应优先查看 `task_completion_summary`。
+
+## 一条命令运行 demo
+
+从仓库根目录运行：
+
+```bash
+npm run demo:golden-path
+```
+
+等价底层命令：
+
+```bash
+node tools/vibe-release-check/index.mjs --suite golden-path --quiet
+```
+
+该 suite 会依次验证：
+
+```bash
+node tools/vibe-runtime/index.mjs methodology --gate --kind product-spec --from-file examples/golden-path/product-spec.md --json
+node tools/vibe-runtime/index.mjs methodology --gate --kind implementation-plan --from-file examples/golden-path/implementation-plan.md --json
+node tools/vibe-runtime/index.mjs completion --evidence-bundle --from-product-spec examples/golden-path/product-spec.md --from-plan examples/golden-path/implementation-plan.md --from-test-evidence examples/golden-path/test-evidence.json --from-diff-coverage examples/golden-path/diff-coverage.json --json
+```
+
+## 如何读取 readiness
+
+这个 demo 不是 full compliance。若直接查看 completion bundle JSON，顶层 `ok=false` 通常只表示缺少 product discovery、UI design、architecture、traceability、acceptance、commit readiness 等完整链路产物。
+
+最小 team-mode 应优先确认 `completion_evidence.task_completion_summary`：
+
+- `readiness_classification=team_mode_evidence_ready`
+- `local_task_ready=true`
+- `minimum_local_evidence_missing=[]`
+- `full_compliance_evidence_missing` 只包含升级到 full compliance 前需要补齐的 artifact 或 engineering evidence
+- `unsafe_release_actions_detected=[]`
+
+如果这些字段符合预期，说明本地测试证据、diff coverage 和实现计划任务已经形成最小可追踪闭环。需要排障时，再查看底层 `test_evidence_gate_ok`、`diff_coverage_gate_ok`、`implementation_plan_gate_ok`、`implementation_alignment_ok` 以及 git 写入边界字段。
+
+## 迁移到你的项目
+
+跑通 demo 后，业务项目不需要复制 full-chain fixture。先准备四个最小 team-mode 资产：
+
+```text
+product-spec.md
+implementation-plan.md
+test-evidence.json
+diff-coverage.json
+```
+
+建议做法：
+
+1. 从 `templates/product-spec.md` 和 `templates/implementation-plan.md` 起草业务 artifact。
+2. 从 `templates/evidence/test-evidence.json` 和 `templates/evidence/diff-coverage.json` 复制 evidence 模板。
+3. 替换真实 `task_refs`、`scenario_refs`、`command`、`exit_code`、`timestamp`、`output_digest`、`planned_files`、`changed_files` 和每个 changed file digest。
+4. 确认 evidence 中的边界声明仍为只读：runtime 没有运行测试、读取 git diff 或写 git。
+5. 依次运行 product-spec gate、implementation-plan gate 和 completion evidence bundle。
+
+业务项目最小验证命令：
+
+```bash
+node tools/vibe-runtime/index.mjs methodology --gate --kind product-spec --from-file product-spec.md --json
+node tools/vibe-runtime/index.mjs methodology --gate --kind implementation-plan --from-file implementation-plan.md --json
+node tools/vibe-runtime/index.mjs completion --evidence-bundle --from-product-spec product-spec.md --from-plan implementation-plan.md --from-test-evidence test-evidence.json --from-diff-coverage diff-coverage.json --json
+```
+
+需要升级到 full compliance 的典型信号：
+
+- 交付涉及高风险发布、跨团队审计或外部合规要求。
+- 需要证明 product discovery、UI、architecture、traceability、acceptance 和 commit readiness 的完整链路。
+- `blocked_reasons` 指向缺少上游 artifact，而团队不能接受这些缺口作为人工例外。
+
+## 边界
+
+这个 demo 不执行 workflow skills、测试、git、subagents、MCP、platform APIs、PR 创建或 merge。