create-yss-spec 3.0.1 → 3.1.0

package/template/.cursor/skills/yss-product-lifecycle/references/orchestration-contract.yaml

@@ -1,4 +1,19 @@
 schema_version: 1
+backend_architecture_identity_policy:
+  source: docs/agents/yss-skill-registry.yaml#architecture_profiles
+  schema: docs/process/schemas/backend-architecture-identity.schema.json
+  required_surfaces: [engineering-baseline, repository-registration, scaffold-manifest, slice-contract, work-unit, execution-result]
+  agreement: exact-identity-and-digest
+  missing_or_drift: blocked-and-recompile
+  new_profile_readiness: supported-only
+service_project_initialization:
+  work_unit: work-unit.service-project-initialization
+  skill: yss-mvc-data-analysis-project-initializer
+  architecture_profile: mvc-data-analysis-v1
+  context_inputs: [context_handoff_ref, context_handoff_digest]
+  approval: current-schema-v3-scaffold-contract-and-user-confirmed-architecture
+  parent_ownership: service-references-and-handoff-only
+  child_ownership: independent-git-project-instance-root-context-and-lifecycle
 supported_state_schema_versions: [1]
 
 implementation_path_policy:
@@ -25,6 +40,7 @@ checkpoint_policy:
   flush_immediately_on: [blocked, responsibility_changed, asset_approval]
   preserve_stage_causality: true
   required_stage_trace_fields: [stage, upstream_refs, artifact_refs, gate_decisions, downstream_impacts]
+  project_instance_stage_exit_requires_context_reconciliation: true
 
 modes:
   route: read_only
@@ -38,14 +54,6 @@ entry_routing:
   valid_modes: [template-source, project-instance]
   invalid_manifest:
     action: migration-check
-  direct_matt_entry:
-    skill: ask-matt
-    delegate_to: yss-product-lifecycle
-    requires_valid_manifest: true
-    action: navigate-only
-    lifecycle_state_mutation: forbidden
-    lifecycle_artifact_write: forbidden
-    return_to_orchestrator: required
   formal_user_entry:
     skills: [setup-matt-pocock-skills, grill-with-docs, to-spec, to-tickets, implement]
     action: lifecycle-validate-and-accept
@@ -87,7 +95,7 @@ workflow_execution_result:
       normalize_to: workflow-execution-result-v1
       removal_target: schema_version_2
   result_values: [completed, blocked, needs-human, failed]
-  required: [result_schema, work_unit, workflow_reference, result, evidence_refs, changed_artifacts, new_impacts, stale_candidates, next_route, blocking_signals]
+  required: [result_schema, work_unit, workflow_reference, result, context_reconciliation, evidence_refs, changed_artifacts, new_impacts, stale_candidates, next_route, blocking_signals]
   unavailable_skill:
     required: [skill, provider, fallback, resolution]
     blocking_result: blocked
@@ -97,6 +105,12 @@ workflow_execution_result:
   completed_requires_readable_evidence_refs: true
   evidence_ref_validation: readable-or-resolvable
   completed_requires_no_blocking_signals: true
+  context_reconciliation:
+    schema_ref: docs/process/schemas/context-reconciliation.schema.json
+    validator: scripts/verify-context-reconciliation
+    project-instance: {required_status: reconciled, readable_ref_required: true, transition_without_reconciliation: blocked}
+    template-source: {required_status: not-applicable, reason_required: true}
+    creates_gate: false
   workflow_reference:
     required: [source, skill, invocation_mode]
     allowed_sources: [yss-product-lifecycle, mattpocock/skills]
@@ -170,9 +184,9 @@ task_package:
 # may prepare, validate and accept their results, but cannot invoke them or create
 # their formal artifacts on their behalf.
 matt_invocation_boundary:
-  user_invoked_skills: [ask-matt, grill-me, grill-with-docs, handoff, implement, improve-codebase-architecture, loop-me, setup-matt-pocock-skills, setup-ts-deep-modules, teach, to-questionnaire, to-spec, to-tickets, triage, wait-what, wayfinder, writing-beats, writing-fragments, writing-shape]
+  user_invoked_skills: [grill-me, grill-with-docs, handoff, implement, improve-codebase-architecture, setup-matt-pocock-skills, to-questionnaire, to-spec, to-tickets, triage, wait-what, wayfinder]
   lifecycle_managed_user_entries: [setup-matt-pocock-skills, grill-with-docs, to-spec, to-tickets, implement]
-  model_invoked_skills: [code-review, codebase-design, diagnosing-bugs, domain-modeling, grilling, migrate-to-shoehorn, prototype, resolving-merge-conflicts, scaffold-exercises, setup-pre-commit, tdd, writing-for-agents, yss-research]
+  model_invoked_skills: [code-review, codebase-design, diagnosing-bugs, domain-modeling, grilling, prototype, resolving-merge-conflicts, tdd, writing-for-agents, yss-research]
   lifecycle_allowed_model_invoked_skills: [code-review, codebase-design, diagnosing-bugs, domain-modeling, grilling, prototype, tdd, yss-research]
   lifecycle_may_invoke_user_invoked: false
   formal_artifact_owner: explicit-user-entry
@@ -183,13 +197,13 @@ skill_source_contract:
   lock_version: 3
   source_revisions_required: [mattpocock/skills, iloveZzz/yss-ui]
   adaptation_ref_required_when_effective_diff: true
-  retired_shared_skills: [batch-grill-me, product-design-prototype, yss-dictionary, yss-jdbc, yss-log, yss-taskflow, yss-backend-scaffold-application, yss-backend-scaffold-domain, yss-backend-scaffold-infrastructure, yss-backend-scaffold-web]
+  retired_shared_skills: [ask-matt, batch-grill-me, dispatching-parallel-agents, loop-me, migrate-to-shoehorn, product-design-prototype, prototype-page-acceptance, scaffold-exercises, setup-pre-commit, setup-ts-deep-modules, teach, writing-beats, writing-fragments, writing-shape, yss-dictionary, yss-jdbc, yss-log, yss-microapp-commit, yss-page-module-development, yss-taskflow, yss-backend-scaffold-application, yss-backend-scaffold-domain, yss-backend-scaffold-infrastructure, yss-backend-scaffold-web]
 
 # 生命周期默认走原生工作单元；Matt user-invoked skill 仅保留为兼容入口。
 lifecycle_native_entries:
   default_entry: yss-product-lifecycle
   formal_artifact_owner: yss-product-lifecycle
-  user_confirmation_required_at: [spec-baseline, prototype-confirmation, openapi-freeze, merge-or-release]
+  user_confirmation_policy_ref: docs/agents/digital-human-roles.yaml#user_decision_policy
   compatibility_entries:
     to-spec: lifecycle-validate-and-accept
     to-tickets: lifecycle-validate-and-accept
@@ -241,8 +255,8 @@ work_unit_routes:
   work-unit.prototype-design:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-prototype-stage
-    supporting_skills: [prototype-review, yss-design-system, product-design:index, yss-antd-design]
-    skills: [prototype-review, yss-design-system, yss-prototype-stage, product-design:index, yss-antd-design]
+    supporting_skills: [prototype-review, yss-design-system, product-design:index, yss-antdv-next-design, yss-antd-design]
+    skills: [prototype-review, yss-design-system, yss-prototype-stage, product-design:index, yss-antdv-next-design, yss-antd-design]
     execution_order: [yss-design-system, low-fidelity-assets, prototype-review, prototype-profile-routing, profile-adapter-build, browser-design-qa-accessibility, user-confirmation]
     profile_routing_ref: .agents/skills/yss-prototype-stage/references/prototype-profile-routing.md
     prototype_adapter_ref: .agents/skills/yss-prototype-stage/references/product-design-adapter.md
@@ -254,7 +268,7 @@ work_unit_routes:
         H1: {kind: visual-review, adapter: static-html, node_runtime_required: false, antd_facts: not-applicable}
         H2: {kind: flow-review, adapter: runnable-flow, react_antd: supported-not-required, antd_facts: conditional}
     implementation_handoff: {production_component_assumptions: required-array, verification_targets: frontend-implementation-only}
-    version_boundary: {h2_design_standard: ant-design-v6-when-applicable, prototype_must_not_call: yss-ui, production_version_source: implementation-lockfile}
+    version_boundary: {h2_design_standard: vue-antdv-next-default-react-antd-explicit-compatibility, prototype_must_not_call: yss-ui, production_version_source: implementation-lockfile}
     human_gate: prototype-confirmation
     applies_when: product_design_impact
     not_applicable_reason: no_ui_or_product_design_impact
@@ -287,13 +301,13 @@ work_unit_routes:
   work-unit.slice-implementation:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-implementation-contract-compiler
-    supporting_skills: [tdd, yss-ui, yss-ui-business-page-generation, yss-page-module-development]
+    supporting_skills: [tdd, yss-ui, yss-ui-business-page-generation]
     compatibility: {source: mattpocock/skills, skill: implement, invocation_mode: reference, formal_artifact_owner: explicit-user-entry}
-    skills: [tdd, yss-implementation-contract-compiler, yss-ui, yss-ui-business-page-generation, yss-page-module-development]
+    skills: [tdd, yss-implementation-contract-compiler, yss-ui, yss-ui-business-page-generation]
     frontend_route:
       primary_skill: yss-ui
       page_generation_skill: yss-ui-business-page-generation
-      page_orchestration_skill: yss-page-module-development
+      page_orchestration_skill: yss-ui-business-page-generation
       conditional_skills:
         api_impact: [yss-api-integration]
         formily_impact: [yss-formily, formily-foundation, formily-linkage-effects, formily-mode-slot-detail, formily-step-flow]
@@ -323,8 +337,8 @@ work_unit_routes:
   work-unit.code-review:
     native: {source: yss-product-lifecycle, skill: code-review, invocation_mode: model-invoked}
     primary_skill: code-review
-    supporting_skills: [alibaba-java-code-style, yss-ui, yss-design-system, yss-page-module-development, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
-    skills: [code-review, alibaba-java-code-style, yss-ui, yss-design-system, yss-page-module-development, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
+    supporting_skills: [alibaba-java-code-style, yss-ui, yss-design-system, yss-ui-business-page-generation, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
+    skills: [code-review, alibaba-java-code-style, yss-ui, yss-design-system, yss-ui-business-page-generation, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
     review_standards_route:
       unique_default_skill: code-review
       second_generic_review_skill: forbidden
@@ -337,7 +351,7 @@ work_unit_routes:
         checkable_rule_without_machine: not-a-pass
       conditional_skills:
         backend_impact: [alibaba-java-code-style, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
-        ui_impact: [yss-ui, yss-design-system, yss-page-module-development]
+        ui_impact: [yss-ui, yss-design-system, yss-ui-business-page-generation]
       not_applicable_reasons:
         backend_impact: no_backend_impact
         ui_impact: no_ui_impact
@@ -506,6 +520,7 @@ review_input:
 
 git_authorization:
   natural_language_intent_is_authorization: false
+  explicit_scoped_user_reply_may_be_normalized: true
   commit:
     requires_explicit_user_authorization: true
     required: [commit_authorized, commit_scope, commit_authorization_ref]
@@ -541,21 +556,66 @@ git_authorization:
 
 seam_deferred_required: [risk, owner, follow_up_ticket, verification_plan, target_version_or_release_date]
 
+scaffold_architecture_decision:
+  applies_when: [backend_impact, scaffold_status_required]
+  owner: yss-product-lifecycle
+  stage: work-unit.technical-analysis
+  timing: after-impact-and-engineering-baseline-inputs-before-scaffold-contract-compilation
+  source: scaffold-architecture-decisions.yaml
+  schema_version: 1
+  statuses: [undecided, recommended, awaiting-user-decision, user-confirmed, lifecycle-approved, consumed, stale]
+  user_choices:
+    domain-driven:
+      display_name: DDD 开发脚手架
+      recommendation_signals: [aggregate-invariant, complex-state-machine, cross-aggregate-consistency, domain-event, complex-concurrency]
+    layered-mvc:
+      display_name: MVC 开发脚手架
+      recommendation_signals: [crud, reporting-query, data-transformation, external-system-orchestration, thin-domain]
+  recommendation_policy:
+    evidence_required: true
+    strong_domain_signal_prefers: domain-driven
+    all_strong_domain_signals_absent_and_thin_domain_prefers: layered-mvc
+    user_may_override_soft_recommendation: true
+    override_reason_required: true
+    unsupported_profile_is_hard_blocker: true
+  interaction:
+    generator_is_non_interactive: true
+    main_project_has_no_silent_default: true
+    child_projects_prefill_parent_default: true
+    batch_confirmation_required: true
+    prompt_fields: [project, responsibility, agent_recommendation, recommendation_reasons, inherited_from, current_choice, platform_profile, architecture_profile, verification_database, production_database, resolved_modules, warnings]
+    missing_or_deferred_action: blocked
+  inheritance:
+    modes: [root-default, inherit, override]
+    parent_change_stales_inherited_children: true
+    explicit_overrides_survive_parent_change: true
+    shared_profile_change_stales_all_affected: true
+    new_child_requires_confirmation: true
+  persistence:
+    required: [decision_id, project_id, parent_project_id, recommended_architecture, recommendation_reasons, confirmed_architecture, override_reason, inheritance_mode, inherited_from, platform_profile, architecture_profile, verification_database, production_database, requested_capabilities, resolved_modules, resolution_version, user_confirmation, decision_inputs_digest, status]
+    downstream_reference: [decision_ref, decision_id, decision_digest]
+    no_new_gate: true
+  change_policy:
+    before_lifecycle_approval: update-decision
+    after_lifecycle_approval_before_generation: stale-contract-and-recompile
+    after_generation: separate-architecture-migration-work-unit
+
 backend_scaffold:
   applies_when: [backend_impact]
   scaffold_statuses: [existing, required, initialized]
   required_status: required
   sequence:
     after: [prototype_review, prototype_verification, antd_cli_verification, browser_verification, prototype_confirmation, engineering_baseline]
-    before_generator: [yss-implementation-contract-compiler-scaffold-contract, lifecycle-approve-scaffold-contract]
+    before_generator: [scaffold-architecture-decision-user-confirmed, scaffold-architecture-decision-lifecycle-approved, yss-implementation-contract-compiler-scaffold-contract, lifecycle-approve-scaffold-contract]
     before: [business_code_generation, implement]
-  generator_skill: yss-ddd-scaffold-generator
-  baseline_skill: yss-backend-scaffold-parent
+  generator_routes:
+    domain-driven: { recipe: backend.ddd-scaffold, generator_skill: yss-ddd-scaffold-generator, baseline_skills: [yss-backend-scaffold-parent] }
+    layered-mvc: { recipe: backend.mvc-scaffold, generator_skill: yss-layered-mvc-scaffold-generator, baseline_skills: [] }
   tdd_mode: controlled-generation
   contract_schema:
-    schema_version: 2
+    schema_version: 3
     identity: service-engineering-baseline
-    required: [contract_id, contract_version, scaffold_request_id, status, compiler_draft_ref, lifecycle_approval_ref, persisted_ref, current_version, implementation_repository, backend_repository, scaffold_status, project_name, target_output_dir, base_package, maven_coordinates, profiles, allowed_write_paths, expected_evidence_files, verification_commands, approval, work_unit, generation_policy]
+    required: [contract_id, contract_version, scaffold_request_id, status, compiler_draft_ref, lifecycle_approval_ref, persisted_ref, current_version, implementation_repository, backend_repository, scaffold_status, project_name, target_output_dir, base_package, architecture_family, generator_skill, decision_ref, decision_id, decision_digest, maven_coordinates, profiles, module_profile, allowed_write_paths, expected_evidence_files, verification_commands, approval, work_unit, generation_policy]
     status_by_owner:
       router: [draft, ready-for-lifecycle-review, blocked]
       lifecycle: [approved, stale, blocked]
@@ -572,22 +632,20 @@ backend_scaffold:
       parent_required: [group_id, artifact_id, version]
       yss_components_version: 2.0.0-SNAPSHOT
     profiles:
-      required: [architecture, persistence, database, platform, validation_namespace, dto_placement, repository]
-      supported_initial:
-        architecture: target-domain-model
-        persistence: mybatis-plus
-        database: mysql
-        platform: spring-boot-2.7-jdk8
-        validation_namespace: javax
-        dto_placement: web
-        repository: yss-internal
-      unsupported: [old-architecture-profile, client-in-domain, mybatis, spring-boot-3, jakarta, separate-client-module]
+      discriminant: architecture_family
+      domain-driven: { generator_skill: yss-ddd-scaffold-generator, architecture: target-domain-model, persistence: mybatis-plus, verification_database: h2, production_database: not-bound, platform: spring-boot-2.7-jdk8, validation_namespace: javax, dto_placement: web, repository: yss-internal }
+      layered-mvc: { generator_skill: yss-layered-mvc-scaffold-generator, architecture: layered-mvc, persistence: mybatis-plus, verification_database: h2, production_database: not-bound, platform: spring-boot-2.7-jdk8, validation_namespace: javax, repository: yss-internal }
+      unsupported: [old-architecture-profile, mybatis, spring-boot-3, jakarta, arbitrary-module-combination]
+    module_profile:
+      required: [requested_capabilities, resolved_modules, resolution_version]
+      resolution_version: 1
     unsupported_inputs:
       schema_v1: reject-no-auto-upgrade
+      schema_v2_new_generation: reject-no-auto-upgrade
       slice_id: forbidden-as-scaffold-identity
       existing_project: reject-no-scaffold-migration
-  required_inputs: [implementation_repository, backend_repository, scaffold_status, scaffold_target_confirmed, scaffold_request_id, target_output_dir, project_name, base_package, maven_group_id, project_version, parent_group_id, parent_artifact_id, parent_version, yss_components_version, architecture_profile, persistence_profile, database, platform_profile, validation_namespace, dto_placement, repository_profile, scaffold_contract_file, scaffold_contract_draft, scaffold_contract_id, scaffold_contract_version, scaffold_contract_status, scaffold_contract_approved, scaffold_contract_compiler_draft_ref, scaffold_contract_lifecycle_approval_ref, scaffold_contract_persisted, scaffold_contract_persisted_ref, scaffold_contract_current_version]
-  required_evidence: [generator_inputs, expected_files, scaffold_generation_manifest_v2, generated_project_structure, generation_execution_result, verification_execution_result, architecture_rules, ./mvnw_validate, ./mvnw_test, ./mvnw_package, yss_skill_execution_result]
+  required_inputs: [implementation_repository, backend_repository, scaffold_status, scaffold_target_confirmed, scaffold_request_id, target_output_dir, project_name, base_package, architecture_family, generator_skill, decision_ref, decision_id, decision_digest, maven_group_id, project_version, parent_group_id, parent_artifact_id, parent_version, yss_components_version, architecture_profile, persistence_profile, verification_database, production_database, platform_profile, validation_namespace, dto_placement, repository_profile, requested_capabilities, resolved_modules, resolution_version, scaffold_contract_file, scaffold_contract_draft, scaffold_contract_id, scaffold_contract_version, scaffold_contract_status, scaffold_contract_approved, scaffold_contract_compiler_draft_ref, scaffold_contract_lifecycle_approval_ref, scaffold_contract_persisted, scaffold_contract_persisted_ref, scaffold_contract_current_version]
+  required_evidence: [scaffold_architecture_decision, user_confirmation_ref, decision_digest, generator_inputs, expected_files, scaffold_generation_manifest_v3, generated_project_structure, generation_execution_result, verification_execution_result, architecture_rules, ./mvnw_validate, ./mvnw_test, ./mvnw_package, yss_skill_execution_result]
   generation_options:
     with_example: false
     force: forbidden-by-default
@@ -595,7 +653,9 @@ backend_scaffold:
     template_upgrade: unsupported
     old_project_migration: unsupported-separate-architecture-modernization-initiative
   forbidden_generation: [business_rules, state_machine, permission, transaction, complex_query, error_mapping, user_visible_behavior, business_example_crud, unapproved_force_overwrite]
-  after_generation: [yss-backend-scaffold-parent, yss-implementation-contract-compiler]
+  after_generation:
+    domain-driven: [yss-backend-scaffold-parent, yss-implementation-contract-compiler]
+    layered-mvc: [yss-implementation-contract-compiler]
   existing_or_initialized: [baseline_evidence, wrapper_verification, implementation_contract_recompile]
   verification:
     commands: ["./mvnw validate", "./mvnw test", "./mvnw package"]
@@ -739,19 +799,19 @@ ready_for_agent:
 frontend_implementation_plan:
   applies_when: [ui_impact]
   required_before: [ready_for_agent]
-  required: [prototype_ref, spec_ref, route_and_page_inventory, visual_acceptance_cases, desktop_viewport, narrow_viewport, state_cases, pnpm_commands]
+  required: [prototype_ref, spec_ref, visual_baseline, route_and_page_inventory, baseline_case_ids, desktop_viewport, narrow_viewport, state_cases, pnpm_commands]
   schema: docs/process/schemas/frontend-implementation-evidence.schema.json
   validator: scripts/verify-frontend-implementation-evidence
-  acceptance: [kind_plan, template_false, status_approved, no_template_placeholders, readable_baseline_refs, non_empty_acceptance_cases]
+  acceptance: [kind_plan, template_false, status_approved, no_template_placeholders, readable_baseline_refs, approved_visual_baseline_digest_current, selected_case_ids_exist]
 
 frontend_implementation_verification:
   applies_when: [ui_impact]
   required_before: [release]
-  required: [prototype_ref, spec_ref, route_and_page_inventory, desktop_visual_evidence, narrow_view_visual_evidence, loading_empty_error_permission_interaction_results, console_warning_check, pnpm_commands, uncovered_differences, difference_owner]
+  required: [prototype_ref, spec_ref, visual_baseline, route_and_page_inventory, case_results, interaction_results, console_warning_check, pnpm_commands, actual_verification, uncovered_differences, difference_owner]
   verification: [actual_command, exit_code, executed_at, evidence_ref]
   schema: docs/process/schemas/frontend-implementation-evidence.schema.json
   validator: scripts/verify-frontend-implementation-evidence
-  acceptance: [kind_verification, template_false, status_approved, no_template_placeholders, console_warning_pass, independent_review_approved]
+  acceptance: [kind_verification, template_false, status_approved, no_template_placeholders, visual_baseline_identity_and_digest_match, case_results_pair_every_selected_case, no_unexplained_difference, console_warning_pass, pnpm_exit_codes_zero, independent_review_approved]
   blocked_when: [unexplained_visual_difference, missing_visual_evidence, typecheck_only, claimed_alignment_without_evidence]
   on_new_impact: [new_impacts, drift, reroute]
 
@@ -850,8 +910,8 @@ external_input_pause:
   reason_code: external-input-required
   reason: required decision-maker input is not available to the Agent
   required: [questionnaire_ref, recipient_role, requested_outputs, resume_route]
-  response_required: [response_ref, reclassified_impact, updated_authoritative_asset]
-  resume_requires: [response_ref, reclassified_impact, updated_authoritative_asset]
+  response_required: [response_ref, user_decisions, reclassified_impact, updated_authoritative_asset]
+  resume_requires: [response_ref, user_decisions, reclassified_impact, updated_authoritative_asset]
 
 prototype_modes:
   matt_logic:
@@ -871,3 +931,16 @@ behavioral_invariants:
   wait_what_preserves_state: true
   human_checkpoint_required_for_manual_steps: true
   diagnostics_redact_secrets: true
+
+user_decision_evidence:
+  policy_ref: docs/agents/digital-human-roles.yaml#user_decision_policy
+  schema_ref: docs/process/schemas/user-decision.schema.json
+  protocol_ref: references/user-decisions.md
+  verifier: scripts/verify-user-decision
+  workflow_result_fields: [user_decisions, user_decision_not_applicable]
+  implementation_fields: [user_decisions, slice_contract_ref, vertical_slice_ticket_ref]
+  checkpoint_carrier: human_review
+  professional_review_replaced: false
+  response_absent: paused-human-gate
+  invalid_response: blocked
+  basis_changed: stale

package/template/.cursor/skills/yss-product-lifecycle/references/orchestration.md

@@ -27,9 +27,11 @@ Matt phase boundary 是工作阶段之间的上下文决策，不是新的生命
 
 ## 原型到后端脚手架的接力
 
-`prototype_confirmation` 通过后，先判断实现仓库登记中的 backend `scaffold_status`。当状态为 `required` 时，先完成工程基线，由 `yss-implementation-contract-compiler` 编译脚手架 `controlled-generation` 工作单元合同，生命周期编排器批准并持久化后才能运行生成器；顺序为：工程基线 → 实现合同编译器 脚手架合同 draft → 生命周期批准/持久化 → 脚手架生成 → `yss-backend-scaffold-parent` 基线校验 → 实现合同编译器 合同重编译。`existing` / `initialized` 不重复全量生成，但不能跳过基线校验和 实现合同编译器 重编译。
+`prototype_confirmation` 通过后，先判断实现仓库登记中的 backend `scaffold_status`。当状态为 `required` 时，在工程基线中先完成脚手架架构选择：Agent 按领域复杂度给出 `domain-driven` / `layered-mvc` 推荐和依据，本体选择作为子项目预填默认值，用户通过批量表确认全部项目或逐项覆盖。选择写入 `scaffold-architecture-decisions.yaml`；处于 `undecided`、`recommended`、`awaiting-user-decision` 或 `stale` 时必须阻断，不得默认 DDD，也不得在生成器内交互。
 
-脚手架工作单元必须使用结构化合同 JSON 文件，至少记录 `contract_id`、`contract_version`、`slice_id`、实现合同编译器 draft 引用、生命周期批准引用、持久化引用、当前版本、允许写路径、预期证据文件和验证命令；批准记录至少含 `approval_ref`、`approver`、`persisted_ref`、`current_version`。生成器必须读取该合同文件并校验状态、版本、skill、工作模式和固定命令，不能只接受任意字符串参数。它还必须记录生成器输入、预期文件、目标目录、实际 `./mvnw validate` / `./mvnw test` / `./mvnw package` 结果和 YSS Skill Execution Result。三条命令必须由受控工作单元真实执行，逐条留存 `exit_code`、`duration_ms`、stdout/stderr 引用和执行时间；生成器打印的下一步命令不构成证据。生命周期生成关闭 `--with-example`；非空目标目录使用 `--force` 默认阻断，除非覆盖范围、备份、回滚点和批准引用已进入合同。脚手架不得把业务规则、状态机、权限、事务、复杂查询、错误映射或用户可见行为放进生成物；`validate` 通过、输出目录存在或生成器成功都不是生命周期批准、架构放行或 `ready-for-agent`。
+选择达到 `lifecycle-approved` 且 digest 当前后，由 `yss-implementation-contract-compiler` 编译脚手架 schema v3 `controlled-generation` 工作单元合同，生命周期批准并持久化后才能运行对应生成器。顺序为：工程基线与架构推荐 → 用户确认与选择持久化 → 实现合同编译器脚手架合同 draft → 生命周期批准/持久化 → `domain-driven` 使用 `yss-ddd-scaffold-generator` 或 `layered-mvc` 使用 `yss-layered-mvc-scaffold-generator` → 对应基线/Manifest v3 校验 → 实现合同编译器业务合同重编译。`existing` / `initialized` 不重复生成；架构转换必须单独立项。
+
+脚手架工作单元必须使用结构化 schema v3 合同 JSON，至少记录 `contract_id`、`contract_version`、`scaffold_request_id`、`architecture_family`、`generator_skill`、`decision_ref/id/digest`、Profile、能力模块闭包、实现合同编译器 draft 引用、生命周期批准引用、持久化引用、当前版本、允许写路径、预期证据文件和验证命令；不得使用 `slice_id` 伪造工程基线身份。生成器必须读取合同和决策文件并校验状态、digest、版本、skill、工作模式与固定命令。三条 Wrapper 命令必须由受控工作单元真实执行，逐条留存 `exit_code`、`duration_ms`、stdout/stderr 引用和执行时间；生成器打印的下一步命令不构成证据。非空目标、`--force`、旧项目迁移和模板升级均阻断。脚手架不得生成业务规则、状态机、权限、事务、复杂查询、错误映射、用户可见行为或示例业务 API；`validate` 通过、输出目录存在或生成器成功都不是生命周期批准、架构放行或 `ready-for-agent`。
 
 脚手架完成后，所有后续生成的后端代码仍必须重新消费当前版本的批准 Slice Implementation Contract、YSS skill 依赖闭包、允许写路径、预期证据和 Execution Result。业务行为使用 `behavior-tdd`；只有机械结构、样板、配置和冻结客户端使用 `controlled-generation`。缺少合同、skill、证据或实际验证时立即阻断；生成范围从机械内容变成业务行为时触发完整重路由。
 
@@ -76,9 +78,13 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 
 `repository_scope: git-submodule` 时授权按仓分别计算：禁止在 detached HEAD 提交；commit / push 顺序必须先子仓、再父仓 gitlink（`superproject-gitlink-update`）；父仓 push 使用 `git push --recurse-submodules=check`。空 gitlink、detached HEAD、`--force` 覆盖挂载点不得当成普通目录脚手架，也不得把实现源码复制进 Harness。登记字段必须能与 `harness-apps` / `external-repository` 区分，并对照工作树 gitlink。
 
+## 用户决定与恢复
+
+关键决定使用 [真实用户回复协议](user-decisions.md)，消费角色注册表的 `user_decision_policy`。会签前先形成可审阅资产；恢复、阶段流转、实施派发和发布时校验原始回复及当前资产摘要。普通会签的数字人审查与用户决定分别保留，关键决定不得以数字人会签、无反对意见或超时放行。等待只阻断依赖事项；新的 `user_decisions` 引用通过 Workflow Execution Result、checkpoint 和任务包传递。
+
 ## 必须暂停
 
-- Spec baseline、需求冻结、原型确认、OpenAPI Freeze 或 Architecture Review 等普通门禁等待会签裁决（数字人或生物人，以 `docs/agents/digital-human-roles.yaml` 的 `gate_policy` 为准）。暂停输出必须包含：门禁 ID、指定 `role_id`、`runtime_id`、会签文件路径。恢复前执行 `scripts/verify-approval-record`；角色错误、起草者自签或生物人门禁被数字人关闭时返回 `blocked`，不得标 `approved`。
+- Spec baseline、需求冻结、原型确认、OpenAPI Freeze 或 Architecture Review 等普通门禁等待会签裁决（数字人或生物人，以 `docs/agents/digital-human-roles.yaml` 的 `gate_policy` 为准）。暂停输出必须包含：门禁 ID、指定 `role_id`、`runtime_id`、会签文件路径。恢复前执行 `scripts/verify-approval-record --require-approved`；角色错误、起草者自签或生物人门禁被数字人关闭时返回 `blocked`，不得标 `approved`。
 - 需要目标仓库、外部凭据、发布窗口或其他新授权。
 - 状态与证据冲突且无法可靠重建。
 - 专项 skill 失败或返回不可验收结果。

package/template/.cursor/skills/yss-product-lifecycle/references/state-model.md

@@ -11,7 +11,7 @@
 | `tracker.kind` | `local-markdown`、`github`、`gitlab` |
 | `ticket.role` | `needs-triage`、`needs-info`、`ready-for-agent`、`ready-for-human`、`wontfix` |
 
-Matt 五态不得扩义。资产的 `ready-for-human` 与 Ticket label 必须带命名空间表达。`paused-human-gate` 表示等待 `docs/agents/digital-human-roles.yaml` 指定的会签人（数字人或生物人），不是「必须是生物人」。
+Matt 五态不得扩义。资产的 `ready-for-human` 与 Ticket label 必须带命名空间表达。`paused-human-gate` 表示等待 `docs/agents/digital-human-roles.yaml` 指定的会签人（数字人或生物人），不是「必须是生物人」。但 `user_decision_policy` 命中的关键决定还必须有真实用户回复，数字人会签不能解除该等待。
 
 ## 上下文与外部输入证据
 
@@ -38,6 +38,7 @@ phase_boundary:
 
 ```text
 required gates ∈ {approved, not-applicable}
+AND 关键决定及当前切片实施范围已有可追溯、当前且未撤回的真实用户批准
 AND related artifacts 不含 stale（若命中领域影响，`artifact.tactical-design` 或嵌入式 Tactical DDD Check 引用必须为当前版本）
 AND blocking edges 全部关闭
 AND implementation repo/branch/CI/test/rollback 已明确
@@ -49,7 +50,7 @@ AND Slice Implementation Contract 已由生命周期编排器批准并持久化
 AND Slice Implementation Contract 的 `ticket_ref` 与 `vertical_slice_ticket_ref` 完全一致
 AND 当前工作单元消费的 contract_id/version 与最新批准版本一致
 AND Backend Slice Implementation Contract（后端适用）和 Build Architecture Checklist 已完成
-AND backend 影响且 scaffold_status=required 时，原型确认后的脚手架策略、`yss-backend-scaffold-parent` 基线、Wrapper 验证和 实现合同编译器 重编译均已完成
+AND backend 影响且 scaffold_status=required 时，脚手架架构选择已由用户确认并达到 lifecycle-approved、schema v3 合同与 Manifest v3 当前、对应 DDD / Layered MVC 基线、Wrapper 验证和 实现合同编译器重编译均已完成
 AND 所有后续生成代码均绑定主 YSS skill、依赖闭包、允许写路径、预期证据和 YSS Skill Execution Result
 AND UI 影响切片的前端实现还原计划已通过 schema 校验、`template=false`、`status=approved`，且基线引用可读取
 ```
@@ -58,6 +59,8 @@ AND UI 影响切片的前端实现还原计划已通过 schema 校验、`templat
 
 发布前还必须满足所有已触发门禁均为 `approved` 或 `not-applicable`；UI 影响切片必须额外通过 `gate.frontend-implementation-verified`，不能只凭 fresh verification 和回滚点放行。
 
+任何 `project-instance` 工作单元进入下一步、任何阶段会签暂停或阶段完成 checkpoint，还必须引用当前工作单元的 `context_reconciliation`。其中 `status=reconciled`、`context_ref=CONTEXT.md`、`document_digest` 与 `referenced_terms_digest` 必须和根目录唯一 `CONTEXT.md` 一致；该证据不改变门禁数量。`template-source` 仅允许以带原因的 `not-applicable` 表示它只校验模板合同，不产生产品业务术语。
+
 用户显式运行 `to-tickets` 后，垂直切片初始 Ticket 状态固定为 `ready-for-human`。原生路径执行 `work-unit.ticket-decomposition` 时同样必须产生等价的垂直切片和 `Workflow Execution Result` 证据。只有 `yss-product-lifecycle` 复算上述公式全部为真后，才能把它提升为 `ready-for-agent`；生命周期不会自动调用 `to-tickets`，但不得跳过 Ticket 正式化工作单元。其默认标签也不参与该裁决。
 
 ## Review 与 Git 授权状态
@@ -110,3 +113,5 @@ pause:
 读取状态块后必须重新读取引用资产、审查记录、Ticket 最新事件和相关 Git 变化。时间戳只能提示变化，不能单独证明语义失效；应比较内容和影响面。冲突时以权威资产为准，记录修复原因，然后重算依赖、门禁和可执行 frontier。
 
 所有暂停/阻塞必须填写结构化 `pause`：`reason_code`、`gate_ref` 或证据引用、`owner_or_authority`、`resume_condition`、`next_work_unit`。`lifecycle.status` 保持粗粒度，恢复条件以 `pause` 为准。
+
+用户决定不新增状态；等待和恢复的引用字段、失效与复用规则见 [user-decisions.md](user-decisions.md)。

package/template/.cursor/skills/yss-product-lifecycle/references/user-decisions.md

@@ -0,0 +1,56 @@
+# 关键决策的真实用户回复协议
+
+适用门禁、工作单元和条件事项只由 `docs/agents/digital-human-roles.yaml.user_decision_policy` 定义。本协议解释执行和证据格式，不新增阶段、门禁或 Ticket 状态。专业审查记录与用户决定分别保存；关键决定缺少任一适用条件都不能放行。
+
+## 六条执行规则
+
+1. **先展示，再决定**：先完成可独立执行的检查和可审阅材料，展示资产链接、版本、关键变化、风险、推荐方案、批准范围和批准后的动作。优先使用 `renderDecisionRequest(request)` 生成完整展示文本；也接受原始消息已完整覆盖各项资产、版本、变化、风险、范围、推荐方案和后续动作的等价展示，不能因格式不同重复询问。不得请用户批准尚未形成的资产。
+2. **绑定原始回复**：保存回复人、原始消息引用、回复时间、原文、决定、对应事项、范围及请求摘要。Agent 只能整理，不得生成、推测或补造用户同意。来源记录是可追溯证据，不是密码学身份认证。
+3. **无回复就等待**：超时、默认选项、数字人同意、无反对意见和 Agent 自述均无效。依赖该决定的工作保持 `paused-human-gate` / `ready-for-human`；来源错误等使用 `blocked`。独立工作可以继续，不得借其完成清除未决决定。
+4. **回复必须指向明确**：单项明确请求的“同意”有效。多项需要逐项指定、清楚的子集或“同意以上全部事项”；“继续”不算全部批准。拒绝、修改意见和撤回均保留为有效回复，但不放行。编排器结合原文判定语义；机器核验结构、明确性底线、来源和绑定，不能用自填 `approved` 覆盖相反原文。
+5. **复用已有有效确认**：同一版本、范围和依据不重复询问，不按时间自动过期。相关资产或依据摘要变化、范围扩大或撤回时，旧批准失效；展示差异后重新确认。无关文件变化不触发重新确认。回复按来源时间追加，禁止删除拒绝、修改或撤回记录来恢复旧批准。
+6. **提问者和负责人分开**：默认回复人为提问者。其他业务、技术或发布负责人必须由提问者在原始消息中明确指定，包含对应事项和负责人；数字人不得自行代任。用户表达使用自然语言，内部 ID 和引用由 Agent 整理。
+
+## 记录与来源
+
+使用 `docs/process/schemas/user-decision.schema.json` 和 `docs/process/templates/user-decision-template.yaml`。存于 `docs/.scratch/<feature>/decisions/<request-id>.yaml`；已展示的请求快照不改写，修改方案产生新请求并保留旧引用。请求中的 `subject` 指向可独立摘要的资产正文或冻结快照，批准记录另存，避免正文包含自己的批准摘要形成循环。`basis` 列出影响决定的额外冻结依据。
+
+原始消息可由运行时直接读取，或保存为原始会话导出 / 用户提供的确认文件。跨平台统一捕获封装如下；字段必须来自原始来源，保留原始引用和完整原文，不能把 Agent 编写的摘要包装成来源：
+
+```yaml
+source_kind: session-export # platform-message | session-export | user-confirmation-file
+messages:
+  - id: <原始消息 ID>
+    original_ref: <平台消息链接或用户文件原始位置>
+    principal_ref: <原始作者标识>
+    actor_kind: biological-human # 展示请求的 Agent 消息使用 digital-human
+    sent_at: <原始时间，ISO 8601>
+    text: <完整原文>
+    reply_to: <回复关联的原始请求展示消息引用> # 回复必需；用户确认文件也可携带 request_digest
+```
+
+决定记录中的 `source` 绑定 `kind/ref/digest/message_id`。`ref` 必须可读；平台引用可经运行时的只读解析器提供，CLI 默认读取本地原始捕获封装。不能读取消息时使用原始导出或用户确认文件，不能仅填 URL 假定读取成功。文件摘要只能证明捕获内容一致，不证明作者身份；可信作者与消息内容由运行时或用户提供来源建立。
+
+回复人、时间、原文必须与来源一致。来源还须通过原始 `reply_to` 或用户确认文件中的 `request_digest` 指向当前展示，不能把其他对话中的“同意”嫁接到本次批准。平台没有显式 reply-to 时，可以使用同一原始会话导出中紧邻回复之前、原文和原始引用均匹配的请求消息建立关联；无法建立来源关联就保持等待，不由 Agent 虚构。多项映射使用 `single`、`explicit-items`、`explicit-all`；负责人不同的事项分别回复。`decision` 为 `approved/rejected/changes-requested/unclear/revoked`，只对回复列出的事项和范围生效。需要自然语言补充澄清时保持等待，不要求用户手填内部 schema。
+
+`requestDigest` 对请求除 `presented_source` 外的字段按键排序摘要，避免展示来源循环；展示文本包含该摘要。历史有效回复可导入原始展示消息的完整记录；只要原始展示覆盖当前决定且来源、范围与摘要可核验，即可复用，不要求补发模板消息。不能伪造已展示的新格式。无法证明历史请求与当前资产等价时，重新展示并确认。
+
+## 消费边界
+
+`scripts/verify-user-decision --requirements <当前事项.json> <决定记录.yaml>` 校验当前消费者要求的 `boundary/subject_ref/scope`；未给 `--requirements` 时校验请求中全部事项。无回复的草案可以保存，但不能通过批准验证。局部批准只允许已明确批准的事项推进。
+
+会签记录新增 `subject_ref`、`approval_scope` 和 `user_decision_ref`；checkpoint 门禁同时声明 `subject_ref/approval_scope` 并与会签记录一致。`verify-approval-record` 默认严格验证当前放行条件，`--require-approved` 是显式等价选项；只有 `--history` 仅检查历史记录结构，不构成批准。恢复和门禁关闭必须使用严格校验。旧数字人记录仍可读取和用于专业审查，不自动升级成用户决定。
+
+Workflow Execution Result 使用 `user_decisions` 保存当前要求与证据引用。`user_decision_not_applicable` 仅对未命中的既有技术条件门禁记录 `boundary/reason`，不得跳过已经执行的业务决策。完成结果通过 `validateNextRoute(..., result)` 检查；两参数调用仅检查路由结构，不能证明可以实际流转。
+
+checkpoint 的 `human_review` 保存 `user_decisions`、`required_decisions`、`not_applicable` 和需要时的 `external_input`。`stage_trace.completed_work_unit` 标识已完成单元；进入实施时 `human_review.implementation` 保存当前切片及持久化合同引用。等待态可以保存；恢复、流转和完成时重新核验。外部回复、新授权、风险接受均以同一决定记录作为恢复依据，不能以工具恢复或默认答案替代。
+
+## 首次实施与脚手架
+
+首次实施批准的主体为功能级 `implementation-scope` 清单，`slices` 每行包含：`ticket_ref`、`contract`（ref/version/digest）、`repositories`、`allowed_write_paths`、`baselines`（ref/version/digest）。仓库与写路径必须对应当前合同 `common.project_roots/allowed_write_paths`；基线包含合同引用的工程基线。`scope` 使用批准的切片引用集合。合同、范围或基线变化时回到确认；已覆盖的后续切片复用原记录。
+
+实施就绪和派发必须同时提供 `user_decisions`、`slice_contract_ref` 与 `vertical_slice_ticket_ref`。Worker 任务包通过 `user_decisions` 传递记录，不能只声明 `ready_for_agent=true`。
+
+脚手架 `user_confirmation` 新增 `user_decision_ref/decision_subject_ref`，主体为生成前的决策输入快照；当前范围至少包含项目 ID、确认的架构和 `decision_inputs_digest`。先获得真实回复，再由生命周期批准生成合同；不能回到生成器内提问。
+
+Git commit/push、外部动作仍分别检查已有授权和其范围。用户对一个具体动作的明确自然语言授权可整理成结构化记录，不必再次要求填写内部字段；生命周期批准不隐含其他动作授权。

package/template/.cursor/skills/yss-prototype-stage/SKILL.md

@@ -10,11 +10,11 @@ description: Use when a YSS feature has product-design impact on a primary flow,
 ## 进入条件与主入口
 
 - 先由 `yss-product-lifecycle` 判断产品设计影响；无行为变化的孤立视觉修复记录 `not-applicable`，不创建空资产。
-- 先读取 Spec、产品总体设计、`CONTEXT.md`、`yss-design-system` 与 `docs/design/design.md`，形成交互说明、低保真页面/流程和状态矩阵。
+- 先读取 Spec、产品总体设计、`CONTEXT.md`、`yss-design-system`，再按 `DESIGN.md` → `docs/design/design.md` → `docs/design/tokens/*` 顺序消费设计基线，形成交互说明、低保真页面/流程和状态矩阵。
 - 用独立 `prototype-review` 评审低保真与状态；未通过不得选择档位或构建原型交付物。
 - 按 [原型档位路由](references/prototype-profile-routing.md) 选择 H1/H2 中满足当前决策风险的最低档位。没有充分证据时默认 H2。
 - Codex 按档位消费 `product-design:index` 的 focused workflow；H1 可直接走静态适配器，H2 使用 `get-context/image-to-code/design-qa`。其他 Agent 必须交付等价合同资产。
-- `high-fidelity-html-prototype` 仅为历史兼容入口；新资产统一为 `artifact.prototype-deliverable` 与 schema v3。
+- `high-fidelity-html-prototype` 仅为历史兼容入口；新资产统一为 `artifact.prototype-deliverable`、Prototype Evidence schema v4 与 Visual Baseline schema v1。
 
 ## 执行顺序
 
@@ -22,23 +22,23 @@ description: Use when a YSS feature has product-design impact on a primary flow,
 2. 完成独立 `prototype-review`，提取仍需由原型回答的风险。
 3. 计算并记录 `prototype_profile`。新视觉方向或信息架构不确定时执行三方案 ideation；复用已批准模式时记录 `not-applicable` 与 source visual。
 4. H1 用 `prototype-contract.mjs prepare-static` 生成无 Node 运行时的静态适配器；H2 按 `references/product-design-adapter.md` 构建可运行流程。
-5. 自动采集版本、digest、视口、截图、console 与扫描结果，写入 feature 级 schema v3 `prototype-evidence.yaml`；人工只补决策、风险、允许差异和用户确认。
+5. 自动采集版本、digest、视口、截图、console 与扫描结果。截图按 `route + page + state + viewport + theme + locale + data_scenario` 写入 `Visual Baseline Bundle`，执行 `visual-baseline-contract.mjs seal` 后由 feature 级 schema v4 `prototype-evidence.yaml` 引用；人工只补决策、风险、允许差异和用户确认。
 6. 以统一六轴 Design QA 和档位验证矩阵完成浏览器/无障碍验证。用户确认后才可校准 Spec、分析 API 影响或进入 实现合同编译器 readiness。
 
 ## 档位边界
 
 - H1 `visual-review`：浏览器可复验的 HTML/CSS/少量 JS 或设计工具导出；不得要求 `package.json`、lockfile、Node 或 AntD CLI。
-- H2 `flow-review`：主流程与关键异常状态可操作；React/Vite + Ant Design v6 是受支持默认，但不是唯一实现。只有实际使用 AntD 时才消费版本事实或新鲜 fact pack。
+- H2 `flow-review`：主流程与关键异常状态可操作；Vue 3/Vite + Antdv Next 是受支持默认。React/Vite + Ant Design v6 仅作为显式兼容路线；只消费与实际 `component_basis` 匹配的精确版本事实或 fresh fact pack。
 - 原型代码默认 throwaway；可复用的是项目 Token、组件语义映射、状态、测试场景和验收标准。任何源码进入生产仍需 实现合同编译器、Slice Contract 和 TDD。
 - 原型阶段不得调用 `yss-ui`，不得读取生产组件 API 来制造“真实组件原型”。需要核验真实 YSS/AntDV 组件的事项写入 `implementation_handoff`，由前端实现计划、已批准切片的实现和实现还原验证负责。
 
 ## 事实、QA 与确认
 
-优先级固定为：项目 `docs/design/design.md` / Token 覆盖 → 当前功能语义 → 相关上游组件事实。H2 使用 AntD 时，fact pack 仅在精确版本、组件集合和项目 Token digest 均匹配且无新 API 疑问时可复用；否则做增量查询。`antd lint/doctor` 只对相关 React 源执行。
+优先级固定为：项目根 `DESIGN.md` 规范 Token / 组件变体 → `docs/design/design.md` 治理解释 → `docs/design/tokens/*` 派生快照 → 当前功能语义 → 相关上游组件事实。H2 默认通过 `yss-antdv-next-design` 使用 Antdv Next exact-version fact pack；只有显式选择 `react-antd-6` 时才调用 `yss-antd-design`。fact pack 仅在精确版本、组件集合、根 `DESIGN.md` digest 和项目 Token digest 均匹配且无新 API 疑问时可复用；否则做增量查询。`antd lint/doctor` 只对 React 兼容路线的相关源文件执行。
 
-Design QA 合并 visual、layout、interaction、content、accessibility、cross-platform 六轴，不再建立第二份评审。所有档位至少证明 desktop/narrow 非空渲染、项目 Token、console 和基础键盘/焦点/对比度；H2 追加主流程、关键异常、200% zoom/reduced motion 与按风险视觉回归。
+Design QA 合并 visual、layout、interaction、content、accessibility、cross-platform 六轴，不再建立第二份评审。所有档位至少证明 desktop/narrow 非空渲染、项目 Token、console 和基础键盘/焦点/对比度；H2 追加主流程、关键异常、200% zoom/reduced motion 与按风险视觉回归。图片是视觉基准而非唯一事实来源；模型必须从 `visual-baseline.yaml` 的 `case_id` 读取对应语义引用，禁止靠目录 glob 猜测页面含义。
 
-用户确认只描述原型确认了什么、哪些范围可操作、哪些为模拟或 gap，以及接受/拒绝结论；不要求用户确认技术栈、CLI 或构建细节。
+用户确认必须绑定提问者或其明确指定负责人的原始回复，使用生命周期 `user_decision_policy` 和统一用户决定记录；产品数字人只提供确认建议，不能代答。正式证据追加 `user_decision_ref/decision_subject_ref`，校验原型、视觉基线和操作范围与用户所见快照一致。用户确认只描述原型确认了什么、哪些范围可操作、哪些为模拟或 gap，以及接受/拒绝结论；不要求用户确认技术栈、CLI 或构建细节。
 
 `gate.prototype-reviewed`、`gate.prototype-verified`、`gate.user-confirmation` 保持三个既有门禁。档位选择是 `gate.prototype-verified` 的输入证据，不增加新门禁，也不授权实现。
 
@@ -47,10 +47,11 @@ Design QA 合并 visual、layout、interaction、content、accessibility、cross
 - 档位、上游融合与迁移：[prototype-profile-routing.md](references/prototype-profile-routing.md)
 - 渲染适配、fact pack 与命令：[product-design-adapter.md](references/product-design-adapter.md)
 - 证据模板：`docs/design/templates/prototype-evidence-template.yaml`
+- Visual Baseline 模板与 schema：`docs/design/templates/visual-baseline-template.yaml`、`docs/design/schemas/visual-baseline.schema.json`
 
 ## 常见错误
 
-- 把所有原型强制成 React/AntD，或把单个 HTML 文件当成所有档位的答案。
+- 继续把 React/AntD 当作 H2 默认，或把单个 HTML 文件当成所有档位的答案。
 - 低保真未评审就选择技术栈；用主观评分代替确定性触发规则。
 - H1 伪造 lockfile/AntD 段，或 H2 声称已验证生产 YSS/AntDV 真实组件。
 - 重复抄写机器可采集的版本、digest、截图和 console；创建第二份状态机、QA 或 handoff 资产。

package/template/.cursor/skills/yss-prototype-stage/references/product-design-adapter.md

@@ -24,36 +24,59 @@ node .agents/skills/yss-prototype-stage/scripts/prototype-contract.mjs validate-
 
 ## H2：可运行流程
 
-H2 可选择任何能稳定浏览器交付的轻量前端实现。采用 Product Design React/Vite + Ant Design v6 时：
+H2 可选择任何能稳定浏览器交付的轻量前端实现。默认 `component_basis=vue-antdv-next`，使用 Vue 3/Vite + Antdv Next：
 
 ```bash
 node .agents/skills/yss-prototype-stage/scripts/prototype-contract.mjs prepare-flow \
   --project-root <project-root> \
   --root <prototype-root> \
   --feature <feature> \
-  --target-antd-version <exact-6.x-version> \
   --pnpm-version <actual-pnpm-version>
 
 node .agents/skills/yss-prototype-stage/scripts/prototype-contract.mjs validate-project \
-  --profile H2 --root <prototype-root> \
-  --target-antd-version <exact-6.x-version>
+  --profile H2 --root <prototype-root>
 ```
 
-`prepare-flow` 只做机械适配：精确写入 `antd`、登记 pnpm、生成 `src/yss-theme.js` 与 adapter manifest。随后用 `ConfigProvider theme={yssTheme}`、`pnpm install`、`pnpm build` 形成可移植静态输出。H2 不使用 AntD 时无需执行该命令，在证据中写明 component basis，不能创建空 AntD 段。
+默认命令生成最小 Vue/Vite starter，精确写入 `antdv-next@1.5.2`、`vue@3.5.21`、`vite@6.4.2`、`@vitejs/plugin-vue@5.2.4`，登记实际 pnpm，生成 Vue 入口、`src/yss-theme.js` 与 provider-neutral adapter schema v3。设计 workflow 在 starter 中替换占位页面，再以 `ConfigProvider`、`pnpm install`、`pnpm build` 形成可移植静态输出。已有 Vue 页面不会被重写，但必须通过合同验证。
 
-### AntD fact pack
+显式兼容 React/Vite + Ant Design v6 时传入：
 
-建议目录为 `docs/design/facts/antd/<exact-version>/`，至少包含 `manifest.json`、design-md 摘要、组件事实与 digest。只有以下全部相等才为 fresh：
+```bash
+node .agents/skills/yss-prototype-stage/scripts/prototype-contract.mjs prepare-flow \
+  --project-root <project-root> \
+  --root <prototype-root> \
+  --feature <feature> \
+  --component-basis react-antd-6 \
+  --library-version <exact-6.x-version> \
+  --pnpm-version <actual-pnpm-version>
+```
+
+历史 `--target-antd-version` 继续映射到 `react-antd-6`，只为在途兼容，不再是默认调用。其他 H2 基座必须在证据中明确记录，不得伪造 Antdv Next 或 AntD 字段。
 
-- manifest 的 exact AntD version 等于原型 lockfile；
+### Provider fact pack
+
+默认目录为 `docs/design/facts/antdv-next/<exact-version>/`；React 兼容路线使用 `docs/design/facts/antd/<exact-version>/`。至少包含 `manifest.json`、design-md 摘要、组件事实与 digest。只有以下全部相等才为 fresh：
+
+- manifest 的 package 与 exact version 等于原型 lockfile；
 - 所需组件均被覆盖；
-- `project_token_baseline_digest` 等于当前设计基线；
+- 根 `DESIGN.md` path / digest 与当前规范源相等；
+- `project_token_baseline_digest` 等于当前 Token 派生基线；
 - 没有新的 API/semantic 疑问。
 
-不满足时只查询缺失或变化的事实。`lint/doctor` 只在存在相关 React 源时运行。不要创建占位 fact 目录；feature 证据只引用实际 manifest。
+不满足时只查询缺失或变化的事实。默认 Vue 路线调用 `yss-antdv-next-design`；React 兼容路线调用 `yss-antd-design`，且 `lint/doctor` 只在存在相关 React 源时运行。不要创建占位 fact 目录；feature 证据只引用实际 manifest。
 
 ## 共同映射与验证
 
 映射的是 semantic role、项目 Token、状态和验收行为，不是 React API 表面。默认视口为 desktop `1440x900` 与 narrow `390x844`；按影响追加其他断点。Design QA 固定写 feature 级 verification 路径，并按 visual/layout/interaction/content/accessibility/cross-platform 六轴执行。
 
+浏览器/Design QA 将每个风险驱动 case 捕获为 PNG，写入 `docs/.scratch/<feature>/handoff/visual-baseline-v<version>/images/`，并从 `docs/design/templates/visual-baseline-template.yaml` 生成 manifest。截图必须使用固定数据、sRGB、DPR 1，等待字体完成，关闭动画、过渡和光标闪烁；长页面使用固定滚动分段。捕获完成后运行：
+
+```bash
+node .agents/skills/yss-prototype-stage/scripts/visual-baseline-contract.mjs seal \
+  docs/.scratch/<feature>/handoff/visual-baseline-v1/visual-baseline.yaml \
+  --bundle-root docs/.scratch/<feature>/handoff/visual-baseline-v1
+```
+
+`seal` 校验 PNG 尺寸与大小并写入图像和整包摘要；随后以 `validate` 重验。模型和下游实现只从 manifest 的 `case_id` 取图，不通过 glob 推断含义。工作目录可位于被忽略的 `.scratch`，但 Strategic Design Handoff 必须携带或引用可读取的自包含 Bundle。
+
 H1/H2 的条件验证矩阵与实现阶段交接规则见 [prototype-profile-routing.md](prototype-profile-routing.md)。原型阶段禁止调用 `yss-ui`；真实组件事实只在批准后的前端实现与实现还原验证中取得。