scene-capability-engine 3.0.1 → 3.0.2

package/docs/upgrade-guide.md

@@ -1,6 +1,6 @@
 # Project Upgrade Guide
 
-This guide explains how to upgrade your Kiro Spec Engine (KSE) project to newer versions.
+This guide explains how to upgrade your Scene Capability Engine (sce) project to newer versions.
 
 ## Table of Contents
 
@@ -15,7 +15,7 @@ This guide explains how to upgrade your Kiro Spec Engine (KSE) project to newer
 
 ## Overview
 
-The `kse upgrade` command safely upgrades your project to newer KSE versions. It handles version gaps, runs migration scripts, and preserves all your content.
+The `sce upgrade` command safely upgrades your project to newer sce versions. It handles version gaps, runs migration scripts, and preserves all your content.
 
 **Key Features**:
 - ✅ Automatic version gap detection
@@ -33,37 +33,37 @@ The `kse upgrade` command safely upgrades your project to newer KSE versions. It
 
 ```bash
 # Check project version
-kse version-info
+sce version-info
 
 # Output:
 # 📦 Version Information
 # 
 # Project:
-#   kse version: 1.0.0
+#   sce version: 1.0.0
 #   Template version: 1.0.0
 #   Created: 2026-01-20 10:00:00
 #   Last upgraded: 2026-01-20 10:00:00
 # 
 # Installed:
-#   kse version: 1.2.1
+#   sce version: 1.2.1
 # 
 # ⚠️  Upgrade available
-#   Run kse upgrade to update to v1.2.1
+#   Run sce upgrade to update to v1.2.1
 ```
 
 ### Check for Version Mismatch
 
-KSE automatically warns you when versions don't match:
+sce automatically warns you when versions don't match:
 
 ```bash
-kse status
+sce status
 
 # Output:
 # ⚠️  Version Mismatch Detected
-#   Project initialized with kse v1.0.0
-#   Current kse version: v1.2.1
+#   Project initialized with sce v1.0.0
+#   Current sce version: v1.2.1
 # 
-# 💡 Tip: Run kse upgrade to update project templates
+# 💡 Tip: Run sce upgrade to update project templates
 #   Or use --no-version-check to suppress this warning
 ```
 
@@ -72,7 +72,7 @@ kse status
 1. **Commit your changes** (if using version control):
    ```bash
    git add -A
-   git commit -m "Before KSE upgrade"
+   git commit -m "Before sce upgrade"
    ```
 
 2. **Ensure no pending work**:
@@ -91,7 +91,7 @@ kse status
 
 1. **Run the upgrade command**:
    ```bash
-   kse upgrade
+   sce upgrade
    ```
 
 2. **Review the upgrade plan**:
@@ -148,7 +148,7 @@ kse status
         - No migration script needed
    
    📦 Backup: upgrade-2026-01-23-110000
-     Run kse rollback if you encounter issues
+     Run sce rollback if you encounter issues
    
    🔥 Upgrade complete!
    ```
@@ -158,7 +158,7 @@ kse status
 Preview the upgrade plan without making changes:
 
 ```bash
-kse upgrade --dry-run
+sce upgrade --dry-run
 ```
 
 **Output**:
@@ -178,7 +178,7 @@ Migrations that would be executed:
 Skip all confirmations:
 
 ```bash
-kse upgrade --auto
+sce upgrade --auto
 ```
 
 **Use cases**:
@@ -191,7 +191,7 @@ kse upgrade --auto
 Target a specific version instead of latest:
 
 ```bash
-kse upgrade --to 1.2.0
+sce upgrade --to 1.2.0
 ```
 
 ---
@@ -204,7 +204,7 @@ kse upgrade --to 1.2.0
 
 **Command**:
 ```bash
-kse upgrade
+sce upgrade
 ```
 
 **What happens**:
@@ -220,7 +220,7 @@ kse upgrade
 
 **Command**:
 ```bash
-kse upgrade
+sce upgrade
 ```
 
 **What happens**:
@@ -241,7 +241,7 @@ kse upgrade
 
 **Command**:
 ```bash
-kse upgrade
+sce upgrade
 ```
 
 **What happens**:
@@ -274,7 +274,7 @@ Proceed with upgrade? (Y/n)
 
 **Command**:
 ```bash
-kse upgrade
+sce upgrade
 ```
 
 **Output**:
@@ -302,16 +302,16 @@ kse upgrade
   Migration 1.1.0 → 1.2.0 failed: File not found
 
 📦 Backup available: upgrade-2026-01-23-110000
-  Run kse rollback to restore
+  Run sce rollback to restore
 ```
 
 **Solution**:
 ```bash
 # Rollback to previous state
-kse rollback
+sce rollback
 
 # Check what went wrong
-kse doctor
+sce doctor
 
 # Try again or report issue
 ```
@@ -368,7 +368,7 @@ Check what a migration will do:
 
 ```bash
 # Dry run shows migration details
-kse upgrade --dry-run
+sce upgrade --dry-run
 ```
 
 ---
@@ -377,12 +377,12 @@ kse upgrade --dry-run
 
 ### Problem: "No version.json found"
 
-**Cause**: Project not initialized with KSE
+**Cause**: Project not initialized with sce
 
 **Solution**:
 ```bash
 # Use adopt instead of upgrade
-kse adopt
+sce adopt
 ```
 
 ---
@@ -394,11 +394,11 @@ kse adopt
 **Solution**:
 ```bash
 # Check current version
-kse version-info
+sce version-info
 
 # Upgrade only works forward
 # To go back, use rollback:
-kse rollback
+sce rollback
 ```
 
 ---
@@ -416,7 +416,7 @@ kse rollback
 
 **Step 2**: Rollback
 ```bash
-kse rollback
+sce rollback
 ```
 
 **Step 3**: Report the issue
@@ -460,7 +460,7 @@ ls .kiro/backups/
 rm -rf .kiro/backups/old-backup-id
 
 # Try upgrade again
-kse upgrade
+sce upgrade
 ```
 
 ---
@@ -473,7 +473,7 @@ kse upgrade
 
 **Temporary**:
 ```bash
-kse status --no-version-check
+sce status --no-version-check
 ```
 
 **Permanent** (not recommended):
@@ -491,10 +491,10 @@ export KIRO_NO_VERSION_CHECK=1
 Don't fall too far behind:
 ```bash
 # Check for updates monthly
-kse version-info
+sce version-info
 
 # Upgrade when available
-kse upgrade
+sce upgrade
 ```
 
 ### 2. Test After Upgrade
@@ -502,13 +502,13 @@ kse upgrade
 Verify everything works:
 ```bash
 # Check status
-kse status
+sce status
 
 # Run doctor
-kse doctor
+sce doctor
 
 # Test your specs
-kse enhance requirements .kiro/specs/your-spec/requirements.md
+sce enhance requirements .kiro/specs/your-spec/requirements.md
 ```
 
 ### 3. Keep Upgrade History
@@ -522,7 +522,7 @@ ls -lt .kiro/backups/ | head -6
 ### 4. Read Release Notes
 
 Check what changed:
-- See CHANGELOG.md in KSE repository
+- See CHANGELOG.md in sce repository
 - Review breaking changes
 - Understand new features
 
@@ -531,8 +531,8 @@ Check what changed:
 For large version gaps:
 ```bash
 # Instead of 1.0.0 → 2.0.0 directly
-# Let KSE handle incremental upgrades
-kse upgrade  # Automatically: 1.0.0 → 1.1.0 → 1.2.0 → 2.0.0
+# Let sce handle incremental upgrades
+sce upgrade  # Automatically: 1.0.0 → 1.1.0 → 1.2.0 → 2.0.0
 ```
 
 ---
@@ -551,8 +551,8 @@ kse upgrade  # Automatically: 1.0.0 → 1.1.0 → 1.2.0 → 2.0.0
 ### Checking Compatibility
 
 ```bash
-# KSE automatically checks compatibility
-kse upgrade
+# sce automatically checks compatibility
+sce upgrade
 
 # If incompatible, you'll see:
 # ❌ Error: Incompatible versions
@@ -570,7 +570,7 @@ If upgrade fails or causes issues:
 
 ```bash
 # List backups
-kse rollback
+sce rollback
 
 # Select the upgrade backup
 # Restore to previous state
@@ -599,14 +599,14 @@ After successful upgrade:
 
 1. **Verify the upgrade**:
    ```bash
-   kse version-info
-   kse status
+   sce version-info
+   sce status
    ```
 
 2. **Check .gitignore configuration**:
    The upgrade process automatically checks and fixes your `.gitignore` for team collaboration. If you see a warning about .gitignore, you can manually fix it:
    ```bash
-   kse doctor --fix-gitignore
+   sce doctor --fix-gitignore
    ```
    Learn more: [Team Collaboration Guide](./team-collaboration-guide.md)
 
@@ -630,9 +630,9 @@ After successful upgrade:
 
 - **Documentation**: Check README.md
 - **Issues**: https://github.com/heguangyong/scene-capability-engine/issues
-- **Version Info**: `kse version-info`
-- **System Check**: `kse doctor`
-- **Rollback**: `kse rollback`
+- **Version Info**: `sce version-info`
+- **System Check**: `sce doctor`
+- **Rollback**: `sce rollback`
 
 ---
 

package/docs/value-observability-guide.md

@@ -1,6 +1,6 @@
 # Value Observability Guide
 
-> Turn Spec delivery into measurable weekly outcomes with `kse value metrics`.
+> Turn Spec delivery into measurable weekly outcomes with `sce value metrics`.
 
 ---
 
@@ -12,7 +12,7 @@ Most AI-assisted workflows can ship code, but they often cannot answer:
 - Is quality improving or degrading?
 - Should we pass Day30/Day60 gate based on evidence?
 
-kse solves this with machine-readable KPI snapshots, baseline derivation, trend analysis, and gate-ready summaries.
+sce solves this with machine-readable KPI snapshots, baseline derivation, trend analysis, and gate-ready summaries.
 
 ---
 
@@ -20,16 +20,16 @@ kse solves this with machine-readable KPI snapshots, baseline derivation, trend
 
 ```bash
 # 0) Generate sample input (first-time setup)
-kse value metrics sample --out ./kpi-input.json --period 2026-W10 --json
+sce value metrics sample --out ./kpi-input.json --period 2026-W10 --json
 
 # 1) Snapshot this week
-kse value metrics snapshot --input ./kpi-input.json --period 2026-W10 --checkpoint day-60 --json
+sce value metrics snapshot --input ./kpi-input.json --period 2026-W10 --checkpoint day-60 --json
 
 # 2) Build baseline from earliest history snapshots
-kse value metrics baseline --from-history 3 --period 2026-W10 --json
+sce value metrics baseline --from-history 3 --period 2026-W10 --json
 
 # 3) Analyze trend risk from latest snapshots
-kse value metrics trend --window 6 --json
+sce value metrics trend --window 6 --json
 ```
 
 ---

package/docs/zh/README.md

@@ -1,6 +1,6 @@
-# kse 文档索引
+# sce 文档索引
 
-> kse (Kiro Spec Engine) 的完整文档 - AI 辅助开发的上下文管理系统
+> sce (Scene Capability Engine) 的完整文档 - AI 辅助开发的上下文管理系统
 
 ---
 
@@ -12,35 +12,35 @@
 
 ## 📚 文档概述
 
-本文档集合提供了使用 kse 进行 Spec 驱动开发所需的一切。无论你是初学者还是高级用户，你都会在这里找到所需的指导。
+本文档集合提供了使用 sce 进行 Spec 驱动开发所需的一切。无论你是初学者还是高级用户，你都会在这里找到所需的指导。
 
 ---
 
-## ⭐ 为什么团队选择 kse
+## ⭐ 为什么团队选择 sce
 
 - **结构化交付**：先需求、后设计、再任务，实现路径可追踪。
 - **可并行扩展**：支持依赖感知的多 Spec 编排，减少串行等待。
-- **双轨交接闭环**：`kse auto handoff run` 一条命令完成 plan/queue/batch/observability，支持 `--continue-from` 续跑，并输出可直接执行的后续建议命令。
+- **双轨交接闭环**：`sce auto handoff run` 一条命令完成 plan/queue/batch/observability，支持 `--continue-from` 续跑，并输出可直接执行的后续建议命令。
 - **结果可量化**：通过 KPI 快照、基线、趋势命令持续度量交付质量。
-- **工具无锁定**：可与 Claude、Cursor、Windsurf、Copilot、Kiro 协作。
+- **工具无锁定**：可与 Claude、Cursor、Windsurf、Copilot、SCE 协作。
 - **治理能力内建**：文档治理、锁管理、环境/工作区控制和审计链路。
 
 ---
 
 ## 🚀 入门指南
 
-从这里开始你的 kse 之旅：
+从这里开始你的 sce 之旅：
 
 ### [快速入门指南](quick-start.md)
 **5 分钟教程** - 从安装到第一个 AI 辅助功能实现
-- 安装 kse
+- 安装 sce
 - 创建你的第一个 Spec
 - 导出上下文
 - 使用 AI 工具实现功能
 
 ### [常见问题 (FAQ)](faq.md)
-**常见问题解答** - 关于 kse 的快速答案
-- kse 是什么？
+**常见问题解答** - 关于 sce 的快速答案
+- sce 是什么？
 - 它如何与 AI 工具配合使用？
 - 我应该使用哪个 AI 工具？
 - 常见误解
@@ -56,7 +56,7 @@
 
 ## 📋 核心概念
 
-深入理解 kse 的工作原理：
+深入理解 sce 的工作原理：
 
 ### [Spec 工作流](spec-workflow.md)
 **深入指南** - 理解 Spec 驱动开发
@@ -67,13 +67,13 @@
 
 ### [集成模式](integration-modes.md)
 **三种集成方式** - 选择最适合你的模式
-- 原生集成（Kiro、Windsurf）
+- 原生集成（SCE、Windsurf）
 - 手动导出（Claude、Cursor、ChatGPT）
 - Watch 模式（所有工具）
 - 每种模式的优缺点
 
 ### [命令参考](../command-reference.md)
-**完整命令列表** - 所有 kse 命令及示例
+**完整命令列表** - 所有 sce 命令及示例
 - 项目设置命令
 - 上下文管理命令
 - 任务管理命令
@@ -99,8 +99,8 @@
 - Watch 模式
 - 自动化工作流
 
-#### [Kiro 指南](tools/kiro-guide.md)
-**Kiro IDE** - 专为 Spec 驱动开发设计
+#### [SCE 指南](tools/SCE-guide.md)
+**AI IDE** - 专为 Spec 驱动开发设计
 - 完全原生集成
 - 可视化工具
 - 零配置
@@ -160,7 +160,7 @@
 对于有经验的用户：
 
 ### [采用指南](adoption-guide.md)
-**在现有项目中采用 kse** - 迁移策略
+**在现有项目中采用 sce** - 迁移策略
 - 评估你的项目
 - 采用策略
 - 迁移现有文档
@@ -179,13 +179,13 @@
 - remediation 队列回灌闭环
 
 ### [331-poc 双轨协同对接手册](../331-poc-dual-track-integration-guide.md)
-**331-poc 与 kse 协同执行指南** - 交接契约、接入命令链、主从闭环验收
+**331-poc 与 sce 协同执行指南** - 交接契约、接入命令链、主从闭环验收
 - 331 深化成果输入约束
-- KSE 侧模板/ontology/gate 验证流程
+- sce 侧模板/ontology/gate 验证流程
 - 双仓协同失败回退策略
 
 ### [331-poc 适配路线图](../331-poc-adaptation-roadmap.md)
-**KSE 侧持续适配清单** - 已完成、下一阶段、中期增强与长期目标
+**sce 侧持续适配清单** - 已完成、下一阶段、中期增强与长期目标
 - handoff 自动化命令演进
 - 主从编排与门禁增强
 - 跨轮次回归与发布治理集成
@@ -197,7 +197,7 @@
 - Day30/Day60 门禁输入复用
 
 ### [升级指南](upgrade-guide.md)
-**版本升级** - 保持 kse 最新
+**版本升级** - 保持 sce 最新
 - 升级过程
 - 版本兼容性
 - 迁移指南
@@ -229,7 +229,7 @@
 - 审查工作流
 
 ### [开发者指南](developer-guide.md)
-**贡献和扩展 kse** - 对于贡献者
+**贡献和扩展 sce** - 对于贡献者
 - 项目结构
 - 开发设置
 - 贡献指南
@@ -332,7 +332,7 @@
 
 **准备好开始了吗？** 🚀
 
-从[快速入门指南](quick-start.md)开始你的 kse 之旅！
+从[快速入门指南](quick-start.md)开始你的 sce 之旅！
 
 ---