scene-capability-engine 3.3.23 → 3.3.25

package/lib/spec-gate/rules/default-rules.js

@@ -1,6 +1,7 @@
 const fs = require('fs-extra');
 const path = require('path');
 const docsCommand = require('../../commands/docs');
+const { validateSpecDomainArtifacts } = require('../../spec/domain-modeling');
 
 function createDefaultRules(projectPath = process.cwd()) {
   return [
@@ -75,6 +76,13 @@ function createDefaultRules(projectPath = process.cwd()) {
         };
       }
     },
+    {
+      id: 'domain_scene_modeling',
+      description: 'Verify mandatory problem-domain mind map and scene-spec artifacts',
+      async execute(context) {
+        return validateSpecDomainArtifacts(projectPath, context.specId, fs);
+      }
+    },
     {
       id: 'config_consistency',
       description: 'Verify project-level sce config baseline exists',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scene-capability-engine",
-  "version": "3.3.23",
+  "version": "3.3.25",
   "description": "SCE (Scene Capability Engine) - A CLI tool and npm package for spec-driven development with AI coding assistants.",
   "main": "index.js",
   "bin": {
@@ -69,11 +69,12 @@
     "report:release-ops-weekly": "node scripts/release-ops-weekly-summary.js --json",
     "gate:release-ops-weekly": "node scripts/release-weekly-ops-gate.js",
     "gate:errorbook-release": "node scripts/errorbook-release-gate.js --fail-on-block",
+    "gate:errorbook-registry-health": "node scripts/errorbook-registry-health-gate.js",
     "gate:git-managed": "node scripts/git-managed-gate.js --fail-on-violation",
     "gate:release-asset-integrity": "node scripts/release-asset-integrity-check.js",
     "report:release-risk-remediation": "node scripts/release-risk-remediation-bundle.js --json",
     "report:moqui-core-regression": "node scripts/moqui-core-regression-suite.js --json",
-    "prepublishOnly": "npm run test:full && npm run test:skip-audit && npm run test:sce-tracking && npm run test:brand-consistency && npm run gate:git-managed && npm run gate:errorbook-release && npm run report:interactive-governance -- --fail-on-alert",
+    "prepublishOnly": "npm run test:full && npm run test:skip-audit && npm run test:sce-tracking && npm run test:brand-consistency && npm run gate:git-managed && npm run gate:errorbook-registry-health && npm run gate:errorbook-release && npm run report:interactive-governance -- --fail-on-alert",
     "publish:manual": "npm publish --access public",
     "install-global": "npm install -g .",
     "uninstall-global": "npm uninstall -g scene-capability-engine"

package/template/.sce/steering/CORE_PRINCIPLES.md

@@ -72,6 +72,17 @@
 
 **目标**: 用户说"开始执行 Spec XX"，AI 自主完成所有任务交付功能
 
+### 4.2 强制默认自主推进（无二次确认）⚡
+
+**核心**: 默认执行策略必须是“自主闭环推进”，不是“每步等待确认”
+
+**默认行为**:
+1) 接到任务后直接进入：分析 → 修改 → 测试 → 修复 → 提交 → 推送（若已配置远端）  
+2) 非阻断性问题（可自行定位/修复）不得暂停等待用户二次确认  
+3) 仅在以下情况允许中断并请求用户介入：外部权限缺失、不可恢复致命错误、生产高风险变更、业务目标冲突
+
+**强制要求**: 不得以“先等你确认再继续”替代执行；未形成可验证结果前不得提前结束
+
 ### 5. 上下文管控
 
 **主动管控避免 token 耗尽**
@@ -158,6 +169,8 @@
 
 **复杂问题定位方法**: 优先使用 debug 日志与可观测信号定位（输入、输出、关键分支、异常栈、上下文参数），先还原执行路径再下结论
 
+**两轮失败强制调试规则**: 同一问题连续 2 轮修复仍未达到目标验证（测试/门禁/验收）时，必须切换到 debug 定位模式；先补充结构化 debug 日志与关键观测点，复现并固化失败证据，再进入第 3 轮修复。❌ 禁止在未接入调试证据前继续盲改
+
 **修复后清理要求**: 问题修复并验证通过后，必须清理临时 debug 日志、临时埋点、一次性脚本和调试开关；需要长期保留的日志必须转为可配置观测项且默认关闭
 
 **允许的临时措施**: 仅在生产止血场景可临时绕行，但必须同时给出根因修复任务、回滚条件和截止时间
@@ -189,6 +202,22 @@
 
 **目标**: 保证跨 Agent 连续性、可追溯历史、上下文可控，避免因 Agent session 长短差异导致上下文漂移
 
+### 14. 问题域思维导图 + 场景化 Spec 强制原则 🧠
+
+**核心**: Spec 推进必须先完成“问题域思维导图”与“场景化 Spec 契约”，再进入实现与修复闭环
+
+**硬规则**:
+1) 每个 Spec 必须具备：
+   - `.sce/specs/<spec>/custom/problem-domain-map.md`
+   - `.sce/specs/<spec>/custom/scene-spec.md`
+   - `.sce/specs/<spec>/custom/problem-domain-chain.json`
+2) `problem-domain-map` 必须包含：Root Problem、Mind Map、Layered Exploration Chain、Correction Loop
+3) `scene-spec` 必须包含：Scene Definition、Ontology Coverage、Decision & Execution Path、Acceptance & Gate
+4) `problem-domain-chain.json` 必须包含可机读思维链：problem/ontology/hypotheses/risks/decision_execution_path/correction_loop/verification
+5) 默认门禁强制校验上述结构，缺失即 `no-go`
+
+**目标**: 用全局问题域视角 + 场景契约约束，减少方向性错误与盲改，提升纠偏效率
+
 ---
 
-v18.0 | 2026-02-27 | 强化根因修复与临时兜底发布门禁原则
+v21.0 | 2026-03-01 | 强化“强制默认自主推进（无二次确认）”执行基线