scene-capability-engine 3.3.5 → 3.3.10

package/docs/adoption-guide.md

@@ -65,10 +65,10 @@ Adoption Plan:
 📦 Creating backup... ✅ backup-20260128-143022
 ✓ Validating backup... ✅ 5 files verified
 📝 Updating files...
-  ✅ .kiro/steering/CORE_PRINCIPLES.md
-  ✅ .kiro/steering/ENVIRONMENT.md
-  ✅ .kiro/tools/ultrawork_enhancer.py
-  ⏭️  .kiro/specs/ (preserved)
+  ✅ .sce/steering/CORE_PRINCIPLES.md
+  ✅ .sce/steering/ENVIRONMENT.md
+  ✅ .sce/tools/ultrawork_enhancer.py
+  ⏭️  .sce/specs/ (preserved)
 ✅ Adoption completed successfully!
 
 📊 Summary:
@@ -94,7 +94,7 @@ sce adopt --dry-run
 ### Automatic Detection
 
 The system automatically detects your project state:
-- Checks for existing `.kiro/` directory
+- Checks for existing `.sce/` directory
 - Reads version information
 - Identifies user content (specs, custom files)
 - Detects potential conflicts
@@ -105,11 +105,11 @@ Based on detection, it chooses the optimal mode:
 
 | Project State | Selected Mode | What Happens |
 |--------------|---------------|--------------|
-| No `.kiro/` | **Fresh** | Creates complete structure |
-| `.kiro/` + same version | **Skip** | Already up-to-date |
-| `.kiro/` + older version | **Smart Update** | Updates templates only |
-| `.kiro/` + newer version | **Warning** | Version mismatch alert |
-| `.kiro/` + no version | **Smart Adopt** | Full adoption with backup |
+| No `.sce/` | **Fresh** | Creates complete structure |
+| `.sce/` + same version | **Skip** | Already up-to-date |
+| `.sce/` + older version | **Smart Update** | Updates templates only |
+| `.sce/` + newer version | **Warning** | Version mismatch alert |
+| `.sce/` + no version | **Smart Adopt** | Full adoption with backup |
 
 ### Automatic Conflict Resolution
 
@@ -136,10 +136,10 @@ Before any modifications:
 
 ### 1. Fresh Adoption
 
-**When**: No `.kiro/` directory exists
+**When**: No `.sce/` directory exists
 
 **Actions**:
-- Creates complete `.kiro/` structure
+- Creates complete `.sce/` structure
 - Copies all template files
 - Creates `version.json`
 - No conflicts, no backup needed
@@ -150,7 +150,7 @@ $ sce adopt
 
 Mode: Fresh
 Actions:
-  - Create .kiro/ directory structure
+  - Create .sce/ directory structure
   - Copy template files
   - Create version.json
 
@@ -180,7 +180,7 @@ No changes needed.
 
 ### 3. Smart Update
 
-**When**: Existing `.kiro/` with older version
+**When**: Existing `.sce/` with older version
 
 **Actions**:
 - Backs up files that will change
@@ -202,10 +202,10 @@ Preserved: 3 specs, CURRENT_CONTEXT.md
 
 ### 4. Smart Adopt
 
-**When**: `.kiro/` exists but no version info
+**When**: `.sce/` exists but no version info
 
 **Actions**:
-- Backs up entire `.kiro/` directory
+- Backs up entire `.sce/` directory
 - Adopts with full structure
 - Preserves user content
 - Creates version.json
@@ -392,13 +392,13 @@ Problem: Unable to create backup of existing files
 
 Possible causes:
   - Insufficient disk space
-  - Permission denied for .kiro/backups/
+  - Permission denied for .sce/backups/
   - File system error
 ```
 
 **Solutions**:
 1. Free up disk space (need ~50MB)
-2. Check file permissions: `ls -la .kiro/`
+2. Check file permissions: `ls -la .sce/`
 3. Try running with elevated permissions (if appropriate)
 
 ---
@@ -409,18 +409,18 @@ Possible causes:
 ```
 ❌ Error: Permission Denied
 
-Problem: Cannot write to .kiro/ directory
+Problem: Cannot write to .sce/ directory
 ```
 
 **Solutions**:
 ```bash
 # Check permissions
-ls -la .kiro/
+ls -la .sce/
 
 # Fix permissions (Unix/Mac)
-chmod -R u+w .kiro/
+chmod -R u+w .sce/
 
-# Windows: Right-click .kiro/ → Properties → Security → Edit
+# Windows: Right-click .sce/ → Properties → Security → Edit
 ```
 
 ---
@@ -535,8 +535,8 @@ sce version-info
 
 Don't delete automatic backups immediately:
 ```bash
-# Backups are in .kiro/backups/
-ls .kiro/backups/
+# Backups are in .sce/backups/
+ls .sce/backups/
 ```
 
 ### 5. Use Verbose for Debugging
@@ -554,7 +554,7 @@ After adoption, your project will have:
 
 ```
 your-project/
-├── .kiro/                          # sce core directory
+├── .sce/                          # sce core directory
 │   ├── version.json                # Version tracking
 │   ├── specs/                      # Spec storage
 │   ├── steering/                   # AI behavior rules
@@ -594,18 +594,18 @@ After successful adoption:
    ```
 
 4. **Read the spec workflow guide**:
-   - See `.kiro/specs/SPEC_WORKFLOW_GUIDE.md`
+   - See `.sce/specs/SPEC_WORKFLOW_GUIDE.md`
 
 5. **Explore Ultrawork**:
    ```bash
-   sce enhance requirements .kiro/specs/01-00-my-feature/requirements.md
+   sce enhance requirements .sce/specs/01-00-my-feature/requirements.md
    ```
 
 ---
 
 ## Getting Help
 
-- **Documentation**: Check README.md in your `.kiro/` directory
+- **Documentation**: Check README.md in your `.sce/` directory
 - **System Check**: `sce doctor`
 - **Version Info**: `sce version-info`
 - **Issues**: https://github.com/heguangyong/scene-capability-engine/issues

package/docs/agent-hooks-analysis.md

@@ -137,7 +137,7 @@ Hooks can perform two types of actions:
   "name": "Auto-generate prompts",
   "when": {
     "type": "fileEdited",
-    "patterns": ["**/.kiro/specs/*/requirements.md", "**/.kiro/specs/*/design.md"]
+    "patterns": ["**/.sce/specs/*/requirements.md", "**/.sce/specs/*/design.md"]
   },
   "then": {
     "type": "askAgent",
@@ -306,7 +306,7 @@ Hooks can perform two types of actions:
 **Goal**: Basic hook support in sce
 
 **Tasks**:
-1. Add hook configuration to `.kiro/hooks/` directory
+1. Add hook configuration to `.sce/hooks/` directory
 2. Create hook templates for common use cases
 3. Add `sce hooks` command group:
    - `sce hooks list` - List all hooks
@@ -400,7 +400,7 @@ Hooks can perform two types of actions:
 ### Hook Storage
 
 ```
-.kiro/
+.sce/
 ├── hooks/
 │   ├── auto-sync.json
 │   ├── quality-gate.json
@@ -555,7 +555,7 @@ Watch mode provides automation for developers not using AI IDE. It monitors file
                ▼
 ┌─────────────────────────────────────┐
 │     Execution Logger                │
-│  (.kiro/watch/execution.log)        │
+│  (.sce/watch/execution.log)        │
 └─────────────────────────────────────┘
 ```
 
@@ -580,15 +580,15 @@ sce watch stop
 
 ### Configuration
 
-Watch mode uses `.kiro/watch-config.json`:
+Watch mode uses `.sce/watch-config.json`:
 
 ```json
 {
   "enabled": true,
   "patterns": [
     "**/tasks.md",
-    "**/.kiro/specs/*/requirements.md",
-    "**/.kiro/specs/*/design.md"
+    "**/.sce/specs/*/requirements.md",
+    "**/.sce/specs/*/design.md"
   ],
   "actions": {
     "**/tasks.md": {
@@ -639,7 +639,7 @@ Watch mode uses `.kiro/watch-config.json`:
 **Without Automation**:
 ```bash
 # 1. Edit tasks.md
-vim .kiro/specs/my-spec/tasks.md
+vim .sce/specs/my-spec/tasks.md
 
 # 2. Save file
 
@@ -662,7 +662,7 @@ sce workspace sync
 sce context export my-spec
 
 # 3. Copy to other tool
-cat .kiro/specs/my-spec/context-export.md
+cat .sce/specs/my-spec/context-export.md
 ```
 
 **Time**: ~1 minute per export
@@ -762,7 +762,7 @@ Start with Phase 1 (foundation) to validate the approach, then expand to Phase 2
   "enabled": true,
   "when": {
     "type": "fileEdited",
-    "patterns": ["**/.kiro/specs/*/tasks.md"]
+    "patterns": ["**/.sce/specs/*/tasks.md"]
   },
   "then": {
     "type": "askAgent",

package/docs/architecture.md

@@ -93,7 +93,7 @@ This document provides detailed architecture diagrams and explanations for Scene
                                   ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │                        File System                                   │
-│                    (.kiro/, backups/, etc.)                         │
+│                    (.sce/, backups/, etc.)                         │
 └─────────────────────────────────────────────────────────────────────┘
 ```
 
@@ -264,7 +264,7 @@ This document provides detailed architecture diagrams and explanations for Scene
 
 ```
 ┌─────────────────────────────────────────────────────────────┐
-│                    Project .kiro/                            │
+│                    Project .sce/                            │
 │  ├── specs/                                                  │
 │  ├── steering/                                               │
 │  ├── tools/                                                  │
@@ -284,7 +284,7 @@ This document provides detailed architecture diagrams and explanations for Scene
                           │
                           ▼
 ┌─────────────────────────────────────────────────────────────┐
-│              .kiro/backups/backup-{timestamp}/               │
+│              .sce/backups/backup-{timestamp}/               │
 │  ├── specs/                                                  │
 │  ├── steering/                                               │
 │  ├── tools/                                                  │
@@ -310,7 +310,7 @@ This document provides detailed architecture diagrams and explanations for Scene
                           │
                           ▼
 ┌─────────────────────────────────────────────────────────────┐
-│                    Project .kiro/                            │
+│                    Project .sce/                            │
 │  (Restored to backup state)                                  │
 └─────────────────────────────────────────────────────────────┘
 ```
@@ -326,13 +326,13 @@ START
   │
   ▼
 ┌─────────────────────┐
-│ Detect: No .kiro/   │
+│ Detect: No .sce/   │
 │ Mode: Fresh         │
 └──────┬──────────────┘
        │
        ▼
 ┌─────────────────────┐
-│ Create .kiro/       │
+│ Create .sce/       │
 │ directory structure │
 └──────┬──────────────┘
        │
@@ -368,7 +368,7 @@ START
   ▼
 ┌─────────────────────┐
 │ Detect: Partial     │
-│ .kiro/ exists but   │
+│ .sce/ exists but   │
 │ incomplete          │
 └──────┬──────────────┘
        │
@@ -416,7 +416,7 @@ START
   ▼
 ┌─────────────────────┐
 │ Detect: Full        │
-│ .kiro/ complete but │
+│ .sce/ complete but │
 │ old version         │
 └──────┬──────────────┘
        │
@@ -593,7 +593,7 @@ START
   ▼
 ┌─────────────────────┐
 │ Validate source     │
-│ .kiro/ exists       │
+│ .sce/ exists       │
 └──────┬──────────────┘
        │
        ▼
@@ -605,12 +605,12 @@ START
        ▼
 ┌─────────────────────┐
 │ Create backup dir   │
-│ .kiro/backups/...   │
+│ .sce/backups/...   │
 └──────┬──────────────┘
        │
        ▼
 ┌─────────────────────┐
-│ Copy .kiro/ content │
+│ Copy .sce/ content │
 │ recursively         │
 └──────┬──────────────┘
        │
@@ -668,13 +668,13 @@ START
        ▼
 ┌─────────────────────┐
 │ Clear current       │
-│ .kiro/ content      │
+│ .sce/ content      │
 └──────┬──────────────┘
        │
        ▼
 ┌─────────────────────┐
 │ Copy backup content │
-│ to .kiro/           │
+│ to .sce/           │
 └──────┬──────────────┘
        │
        ▼

package/docs/articles/ai-driven-development-philosophy-and-practice.en.md

@@ -325,11 +325,11 @@ Completely transforming waterfall documents from "human high-cost burden" to "AI
 
 #### Natural Implementation of High Cohesion, Low Coupling
 
-Each feature has an independent `.kiro/specs/<name>/` folder, with the three-piece set isolated very cleanly, with coupling forcibly reduced to the minimum by design principles.
+Each feature has an independent `.sce/specs/<name>/` folder, with the three-piece set isolated very cleanly, with coupling forcibly reduced to the minimum by design principles.
 
 #### Leverage Point for Principle-Driven Agents
 
-The `.kiro/steering/` directory + steering rules are exactly what you called the "**use experience to set principles to drive agents**" implementation. AI is no longer free-wheeling but guided by rules, much more robust than simple prompt engineering.
+The `.sce/steering/` directory + steering rules are exactly what you called the "**use experience to set principles to drive agents**" implementation. AI is no longer free-wheeling but guided by rules, much more robust than simple prompt engineering.
 
 #### Ultrawork Spirit + Sisyphus Metaphor
 
@@ -380,7 +380,7 @@ Thank you for Guangyong's generous sharing! Haha, regarding "plagiarism"—I pre
 
 #### Response and Expansion on Steering Rules
 
-Your description is very precise: steering constructs a set of "regions," isolating and storing core principles, project environment, and context separately, driving operations through unified indexing. This highly aligns with the project's actual structure—from my analysis of the repository (based on the latest README and directory layout), `.kiro/steering/` is precisely this "principle level" core container, optional but powerful, used to store development rules (like coding conventions, standards, and workflow enforcement), guiding AI Agent behavioral consistency.
+Your description is very precise: steering constructs a set of "regions," isolating and storing core principles, project environment, and context separately, driving operations through unified indexing. This highly aligns with the project's actual structure—from my analysis of the repository (based on the latest README and directory layout), `.sce/steering/` is precisely this "principle level" core container, optional but powerful, used to store development rules (like coding conventions, standards, and workflow enforcement), guiding AI Agent behavioral consistency.
 
 **Regional Division and Timeliness**: This embodies the philosophical beauty of cyclical properties.
 

package/docs/articles/ai-driven-development-philosophy-and-practice.md

@@ -331,11 +331,11 @@ MCP 是提供给 AI 的 Model Context Protocol（模型上下文协议）。
 
 #### 高内聚、低耦合的天然实现
 
-每个 feature 一个独立的 `.kiro/specs/<name>/` 文件夹，三件套隔离得非常干净，耦合度被设计原则强行压到最低。
+每个 feature 一个独立的 `.sce/specs/<name>/` 文件夹，三件套隔离得非常干净，耦合度被设计原则强行压到最低。
 
 #### 原则驱动 Agent 的着力点
 
-`.kiro/steering/` 目录 + steering rules，正是您说的"**用经验设定原则来驱动 agent**"的落地形态。AI 不再是自由发挥，而是被规则引导，这比单纯 prompt engineering 稳健得多。
+`.sce/steering/` 目录 + steering rules，正是您说的"**用经验设定原则来驱动 agent**"的落地形态。AI 不再是自由发挥，而是被规则引导，这比单纯 prompt engineering 稳健得多。
 
 #### Ultrawork spirit + Sisyphus 隐喻
 
@@ -386,7 +386,7 @@ Spec 本身就是**边界 + 愿力**的具现：
 
 #### 对 steering 规则的回应与扩展
 
-您的描述非常精准：steering 构建一套"区域"（regions），将核心原则、项目环境和上下文分别隔离存放，通过统一索引推动运作。这与项目实际结构高度契合——从我对仓库的分析看（基于最新 README 和目录布局），`.kiro/steering/` 正是这个"原则层面"的核心容器，可选但强大，用于存储开发规则（如编码约定、标准和工作流强制），指导 AI Agent 的行为一致性。
+您的描述非常精准：steering 构建一套"区域"（regions），将核心原则、项目环境和上下文分别隔离存放，通过统一索引推动运作。这与项目实际结构高度契合——从我对仓库的分析看（基于最新 README 和目录布局），`.sce/steering/` 正是这个"原则层面"的核心容器，可选但强大，用于存储开发规则（如编码约定、标准和工作流强制），指导 AI Agent 的行为一致性。
 
 **区域划分与时效性**：这体现了周期属性的哲学美感。
 

package/docs/autonomous-control-guide.md

@@ -40,7 +40,7 @@ sce auto close-loop "build autonomous close-loop and master/sub multi-spec execu
 
 # Persist DoD evidence into a custom report file
 sce auto close-loop "build autonomous close-loop and master/sub multi-spec execution for sce" \
-  --dod-report ".kiro/reports/close-loop-dod.json"
+  --dod-report ".sce/reports/close-loop-dod.json"
 
 # Resume interrupted close-loop from latest session
 sce auto close-loop --resume latest
@@ -58,7 +58,7 @@ sce auto close-loop "build autonomous close-loop and master/sub multi-spec execu
   --replan-strategy fixed
 
 # Batch mode: run multiple goals autonomously (each goal gets its own master/sub portfolio)
-sce auto close-loop-batch .kiro/goals.json --json
+sce auto close-loop-batch .sce/goals.json --json
 
 # Program mode: decompose one broad goal into multiple batch goals automatically
 sce auto close-loop-batch \
@@ -83,20 +83,20 @@ sce auto close-loop-program \
   --program-max-elapsed-minutes 60 \
   --program-max-agent-budget 12 \
   --program-max-total-sub-specs 80 \
-  --program-kpi-out .kiro/reports/close-loop-program-kpi.json \
-  --program-audit-out .kiro/reports/close-loop-program-audit.json \
+  --program-kpi-out .sce/reports/close-loop-program-kpi.json \
+  --program-audit-out .sce/reports/close-loop-program-audit.json \
   --json
 
 # Controller command: drain queue goals with autonomous close-loop-program runtime
-sce auto close-loop-controller .kiro/auto/program-queue.lines \
+sce auto close-loop-controller .sce/auto/program-queue.lines \
   --dequeue-limit 2 \
   --max-cycles 20 \
-  --controller-done-file .kiro/auto/program-done.lines \
-  --controller-failed-file .kiro/auto/program-failed.lines \
+  --controller-done-file .sce/auto/program-done.lines \
+  --controller-failed-file .sce/auto/program-failed.lines \
   --json
 
 # Persistent controller mode: keep polling queue and execute new goals automatically
-sce auto close-loop-controller .kiro/auto/program-queue.lines \
+sce auto close-loop-controller .sce/auto/program-queue.lines \
   --wait-on-empty \
   --poll-seconds 30 \
   --max-cycles 1000 \
@@ -107,63 +107,63 @@ sce auto close-loop-controller --controller-resume latest --json
 
 # Recovery command: consume diagnostics and auto-recover unresolved goals
 sce auto close-loop-recover latest --json
-sce auto close-loop-recover .kiro/auto/close-loop-batch-summaries/batch-20260215090000.json \
+sce auto close-loop-recover .sce/auto/close-loop-batch-summaries/batch-20260215090000.json \
   --use-action 2 \
   --recover-until-complete \
   --recover-max-rounds 3 \
   --recover-max-minutes 20 \
   --recovery-memory-ttl-days 30 \
   --recovery-memory-scope release-main \
-  --program-audit-out .kiro/reports/close-loop-recover-audit.json \
+  --program-audit-out .sce/reports/close-loop-recover-audit.json \
   --dry-run --json
 
 # Default autonomous batch run (continue-on-error + adaptive scheduling + retry-until-complete)
-sce auto close-loop-batch .kiro/goals.json --json
+sce auto close-loop-batch .sce/goals.json --json
 
 # Batch parallel mode: run multiple goals concurrently
-sce auto close-loop-batch .kiro/goals.json --batch-parallel 3 --json
+sce auto close-loop-batch .sce/goals.json --batch-parallel 3 --json
 
 # Batch with global agent budget (automatic per-goal maxParallel throttling)
-sce auto close-loop-batch .kiro/goals.json \
+sce auto close-loop-batch .sce/goals.json \
   --batch-parallel 3 \
   --batch-agent-budget 6 \
   --json
 
 # Batch priority scheduling with aging (favor complex goals, prevent starvation)
-sce auto close-loop-batch .kiro/goals.json \
+sce auto close-loop-batch .sce/goals.json \
   --batch-priority critical-first \
   --batch-aging-factor 3 \
   --json
 
 # Auto-retry failed/stopped goals in the same batch run
-sce auto close-loop-batch .kiro/goals.json \
+sce auto close-loop-batch .sce/goals.json \
   --batch-retry-rounds 1 \
   --batch-retry-strategy adaptive \
   --json
 
 # Keep retrying until all goals complete (bounded)
-sce auto close-loop-batch .kiro/goals.json \
+sce auto close-loop-batch .sce/goals.json \
   --batch-retry-until-complete \
   --batch-retry-max-rounds 10 \
   --json
 
 # Disable autonomous closed-loop batch policy (only when you need legacy/manual tuning)
-sce auto close-loop-batch .kiro/goals.json \
+sce auto close-loop-batch .sce/goals.json \
   --no-batch-autonomous \
   --json
 
 # Resume a stopped/failed batch from previous summary output
-sce auto close-loop-batch --resume-from-summary .kiro/reports/close-loop-batch.json --json
+sce auto close-loop-batch --resume-from-summary .sce/reports/close-loop-batch.json --json
 
 # Resume from latest persisted batch summary session
 sce auto close-loop-batch --resume-from-summary latest --json
 
 # Resume only failed/error goals from summary
-sce auto close-loop-batch --resume-from-summary .kiro/reports/close-loop-batch.json \
+sce auto close-loop-batch --resume-from-summary .sce/reports/close-loop-batch.json \
   --resume-strategy failed-only --json
 
 # Batch dry-run for portfolio planning only
-sce auto close-loop-batch .kiro/goals.txt --format lines --dry-run --json
+sce auto close-loop-batch .sce/goals.txt --format lines --dry-run --json
 ```
 
 Default DoD gates:
@@ -177,12 +177,12 @@ Optional DoD gates:
 - `--dod-tasks-closed`: enforce closed checklist items in `tasks.md`
 
 DoD evidence archive:
-- Default output: `.kiro/specs/<master-spec>/custom/dod-report.json`
+- Default output: `.sce/specs/<master-spec>/custom/dod-report.json`
 - `--dod-report <path>`: override report path
 - `--no-dod-report`: disable report generation
 
 Session persistence and resume:
-- Default session archive: `.kiro/auto/close-loop-sessions/*.json`
+- Default session archive: `.sce/auto/close-loop-sessions/*.json`
 - `--session-id <id>`: override generated session id
 - `--resume <session-or-file>`: continue from prior session (supports `latest`)
 - `--no-session`: disable session snapshot persistence
@@ -195,13 +195,13 @@ Session persistence and resume:
   - Stats JSON output includes `criteria`, completion/failure rates, `sub_spec_count_sum`, `master_spec_counts`, and `latest_sessions`.
 
 Spec directory maintenance:
-- `sce auto spec-session list [--limit <n>] [--json]`: inspect spec directory inventory under `.kiro/specs`
+- `sce auto spec-session list [--limit <n>] [--json]`: inspect spec directory inventory under `.sce/specs`
 - `sce auto spec-session prune --keep <n> [--older-than-days <n>] [--no-protect-active] [--protect-window-days <n>] [--show-protection-reasons] [--dry-run] [--json]`: prune old spec directories by retention policy (default protects active/recent specs)
   - Protection sources include collaboration state, close-loop sessions, batch summaries, and controller sessions (via nested batch summary references).
   - JSON output always includes `protection_ranking_top`; enable `--show-protection-reasons` for full `protection_ranking` and per-spec reason payload.
 
 Batch summary session persistence and maintenance:
-- Default batch summary archive: `.kiro/auto/close-loop-batch-summaries/*.json`
+- Default batch summary archive: `.sce/auto/close-loop-batch-summaries/*.json`
 - `--batch-session-id <id>`: override generated batch summary session id
 - `--batch-session-keep <n>`: auto-prune archive and keep newest `n` summaries after each batch run
 - `--batch-session-older-than-days <n>`: when pruning, only delete summaries older than `n` days
@@ -213,7 +213,7 @@ Batch summary session persistence and maintenance:
   - Stats JSON output includes `criteria`, completion/failure rates, goal-volume sums, processed ratio, and `latest_sessions`.
 
 Controller summary session persistence and maintenance:
-- Default controller summary archive: `.kiro/auto/close-loop-controller-sessions/*.json`
+- Default controller summary archive: `.sce/auto/close-loop-controller-sessions/*.json`
 - `--controller-session-id <id>`: override generated controller session id
 - `--controller-session-keep <n>`: auto-prune archive and keep newest `n` summaries after each controller run
 - `--controller-session-older-than-days <n>`: when pruning, only delete summaries older than `n` days
@@ -233,7 +233,7 @@ Cross-archive governance snapshot:
   - `--dry-run` can be combined with `--apply` to validate maintenance impact before deletion.
 - `sce auto governance close-loop [--max-rounds <n>] [--target-risk <low|medium|high>] [--governance-resume <session|latest|file>] [--governance-resume-allow-drift] [--governance-session-id <id>] [--no-governance-session] [--governance-session-keep <n>] [--governance-session-older-than-days <n>] [--execute-advisory] [--advisory-recover-max-rounds <n>] [--advisory-controller-max-cycles <n>] [--plan-only] [--dry-run] [--json]`: governance round-loop runner.
   - Orchestrates repeated `governance maintain` rounds until target risk or stop condition is reached.
-  - Governance close-loop sessions persist by default at `.kiro/auto/governance-close-loop-sessions`; use `--governance-resume` to continue interrupted governance loops.
+  - Governance close-loop sessions persist by default at `.sce/auto/governance-close-loop-sessions`; use `--governance-resume` to continue interrupted governance loops.
   - Resume defaults inherit persisted governance policy (`target_risk`, `execute_advisory`, `advisory_policy`) to avoid accidental configuration drift; explicit drift is blocked unless `--governance-resume-allow-drift` is set.
   - `--governance-session-keep` enables automatic post-run governance session pruning (optional age window via `--governance-session-older-than-days`) while preserving the current run session file.
   - `--execute-advisory` enables automatic advisory action execution when detected (`recover-latest`, `controller-resume-latest`), with autonomous source selection (latest recoverable summary / latest pending controller session) and `skipped` telemetry when no actionable source exists.
@@ -243,7 +243,7 @@ Cross-archive governance snapshot:
 - `sce auto governance session prune [--keep <n>] [--older-than-days <n>] [--dry-run] [--json]`: enforce governance session retention policy.
 
 Recovery memory maintenance:
-- Default recovery memory file: `.kiro/auto/close-loop-recovery-memory.json`
+- Default recovery memory file: `.sce/auto/close-loop-recovery-memory.json`
 - `sce auto recovery-memory show [--scope <scope>] [--json]`: inspect learned failure signatures and action stats (optionally by scope)
 - `sce auto recovery-memory scopes [--json]`: inspect aggregated recovery-memory metrics grouped by scope
 - `sce auto recovery-memory prune [--older-than-days <n>] [--scope <scope>] [--dry-run] [--json]`: prune stale memory entries (optionally by scope)
@@ -284,11 +284,11 @@ Batch multi-goal autonomous execution:
 - `--batch-session-id <id>`: set explicit id for persisted batch summary session
 - `--batch-session-keep <n>`: keep newest `n` persisted batch summary sessions (`0-1000`)
 - `--batch-session-older-than-days <n>`: when pruning persisted batch summaries, only delete sessions older than `n` days (`0-36500`)
-- `--spec-session-keep <n>`: keep newest `n` spec directories under `.kiro/specs` after run (`0-5000`)
+- `--spec-session-keep <n>`: keep newest `n` spec directories under `.sce/specs` after run (`0-5000`)
 - `--spec-session-older-than-days <n>`: when pruning specs, only delete directories older than `n` days (`0-36500`)
 - `--no-spec-session-protect-active`: allow pruning active/recently referenced spec directories
 - `--spec-session-protect-window-days <n>`: protection window (days) for recent session references during spec pruning (`0-36500`, default `7`)
-- `--spec-session-max-total <n>`: spec directory budget ceiling under `.kiro/specs` (`1-500000`)
+- `--spec-session-max-total <n>`: spec directory budget ceiling under `.sce/specs` (`1-500000`)
 - `--spec-session-max-created <n>`: spec growth guard for maximum estimated created directories per run (`0-500000`)
 - `--spec-session-max-created-per-goal <n>`: spec growth guard for estimated created directories per processed goal (`0-1000`)
 - `--spec-session-max-duplicate-goals <n>`: goal-input duplicate guard for batch inputs (`0-500000`)
@@ -341,7 +341,7 @@ Close-loop program command:
 Close-loop controller command:
 - Command: `sce auto close-loop-controller [queue-file]`
 - Runs a queue-driven autonomous loop: dequeue broad goals, execute each by `close-loop-program`, persist remaining queue, and continue until stop condition.
-- Queue file defaults to `.kiro/auto/close-loop-controller-goals.lines`; supports `auto|json|lines` parsing via `--queue-format`.
+- Queue file defaults to `.sce/auto/close-loop-controller-goals.lines`; supports `auto|json|lines` parsing via `--queue-format`.
 - `--controller-resume <session-or-file>` resumes queue/controller context from persisted controller session (`latest`, session id, or file path).
 - Duplicate broad goals are deduped by default; use `--no-controller-dedupe` to preserve raw queue duplicates.
 - `--dequeue-limit <n>` controls how many queued goals are consumed in one cycle (`1-100`, default: all pending goals).
@@ -350,7 +350,7 @@ Close-loop controller command:
 - Controller lease lock is enabled by default to prevent concurrent queue corruption (`--controller-lock-file`, `--controller-lock-ttl-seconds`, `--no-controller-lock`).
 - `--stop-on-goal-failure` stops controller immediately on the first failed dequeued goal.
 - `--controller-done-file` / `--controller-failed-file` append per-goal archive lines for downstream ops and replay.
-- Controller summaries are persisted by default (`.kiro/auto/close-loop-controller-sessions`); use `--controller-session-id`, `--controller-session-keep`, `--controller-session-older-than-days`, `--no-controller-session` as needed.
+- Controller summaries are persisted by default (`.sce/auto/close-loop-controller-sessions`); use `--controller-session-id`, `--controller-session-keep`, `--controller-session-older-than-days`, `--no-controller-session` as needed.
 - `--controller-print-program-summary` prints each nested program summary in realtime during controller execution.
 - Supports full program governance/gate/recovery policy controls (`--program-*`, `--batch-*`, `--continue-on-error`, `--recovery-memory-scope`, `--dry-run`, `--json`).
 - Output summary includes `history`, `results`, final `pending_goals`, `stop_reason`, `exhausted`, dedupe/lock/session, and resume-source telemetry.
@@ -506,7 +506,7 @@ sce auto stop
 
 ### Global Configuration
 
-Location: `.kiro/auto/config.json`
+Location: `.sce/auto/config.json`
 
 ```json
 {
@@ -543,7 +543,7 @@ Location: `.kiro/auto/config.json`
 
 ### Per-Spec Configuration
 
-Location: `.kiro/specs/{spec-name}/auto-config.json`
+Location: `.sce/specs/{spec-name}/auto-config.json`
 
 Per-spec configuration overrides global settings.
 
@@ -773,7 +773,7 @@ sce auto resume
 ### Custom Recovery Strategies
 
 ```javascript
-// In your project's .kiro/auto/custom-strategies.js
+// In your project's .sce/auto/custom-strategies.js
 module.exports = {
   'custom-fix': async (error, context) => {
     // Your custom recovery logic
@@ -847,5 +847,5 @@ A: Simply don't use `sce auto` commands. Use regular `sce` commands for interact
 
 - [Spec Workflow Guide](./spec-workflow.md)
 - [Testing Strategy](./testing-strategy.md)
-- [CORE_PRINCIPLES](./.kiro/steering/CORE_PRINCIPLES.md)
+- [CORE_PRINCIPLES](./.sce/steering/CORE_PRINCIPLES.md)
 - [Command Reference](./command-reference.md)