@zeyue0329/xiaoma-cli 1.0.37 → 1.0.39

package/xiaoma-core/agents/intelligent-template-adapter.yaml

@@ -158,7 +158,8 @@ multi_dimensional_quality_validation:
 
       - field_format_validation:
           user_story_format: "^\\*\\*作为\\*\\*.*\\*\\*我希望\\*\\*.*\\*\\*以便\\*\\*.*"
-          status_values: ["Draft", "Approved", "InProgress", "Review", "Done", "Completed"]
+          status_values:
+            ["Draft", "Approved", "InProgress", "Review", "Done", "Completed"]
           table_format: "MARKDOWN_TABLE"
           validation_method: "REGEX_AND_FORMAT_CHECK"
 
@@ -192,7 +193,8 @@ multi_dimensional_quality_validation:
     scoring:
       weight: 25
       pass_threshold: 90
-      improvement_strategies: ["content_enhancement", "clarity_improvement", "accuracy_correction"]
+      improvement_strategies:
+        ["content_enhancement", "clarity_improvement", "accuracy_correction"]
 
   # 维度3：跨文档一致性
   cross_document_consistency_validation:
@@ -220,7 +222,11 @@ multi_dimensional_quality_validation:
       weight: 20
       pass_threshold: 95
       correction_strategies:
-        ["terminology_standardization", "format_alignment", "reference_correction"]
+        [
+          "terminology_standardization",
+          "format_alignment",
+          "reference_correction",
+        ]
 
   # 维度4：实施可行性
   implementation_feasibility_validation:
@@ -248,7 +254,11 @@ multi_dimensional_quality_validation:
       weight: 15
       pass_threshold: 85
       improvement_actions:
-        ["design_optimization", "feasibility_enhancement", "implementation_guidance"]
+        [
+          "design_optimization",
+          "feasibility_enhancement",
+          "implementation_guidance",
+        ]
 
   # 维度5：业务价值对齐
   business_value_alignment_validation:
@@ -270,7 +280,11 @@ multi_dimensional_quality_validation:
       weight: 10
       pass_threshold: 80
       enhancement_strategies:
-        ["value_clarification", "requirement_refinement", "stakeholder_alignment"]
+        [
+          "value_clarification",
+          "requirement_refinement",
+          "stakeholder_alignment",
+        ]
 
 # ========== 自动纠错和改进系统 ==========
 auto_correction_and_improvement_system:

package/xiaoma-core/agents/master-execution-engine.yaml

@@ -304,7 +304,12 @@ quality_gate_system:
       type: "CRITICAL_GATE"
 
     - phase: "phase_2_intelligent_task_planning"
-      gates: ["TASK_ANALYSIS_VALIDATION", "STRATEGY_FEASIBILITY_CHECK", "QA_READINESS_VALIDATION"]
+      gates:
+        [
+          "TASK_ANALYSIS_VALIDATION",
+          "STRATEGY_FEASIBILITY_CHECK",
+          "QA_READINESS_VALIDATION",
+        ]
       type: "CRITICAL_GATE"
 
     - phase: "phase_3_automated_content_generation"
@@ -330,14 +335,16 @@ quality_gate_system:
       type: "CRITICAL_GATE"
 
     - phase: "phase_5_delivery_preparation"
-      gates: ["REPORTING_QUALITY_VALIDATION", "DELIVERY_READINESS_FINAL_VALIDATION"]
+      gates:
+        ["REPORTING_QUALITY_VALIDATION", "DELIVERY_READINESS_FINAL_VALIDATION"]
       type: "CRITICAL_GATE"
 
 # ========== 自动纠错和恢复系统 ==========
 automated_correction_and_recovery_system:
   correction_strategies:
     - strategy: "IMMEDIATE_AUTO_CORRECTION"
-      triggers: ["syntax_errors", "format_violations", "missing_required_sections"]
+      triggers:
+        ["syntax_errors", "format_violations", "missing_required_sections"]
       actions:
         - apply_template_format_correction
         - perform_syntax_standardization
@@ -355,7 +362,8 @@ automated_correction_and_recovery_system:
       max_attempts: 3
 
     - strategy: "COMPREHENSIVE_REFINEMENT_CYCLE"
-      triggers: ["integration_validation_failure", "business_value_misalignment"]
+      triggers:
+        ["integration_validation_failure", "business_value_misalignment"]
       actions:
         - perform_holistic_document_review
         - apply_comprehensive_improvement_strategies
@@ -400,7 +408,13 @@ monitoring_and_reporting_system:
 
   comprehensive_reporting:
     - report: "EXECUTIVE_SUMMARY_REPORT"
-      content: ["overall_quality_score", "key_achievements", "critical_issues", "recommendations"]
+      content:
+        [
+          "overall_quality_score",
+          "key_achievements",
+          "critical_issues",
+          "recommendations",
+        ]
       audience: "STAKEHOLDERS_AND_MANAGEMENT"
 
     - report: "DETAILED_TECHNICAL_REPORT"

package/xiaoma-core/agents/workflow-executor.md

@@ -3,6 +3,7 @@
 > **🔥🔥🔥 核心使命：完全自动化、连续执行、绝不中断询问**
 >
 > 本智能体的核心价值是**自动化工作流执行**。当用户执行 `*run-requirements-analysis` 或 `*run-story-development` 时，你必须像自动化流水线一样连续执行所有步骤，**绝对禁止**在中间步骤暂停询问用户：
+>
 > - 🚫 **禁止**："是否继续执行下一步骤？"
 > - 🚫 **禁止**："是否先查看已生成的文档？"
 > - 🚫 **禁止**："请选择 A/B/C"
@@ -43,8 +44,8 @@ activation-instructions:
   - 保持角色！
   - 关键提示: 激活时，仅向用户打招呼，自动运行 `*help`，然后停止以等待用户请求协助或给出命令。唯一的例外是激活参数中也包含了命令。
   - ⚠️⚠️⚠️ 自动化执行模式（极其重要）: 当用户执行 *run-requirements-analysis 或 *run-story-development 时，加载对应的工作流 YAML 文件，然后**必须自动连续执行工作流中定义的所有步骤（sequence），绝对不要在任何中间步骤停下来询问用户是否继续、是否查看文档、或提供选项让用户选择**。只有在遇到真正的错误（如文件不存在、执行失败）、质量门控失败、或明确需要人工决策时才暂停等待用户输入。
-  - 进度报告: 在执行每个步骤时，简要报告当前进度（例如："✅ 步骤 2/6 完成: Architect 现有架构分析"），然后**立即无需确认地**继续执行下一步骤。不要询问"是否继续"、不要提供"选项A/B/C"、不要问"您希望如何操作"，直接执行即可。
-  - 🚫 禁止行为: 绝对不要在步骤间暂停并问："是否希望我继续？"、"是否先查看文档？"、"请选择A/B/C"。这些都是不必要的中断。工作流必须像流水一样连续执行。
+  - "进度报告: 在执行每个步骤时，简要报告当前进度（例如：'✅ 步骤 2/6 完成: Architect 现有架构分析'），然后**立即无需确认地**继续执行下一步骤。不要询问'是否继续'、不要提供'选项A/B/C'、不要问'您希望如何操作'，直接执行即可。"
+  - "🚫 禁止行为: 绝对不要在步骤间暂停并问：'是否希望我继续？'、'是否先查看文档？'、'请选择A/B/C'。这些都是不必要的中断。工作流必须像流水一样连续执行。"
 
 agent:
   name: workflow-executor
@@ -72,8 +73,8 @@ persona:
     - 🔥🔥🔥 最高优先级原则：当执行 *run-requirements-analysis 或 *run-story-development 时，必须像自动化流水线一样连续执行所有步骤，绝对禁止在中间暂停询问用户。这是自动化工作流执行器的核心使命，违反此原则将完全失去自动化的意义。
     - 自动切换智能体：根据工作流定义，自动使用 /analyst、/architect、/pm、/po、/sm、/dev、/qa 等命令切换到相应的智能体角色
     - 连续执行模式：完成一个步骤后，立即显示简短进度（1-2行）并**无需任何确认**直接进入下一个步骤，直到整个工作流完成或遇到真正的技术错误
-    - 🚫 严禁中断询问：不要问"是否继续"、"请选择"、"您希望"等问题。用户启动工作流就是明确要求自动执行到底。唯一允许暂停的情况：文件不存在、执行报错、质量门控失败。
-    - ✅ 正确的进度报告格式：简短报告 + 立即继续，例如："✅ 步骤 3/6 完成: PM 创建 PRD → 立即开始步骤 4/6: PM 拆分史诗..."
+    - "🚫 严禁中断询问：不要问'是否继续'、'请选择'、'您希望'等问题。用户启动工作流就是明确要求自动执行到底。唯一允许暂停的情况：文件不存在、执行报错、质量门控失败。"
+    - "✅ 正确的进度报告格式：简短报告 + 立即继续，例如：'✅ 步骤 3/6 完成: PM 创建 PRD → 立即开始步骤 4/6: PM 拆分史诗...'"
 
 # 所有命令在使用时都需要 * 前缀 (例如, *help, *run-requirements-analysis)
 commands:
@@ -196,6 +197,7 @@ workflow_stages:
 **总耗时**: 约 1.5-2.5 小时
 
 **成功标准**:
+
 - ✅ 所有文档生成完成
 - ✅ 所有质量门控通过
 - ✅ 准备就绪进入用户故事开发阶段
@@ -308,6 +310,7 @@ workflow_stages:
 **总耗时**: 每个用户故事约 40-70 分钟（取决于复杂度）
 
 **成功标准**:
+
 - ✅ 所有用户故事状态为 Done
 - ✅ 所有测试通过
 - ✅ 所有质量门控通过
@@ -421,6 +424,7 @@ quality_gates:
 ```
 
 **🔥 重要说明 - 完全自动化执行**：
+
 - ✅ 工作流会**像流水线一样自动连续执行所有步骤**，完全无需在每个步骤后手动确认
 - ✅ 每个步骤完成后会显示简要进度报告（1-2行），然后**立即自动**进入下一步骤
 - ✅ 你只需要执行 `*run-requirements-analysis` 一次，然后等待所有 6 个步骤自动完成（约 1.5-2.5 小时）

package/xiaoma-core/agents/xiaoma-master.md

@@ -27,7 +27,7 @@ activation-instructions:
   - 关键规则: 当执行来自依赖项的正式任务工作流时，所有任务指令都会覆盖任何冲突的基础行为约束。带有 elicit=true 的交互式工作流需要用户交互，不能为了效率而绕过。
   - 在列出任务/模板或在对话中呈现选项时，始终以编号选项列表的形式显示，允许用户输入数字进行选择或执行
   - 保持角色！
-  - '关键提示: 启动期间请勿扫描文件系统或加载任何资源，仅在收到命令时执行（例外：激活期间读取 xiaoma-core/core-config.yaml）'
+  - "关键提示: 启动期间请勿扫描文件系统或加载任何资源，仅在收到命令时执行（例外：激活期间读取 xiaoma-core/core-config.yaml）"
   - 关键提示: 不要自动运行发现任务
   - 关键提示: 除非用户输入 *kb，否则绝不加载 root/data/bmad-kb.md
   - 关键提示: 激活时，仅向用户打招呼，自动运行 *help，然后停止以等待用户请求协助或给出命令。唯一的例外是激活参数中也包含了命令。

package/xiaoma-core/data/test-levels-framework.md

@@ -27,10 +27,10 @@ Comprehensive guide for determining appropriate test levels (unit, integration,
 
 ```yaml
 unit_test:
-  component: 'PriceCalculator'
-  scenario: 'Calculate discount with multiple rules'
-  justification: 'Complex business logic with multiple branches'
-  mock_requirements: 'None - pure function'
+  component: "PriceCalculator"
+  scenario: "Calculate discount with multiple rules"
+  justification: "Complex business logic with multiple branches"
+  mock_requirements: "None - pure function"
 ```
 
 ### Integration Tests
@@ -54,10 +54,10 @@ unit_test:
 
 ```yaml
 integration_test:
-  components: ['UserService', 'AuthRepository']
-  scenario: 'Create user with role assignment'
-  justification: 'Critical data flow between service and persistence'
-  test_environment: 'In-memory database'
+  components: ["UserService", "AuthRepository"]
+  scenario: "Create user with role assignment"
+  justification: "Critical data flow between service and persistence"
+  test_environment: "In-memory database"
 ```
 
 ### End-to-End Tests
@@ -81,10 +81,10 @@ integration_test:
 
 ```yaml
 e2e_test:
-  journey: 'Complete checkout process'
-  scenario: 'User purchases with saved payment method'
-  justification: 'Revenue-critical path requiring full validation'
-  environment: 'Staging with test payment gateway'
+  journey: "Complete checkout process"
+  scenario: "User purchases with saved payment method"
+  justification: "Revenue-critical path requiring full validation"
+  environment: "Staging with test payment gateway"
 ```
 
 ## Test Level Selection Rules

package/xiaoma-core/tasks/analyze-existing-database.md

@@ -11,7 +11,7 @@
 ```yaml
 action: check_existing_documentation
 path: docs/database/
-pattern: '{project_name}-database.md'
+pattern: "{project_name}-database.md"
 ```
 
 ### 2. 连接数据库

package/xiaoma-core/tasks/apply-qa-fixes.md

@@ -15,13 +15,13 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
 
 ```yaml
 required:
-  - story_id: '{epic}.{story}' # e.g., "2.2"
+  - story_id: "{epic}.{story}" # e.g., "2.2"
   - qa_root: from `xiaoma-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
   - story_root: from `xiaoma-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
 
 optional:
-  - story_title: '{title}' # derive from story H1 if missing
-  - story_slug: '{slug}' # derive from title (lowercase, hyphenated) if missing
+  - story_title: "{title}" # derive from story H1 if missing
+  - story_slug: "{slug}" # derive from title (lowercase, hyphenated) if missing
 ```
 
 ## QA Sources to Read

package/xiaoma-core/tasks/batch-story-generation.md

@@ -73,7 +73,7 @@ prioritization_algorithm:
     - implementation_risk: 实现风险评估
 
   priority_calculation:
-    formula: 'business_value * user_impact / (dependency_weight + risk_factor)'
+    formula: "business_value * user_impact / (dependency_weight + risk_factor)"
 
   priority_levels:
     - p0_critical: 关键路径故事
@@ -181,12 +181,12 @@ enhanced_story_generation:
 dependency_graph:
   nodes:
     - id: US001
-      title: '用户注册与登录'
+      title: "用户注册与登录"
       priority: P0
       estimated_effort: 3
 
     - id: US002
-      title: '权限管理基础'
+      title: "权限管理基础"
       priority: P0
       estimated_effort: 5
 
@@ -194,26 +194,26 @@ dependency_graph:
     - from: US001
       to: US002
       type: technical_dependency
-      description: '权限管理需要用户身份认证'
+      description: "权限管理需要用户身份认证"
 
     - from: US002
       to: US013
       type: business_flow_dependency
-      description: '个人信息管理需要权限控制'
+      description: "个人信息管理需要权限控制"
 
 critical_paths:
   - path: [US001, US002, US013, US025]
     duration: 15
-    description: '用户管理关键路径'
+    description: "用户管理关键路径"
 
 parallel_groups:
   - group_id: A
     stories: [US001, US002, US013]
-    focus: '用户管理'
+    focus: "用户管理"
 
   - group_id: B
     stories: [US003, US014, US025]
-    focus: '数据管理'
+    focus: "数据管理"
 ```
 
 ## Automation Integration
@@ -222,18 +222,18 @@ parallel_groups:
 
 ```yaml
 integration_points:
-  trigger_command: '*generate-all-stories'
+  trigger_command: "*generate-all-stories"
 
   input_sources:
-    - file: 'prd.md'
+    - file: "prd.md"
       validator: prd_completeness_check
-    - file: 'database_design.md'
+    - file: "database_design.md"
       validator: schema_consistency_check
 
   output_handlers:
-    - target: 'project_story_backlog.md'
+    - target: "project_story_backlog.md"
       post_processor: priority_validation
-    - target: 'stories/'
+    - target: "stories/"
       post_processor: story_format_validation
 ```
 
@@ -296,19 +296,19 @@ dynamic_adjustment:
 ```yaml
 error_scenarios:
   incomplete_prd:
-    detection: 'PRD缺少关键信息章节'
-    handling: '生成缺失信息提示，暂停生成'
-    recovery: '要求补充PRD信息后重新生成'
+    detection: "PRD缺少关键信息章节"
+    handling: "生成缺失信息提示，暂停生成"
+    recovery: "要求补充PRD信息后重新生成"
 
   conflicting_requirements:
-    detection: '需求之间存在逻辑冲突'
-    handling: '标记冲突点，生成冲突报告'
-    recovery: '人工review和冲突解决'
+    detection: "需求之间存在逻辑冲突"
+    handling: "标记冲突点，生成冲突报告"
+    recovery: "人工review和冲突解决"
 
   circular_dependencies:
-    detection: '故事间存在循环依赖'
-    handling: '依赖环检测和报告'
-    recovery: '自动依赖重构建议'
+    detection: "故事间存在循环依赖"
+    handling: "依赖环检测和报告"
+    recovery: "自动依赖重构建议"
 ```
 
 ### 质量保证措施

package/xiaoma-core/tasks/create-enhanced-story-with-database.md

@@ -49,12 +49,12 @@
 #### 2.1 基础信息填写
 
 ```yaml
-epic_num: '{{epic_number}}'
-story_num: '{{story_number}}'
-story_title_short: '{{story_title}}'
-role: '{{user_role}}'
-action: '{{user_action}}'
-benefit: '{{user_benefit}}'
+epic_num: "{{epic_number}}"
+story_num: "{{story_number}}"
+story_title_short: "{{story_title}}"
+role: "{{user_role}}"
+action: "{{user_action}}"
+benefit: "{{user_benefit}}"
 ```
 
 #### 2.2 数据库设计部分填写

package/xiaoma-core/tasks/nfr-assess.md

@@ -94,16 +94,16 @@ nfr_validation:
   _assessed: [security, performance, reliability, maintainability]
   security:
     status: CONCERNS
-    notes: 'No rate limiting on auth endpoints'
+    notes: "No rate limiting on auth endpoints"
   performance:
     status: PASS
-    notes: 'Response times < 200ms verified'
+    notes: "Response times < 200ms verified"
   reliability:
     status: PASS
-    notes: 'Error handling and retries implemented'
+    notes: "Error handling and retries implemented"
   maintainability:
     status: CONCERNS
-    notes: 'Test coverage at 65%, target is 80%'
+    notes: "Test coverage at 65%, target is 80%"
 ```
 
 ## Deterministic Status Rules
@@ -333,10 +333,10 @@ performance_deep_dive:
     p99: 350ms
   database:
     slow_queries: 2
-    missing_indexes: ['users.email', 'orders.user_id']
+    missing_indexes: ["users.email", "orders.user_id"]
   caching:
     hit_rate: 0%
-    recommendation: 'Add Redis for session data'
+    recommendation: "Add Redis for session data"
   load_test:
     max_rps: 150
     breaking_point: 200 rps

package/xiaoma-core/tasks/project-integration-testing.md

@@ -351,46 +351,46 @@ delivery_readiness:
 # integration_test_report.yaml
 test_report:
   executive_summary:
-    overall_status: 'PASSED'
-    system_readiness: 'READY_FOR_DEPLOYMENT'
+    overall_status: "PASSED"
+    system_readiness: "READY_FOR_DEPLOYMENT"
     critical_issues: 0
     total_test_cases: 2847
     pass_rate: 98.7%
 
   module_integration_results:
     user_management_module:
-      status: 'PASSED'
+      status: "PASSED"
       test_cases: 456
       pass_rate: 99.1%
       critical_issues: 0
 
     data_management_module:
-      status: 'PASSED'
+      status: "PASSED"
       test_cases: 623
       pass_rate: 98.9%
       critical_issues: 0
 
   performance_results:
     load_testing:
-      baseline_load: 'PASSED'
-      peak_load: 'PASSED'
-      sustained_load: 'PASSED'
+      baseline_load: "PASSED"
+      peak_load: "PASSED"
+      sustained_load: "PASSED"
 
     response_time_analysis:
-      average_api_response: '245ms'
-      p95_response_time: '680ms'
-      p99_response_time: '1.2s'
+      average_api_response: "245ms"
+      p95_response_time: "680ms"
+      p99_response_time: "1.2s"
 
   security_assessment:
-    vulnerability_scan: 'PASSED'
-    penetration_test: 'PASSED'
-    compliance_check: 'PASSED'
+    vulnerability_scan: "PASSED"
+    penetration_test: "PASSED"
+    compliance_check: "PASSED"
     high_severity_issues: 0
 
   recommendations:
-    - '优化数据库查询性能，减少p99响应时间'
-    - '增加API监控告警机制'
-    - '完善错误处理和用户友好提示'
+    - "优化数据库查询性能，减少p99响应时间"
+    - "增加API监控告警机制"
+    - "完善错误处理和用户友好提示"
 ```
 
 ### 交付清单
@@ -399,28 +399,28 @@ test_report:
 # delivery_checklist.yaml
 delivery_package:
   code_deliverables:
-    - source_code: '完整源代码包'
-    - build_artifacts: '构建产物'
-    - database_scripts: '数据库部署脚本'
-    - configuration_files: '配置文件模板'
+    - source_code: "完整源代码包"
+    - build_artifacts: "构建产物"
+    - database_scripts: "数据库部署脚本"
+    - configuration_files: "配置文件模板"
 
   documentation:
-    - api_documentation: 'API接口文档'
-    - deployment_guide: '部署指南'
-    - user_manual: '用户使用手册'
-    - maintenance_guide: '维护运营指南'
+    - api_documentation: "API接口文档"
+    - deployment_guide: "部署指南"
+    - user_manual: "用户使用手册"
+    - maintenance_guide: "维护运营指南"
 
   test_artifacts:
-    - test_suites: '完整测试套件'
-    - test_data: '测试数据集'
-    - performance_benchmarks: '性能基准报告'
-    - security_audit_report: '安全审计报告'
+    - test_suites: "完整测试套件"
+    - test_data: "测试数据集"
+    - performance_benchmarks: "性能基准报告"
+    - security_audit_report: "安全审计报告"
 
   operational_requirements:
-    - infrastructure_specifications: '基础设施规格'
-    - monitoring_configuration: '监控配置'
-    - backup_procedures: '备份程序'
-    - disaster_recovery_plan: '灾难恢复计划'
+    - infrastructure_specifications: "基础设施规格"
+    - monitoring_configuration: "监控配置"
+    - backup_procedures: "备份程序"
+    - disaster_recovery_plan: "灾难恢复计划"
 ```
 
 ## Integration with Full Requirement Orchestrator
@@ -430,21 +430,21 @@ delivery_package:
 ```yaml
 orchestrator_integration:
   trigger_conditions:
-    all_stories_completed: '所有用户故事状态为Done'
-    individual_story_tests_passed: '所有故事单元测试通过'
-    dependency_integration_ready: '依赖集成就绪'
+    all_stories_completed: "所有用户故事状态为Done"
+    individual_story_tests_passed: "所有故事单元测试通过"
+    dependency_integration_ready: "依赖集成就绪"
 
-  execution_command: '*execute-project-integration'
+  execution_command: "*execute-project-integration"
 
   success_criteria:
-    integration_tests_passed: '集成测试100%通过'
-    performance_benchmarks_met: '性能基准达标'
-    security_validation_complete: '安全验证完成'
+    integration_tests_passed: "集成测试100%通过"
+    performance_benchmarks_met: "性能基准达标"
+    security_validation_complete: "安全验证完成"
 
   failure_handling:
-    rollback_strategy: '回滚到最后稳定版本'
-    issue_triage: '问题分级和分配'
-    remediation_planning: '修复计划制定'
+    rollback_strategy: "回滚到最后稳定版本"
+    issue_triage: "问题分级和分配"
+    remediation_planning: "修复计划制定"
 ```
 
 ## Usage Examples

package/xiaoma-core/tasks/qa-gate.md

@@ -29,11 +29,11 @@ Slug rules:
 
 ```yaml
 schema: 1
-story: '{epic}.{story}'
+story: "{epic}.{story}"
 gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: '1-2 sentence explanation of gate decision'
-reviewer: 'Quinn'
-updated: '{ISO-8601 timestamp}'
+status_reason: "1-2 sentence explanation of gate decision"
+reviewer: "Quinn"
+updated: "{ISO-8601 timestamp}"
 top_issues: [] # Empty array if no issues
 waiver: { active: false } # Only set active: true if WAIVED
 ```
@@ -42,20 +42,20 @@ waiver: { active: false } # Only set active: true if WAIVED
 
 ```yaml
 schema: 1
-story: '1.3'
+story: "1.3"
 gate: CONCERNS
-status_reason: 'Missing rate limiting on auth endpoints poses security risk.'
-reviewer: 'Quinn'
-updated: '2025-01-12T10:15:00Z'
+status_reason: "Missing rate limiting on auth endpoints poses security risk."
+reviewer: "Quinn"
+updated: "2025-01-12T10:15:00Z"
 top_issues:
-  - id: 'SEC-001'
+  - id: "SEC-001"
     severity: high # ONLY: low|medium|high
-    finding: 'No rate limiting on login endpoint'
-    suggested_action: 'Add rate limiting middleware before production'
-  - id: 'TEST-001'
+    finding: "No rate limiting on login endpoint"
+    suggested_action: "Add rate limiting middleware before production"
+  - id: "TEST-001"
     severity: medium
-    finding: 'No integration tests for auth flow'
-    suggested_action: 'Add integration test coverage'
+    finding: "No integration tests for auth flow"
+    suggested_action: "Add integration test coverage"
 waiver: { active: false }
 ```
 
@@ -63,20 +63,20 @@ waiver: { active: false }
 
 ```yaml
 schema: 1
-story: '1.3'
+story: "1.3"
 gate: WAIVED
-status_reason: 'Known issues accepted for MVP release.'
-reviewer: 'Quinn'
-updated: '2025-01-12T10:15:00Z'
+status_reason: "Known issues accepted for MVP release."
+reviewer: "Quinn"
+updated: "2025-01-12T10:15:00Z"
 top_issues:
-  - id: 'PERF-001'
+  - id: "PERF-001"
     severity: low
-    finding: 'Dashboard loads slowly with 1000+ items'
-    suggested_action: 'Implement pagination in next sprint'
+    finding: "Dashboard loads slowly with 1000+ items"
+    suggested_action: "Implement pagination in next sprint"
 waiver:
   active: true
-  reason: 'MVP release - performance optimization deferred'
-  approved_by: 'Product Owner'
+  reason: "MVP release - performance optimization deferred"
+  approved_by: "Product Owner"
 ```
 
 ## Gate Decision Criteria