scene-capability-engine 3.3.5 → 3.3.10

package/docs/cross-tool-guide.md

@@ -90,7 +90,7 @@ sce adopt
 
 ### Best Practices
 
-- Keep steering rules in `.kiro/steering/` for automatic loading
+- Keep steering rules in `.sce/steering/` for automatic loading
 - Use `CURRENT_CONTEXT.md` to maintain session context
 - Leverage agent hooks for automated workflows
 - Use multi-user workspaces for team collaboration
@@ -116,8 +116,8 @@ Claude Code requires manual context loading via exported files.
 
 2. **Copy exported file**:
    ```bash
-   # Location: .kiro/specs/01-00-user-authentication/context-export.md
-   cat .kiro/specs/01-00-user-authentication/context-export.md
+   # Location: .sce/specs/01-00-user-authentication/context-export.md
+   cat .sce/specs/01-00-user-authentication/context-export.md
    ```
 
 3. **Load into Claude Code**:
@@ -464,7 +464,7 @@ sce context export <spec> --no-design
 **Solution**: Manual update required for non-SCE tools
 ```bash
 # Edit tasks.md manually
-vim .kiro/specs/<spec-name>/tasks.md
+vim .sce/specs/<spec-name>/tasks.md
 
 # Or use sce commands
 sce task claim <spec> <task-id>
@@ -536,10 +536,10 @@ For other tools: Manual coordination required
 ## Additional Resources
 
 - [sce Documentation](../README.md)
-- [Spec Workflow Guide](../.kiro/specs/SPEC_WORKFLOW_GUIDE.md)
+- [Spec Workflow Guide](../.sce/specs/SPEC_WORKFLOW_GUIDE.md)
 - [Steering Strategy Guide](./steering-strategy-guide.md)
-- [Phase 1 Summary](../.kiro/specs/03-00-multi-user-and-cross-tool-support/docs/phase-1-summary.md)
-- [Phase 2 Summary](../.kiro/specs/03-00-multi-user-and-cross-tool-support/docs/phase-2-summary.md)
+- [Phase 1 Summary](../.sce/specs/03-00-multi-user-and-cross-tool-support/docs/phase-1-summary.md)
+- [Phase 2 Summary](../.sce/specs/03-00-multi-user-and-cross-tool-support/docs/phase-2-summary.md)
 
 ---
 

package/docs/developer-guide.md

@@ -83,9 +83,9 @@ console.log(analysis.mode); // 'fresh', 'partial', or 'full'
 Implements different adoption modes for various project states.
 
 **Strategies**:
-- `FreshAdoption`: Creates complete .kiro/ structure from scratch
-- `PartialAdoption`: Adds missing components to existing .kiro/
-- `FullAdoption`: Upgrades existing complete .kiro/ to current version
+- `FreshAdoption`: Creates complete .sce/ structure from scratch
+- `PartialAdoption`: Adds missing components to existing .sce/
+- `FullAdoption`: Upgrades existing complete .sce/ to current version
 
 **Usage Example**:
 ```javascript
@@ -270,7 +270,7 @@ module.exports = {
     const changes = [];
     
     // Add new steering file
-    const steeringDir = path.join(projectPath, '.kiro', 'steering');
+    const steeringDir = path.join(projectPath, '.sce', 'steering');
     const envFile = path.join(steeringDir, 'ENVIRONMENT.md');
     
     if (!fs.existsSync(envFile)) {
@@ -282,7 +282,7 @@ module.exports = {
     }
     
     // Update version.json structure
-    const versionFile = path.join(projectPath, '.kiro', 'version.json');
+    const versionFile = path.join(projectPath, '.sce', 'version.json');
     const versionData = await fs.readJson(versionFile);
     
     if (!versionData.upgradeHistory) {
@@ -303,13 +303,13 @@ module.exports = {
     const errors = [];
     
     // Check ENVIRONMENT.md exists
-    const envFile = path.join(projectPath, '.kiro', 'steering', 'ENVIRONMENT.md');
+    const envFile = path.join(projectPath, '.sce', 'steering', 'ENVIRONMENT.md');
     if (!fs.existsSync(envFile)) {
       errors.push('ENVIRONMENT.md not found');
     }
     
     // Check version.json structure
-    const versionFile = path.join(projectPath, '.kiro', 'version.json');
+    const versionFile = path.join(projectPath, '.sce', 'version.json');
     const versionData = await fs.readJson(versionFile);
     if (!versionData.upgradeHistory) {
       errors.push('version.json missing upgradeHistory field');
@@ -609,7 +609,7 @@ test: add property tests for backup system
 
 - [User Adoption Guide](./adoption-guide.md)
 - [User Upgrade Guide](./upgrade-guide.md)
-- [Spec Workflow Guide](../.kiro/specs/SPEC_WORKFLOW_GUIDE.md)
+- [Spec Workflow Guide](../.sce/specs/SPEC_WORKFLOW_GUIDE.md)
 - [GitHub Repository](https://github.com/heguangyong/scene-capability-engine)
 - [Issue Tracker](https://github.com/heguangyong/scene-capability-engine/issues)
 

package/docs/document-governance.md

@@ -58,7 +58,7 @@ Root Violations (2)
      → Delete this file (temporary session notes)
 
 Spec Violations (1)
-  ⚠️  /project/.kiro/specs/01-00-user-login/analysis-report.md
+  ⚠️  /project/.sce/specs/01-00-user-login/analysis-report.md
      Artifact not in subdirectory
      → Move to reports/ subdirectory
 
@@ -188,7 +188,7 @@ Would delete 3 file(s):
 
   🗑️  /project/MVP-PLAN.md
   🗑️  /project/SESSION-2024-01-20.md
-  🗑️  /project/.kiro/specs/01-00-user-login/TEMP-notes.md
+  🗑️  /project/.sce/specs/01-00-user-login/TEMP-notes.md
 
 Run without --dry-run to actually delete these files
 ```
@@ -213,7 +213,7 @@ $ sce docs cleanup --spec 01-00-user-login
 🔥 Cleanup Complete
 
 Deleted 1 file(s):
-  🗑️  .kiro/specs/01-00-user-login/TEMP-notes.md
+  🗑️  .sce/specs/01-00-user-login/TEMP-notes.md
 
 ✅ Cleanup completed successfully
 ```
@@ -263,7 +263,7 @@ $ sce docs validate --all
 
 ❌ 2 error(s):
 
-  ❌ .kiro/specs/02-00-api-feature/requirements.md
+  ❌ .sce/specs/02-00-api-feature/requirements.md
      Missing required file: requirements.md
      → Create requirements.md in 02-00-api-feature
 
@@ -273,7 +273,7 @@ $ sce docs validate --all
 
 ⚠️  1 warning(s):
 
-  ⚠️  .kiro/specs/01-00-user-login/script.js
+  ⚠️  .sce/specs/01-00-user-login/script.js
      Artifact not in subdirectory
      → Move to appropriate subdirectory (reports, scripts, tests, results, docs)
 ```
@@ -319,13 +319,13 @@ $ sce docs archive --spec 01-00-user-login --dry-run
 Would move 3 file(s):
 
   📦 analysis-report.md
-     → .kiro/specs/01-00-user-login/reports/analysis-report.md
+     → .sce/specs/01-00-user-login/reports/analysis-report.md
   
   📦 test-script.js
-     → .kiro/specs/01-00-user-login/scripts/test-script.js
+     → .sce/specs/01-00-user-login/scripts/test-script.js
   
   📦 implementation-guide.md
-     → .kiro/specs/01-00-user-login/docs/implementation-guide.md
+     → .sce/specs/01-00-user-login/docs/implementation-guide.md
 
 Run without --dry-run to actually move these files
 ```
@@ -415,7 +415,7 @@ Running document governance validation...
 
 Found 2 violation(s):
   • /project/TEMP-notes.md - Temporary file in root
-  • .kiro/specs/01-00-user-login/script.js - Misplaced artifact
+  • .sce/specs/01-00-user-login/script.js - Misplaced artifact
 
 Fix violations and try again, or use --no-verify to bypass.
 
@@ -475,7 +475,7 @@ Temporary Patterns:
   • WIP-*.md
   • MVP-*.md
 
-Configuration file: .kiro/config/docs.json
+Configuration file: .sce/config/docs.json
 To modify: sce docs config --set <key> <value>
 To reset: sce docs config --reset
 ```
@@ -572,14 +572,14 @@ sce docs report
 - Violations over time
 - Cleanup actions over time
 - Recent executions with details
-- Saved to `.kiro/reports/document-compliance-{date}.md`
+- Saved to `.sce/reports/document-compliance-{date}.md`
 
 **Example:**
 ```bash
 $ sce docs report
 
 ✅ Compliance report generated
-   Saved to: .kiro/reports/document-compliance-2024-01-24.md
+   Saved to: .sce/reports/document-compliance-2024-01-24.md
 ```
 
 **Report contents:**
@@ -761,7 +761,7 @@ sce docs config --set temporary-patterns "*-SUMMARY.md,SESSION-*.md,*-COMPLETE.m
 
 ### Configuration File Location
 
-Configuration is stored in `.kiro/config/docs.json`
+Configuration is stored in `.sce/config/docs.json`
 
 You can also edit this file directly:
 
@@ -784,10 +784,10 @@ See the [Troubleshooting Guide](troubleshooting.md#document-governance-issues) f
 **"Permission denied" errors:**
 ```bash
 # Check file permissions
-ls -la .kiro/
+ls -la .sce/
 
 # Fix if needed
-chmod -R u+w .kiro/
+chmod -R u+w .sce/
 ```
 
 **"Not a git repository" (for hooks):**

package/docs/environment-management-guide.md

@@ -30,7 +30,7 @@ sce status
 # If issues are detected, run diagnostics
 sce doctor
 
-# Adopt the project (creates .kiro/ directory)
+# Adopt the project (creates .sce/ directory)
 sce adopt
 
 # sce is now managing your project autonomously
@@ -161,7 +161,7 @@ Run a command in the context of the current environment. Ensures the active envi
 The backup system automatically:
 - Creates timestamped backups before each environment switch
 - Maintains up to 10 backups per target file
-- Stores backups in `.kiro/env-backups/`
+- Stores backups in `.sce/env-backups/`
 - Automatically cleans up old backups
 
 ## Best Practices
@@ -169,11 +169,11 @@ The backup system automatically:
 1. **Adopt projects with sce**: Run `sce adopt` to let sce manage your project autonomously, enabling faster AI-assisted development without constant confirmations
 2. **Use descriptive names**: Choose clear, descriptive names for your environments
 3. **Keep source files in version control**: Store all environment-specific configuration files in your repository
-4. **Selective .kiro/ version control**: Use layered .gitignore strategy:
-   - ✅ **DO commit**: `.kiro/specs/` (Spec documents), `.kiro/steering/CORE_PRINCIPLES.md`, `.kiro/steering/ENVIRONMENT.md`, `.kiro/steering/RULES_GUIDE.md`, `.kiro/tools/`, `.kiro/config/`
-   - ❌ **DO NOT commit**: `.kiro/steering/CURRENT_CONTEXT.md` (personal context), `.kiro/environments.json` (user-specific), `.kiro/backups/`, `.kiro/logs/`, `.kiro/reports/`
+4. **Selective .sce/ version control**: Use layered .gitignore strategy:
+   - ✅ **DO commit**: `.sce/specs/` (Spec documents), `.sce/steering/CORE_PRINCIPLES.md`, `.sce/steering/ENVIRONMENT.md`, `.sce/steering/RULES_GUIDE.md`, `.sce/tools/`, `.sce/config/`
+   - ❌ **DO NOT commit**: `.sce/steering/CURRENT_CONTEXT.md` (personal context), `.sce/environments.json` (user-specific), `.sce/backups/`, `.sce/logs/`, `.sce/reports/`
    - **Why**: Share Spec documents and team rules, but avoid conflicts from personal state and user-specific configurations
-5. **Share environment templates**: Commit environment configuration JSON files (e.g., `env-local.json`, `env-production.json`) to your repository root or a `config/` directory, not in `.kiro/`
+5. **Share environment templates**: Commit environment configuration JSON files (e.g., `env-local.json`, `env-production.json`) to your repository root or a `config/` directory, not in `.sce/`
 6. **Test switches**: Test environment switches in a safe environment before using in production
 7. **Regular backups**: The system creates automatic backups, but consider additional backup strategies for critical configurations
 8. **Document verification**: Add verification rules to catch configuration errors early

package/docs/examples/add-export-command/design.md

@@ -165,7 +165,7 @@ program
 
 ```javascript
 // Spec not found
-throw new Error(`Spec "${specName}" not found in .kiro/specs/`);
+throw new Error(`Spec "${specName}" not found in .sce/specs/`);
 
 // Invalid format
 throw new Error(`Invalid format "${format}". Use: json, md, or html`);

package/docs/faq.md

@@ -155,13 +155,13 @@ sce context export 01-00-user-login
 3. **Copy to clipboard:**
 ```bash
 # macOS
-cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+cat .sce/specs/01-00-user-login/context-export.md | pbcopy
 
 # Windows
-type .kiro\specs\01-00-user-login\context-export.md | clip
+type .sce\specs\01-00-user-login\context-export.md | clip
 
 # Linux
-cat .kiro/specs/01-00-user-login/context-export.md | xclip -selection clipboard
+cat .sce/specs/01-00-user-login/context-export.md | xclip -selection clipboard
 ```
 
 4. **Paste into Claude:**
@@ -187,8 +187,8 @@ sce context export 01-00-user-login
 
 **Approach 2: File references**
 ```javascript
-// See requirements: .kiro/specs/01-00-user-login/requirements.md
-// See design: .kiro/specs/01-00-user-login/design.md
+// See requirements: .sce/specs/01-00-user-login/requirements.md
+// See design: .sce/specs/01-00-user-login/design.md
 
 class AuthController {
   // Copilot reads nearby files and suggests code
@@ -301,7 +301,7 @@ See [Integration Modes Guide](integration-modes.md) for details.
 
 ```bash
 # Edit any Spec file
-vim .kiro/specs/01-00-user-login/design.md
+vim .sce/specs/01-00-user-login/design.md
 
 # If using watch mode, context auto-updates
 # If using manual export, re-export:
@@ -438,16 +438,16 @@ sce spec bootstrap --name 02-00-refactor-auth-module --non-interactive
 
 ### Can I customize Spec templates?
 
-**Yes!** sce uses templates from `.kiro/templates/`:
+**Yes!** sce uses templates from `.sce/templates/`:
 
 ```bash
 # View current templates
-ls .kiro/templates/
+ls .sce/templates/
 
 # Edit templates
-vim .kiro/templates/requirements.md
-vim .kiro/templates/design.md
-vim .kiro/templates/tasks.md
+vim .sce/templates/requirements.md
+vim .sce/templates/design.md
+vim .sce/templates/tasks.md
 ```
 
 **Example custom template:**
@@ -486,7 +486,7 @@ sce spec bootstrap --name 01-00-feature-b --non-interactive
 ```
 
 **Each project has:**
-- Own `.kiro/` directory
+- Own `.sce/` directory
 - Own `sce.json` config
 - Own Specs
 - Own templates
@@ -499,7 +499,7 @@ sce spec bootstrap --name 01-00-feature-b --non-interactive
 
 **Via git:**
 ```bash
-git add .kiro/specs/01-00-user-login/
+git add .sce/specs/01-00-user-login/
 git commit -m "Add user login Spec"
 git push
 ```

package/docs/handoff-profile-integration-guide.md

@@ -61,9 +61,9 @@ External handoff projects should provide:
 
 Recommended evidence files before `handoff run`:
 
-- `.kiro/reports/release-evidence/moqui-template-baseline.json`
-- `.kiro/reports/handoff-capability-matrix.json` or `.md`
-- `.kiro/reports/release-evidence/moqui-lexicon-audit.json`
+- `.sce/reports/release-evidence/moqui-template-baseline.json`
+- `.sce/reports/handoff-capability-matrix.json` or `.md`
+- `.sce/reports/release-evidence/moqui-lexicon-audit.json`
 
 ## Override Rules
 

package/docs/handoffs/evidence/ontology/moqui-template-baseline-2026-02-17-232922.json

@@ -1,7 +1,7 @@
 {
   "mode": "moqui-template-baseline",
   "generated_at": "2026-02-17T15:29:22.909Z",
-  "template_root": ".kiro\\templates\\scene-packages",
+  "template_root": ".sce\\templates\\scene-packages",
   "filter": {
     "include_all": false,
     "match": "(moqui|erp)"
@@ -22,8 +22,8 @@
   "templates": [
     {
       "template_id": "sce.scene--erp-inventory-reserve-adjust--0.1.0",
-      "template_path": ".kiro\\templates\\scene-packages\\sce.scene--erp-inventory-reserve-adjust--0.1.0",
-      "contract_path": ".kiro\\templates\\scene-packages\\sce.scene--erp-inventory-reserve-adjust--0.1.0\\scene-package.json",
+      "template_path": ".sce\\templates\\scene-packages\\sce.scene--erp-inventory-reserve-adjust--0.1.0",
+      "contract_path": ".sce\\templates\\scene-packages\\sce.scene--erp-inventory-reserve-adjust--0.1.0\\scene-package.json",
       "ontology": {
         "valid": true,
         "error_count": 0
@@ -66,8 +66,8 @@
     },
     {
       "template_id": "sce.scene--erp-order-fulfillment-workflow--0.1.0",
-      "template_path": ".kiro\\templates\\scene-packages\\sce.scene--erp-order-fulfillment-workflow--0.1.0",
-      "contract_path": ".kiro\\templates\\scene-packages\\sce.scene--erp-order-fulfillment-workflow--0.1.0\\scene-package.json",
+      "template_path": ".sce\\templates\\scene-packages\\sce.scene--erp-order-fulfillment-workflow--0.1.0",
+      "contract_path": ".sce\\templates\\scene-packages\\sce.scene--erp-order-fulfillment-workflow--0.1.0\\scene-package.json",
       "ontology": {
         "valid": true,
         "error_count": 0
@@ -110,8 +110,8 @@
     },
     {
       "template_id": "sce.scene--erp-order-query-read--0.1.0",
-      "template_path": ".kiro\\templates\\scene-packages\\sce.scene--erp-order-query-read--0.1.0",
-      "contract_path": ".kiro\\templates\\scene-packages\\sce.scene--erp-order-query-read--0.1.0\\scene-package.json",
+      "template_path": ".sce\\templates\\scene-packages\\sce.scene--erp-order-query-read--0.1.0",
+      "contract_path": ".sce\\templates\\scene-packages\\sce.scene--erp-order-query-read--0.1.0\\scene-package.json",
       "ontology": {
         "valid": true,
         "error_count": 0

package/docs/handoffs/evidence/ontology/moqui-template-baseline-2026-02-17-232922.md

@@ -1,7 +1,7 @@
 # Moqui Template Baseline Report
 
 - Generated at: 2026-02-17T15:29:22.909Z
-- Template root: .kiro\templates\scene-packages
+- Template root: .sce\templates\scene-packages
 - Filter: (moqui|erp)
 - Baseline thresholds: score>=70, valid-rate>=100%
 

package/docs/integration-modes.md

@@ -61,7 +61,7 @@ sequenceDiagram
 You: "Implement the user login feature"
 
 SCE AI: 
-  [Automatically reads .kiro/specs/01-00-user-login/]
+  [Automatically reads .sce/specs/01-00-user-login/]
   [Understands requirements and design]
   [Generates code]
   [Updates tasks.md automatically]
@@ -142,7 +142,7 @@ AI Tool:
 ```bash
 # You run this once
 sce context export 01-00-user-login
-cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+cat .sce/specs/01-00-user-login/context-export.md | pbcopy
 
 # Then paste into AI tool
 You: "Here's my Spec context: [paste]
@@ -151,7 +151,7 @@ You: "Here's my Spec context: [paste]
 AI: [Generates code based on your Spec]
 
 # You update tasks manually
-# Edit .kiro/specs/01-00-user-login/tasks.md
+# Edit .sce/specs/01-00-user-login/tasks.md
 ```
 
 ### Advantages
@@ -174,7 +174,7 @@ AI: [Generates code based on your Spec]
 
 ```bash
 # Add to ~/.bashrc or ~/.zshrc
-alias sce-clip='sce context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
+alias sce-clip='sce context export $1 && cat .sce/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
 
 # Usage
 sce-clip 01-00-user-login
@@ -247,7 +247,7 @@ sce watch status
 Expected output:
 ```
 Watch Mode: Active
-Watching: .kiro/specs/**/*.md
+Watching: .sce/specs/**/*.md
 Actions: context-export
 Last execution: 2 minutes ago
 ```
@@ -258,7 +258,7 @@ Last execution: 2 minutes ago
 
 1. **Edit your Spec** (e.g., add a new requirement)
    ```bash
-   # Edit .kiro/specs/01-00-user-login/requirements.md
+   # Edit .sce/specs/01-00-user-login/requirements.md
    ```
 
 2. **sce automatically detects the change**
@@ -271,7 +271,7 @@ Last execution: 2 minutes ago
 3. **Use updated context immediately**
    ```bash
    # Context is already up-to-date
-   cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+   cat .sce/specs/01-00-user-login/context-export.md | pbcopy
    ```
 
 ### Advantages
@@ -293,9 +293,9 @@ Last execution: 2 minutes ago
 ```json
 {
   "patterns": [
-    ".kiro/specs/**/requirements.md",
-    ".kiro/specs/**/design.md",
-    ".kiro/specs/**/tasks.md"
+    ".sce/specs/**/requirements.md",
+    ".sce/specs/**/design.md",
+    ".sce/specs/**/tasks.md"
   ],
   "actions": [
     {
@@ -375,7 +375,7 @@ sce watch start
 # Terminal 2: Work normally
 # Edit Specs, context auto-updates
 # Copy latest context when needed
-cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+cat .sce/specs/01-00-user-login/context-export.md | pbcopy
 ```
 
 **Benefits:**
@@ -466,7 +466,7 @@ sequenceDiagram
 ### Native Integration Issues
 
 **Problem:** AI doesn't see Spec files  
-**Solution:** Ensure `.kiro/specs/` directory exists and has correct permissions
+**Solution:** Ensure `.sce/specs/` directory exists and has correct permissions
 
 ### Manual Export Issues
 

package/docs/integration-philosophy.md

@@ -45,7 +45,7 @@
 
 AI：好的，让我先查看项目的 Spec
     [自动执行] sce context export 01-00-user-login
-    [读取文件] .kiro/specs/01-00-user-login/context-export.md
+    [读取文件] .sce/specs/01-00-user-login/context-export.md
     
     我看到设计文档中定义了 AuthController...
     [生成代码]
@@ -90,7 +90,7 @@ AI：好的，让我先查看项目的 Spec
 sce context export 01-00-user-login
 
 # 2. 复制内容
-cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+cat .sce/specs/01-00-user-login/context-export.md | pbcopy
 
 # 3. 粘贴到 Claude/ChatGPT
 
@@ -142,9 +142,9 @@ sce watch start
 ```json
 {
   "patterns": [
-    ".kiro/specs/**/requirements.md",
-    ".kiro/specs/**/design.md",
-    ".kiro/specs/**/tasks.md"
+    ".sce/specs/**/requirements.md",
+    ".sce/specs/**/design.md",
+    ".sce/specs/**/tasks.md"
   ],
   "actions": [
     {
@@ -202,7 +202,7 @@ sce watch start
 
 ```bash
 # ~/.bashrc 或 ~/.zshrc
-alias sce-clip='sce context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ 已复制到剪贴板"'
+alias sce-clip='sce context export $1 && cat .sce/specs/$1/context-export.md | pbcopy && echo "✅ 已复制到剪贴板"'
 
 # 使用
 sce-clip 01-00-user-login
@@ -219,13 +219,13 @@ sce-clip 01-00-user-login
 
 项目使用 sce 管理 Spec。实现功能前：
 
-1. 查看 `.kiro/specs/<spec-name>/design.md`
+1. 查看 `.sce/specs/<spec-name>/design.md`
 2. 按照设计实现
-3. 更新 `.kiro/specs/<spec-name>/tasks.md`
+3. 更新 `.sce/specs/<spec-name>/tasks.md`
 
 示例：
-- 设计文档：`.kiro/specs/01-00-user-login/design.md`
-- 任务列表：`.kiro/specs/01-00-user-login/tasks.md`
+- 设计文档：`.sce/specs/01-00-user-login/design.md`
+- 任务列表：`.sce/specs/01-00-user-login/tasks.md`
 ```
 
 ---
@@ -274,7 +274,7 @@ sce serve
 - 做成插件会限制在特定工具
 - CLI 工具更灵活，可以被任何工具调用
 
-### Q: 能否让 AI 工具自动读取 .kiro/ 目录？
+### Q: 能否让 AI 工具自动读取 .sce/ 目录？
 
 **A**: 
 - 部分工具支持（Cursor、Copilot）

package/docs/interactive-customization/331-poc-sce-integration-checklist.md

@@ -63,7 +63,7 @@ Run matrix regression gate in release pipeline (configurable):
 
 ```bash
 node scripts/matrix-regression-gate.js \
-  --baseline .kiro/reports/release-evidence/moqui-template-baseline.json \
+  --baseline .sce/reports/release-evidence/moqui-template-baseline.json \
   --max-regressions 0 \
   --enforce \
   --json
@@ -82,20 +82,20 @@ Security baseline:
 
 ## 5. Evidence Artifacts (Must Keep)
 
-- `.kiro/reports/interactive-governance-report.json`
-- `.kiro/reports/interactive-governance-report.md`
-- `.kiro/reports/interactive-matrix-signals.jsonl`
-- `.kiro/reports/release-evidence/moqui-template-baseline.json`
-- `.kiro/reports/release-evidence/matrix-regression-gate-<tag>.json`
-- `.kiro/reports/release-evidence/matrix-remediation-plan-<tag>.json`
-- `.kiro/reports/release-evidence/matrix-remediation-<tag>.lines`
-- `.kiro/reports/release-evidence/matrix-remediation-high-<tag>.lines`
-- `.kiro/reports/release-evidence/matrix-remediation-medium-<tag>.lines`
-- `.kiro/reports/release-evidence/matrix-remediation-goals-high-<tag>.json`
-- `.kiro/reports/release-evidence/matrix-remediation-goals-medium-<tag>.json`
-- `.kiro/reports/release-evidence/matrix-remediation-phased-plan-<tag>.json`
-- `.kiro/reports/release-evidence/weekly-ops-summary-<tag>.json`
-- `.kiro/reports/release-evidence/weekly-ops-summary-<tag>.md`
+- `.sce/reports/interactive-governance-report.json`
+- `.sce/reports/interactive-governance-report.md`
+- `.sce/reports/interactive-matrix-signals.jsonl`
+- `.sce/reports/release-evidence/moqui-template-baseline.json`
+- `.sce/reports/release-evidence/matrix-regression-gate-<tag>.json`
+- `.sce/reports/release-evidence/matrix-remediation-plan-<tag>.json`
+- `.sce/reports/release-evidence/matrix-remediation-<tag>.lines`
+- `.sce/reports/release-evidence/matrix-remediation-high-<tag>.lines`
+- `.sce/reports/release-evidence/matrix-remediation-medium-<tag>.lines`
+- `.sce/reports/release-evidence/matrix-remediation-goals-high-<tag>.json`
+- `.sce/reports/release-evidence/matrix-remediation-goals-medium-<tag>.json`
+- `.sce/reports/release-evidence/matrix-remediation-phased-plan-<tag>.json`
+- `.sce/reports/release-evidence/weekly-ops-summary-<tag>.json`
+- `.sce/reports/release-evidence/weekly-ops-summary-<tag>.md`
 
 ## 6. Pass Criteria
 
@@ -110,14 +110,14 @@ When matrix regressions are detected:
 
 ```bash
 node scripts/moqui-matrix-remediation-queue.js \
-  --baseline .kiro/reports/release-evidence/moqui-template-baseline.json \
-  --lines-out .kiro/auto/matrix-remediation.lines \
-  --batch-json-out .kiro/auto/matrix-remediation.goals.json \
-  --commands-out .kiro/reports/release-evidence/matrix-remediation-commands.md \
+  --baseline .sce/reports/release-evidence/moqui-template-baseline.json \
+  --lines-out .sce/auto/matrix-remediation.lines \
+  --batch-json-out .sce/auto/matrix-remediation.goals.json \
+  --commands-out .sce/reports/release-evidence/matrix-remediation-commands.md \
   --json
 
 # anti-429 phased mode (recommended default)
-sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.high.json \
+sce auto close-loop-batch .sce/auto/matrix-remediation.goals.high.json \
   --format json \
   --batch-parallel 1 \
   --batch-agent-budget 2 \
@@ -125,7 +125,7 @@ sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.high.json \
   --batch-retry-max-rounds 3 \
   --json
 sleep 30
-sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.medium.json \
+sce auto close-loop-batch .sce/auto/matrix-remediation.goals.medium.json \
   --format json \
   --batch-parallel 1 \
   --batch-agent-budget 2 \
@@ -138,11 +138,11 @@ npm run run:matrix-remediation-phased -- --json
 
 # zero-prep one-shot (prepare from baseline + run phased)
 node scripts/moqui-matrix-remediation-phased-runner.js \
-  --baseline .kiro/reports/release-evidence/moqui-template-baseline.json \
+  --baseline .sce/reports/release-evidence/moqui-template-baseline.json \
   --json
 npm run run:matrix-remediation-from-baseline -- --json
 
 # fallback
-sce auto close-loop-batch .kiro/auto/matrix-remediation.lines --json
-sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.json --format json --json
+sce auto close-loop-batch .sce/auto/matrix-remediation.lines --json
+sce auto close-loop-batch .sce/auto/matrix-remediation.goals.json --format json --json
 ```