scene-capability-engine 3.3.4 → 3.3.10

package/README.md

@@ -94,7 +94,7 @@ Install sce and use it to manage this project with Spec-driven development.
 **Your AI will:**
 1. Install sce globally (`npm install -g scene-capability-engine`)
 2. Adopt it in your project (`sce adopt`)
-3. Read the methodology guide (`.kiro/README.md`)
+3. Read the methodology guide (`.sce/README.md`)
 4. Start working according to Spec-driven approach
 
 **That's it!** Your AI handles everything. No manual steps needed.
@@ -126,7 +126,7 @@ cd your-project
 sce adopt
 ```
 
-This creates a `.kiro/` directory with:
+This creates a `.sce/` directory with:
 - `README.md` - Project development guide for AI
 - `specs/` - Where your Specs live
 - `steering/` - Development rules (optional)
@@ -136,7 +136,7 @@ This creates a `.kiro/` directory with:
 **In your AI tool (Cursor, Claude, Windsurf, etc.), say:**
 
 ```
-Please read .kiro/README.md to understand how this project works.
+Please read .sce/README.md to understand how this project works.
 ```
 
 **Your AI will learn:**
@@ -393,7 +393,7 @@ Structure your work with Requirements → Design → Tasks workflow
 - **Retry Mechanism**: Configurable automatic retry for failed Specs
 - **Real-Time Monitoring**: Track per-Spec status and overall orchestration progress
 - **Graceful Termination**: Stop all sub-agents cleanly (SIGTERM → SIGKILL)
-- **Configurable**: Codex command, args, parallelism, timeout, retries via `.kiro/config/orchestrator.json`
+- **Configurable**: Codex command, args, parallelism, timeout, retries via `.sce/config/orchestrator.json`
 
 **Quick Start**:
 ```bash
@@ -409,7 +409,7 @@ sce orchestrate stop
 
 Tip: `sce spec bootstrap|pipeline run|gate run --specs ...` now defaults to this orchestrate mode automatically.
 
-**Recommended Codex-Orchestrator config (`.kiro/config/orchestrator.json`)**:
+**Recommended Codex-Orchestrator config (`.sce/config/orchestrator.json`)**:
 ```json
 {
   "agentBackend": "codex",
@@ -548,7 +548,7 @@ sce auto close-loop continue       # Shorthand: continue latest interrupted clos
 sce auto continue                  # Shortcut command: continue latest interrupted close-loop session
 sce auto close-loop "<goal>" --dry-run --json  # Preview decomposition plan only
 sce auto close-loop-program "<goal>" --program-govern-until-stable --program-govern-use-action 1 --json # Program-level recovery + governance with remediation action execution
-sce auto close-loop-controller .kiro/auto/program-queue.lines --wait-on-empty --dequeue-limit 2 --json # Queue-driven autonomous controller for broad-goal backlogs
+sce auto close-loop-controller .sce/auto/program-queue.lines --wait-on-empty --dequeue-limit 2 --json # Queue-driven autonomous controller for broad-goal backlogs
 sce auto close-loop-controller --controller-resume latest --json # Resume autonomous controller from latest persisted checkpoint
 sce auto controller-session list --limit 50 --json # Inspect persisted close-loop-controller summary sessions
 sce auto controller-session prune --keep 20 --older-than-days 14 --dry-run --json # Prune old controller summaries by retention policy

package/README.zh.md

@@ -92,7 +92,7 @@ sce value metrics snapshot --input ./kpi-input.json --json
 **你的 AI 会：**
 1. 全局安装 sce（`npm install -g scene-capability-engine`）
 2. 在项目中采用它（`sce adopt`）
-3. 阅读方法论指南（`.kiro/README.md`）
+3. 阅读方法论指南（`.sce/README.md`）
 4. 按照 Spec 驱动方式开始工作
 
 **就这样！** 你的 AI 处理一切。不需要手动步骤。
@@ -124,7 +124,7 @@ cd your-project
 sce adopt
 ```
 
-这会创建一个 `.kiro/` 目录，包含：
+这会创建一个 `.sce/` 目录，包含：
 - `README.md` - 给 AI 的项目开发指南
 - `specs/` - Spec 存放位置
 - `steering/` - 开发规则（可选）
@@ -134,7 +134,7 @@ sce adopt
 **在你的 AI 工具中（Cursor、Claude、Windsurf 等），说：**
 
 ```
-请阅读 .kiro/README.md 了解项目的开发方法。
+请阅读 .sce/README.md 了解项目的开发方法。
 ```
 
 **你的 AI 会学到：**
@@ -348,7 +348,7 @@ sequenceDiagram
 - **重试机制**: 可配置的失败自动重试
 - **实时监控**: 跟踪每个 Spec 状态和整体编排进度
 - **优雅终止**: 干净停止所有子 Agent（SIGTERM → SIGKILL）
-- **可配置**: 通过 `.kiro/config/orchestrator.json` 配置 Codex 命令、参数、并行度、超时、重试次数
+- **可配置**: 通过 `.sce/config/orchestrator.json` 配置 Codex 命令、参数、并行度、超时、重试次数
 
 **快速开始**:
 ```bash
@@ -362,7 +362,7 @@ sce orchestrate status
 sce orchestrate stop
 ```
 
-**推荐 Codex 编排配置（`.kiro/config/orchestrator.json`）**:
+**推荐 Codex 编排配置（`.sce/config/orchestrator.json`）**:
 ```json
 {
   "agentBackend": "codex",
@@ -462,7 +462,7 @@ sce auto close-loop 继续           # 简写：续跑最近一个未完成 clos
 sce auto continue                  # 快捷命令：续跑最近一个未完成 close-loop 会话
 sce auto close-loop "<目标>" --dry-run --json  # 仅预览拆分与依赖计划
 sce auto close-loop-program "<目标>" --program-govern-until-stable --program-govern-use-action 1 --json # 程序级自动恢复 + 治理循环（含 remediation action 执行）直到稳定
-sce auto close-loop-controller .kiro/auto/program-queue.lines --wait-on-empty --dequeue-limit 2 --json # 队列驱动自治控制器，持续处理广义目标积压
+sce auto close-loop-controller .sce/auto/program-queue.lines --wait-on-empty --dequeue-limit 2 --json # 队列驱动自治控制器，持续处理广义目标积压
 sce auto close-loop-controller --controller-resume latest --json # 从最近一次 controller 检查点恢复自治推进
 sce auto controller-session list --limit 50 --json # 查看持久化 close-loop-controller 摘要会话
 sce auto controller-session prune --keep 20 --older-than-days 14 --dry-run --json # 按保留策略清理旧 controller 摘要

package/bin/scene-capability-engine.js

@@ -14,11 +14,17 @@ const rollbackCommand = require('../lib/commands/rollback');
 const watchCommands = require('../lib/commands/watch');
 const workflowsCommand = require('../lib/commands/workflows');
 const registerCollabCommands = require('../lib/commands/collab');
+const { registerSessionCommands } = require('../lib/commands/session');
+const { registerSteeringCommands } = require('../lib/commands/steering');
 const { registerSpecBootstrapCommand } = require('../lib/commands/spec-bootstrap');
 const { registerSpecPipelineCommand } = require('../lib/commands/spec-pipeline');
 const { registerSpecGateCommand } = require('../lib/commands/spec-gate');
 const { registerValueCommands } = require('../lib/commands/value');
 const VersionChecker = require('../lib/version/version-checker');
+const {
+  findLegacyKiroDirectories,
+  migrateLegacyKiroDirectories,
+} = require('../lib/workspace/legacy-kiro-migrator');
 
 const i18n = getI18n();
 const t = (key, params) => i18n.t(key, params);
@@ -111,6 +117,40 @@ function findCommandIndex(args) {
   return -1;
 }
 
+/**
+ * Allowlist commands that can run before legacy workspace migration.
+ * These commands help users discover and execute the migration itself.
+ *
+ * @param {string[]} args
+ * @returns {boolean}
+ */
+function isLegacyMigrationAllowlistedCommand(args) {
+  if (!Array.isArray(args) || args.length === 0) {
+    return false;
+  }
+
+  if (args.includes('-h') || args.includes('--help') || args.includes('-v') || args.includes('--version')) {
+    return true;
+  }
+
+  const commandIndex = findCommandIndex(args);
+  if (commandIndex < 0) {
+    return false;
+  }
+
+  const command = args[commandIndex];
+  if (command === 'help') {
+    return true;
+  }
+
+  if (command === 'workspace') {
+    const subcommand = args[commandIndex + 1];
+    return subcommand === 'legacy-scan' || subcommand === 'legacy-migrate';
+  }
+
+  return false;
+}
+
 // 版本和基本信息
 program
   .name(t('cli.name'))
@@ -145,8 +185,8 @@ program
       projectName = answers.projectName;
     }
 
-    // 检查是否已存在 .kiro 目录
-    const kiroDir = path.join(process.cwd(), '.kiro');
+    // 检查是否已存在 .sce 目录
+    const kiroDir = path.join(process.cwd(), '.sce');
     if (fs.existsSync(kiroDir) && !options.force) {
       console.log(chalk.yellow(t('cli.commands.init.alreadyExists')));
       const { overwrite } = await inquirer.prompt([
@@ -195,7 +235,7 @@ program
     console.log(chalk.red('🔥') + ` Starting ${stage} stage Ultrawork enhancement...`);
     
     // 检查 Python 和工具是否可用
-    const toolPath = path.join(process.cwd(), '.kiro/tools/ultrawork_enhancer.py');
+    const toolPath = path.join(process.cwd(), '.sce/tools/ultrawork_enhancer.py');
     if (!fs.existsSync(toolPath)) {
       console.error(chalk.red('❌ Ultrawork tool not found. Please run: sce init'));
       process.exit(1);
@@ -234,7 +274,7 @@ program
   .option('-t, --template <template-id>', 'Use a template from the library')
   .option('-f, --force', 'Overwrite existing spec directory')
   .action(async (specName, options) => {
-    const specPath = path.join(process.cwd(), '.kiro/specs', specName);
+    const specPath = path.join(process.cwd(), '.sce/specs', specName);
     
     try {
       // Check if using template
@@ -582,6 +622,70 @@ workspaceCmd
     await workspaceCommand.infoWorkspace(name);
   });
 
+workspaceCmd
+  .command('legacy-scan')
+  .description('Scan workspace tree for legacy .kiro directories')
+  .option('--max-depth <n>', 'Maximum recursive scan depth', parseInt)
+  .option('--json', 'Output in JSON format')
+  .action(async (options) => {
+    const workspaceRoot = process.cwd();
+    const candidates = await findLegacyKiroDirectories(workspaceRoot, {
+      maxDepth: Number.isInteger(options.maxDepth) ? options.maxDepth : undefined,
+    });
+
+    if (options.json) {
+      console.log(JSON.stringify({
+        root: workspaceRoot,
+        legacy_directories: candidates,
+        count: candidates.length,
+      }, null, 2));
+      return;
+    }
+
+    if (candidates.length === 0) {
+      console.log(chalk.green('✓ No legacy .kiro directories found.'));
+      return;
+    }
+    console.log(chalk.yellow(`Found ${candidates.length} legacy .kiro director${candidates.length > 1 ? 'ies' : 'y'}:`));
+    for (const dir of candidates) {
+      console.log(chalk.gray(`  - ${dir}`));
+    }
+  });
+
+workspaceCmd
+  .command('legacy-migrate')
+  .description('Migrate legacy .kiro directories to .sce')
+  .option('--dry-run', 'Preview migration actions without writing changes')
+  .option('--max-depth <n>', 'Maximum recursive scan depth', parseInt)
+  .option('--json', 'Output in JSON format')
+  .action(async (options) => {
+    const workspaceRoot = process.cwd();
+    const report = await migrateLegacyKiroDirectories(workspaceRoot, {
+      dryRun: options.dryRun === true,
+      maxDepth: Number.isInteger(options.maxDepth) ? options.maxDepth : undefined,
+    });
+
+    if (options.json) {
+      console.log(JSON.stringify(report, null, 2));
+      return;
+    }
+
+    if (report.scanned === 0) {
+      console.log(chalk.green('✓ No legacy .kiro directories found.'));
+      return;
+    }
+
+    const modeLabel = report.dryRun ? ' (dry-run)' : '';
+    console.log(chalk.green(`Legacy migration completed${modeLabel}.`));
+    console.log(chalk.gray(`Scanned: ${report.scanned}`));
+    console.log(chalk.gray(`Migrated: ${report.migrated}`));
+    console.log(chalk.gray(`Renamed: ${report.renamed}`));
+    console.log(chalk.gray(`Merged: ${report.merged}`));
+    console.log(chalk.gray(`Moved files: ${report.moved_files}`));
+    console.log(chalk.gray(`Deduped files: ${report.deduped_files}`));
+    console.log(chalk.gray(`Conflict files: ${report.conflict_files}`));
+  });
+
 // Environment configuration management commands
 const envCommand = require('../lib/commands/env');
 
@@ -639,6 +743,10 @@ repoCmd
 // Spec-level collaboration commands
 registerCollabCommands(program);
 
+// Universal steering and runtime session commands
+registerSteeringCommands(program);
+registerSessionCommands(program);
+
 // Autonomous control commands
 const { registerAutoCommands } = require('../lib/commands/auto');
 registerAutoCommands(program);
@@ -753,8 +861,8 @@ templatesCmd
 
 // 更新项目配置的辅助函数
 async function updateProjectConfig(projectName) {
-  const envPath = path.join(process.cwd(), '.kiro/steering/ENVIRONMENT.md');
-  const contextPath = path.join(process.cwd(), '.kiro/steering/CURRENT_CONTEXT.md');
+  const envPath = path.join(process.cwd(), '.sce/steering/ENVIRONMENT.md');
+  const contextPath = path.join(process.cwd(), '.sce/steering/CURRENT_CONTEXT.md');
 
   // 更新 ENVIRONMENT.md
   if (fs.existsSync(envPath)) {
@@ -777,11 +885,25 @@ async function updateProjectConfig(projectName) {
   const normalizedArgs = normalizeSpecCommandArgs(process.argv.slice(2));
   process.argv = [process.argv[0], process.argv[1], ...normalizedArgs];
   
-  // Check for bypass flags
+  // Parse startup flags and guardrails
   const args = process.argv.slice(2);
+  const isLegacyAllowlistedCommand = isLegacyMigrationAllowlistedCommand(args);
   const skipCheck = args.includes('--skip-steering-check') || 
                     process.env.KSE_SKIP_STEERING_CHECK === '1';
   const forceCheck = args.includes('--force-steering-check');
+
+  if (!isLegacyAllowlistedCommand) {
+    const legacyDirs = await findLegacyKiroDirectories(process.cwd(), { maxDepth: 6 });
+    if (legacyDirs.length > 0) {
+      console.error(chalk.red(
+        `Legacy workspace migration required: found ${legacyDirs.length} .kiro director${legacyDirs.length > 1 ? 'ies' : 'y'}.`
+      ));
+      console.error(chalk.yellow('SCE blocks all non-migration commands until migration is completed.'));
+      console.error(chalk.gray('Review first:  sce workspace legacy-migrate --dry-run'));
+      console.error(chalk.gray('Apply manually: sce workspace legacy-migrate'));
+      process.exit(2);
+    }
+  }
   
   // Run compliance check
   await runSteeringComplianceCheck({

package/docs/331-poc-adaptation-roadmap.md

@@ -15,7 +15,7 @@
    - 一条命令串行执行 `plan -> queue -> close-loop-batch -> observability`。
    - 支持 `--dry-run` 与失败自动中断。
 7. 新增 handoff 结果归档：
-   - 默认输出 `.kiro/reports/handoff-runs/<session>.json`。
+   - 默认输出 `.sce/reports/handoff-runs/<session>.json`。
    - 汇总每个 spec 的执行状态与阻塞项。
 8. 新增 handoff 门禁策略：
    - `--min-spec-success-rate`
@@ -33,7 +33,7 @@
    - `sce auto handoff run --continue-from <session|latest|file>`。
    - 支持 `--continue-strategy auto|pending|failed-only`。
 13. 新增 release evidence 自动归并：
-   - `handoff run` 结束后自动将批次结果合并到 `.kiro/reports/release-evidence/handoff-runs.json`。
+   - `handoff run` 结束后自动将批次结果合并到 `.sce/reports/release-evidence/handoff-runs.json`。
    - 按 `session_id` 去重更新，失败时写 warning 不阻塞主流程。
 14. 新增回归可视化报表增强：
    - `handoff regression` 输出增加 `risk_layers` 风险分层视图（low/medium/high/unknown）。
@@ -142,7 +142,7 @@
    - `release.yml` 的 Evaluate drift 步骤改为直接调用脚本，消除大段内联 heredoc，降低语法错误与维护成本。
    - 新增 `tests/unit/scripts/release-drift-evaluate.test.js` 覆盖 advisory/enforce/missing history/gate report 写回四类场景。
 2. handoff 质量指标接入 governance 默认评估闭环：
-   - `sce auto governance stats` 默认聚合 `.kiro/reports/release-evidence/handoff-runs.json`，输出 `health.handoff_quality` 快照。
+   - `sce auto governance stats` 默认聚合 `.sce/reports/release-evidence/handoff-runs.json`，输出 `health.handoff_quality` 快照。
    - `risk/concerns/recommendations` 自动纳入 handoff 最新状态、gate、ontology、capability、preflight 阻断等信号。
    - `sce auto governance close-loop` 的阻断判断纳入 handoff 严重质量信号，统一通过 `stop_reason=release-gate-blocked` 回传处置语义。
    - `sce auto governance maintain` 在 handoff 质量阻断时新增 `release-gate-handoff-remediate` 建议动作。

package/docs/331-poc-dual-track-integration-guide.md

@@ -7,7 +7,7 @@
 每一轮从 `E:\workspace\331-poc` 接收以下产物：
 
 1. 完成态 Spec（requirements/design/tasks + `custom/scene.yaml` + `custom/scene-package.json`）。
-2. 模板导出目录：`.kiro/templates/exports/<template-name>/`。
+2. 模板导出目录：`.sce/templates/exports/<template-name>/`。
 3. 交接包：`docs/handoffs/handoff-manifest.json` + 证据文档。
 
 若输入不满足以上三类，sce 侧不进入接入批次。
@@ -56,9 +56,9 @@ npx sce doctor --docs
 
 ```bash
 npx sce scene package-validate --spec <spec-name> --spec-package custom/scene-package.json --strict --json
-npx sce scene ontology validate --package .kiro/specs/<spec-name>/custom --json
-npx sce scene ontology impact --package .kiro/specs/<spec-name>/custom --ref <ref> --max-depth 2 --json
-npx sce scene ontology path --package .kiro/specs/<spec-name>/custom --from <from-ref> --to <to-ref> --json
+npx sce scene ontology validate --package .sce/specs/<spec-name>/custom --json
+npx sce scene ontology impact --package .sce/specs/<spec-name>/custom --ref <ref> --max-depth 2 --json
+npx sce scene ontology path --package .sce/specs/<spec-name>/custom --from <from-ref> --to <to-ref> --json
 ```
 
 ## 2.3 批次 3：模板层接入
@@ -66,10 +66,10 @@ npx sce scene ontology path --package .kiro/specs/<spec-name>/custom --from <fro
 对于 scene package 模板链路（如果本轮包含 scene-package 模板）：
 
 ```bash
-npx sce scene package-publish --spec <spec-name> --out-dir .kiro/templates/scene-packages --json --force
-npx sce scene package-registry --template-dir .kiro/templates/scene-packages --strict --json
-npx sce scene package-gate-template --out .kiro/templates/scene-package-gate-policy.json --profile three-layer --force --json
-npx sce scene package-gate --registry .kiro/templates/scene-packages/registry.json --policy .kiro/templates/scene-package-gate-policy.json --strict --json
+npx sce scene package-publish --spec <spec-name> --out-dir .sce/templates/scene-packages --json --force
+npx sce scene package-registry --template-dir .sce/templates/scene-packages --strict --json
+npx sce scene package-gate-template --out .sce/templates/scene-package-gate-policy.json --profile three-layer --force --json
+npx sce scene package-gate --registry .sce/templates/scene-packages/registry.json --policy .sce/templates/scene-package-gate-policy.json --strict --json
 ```
 
 说明：Spec 模板（`templates create-from-spec` 导出）与 scene package 模板是两条链路，可并行维护，但推荐在同一交接批次一并校验。

package/docs/331-poc-weekly-delivery-checklist.md

@@ -11,7 +11,7 @@ Use this checklist before each integration batch.
   - `custom/scene.yaml`
   - `custom/scene-package.json`
 - Exported template folder:
-  - `.kiro/templates/exports/<template-name>/`
+  - `.sce/templates/exports/<template-name>/`
 - Handoff package:
   - `docs/handoffs/handoff-manifest.json`
   - ontology validation evidence in the same batch window
@@ -42,21 +42,21 @@ npx sce auto handoff run --manifest ../331-poc/docs/handoffs/handoff-manifest.js
 npx sce auto handoff template-diff --manifest ../331-poc/docs/handoffs/handoff-manifest.json --json
 npx sce auto handoff regression --session-id latest --json
 npx sce auto handoff capability-matrix --manifest ../331-poc/docs/handoffs/handoff-manifest.json --fail-on-gap --json
-npx sce scene moqui-baseline --compare-with .kiro/reports/release-evidence/moqui-template-baseline-prev.json --fail-on-portfolio-fail --json
+npx sce scene moqui-baseline --compare-with .sce/reports/release-evidence/moqui-template-baseline-prev.json --fail-on-portfolio-fail --json
 node scripts/moqui-lexicon-audit.js --manifest ../331-poc/docs/handoffs/handoff-manifest.json --fail-on-gap --json
 node scripts/moqui-release-summary.js --fail-on-gate-fail --json
 node scripts/release-ops-weekly-summary.js --json
 node scripts/release-weekly-ops-gate.js
-node scripts/release-risk-remediation-bundle.js --gate-report .kiro/reports/release-evidence/release-gate.json --json
+node scripts/release-risk-remediation-bundle.js --gate-report .sce/reports/release-evidence/release-gate.json --json
 node scripts/release-asset-integrity-check.js
 ```
 
 ## Scene Package Gate Commands
 
 ```bash
-npx sce scene package-registry --template-dir .kiro/templates/scene-packages --strict --json
-npx sce scene package-gate-template --out .kiro/templates/scene-package-gate-policy.json --profile three-layer --force --json
-npx sce scene package-gate --registry .kiro/templates/scene-packages/registry.json --policy .kiro/templates/scene-package-gate-policy.json --strict --json
+npx sce scene package-registry --template-dir .sce/templates/scene-packages --strict --json
+npx sce scene package-gate-template --out .sce/templates/scene-package-gate-policy.json --profile three-layer --force --json
+npx sce scene package-gate --registry .sce/templates/scene-packages/registry.json --policy .sce/templates/scene-package-gate-policy.json --strict --json
 ```
 
 ## Batch Exit Criteria

package/docs/README.md

@@ -94,7 +94,10 @@ Detailed technical documentation:
 - **[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
@@ -107,6 +110,8 @@ Detailed technical documentation:
 - **[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
@@ -195,6 +200,7 @@ Detailed technical documentation:
 - [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)

package/docs/adopt-migration-guide.md

@@ -29,16 +29,16 @@ $ sce adopt
 📦 Analyzing project structure...
 
 ⚠️  Conflicts detected:
-    - .kiro/steering/CORE_PRINCIPLES.md
-    - .kiro/steering/ENVIRONMENT.md
+    - .sce/steering/CORE_PRINCIPLES.md
+    - .sce/steering/ENVIRONMENT.md
 
 ? How to handle conflicts?
   > Skip all
     Overwrite all
     Review each
 
-? Overwrite .kiro/steering/CORE_PRINCIPLES.md? (y/N)
-? Overwrite .kiro/steering/ENVIRONMENT.md? (y/N)
+? Overwrite .sce/steering/CORE_PRINCIPLES.md? (y/N)
+? Overwrite .sce/steering/ENVIRONMENT.md? (y/N)
 ...
 ```
 
@@ -71,9 +71,9 @@ Adoption Plan:
 📦 Creating backup... ✅ backup-20260128-143022
 ✓ Validating backup... ✅ 5 files verified
 📝 Updating files...
-  ✅ .kiro/steering/CORE_PRINCIPLES.md
-  ✅ .kiro/steering/ENVIRONMENT.md
-  ⏭️  .kiro/specs/ (preserved)
+  ✅ .sce/steering/CORE_PRINCIPLES.md
+  ✅ .sce/steering/ENVIRONMENT.md
+  ⏭️  .sce/specs/ (preserved)
 ✅ Adoption completed successfully!
 
 📊 Summary:
@@ -277,7 +277,7 @@ $ sce adopt --interactive
 📦 Analyzing project structure...
 
 ⚠️  Conflicts detected:
-    - .kiro/steering/CORE_PRINCIPLES.md
+    - .sce/steering/CORE_PRINCIPLES.md
 
 ? How to handle conflicts?
   > Skip all
@@ -293,7 +293,7 @@ $ sce adopt --interactive
 
 ### Q: Will my existing projects still work?
 
-**A**: Yes! The new system is fully backward compatible. Your existing `.kiro/` directories will be detected and handled correctly.
+**A**: Yes! The new system is fully backward compatible. Your existing `.sce/` directories will be detected and handled correctly.
 
 ---
 
@@ -357,8 +357,8 @@ This will:
 ### Q: What happens to my specs and custom files?
 
 **A**: They are **always preserved**. The smart system never overwrites:
-- `.kiro/specs/` directory
-- `.kiro/steering/CURRENT_CONTEXT.md`
+- `.sce/specs/` directory
+- `.sce/steering/CURRENT_CONTEXT.md`
 - Any custom files you created
 
 ---
@@ -528,7 +528,7 @@ sce adopt
 Don't delete automatic backups immediately:
 ```bash
 # Keep for at least a week
-ls .kiro/backups/
+ls .sce/backups/
 ```
 
 ### 4. Verify Results
@@ -544,7 +544,7 @@ npm test  # If you have tests
 
 If you customize files, document it:
 ```markdown
-# In .kiro/steering/CUSTOM_RULES.md
+# In .sce/steering/CUSTOM_RULES.md
 ## Customizations
 - Modified CORE_PRINCIPLES.md on 2026-01-28
 - Reason: Project-specific requirements