scene-capability-engine 3.3.26 → 3.4.5

package/bin/scene-capability-engine.js

@@ -29,6 +29,7 @@ const {
   migrateLegacyKiroDirectories,
 } = require('../lib/workspace/legacy-kiro-migrator');
 const { auditSceTracking } = require('../lib/workspace/sce-tracking-audit');
+const { applyTakeoverBaseline } = require('../lib/workspace/takeover-baseline');
 
 const i18n = getI18n();
 const t = (key, params) => i18n.t(key, params);
@@ -167,6 +168,31 @@ function isLegacyMigrationAllowlistedCommand(args) {
   return false;
 }
 
+/**
+ * Commands that should inspect drift before auto-takeover mutates state.
+ *
+ * @param {string[]} args
+ * @returns {boolean}
+ */
+function isTakeoverAutoApplySkippedCommand(args) {
+  if (!Array.isArray(args) || args.length === 0) {
+    return false;
+  }
+
+  const commandIndex = findCommandIndex(args);
+  if (commandIndex < 0) {
+    return false;
+  }
+
+  const command = args[commandIndex];
+  if (command !== 'workspace') {
+    return false;
+  }
+
+  const subcommand = args[commandIndex + 1];
+  return subcommand === 'takeover-audit';
+}
+
 // 版本和基本信息
 program
   .name(t('cli.name'))
@@ -761,6 +787,70 @@ workspaceCmd
     }
   });
 
+workspaceCmd
+  .command('takeover-audit')
+  .description('Audit whether project takeover baseline is aligned with current SCE defaults')
+  .option('--json', 'Output in JSON format')
+  .option('--strict', 'Exit non-zero when takeover drift is detected')
+  .action(async (options) => {
+    const report = await applyTakeoverBaseline(process.cwd(), {
+      apply: false,
+      writeReport: false,
+      sceVersion: packageJson.version
+    });
+
+    if (options.json) {
+      console.log(JSON.stringify(report, null, 2));
+    } else if (!report.detected_project) {
+      console.log(chalk.gray(report.message || 'No .sce project detected.'));
+    } else if (report.passed) {
+      console.log(chalk.green('✓ Takeover baseline audit passed.'));
+      console.log(chalk.gray(`Aligned files: ${report.summary.unchanged}`));
+    } else {
+      console.log(chalk.yellow('⚠ Takeover baseline drift detected.'));
+      console.log(chalk.gray(`Pending fixes: ${report.summary.pending}`));
+      report.files
+        .filter((item) => item.status === 'pending')
+        .forEach((item) => {
+          console.log(chalk.gray(`  - ${item.path}`));
+        });
+    }
+
+    if (report.detected_project && options.strict && !report.passed) {
+      process.exitCode = 1;
+    }
+  });
+
+workspaceCmd
+  .command('takeover-apply')
+  .description('Apply takeover baseline defaults for current SCE operating mode')
+  .option('--json', 'Output in JSON format')
+  .action(async (options) => {
+    const report = await applyTakeoverBaseline(process.cwd(), {
+      apply: true,
+      writeReport: true,
+      sceVersion: packageJson.version
+    });
+
+    if (options.json) {
+      console.log(JSON.stringify(report, null, 2));
+      return;
+    }
+
+    if (!report.detected_project) {
+      console.log(chalk.gray(report.message || 'No .sce project detected.'));
+      return;
+    }
+
+    console.log(chalk.green('✓ Takeover baseline applied.'));
+    console.log(chalk.gray(`Created: ${report.summary.created}`));
+    console.log(chalk.gray(`Updated: ${report.summary.updated}`));
+    console.log(chalk.gray(`Unchanged: ${report.summary.unchanged}`));
+    if (report.report_file) {
+      console.log(chalk.gray(`Report: ${report.report_file}`));
+    }
+  });
+
 // Environment configuration management commands
 const envCommand = require('../lib/commands/env');
 
@@ -979,6 +1069,7 @@ async function updateProjectConfig(projectName) {
   // Parse startup flags and guardrails
   const args = process.argv.slice(2);
   const isLegacyAllowlistedCommand = isLegacyMigrationAllowlistedCommand(args);
+  const skipAutoTakeover = isTakeoverAutoApplySkippedCommand(args);
   const skipCheck = args.includes('--skip-steering-check') || 
                     process.env.KSE_SKIP_STEERING_CHECK === '1';
   const forceCheck = args.includes('--force-steering-check');
@@ -995,6 +1086,18 @@ async function updateProjectConfig(projectName) {
       process.exit(2);
     }
   }
+
+  if (!isLegacyAllowlistedCommand && !skipAutoTakeover) {
+    try {
+      await applyTakeoverBaseline(process.cwd(), {
+        apply: true,
+        writeReport: true,
+        sceVersion: packageJson.version
+      });
+    } catch (_error) {
+      // Startup auto-takeover is best effort and should not block commands.
+    }
+  }
   
   // Run compliance check
   await runSteeringComplianceCheck({

package/docs/README.md

@@ -1,291 +1,89 @@
-# sce Documentation Index
+# SCE Documentation Hub
 
-> Complete guide to sce (Scene Capability Engine)
+This hub focuses on high-value paths for adopting and scaling SCE.
 
 ---
 
-**Version**: 1.46.2  
-**Last Updated**: 2026-02-14
+## Start Here
 
----
-
-## 🚀 Getting Started
-
-**New to sce?** Start here:
-
-- **[Quick Start Guide](quick-start.md)** - Get up and running in 5 minutes
-- **[FAQ](faq.md)** - Frequently asked questions
-- **[Troubleshooting](troubleshooting.md)** - Common issues and solutions
-
-## ⭐ Why Teams Choose sce
-
-- **Structured AI delivery**: Specs enforce Requirements → Design → Tasks before implementation.
-- **Parallel execution at scale**: Orchestrate multiple Specs with dependency-aware scheduling.
-- **Dual-track handoff closure**: `sce auto handoff run` executes plan/queue/batch/observability in one closed loop, supports `--continue-from` resume, and emits executable follow-up recommendations.
-- **Measurable outcomes**: KPI snapshot/baseline/trend commands make delivery quality auditable.
-- **Tool-agnostic workflow**: Works across Claude, Cursor, Windsurf, Copilot, and SCE.
-- **Built-in governance**: Locks, document governance, environment/workspace controls, and audit trails.
-
----
-
-## 📖 Core Concepts
-
-Understand how sce works:
-
-- **[Spec Workflow](spec-workflow.md)** - Understanding the Spec-driven development process
-- **[Integration Modes](integration-modes.md)** - Three ways to integrate sce with AI tools
-- **[Command Reference](command-reference.md)** - Complete list of all sce commands
-
----
-
-## 🛠️ Tool-Specific Guides
-
-Choose your AI tool and learn how to integrate:
-
-### Native Integration
-- **[AI IDE Guide](tools/SCE-guide.md)** - Fully automatic integration
-
-### Manual Export Integration
-- **[Cursor Guide](tools/cursor-guide.md)** - Using sce with Cursor IDE
-- **[Claude Code Guide](tools/claude-guide.md)** - Using sce with Claude Code
-- **[VS Code + Copilot Guide](tools/vscode-guide.md)** - Using sce with VS Code and GitHub Copilot
-
-### Watch Mode Integration
-- **[Windsurf Guide](tools/windsurf-guide.md)** - Using sce with Windsurf (supports watch mode)
-
-### Universal Integration
-- **[Generic AI Tools Guide](tools/generic-guide.md)** - Using sce with any AI tool
-
----
-
-## 📚 Examples
-
-Learn by example with complete Spec demonstrations:
-
-### API Development
-- **[REST API Example](examples/add-rest-api/)** - Complete RESTful API with authentication
-  - Requirements, design, and tasks for a task management API
-  - JWT authentication, CRUD operations, error handling
-  - Node.js + Express + PostgreSQL
-
-### UI Development
-- **[User Dashboard Example](examples/add-user-dashboard/)** - React dashboard with data visualization
-  - Component hierarchy, state management, API integration
-  - Responsive design, charts, loading states
-  - React + Recharts
-
-### CLI Development
-- **[Export Command Example](examples/add-export-command/)** - Adding a new CLI command
-  - Command structure, argument parsing, file I/O
-  - Multiple output formats (JSON, Markdown, HTML)
-  - Node.js + Commander.js
-
----
-
-## 🔧 Reference
-
-Detailed technical documentation:
-
-- **[Command Reference](command-reference.md)** - All sce commands with examples
-- **[Environment Management Guide](environment-management-guide.md)** - Multi-environment configuration management
-- **[Multi-Repository Management Guide](multi-repo-management-guide.md)** - Managing multiple Git repositories
-- **[Value Observability Guide](value-observability-guide.md)** - KPI snapshot, baseline, trend, and gate evidence workflow
-- **[Scene Runtime Guide](scene-runtime-guide.md)** - Scene template engine, quality pipeline, ontology, and Moqui ERP integration
-- **[Moqui Template Core Library Playbook](moqui-template-core-library-playbook.md)** - Default-gated intake flow for absorbing Moqui capabilities into sce templates
-- **[331-poc Dual-Track Integration Guide](331-poc-dual-track-integration-guide.md)** - Handoff contract and integration playbook between 331-poc and sce
-- **[331-poc Adaptation Roadmap](331-poc-adaptation-roadmap.md)** - Ongoing sce-side adaptation backlog and rollout phases
-- **[SCE Capability Matrix Roadmap](sce-capability-matrix-roadmap.md)** - Strategy routing, symbol evidence, self-repair, ontology mapping, and multi-agent merge policy roadmap
-- **[SCE Capability Matrix E2E Example](sce-capability-matrix-e2e-example.md)** - End-to-end example from strategy decision to summary-driven merge block/allow
-- **[Handoff Profile Integration Guide](handoff-profile-integration-guide.md)** - External project intake contract for `default|moqui|enterprise` handoff profiles
-- **[SCE Business Mode Map](sce-business-mode-map.md)** - Default takeover model and `user/ops/dev` mode execution governance
-- **[Multi-Agent Coordination Guide](multi-agent-coordination-guide.md)** - Multi-agent parallel coordination for concurrent development
-- **[Troubleshooting](troubleshooting.md)** - Solutions to common problems
-- **[FAQ](faq.md)** - Answers to frequently asked questions
+- [Quick Start](quick-start.md)
+- [Quick Start with AI Tools](quick-start-with-ai-tools.md)
+- [Command Reference](command-reference.md)
+- [FAQ](faq.md)
+- [Troubleshooting](troubleshooting.md)
 
 ---
 
-## 📋 Additional Guides
+## Delivery Workflows
 
-- **[Adoption Guide](adoption-guide.md)** - Adopting sce in existing projects
-- **[Upgrade Guide](upgrade-guide.md)** - Upgrading sce to newer versions
-- **[Release Checklist](release-checklist.md)** - Repeatable pre-release verification flow
-- **[Security Governance Default Baseline](security-governance-default-baseline.md)** - Default safety, approval, and audit controls for SCE delivery
-- **[SCE Business Mode Map](sce-business-mode-map.md)** - User-mode, ops-mode, and dev-mode capability map with default gate policy
-- **[Business Mode Policy Baseline](interactive-customization/business-mode-policy-baseline.json)** - Executable mode preset contract for `user/ops/dev` routing
-- **[Release-Ready Starter Kit](starter-kit/README.md)** - Starter manifest + workflow sample for external project onboarding
-- **[Release Archive](releases/README.md)** - Index of release notes and validation reports
-- **[Release Notes v1.46.2](releases/v1.46.2.md)** - Summary of value observability and onboarding improvements
-- **[Validation Report v1.46.2](releases/v1.46.2-validation.md)** - Test and package verification evidence
-- **[Environment Management Guide](environment-management-guide.md)** - Managing multiple environments
-- **[Multi-Repository Management Guide](multi-repo-management-guide.md)** - Managing multiple Git repositories
-- **[Scene Runtime Guide](scene-runtime-guide.md)** - Scene template engine, quality pipeline, ontology, and Moqui ERP integration
-- **[Multi-Agent Coordination Guide](multi-agent-coordination-guide.md)** - Multi-agent parallel coordination for concurrent development
-- **[Developer Guide](developer-guide.md)** - Contributing to sce development
-- **[Architecture](architecture.md)** - sce system architecture
-
----
-
-## 🌍 Language
-
-- **English** - You are here
-- **[中文 (Chinese)](zh/README.md)** - Chinese documentation
+- [Spec Workflow](spec-workflow.md)
+- [Autonomous Control Guide](autonomous-control-guide.md)
+- [Multi-Agent Coordination Guide](multi-agent-coordination-guide.md)
+- [Spec Collaboration Guide](spec-collaboration-guide.md)
+- [Spec Locking Guide](spec-locking-guide.md)
 
 ---
 
-## 📊 Documentation by Audience
-
-### For Beginners
-1. [Quick Start Guide](quick-start.md) - Start here!
-2. [FAQ](faq.md) - Common questions
-3. [Tool-Specific Guide](tools/) - Pick your AI tool
-4. [Examples](examples/) - Learn by example
+## Scene, Ontology, and Moqui
 
-### For Intermediate Users
-1. [Spec Workflow](spec-workflow.md) - Deep dive into Specs
-2. [Integration Modes](integration-modes.md) - Choose the right mode
-3. [Command Reference](command-reference.md) - Master all commands
-4. [Troubleshooting](troubleshooting.md) - Solve problems
-
-### For Advanced Users
-1. [Developer Guide](developer-guide.md) - Contribute to sce
-2. [Architecture](architecture.md) - Understand internals
-3. [Manual Workflows Guide](manual-workflows-guide.md) - Advanced workflows
+- [Scene Runtime Guide](scene-runtime-guide.md)
+- [Moqui Template Core Library Playbook](moqui-template-core-library-playbook.md)
+- [Moqui Capability Matrix](moqui-capability-matrix.md)
+- [Moqui Standard Rebuild Guide](moqui-standard-rebuild-guide.md)
+- [SCE Capability Matrix Roadmap](sce-capability-matrix-roadmap.md)
 
 ---
 
-## 📊 Documentation by Task
-
-### Setting Up
-- [Quick Start Guide](quick-start.md) - First-time setup
-- [Adoption Guide](adoption-guide.md) - Add to existing project
-- [Tool-Specific Guides](tools/) - Configure your AI tool
-
-### Creating Specs
-- [Spec Workflow](spec-workflow.md) - How to create Specs
-- [Examples](examples/) - See complete examples
-- [Quick Start Guide](quick-start.md) - Your first Spec
-
-### Using with AI Tools
-- [Integration Modes](integration-modes.md) - Choose integration mode
-- [Tool-Specific Guides](tools/) - Tool-specific instructions
-- [Command Reference](command-reference.md) - Export context commands
+## Governance, Quality, and Release
 
-### Troubleshooting
-- [Troubleshooting](troubleshooting.md) - Common issues
-- [FAQ](faq.md) - Quick answers
-- [GitHub Issues](https://github.com/heguangyong/scene-capability-engine/issues) - Report bugs
+- [Document Governance](document-governance.md)
+- [Security Governance Default Baseline](security-governance-default-baseline.md)
+- [Errorbook Registry Guide](errorbook-registry.md)
+- [Release Checklist](release-checklist.md)
+- [Release Archive](releases/README.md)
 
 ---
 
-## 🎯 Quick Links by Feature
-
-### Spec Management
-- [Creating Specs](spec-workflow.md#stage-1-requirements)
-- [Spec Structure](spec-workflow.md#the-spec-creation-workflow)
-- [Example Specs](examples/)
+## Ops and Platform Management
 
-### Environment Management
 - [Environment Management Guide](environment-management-guide.md)
-- [Environment Commands](command-reference.md#environment-management)
-- [Multi-Environment Workflow](environment-management-guide.md#common-workflows)
-
-### Multi-Repository Management
 - [Multi-Repository Management Guide](multi-repo-management-guide.md)
-- [Repository Commands](command-reference.md#multi-repository-management)
-- [Multi-Repo Workflows](multi-repo-management-guide.md#common-workflows)
-
-### Scene Runtime
-- [Scene Runtime Guide](scene-runtime-guide.md)
-- [Moqui Template Core Library Playbook](moqui-template-core-library-playbook.md)
-- [331-poc Dual-Track Integration Guide](331-poc-dual-track-integration-guide.md)
-- [331-poc Adaptation Roadmap](331-poc-adaptation-roadmap.md)
-- [Handoff Profile Integration Guide](handoff-profile-integration-guide.md)
-- [SCE Business Mode Map](sce-business-mode-map.md)
-- [Release-Ready Starter Kit](starter-kit/README.md)
-- [Security Governance Default Baseline](security-governance-default-baseline.md)
-- [Scene Template Engine](command-reference.md#scene-template-engine)
-- [Scene Quality Pipeline](command-reference.md#scene-template-quality-pipeline)
-- [Scene Ontology](command-reference.md#scene-ontology-enhancement)
-- [Moqui ERP Integration](command-reference.md#moqui-erp-integration)
-
-### KPI Observability
-- [Value Metrics Commands](command-reference.md#value-metrics)
-- [Value Observability Guide](value-observability-guide.md)
-- [Spec Workflow](spec-workflow.md)
-- [Quick Start Guide](quick-start.md)
-
-### Context Export
-- [Manual Export Mode](integration-modes.md#mode-2-manual-export)
-- [Export Commands](command-reference.md#context--prompts)
-- [Using Exported Context](tools/)
-
-### Watch Mode
-- [Watch Mode Guide](integration-modes.md#mode-3-watch-mode)
-- [Watch Commands](command-reference.md#watch-mode)
-- [Windsurf Integration](tools/windsurf-guide.md)
-
-### Task Management
-- [Task Commands](command-reference.md#task-management)
-- [Task Workflow](spec-workflow.md#stage-3-tasks)
-- [Team Collaboration](workspace-info.md)
+- [Team Collaboration Guide](team-collaboration-guide.md)
+- [Manual Workflows Guide](manual-workflows-guide.md)
 
 ---
 
-## 💡 Tips for Using This Documentation
-
-**Finding Information:**
-- Use your browser's search (Ctrl+F / Cmd+F) to find specific topics
-- Check the [FAQ](faq.md) first for quick answers
-- Browse [Examples](examples/) to learn by doing
-
-**Learning Path:**
-1. **Day 1:** [Quick Start Guide](quick-start.md) + [Your Tool Guide](tools/)
-2. **Week 1:** [Spec Workflow](spec-workflow.md) + [Examples](examples/)
-3. **Month 1:** [Integration Modes](integration-modes.md) + [Advanced Features](command-reference.md)
+## Integrations
 
-**Getting Help:**
-- **Quick answers:** [FAQ](faq.md)
-- **Problems:** [Troubleshooting](troubleshooting.md)
-- **Community:** [GitHub Discussions](https://github.com/heguangyong/scene-capability-engine/discussions)
-- **Bugs:** [GitHub Issues](https://github.com/heguangyong/scene-capability-engine/issues)
+- [Cursor Guide](tools/cursor-guide.md)
+- [Claude Code Guide](tools/claude-guide.md)
+- [Windsurf Guide](tools/windsurf-guide.md)
+- [VS Code + Copilot Guide](tools/vscode-guide.md)
+- [Generic AI Tools Guide](tools/generic-guide.md)
 
 ---
 
-## 📝 Documentation Status
+## Value and Observability
 
-| Document | Status | Last Updated |
-|----------|--------|--------------|
-| Quick Start | ✅ Complete | 2026-02-14 |
-| Spec Workflow | ✅ Complete | 2026-01-23 |
-| Integration Modes | ✅ Complete | 2026-01-23 |
-| Tool Guides (6) | ✅ Complete | 2026-01-23 |
-| Examples (3) | ✅ Complete | 2026-01-23 |
-| FAQ | ✅ Complete | 2026-02-11 |
-| Troubleshooting | ✅ Complete | 2026-01-23 |
-| Command Reference | ✅ Complete | 2026-02-14 |
-| Value Observability Guide | ✅ Complete | 2026-02-14 |
-| Environment Management | ✅ Complete | 2026-01-31 |
-| Multi-Repository Management | ✅ Complete | 2026-01-31 |
-| Scene Runtime Guide | ✅ Complete | 2026-02-11 |
-| Multi-Agent Coordination | ✅ Complete | 2026-02-12 |
+- [Value Observability Guide](value-observability-guide.md)
+- [Architecture](architecture.md)
+- [Developer Guide](developer-guide.md)
 
 ---
 
-## 🤝 Contributing to Documentation
-
-Found an error? Want to improve the docs?
+## Community
 
-1. **Report issues:** [GitHub Issues](https://github.com/heguangyong/scene-capability-engine/issues)
-2. **Suggest improvements:** [GitHub Discussions](https://github.com/heguangyong/scene-capability-engine/discussions)
-3. **Submit changes:** [Contributing Guide](../CONTRIBUTING.md)
+- [Community](community.md)
+- [GitHub Discussions](https://github.com/heguangyong/scene-capability-engine/discussions)
+- [GitHub Issues](https://github.com/heguangyong/scene-capability-engine/issues)
 
 ---
 
-## 📄 License
+## Language
 
-Documentation is licensed under [MIT License](../LICENSE).
+- [中文文档索引](zh/README.md)
 
 ---
 
-**Happy Spec-ing!** 🚀
-
+**Version**: 3.3.26  
+**Last Updated**: 2026-03-02

package/docs/command-reference.md

@@ -2,8 +2,8 @@
 
 > Quick reference for all `sce` commands
 
-**Version**: 3.3.25
-**Last Updated**: 2026-02-27
+**Version**: 3.4.5
+**Last Updated**: 2026-03-02
 
 ---
 
@@ -71,6 +71,8 @@ sce spec gate run --spec 01-00-feature-name --scene scene.customer-order-invento
 # Maintain domain modeling artifacts explicitly
 sce spec domain init --spec 01-00-feature-name --scene scene.customer-order-inventory --json
 sce spec domain validate --spec 01-00-feature-name --fail-on-error --json
+sce spec domain validate --spec 01-00-feature-name --fail-on-gap --json
+sce spec domain coverage --spec 01-00-feature-name --json
 sce spec domain refresh --spec 01-00-feature-name --scene scene.customer-order-inventory --json
 
 # Find related historical specs before starting a new analysis
@@ -95,6 +97,11 @@ Spec session governance:
   - `.sce/specs/<spec>/custom/problem-domain-map.md`
   - `.sce/specs/<spec>/custom/scene-spec.md`
   - `.sce/specs/<spec>/custom/problem-domain-chain.json`
+- Closed-loop scene research baseline is now part of domain modeling artifacts:
+  - `problem-domain-map.md` must include `Closed-Loop Research Coverage Matrix`
+  - `scene-spec.md` must include `Closed-Loop Research Contract`
+  - `problem-domain-chain.json` must include `research_coverage` contract
+- `sce spec domain coverage` reports coverage dimensions (scene boundary, entity/relation/rules/policy/flow, failure signals, debug evidence plan, verification gate).
 
 ### Timeline Snapshots
 
@@ -298,9 +305,20 @@ sce workspace legacy-migrate --dry-run --json
 sce workspace tracking-audit
 sce workspace tracking-audit --json
 
+# Audit takeover baseline drift (non-mutating)
+sce workspace takeover-audit
+sce workspace takeover-audit --json
+sce workspace takeover-audit --strict
+
+# Apply takeover baseline defaults explicitly
+sce workspace takeover-apply
+sce workspace takeover-apply --json
+
 # Safety guardrail (default):
 # If legacy .kiro directories exist, sce blocks non-migration commands
 # until manual migration is completed.
+# For adopted projects, startup auto-runs takeover baseline alignment
+# before command execution (best effort, non-blocking).
 
 # Legacy commands (still supported)
 sce workspace sync
@@ -396,6 +414,10 @@ sce errorbook record \
   --status verified \
   --json
 
+# Inspect temporary trial-and-error incident loop
+sce errorbook incident list --state open --json
+sce errorbook incident show <incident-id> --json
+
 # List/show/find entries
 sce errorbook list --status promoted --min-quality 75 --json
 sce errorbook show <entry-id> --json
@@ -448,6 +470,10 @@ SCE_REGISTRY_HEALTH_STRICT=1 node scripts/errorbook-registry-health-gate.js --js
 ```
 
 Curated quality policy (`宁缺毋滥，优胜略汰`) defaults:
+- All issues enter an incident loop by default:
+  - each `errorbook record` writes one staging attempt under `.sce/errorbook/staging/incidents/`
+  - staging incidents preserve full trial-and-error history to avoid repeated mistakes
+  - when record status reaches `verified|promoted|deprecated`, the incident auto-resolves and snapshot is archived under `.sce/errorbook/staging/resolved/`
 - `record` requires: `title`, `symptom`, `root_cause`, and at least one `fix_action`.
 - Fingerprint dedup is automatic; repeated records merge evidence and increment occurrence count.
 - Repeated-failure hard rule: from attempt `#3` of the same fingerprint (two failed rounds already happened), record must include debug evidence.
@@ -482,8 +508,11 @@ Curated quality policy (`宁缺毋滥，优胜略汰`) defaults:
   - branch is ahead/behind upstream
   - upstream is not a GitHub/GitLab remote (when such remotes exist)
 - If project has no GitHub/GitLab remote, gate passes by default (can hard-enforce with `--no-allow-no-remote` or `SCE_GIT_MANAGEMENT_ALLOW_NO_REMOTE=0`).
-- In CI/tag detached-HEAD context (`CI=1` or `GITHUB_ACTIONS=1`), branch/upstream sync checks are relaxed by default.
-  Use `SCE_GIT_MANAGEMENT_STRICT_CI=1` (or `--strict-ci`) to enforce full local-level branch checks in CI.
+- In CI/tag detached-HEAD context (`CI=1` or `GITHUB_ACTIONS=1`), branch/upstream/worktree checks are relaxed by default (advisory warnings only).
+  Use `SCE_GIT_MANAGEMENT_STRICT_CI=1` (or `--strict-ci`) to enforce full local-level branch/worktree checks in CI.
+- When CI generates temporary release artifacts before `npm publish`, you can allow untracked-only worktree drift while keeping tracked-change protection:
+  - `SCE_GIT_MANAGEMENT_ALLOW_UNTRACKED=1` (or `--allow-untracked`)
+  - tracked file changes still fail the gate.
 
 ### Studio Workflow
 
@@ -535,6 +564,22 @@ Stage guardrails are enforced by default:
 - `release` requires `verify`
 - `verify` / `release` reports and failure auto-records inherit `spec_id + domain-chain` context for better root-cause traceability
 
+Problem evaluation mode (default required):
+- Studio now runs problem evaluation on every stage: `plan`, `generate`, `apply`, `verify`, `release`.
+- Default policy file: `.sce/config/problem-eval-policy.json` (also provisioned by template/adopt/takeover baseline).
+- Default hard-block stages: `apply`, `release`.
+- Evaluation combines risk/evidence/readiness and emits adaptive strategy:
+  - `direct-execution`
+  - `controlled-execution`
+  - `evidence-first`
+  - `explore-and-validate`
+  - `debug-first`
+- Evaluation report artifact is written to `.sce/reports/problem-eval/<job-id>-<stage>.json`.
+- Stage metadata and event payload now include `problem_evaluation` summary plus artifact pointer.
+- Environment overrides:
+  - `SCE_PROBLEM_EVAL_MODE=off|advisory|required`
+  - `SCE_PROBLEM_EVAL_DISABLED=1`
+
 Studio gate execution defaults:
 - `verify --profile standard` runs executable gates (unit test script when available, interactive governance report when present, scene package publish-batch dry-run when handoff manifest exists)
 - `release --profile standard` runs executable release preflight (npm pack dry-run, git managed gate, errorbook release gate, weekly ops gate when summary exists, release asset integrity when evidence directory exists, scene package publish-batch ontology gate, handoff capability matrix gate)

package/docs/spec-workflow.md

@@ -4,8 +4,8 @@
 
 ---
 
-**Version**: 1.42.0  
-**Last Updated**: 2026-02-11  
+**Version**: 3.3.26  
+**Last Updated**: 2026-03-02  
 **Audience**: Intermediate  
 **Estimated Time**: 10 minutes
 
@@ -86,6 +86,37 @@ graph LR
 
 ---
 
+## Stage 0: Scene-Closed-Loop Research (Mandatory)
+
+Before implementation, SCE enforces a closed-loop scene research baseline under `.sce/specs/<spec>/custom/`:
+
+- `problem-domain-map.md`
+- `scene-spec.md`
+- `problem-domain-chain.json`
+
+These artifacts must cover:
+
+1. Scene boundary
+2. Entity / relation
+3. Business rule
+4. Decision policy
+5. Execution flow
+6. Failure signals
+7. Debug evidence plan
+8. Verification gates
+
+Commands:
+
+```bash
+sce spec domain init --spec <spec-id> --scene <scene-id>
+sce spec domain coverage --spec <spec-id> --json
+sce spec domain validate --spec <spec-id> --fail-on-gap --json
+```
+
+This is the default way to avoid wrong-direction implementation and to force evidence-based correction loops.
+
+---
+
 ## Stage 1: Requirements
 
 **Purpose:** Define WHAT you're building and WHY
@@ -514,6 +545,6 @@ sce spec bootstrap --name 02-00-your-feature --non-interactive
 
 ---
 
-**Version**: 1.42.0  
-**Last Updated**: 2026-02-11
+**Version**: 3.3.26  
+**Last Updated**: 2026-03-02