scene-capability-engine 3.0.1 → 3.0.2

package/docs/quick-start-with-ai-tools.md

@@ -1,25 +1,25 @@
-# 快速入门：配合 AI 工具使用 kse
+# 快速入门：配合 AI 工具使用 sce
 
-> 5分钟学会如何用 kse 配合 Claude、Cursor、Copilot 等 AI 工具
+> 5分钟学会如何用 sce 配合 Claude、Cursor、Copilot 等 AI 工具
 
 ---
 
-## ⚠️ 重要：kse 的定位
+## ⚠️ 重要：sce 的定位
 
-**kse 不是独立开发工具，而是 AI 工具的增强器**
+**sce 不是独立开发工具，而是 AI 工具的增强器**
 
 ```
 你的工作界面 = AI 工具（Codex/Claude/Cursor）
-kse 的角色 = 后台管理 Spec，为 AI 提供结构化上下文
+sce 的角色 = 后台管理 Spec，为 AI 提供结构化上下文
 ```
 
 **简单理解**：
-- ❌ kse 不是用来写代码的
-- ✅ kse 是用来**组织项目信息**，让 AI 更好地帮你写代码
-- ✅ 你主要在 AI 工具中工作，kse 在后台提供支持
+- ❌ sce 不是用来写代码的
+- ✅ sce 是用来**组织项目信息**，让 AI 更好地帮你写代码
+- ✅ 你主要在 AI 工具中工作，sce 在后台提供支持
 
 **三种使用模式**：
-1. **AI 主动调用 kse**（Windsurf/Cline）- 最佳，完全自动 ⭐
+1. **AI 主动调用 sce**（Windsurf/Cline）- 最佳，完全自动 ⭐
 2. **手动导出上下文**（Claude/ChatGPT）- 当前方式
 3. **Watch Mode 自动化**（所有工具）- 进阶用法
 
@@ -29,13 +29,13 @@ kse 的角色 = 后台管理 Spec，为 AI 提供结构化上下文
 
 ## 核心理念
 
-**kse 是什么？**
+**sce 是什么？**
 - 一个 CLI 工具，帮你管理项目的 Spec（需求、设计、任务）
 - 生成结构化的上下文，让 AI 工具更好地理解你的项目
 
-**为什么需要 kse？**
+**为什么需要 sce？**
 - AI 工具需要清晰的上下文才能生成高质量代码
-- kse 帮你组织和导出这些上下文
+- sce 帮你组织和导出这些上下文
 - 让 AI 按照你的设计和规范工作
 
 ---
@@ -44,7 +44,7 @@ kse 的角色 = 后台管理 Spec，为 AI 提供结构化上下文
 
 ```
 ┌─────────────┐
-│  1. 用 kse  │
+│  1. 用 sce  │
 │  创建 Spec  │
 └──────┬──────┘
        │
@@ -77,17 +77,17 @@ kse 的角色 = 后台管理 Spec，为 AI 提供结构化上下文
 
 ## 5分钟快速开始
 
-### 步骤 1：安装 kse
+### 步骤 1：安装 sce
 
 ```bash
-npm install -g kiro-spec-engine
+npm install -g scene-capability-engine
 ```
 
 ### 步骤 2：初始化项目
 
 ```bash
 cd your-project
-kse adopt
+sce adopt
 ```
 
 这会在项目中创建 `.kiro/` 目录。
@@ -95,7 +95,7 @@ kse adopt
 ### 步骤 3：创建你的第一个 Spec
 
 ```bash
-kse spec bootstrap --name 01-00-user-login --non-interactive
+sce spec bootstrap --name 01-00-user-login --non-interactive
 ```
 
 然后编辑生成的文件：
@@ -106,7 +106,7 @@ kse spec bootstrap --name 01-00-user-login --non-interactive
 ### 步骤 4：导出上下文
 
 ```bash
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 ```
 
 这会生成：`.kiro/specs/01-00-user-login/context-export.md`
@@ -124,7 +124,7 @@ kse context export 01-00-user-login
 
 1. 生成任务提示：
    ```bash
-   kse prompt generate 01-00-user-login 1.1
+   sce prompt generate 01-00-user-login 1.1
    ```
 
 2. 打开 Cursor Composer (Cmd+K)
@@ -157,7 +157,7 @@ kse context export 01-00-user-login
 ### 1. 创建 Spec
 
 ```bash
-kse spec bootstrap --name 01-00-user-login --non-interactive
+sce spec bootstrap --name 01-00-user-login --non-interactive
 ```
 
 ### 2. 编写需求（requirements.md）
@@ -206,7 +206,7 @@ kse spec bootstrap --name 01-00-user-login --non-interactive
 ### 5. 导出上下文
 
 ```bash
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 ```
 
 ### 6. 在 Claude Code 中使用
@@ -242,7 +242,7 @@ Claude：[生成测试代码]
 
 ### Cursor
 ✅ **优势**：IDE 集成，可以直接修改文件  
-📝 **用法**：用 `kse prompt generate` 生成任务提示  
+📝 **用法**：用 `sce prompt generate` 生成任务提示  
 💡 **技巧**：使用 Composer 模式，让 Cursor 直接编辑文件
 
 ### GitHub Copilot
@@ -252,7 +252,7 @@ Claude：[生成测试代码]
 
 ### Windsurf / Cline
 ✅ **优势**：可以执行命令和修改文件  
-📝 **用法**：让 AI 直接运行 `kse` 命令  
+📝 **用法**：让 AI 直接运行 `sce` 命令  
 💡 **技巧**：AI 可以自动导出上下文和更新任务状态
 
 ---
@@ -271,7 +271,7 @@ Claude：[生成测试代码]
 **A**: 使用任务级别的提示：
 ```bash
 # 只导出特定任务的上下文
-kse prompt generate 01-00-user-login 1.1
+sce prompt generate 01-00-user-login 1.1
 ```
 
 ### Q: AI 生成的代码不符合设计怎么办？
@@ -286,13 +286,13 @@ kse prompt generate 01-00-user-login 1.1
 **A**: 使用 Steering Rules：
 ```bash
 # 导出时包含规范
-kse context export 01-00-user-login --steering --steering-files=CORE_PRINCIPLES.md
+sce context export 01-00-user-login --steering --steering-files=CORE_PRINCIPLES.md
 ```
 
 ### Q: 可以自动更新任务状态吗？
 
 **A**: 
-- **Kiro IDE**：支持自动更新
+- **AI IDE**：支持自动更新
 - **其他工具**：需要手动更新 `tasks.md`
 - **未来**：计划支持更多工具的自动更新
 
@@ -315,27 +315,27 @@ kse context export 01-00-user-login --steering --steering-files=CORE_PRINCIPLES.
 
 导出时包含：
 ```bash
-kse context export 01-00-user-login --steering
+sce context export 01-00-user-login --steering
 ```
 
 ### 2. 为不同工具生成不同格式的提示
 
 ```bash
 # 为 Claude 生成
-kse prompt generate 01-00-user-login 1.1 --tool=claude-code
+sce prompt generate 01-00-user-login 1.1 --tool=claude-code
 
 # 为 Cursor 生成
-kse prompt generate 01-00-user-login 1.1 --tool=cursor
+sce prompt generate 01-00-user-login 1.1 --tool=cursor
 
 # 通用格式
-kse prompt generate 01-00-user-login 1.1
+sce prompt generate 01-00-user-login 1.1
 ```
 
 ### 3. 批量导出多个任务
 
 ```bash
 # 导出整个 Spec
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 
 # 然后在 AI 工具中说：
 # "请按顺序实现任务 1.1 到 1.5"
@@ -345,14 +345,14 @@ kse context export 01-00-user-login
 
 ## 总结
 
-**kse 的价值**：
+**sce 的价值**：
 1. ✅ 结构化管理项目需求和设计
 2. ✅ 生成 AI 友好的上下文
 3. ✅ 让 AI 按照你的规范工作
 4. ✅ 跟踪任务进度
 
 **配合 AI 工具的流程**：
-1. 用 kse 写 Spec（需求、设计、任务）
+1. 用 sce 写 Spec（需求、设计、任务）
 2. 导出上下文
 3. 复制给 AI 工具
 4. AI 帮你写代码
@@ -368,8 +368,8 @@ kse context export 01-00-user-login
 **开始使用！** 🚀
 
 ```bash
-npm install -g kiro-spec-engine
-kse adopt
-kse spec bootstrap --name 01-00-my-feature --non-interactive
+npm install -g scene-capability-engine
+sce adopt
+sce spec bootstrap --name 01-00-my-feature --non-interactive
 ```
 

package/docs/quick-start.md

@@ -6,7 +6,7 @@
 
 ## What You'll Learn
 
-- ✅ Install kse and adopt it in your project
+- ✅ Install sce and adopt it in your project
 - ✅ Tell your AI about the methodology
 - ✅ Let AI work according to Spec-driven approach
 
@@ -18,15 +18,15 @@
 
 ---
 
-## Step 1: Install kse (30 seconds)
+## Step 1: Install sce (30 seconds)
 
 ```bash
-npm install -g kiro-spec-engine
+npm install -g scene-capability-engine
 ```
 
 Verify:
 ```bash
-kse --version
+sce --version
 ```
 
 ---
@@ -35,7 +35,7 @@ kse --version
 
 ```bash
 cd your-project
-kse adopt
+sce adopt
 ```
 
 This creates `.kiro/` directory with:
@@ -78,17 +78,17 @@ I need a user login feature with email and password.
 
 ```bash
 # Single-Spec recommended flow
-kse spec bootstrap --name 01-00-user-login --non-interactive
-kse spec pipeline run --spec 01-00-user-login
-kse spec gate run --spec 01-00-user-login --json
+sce spec bootstrap --name 01-00-user-login --non-interactive
+sce spec pipeline run --spec 01-00-user-login
+sce spec gate run --spec 01-00-user-login --json
 
 # Multi-Spec flow (defaults to orchestrate mode)
-kse spec bootstrap --specs "01-00-user-login,01-01-user-session" --max-parallel 3
-kse spec pipeline run --specs "01-00-user-login,01-01-user-session" --max-parallel 3
-kse spec gate run --specs "01-00-user-login,01-01-user-session" --max-parallel 3
+sce spec bootstrap --specs "01-00-user-login,01-01-user-session" --max-parallel 3
+sce spec pipeline run --specs "01-00-user-login,01-01-user-session" --max-parallel 3
+sce spec gate run --specs "01-00-user-login,01-01-user-session" --max-parallel 3
 ```
 
-**The AI uses kse commands automatically** - you don't need to learn them.
+**The AI uses sce commands automatically** - you don't need to learn them.
 
 ---
 
@@ -97,13 +97,13 @@ kse spec gate run --specs "01-00-user-login,01-01-user-session" --max-parallel 3
 Generate a sample KPI input file:
 
 ```bash
-kse value metrics sample --out ./kpi-input.json --period 2026-W10 --json
+sce value metrics sample --out ./kpi-input.json --period 2026-W10 --json
 ```
 
 Then run:
 
 ```bash
-kse value metrics snapshot --input ./kpi-input.json --json
+sce value metrics snapshot --input ./kpi-input.json --json
 ```
 
 If you prefer manual input, use:
@@ -129,13 +129,13 @@ This gives you a machine-readable snapshot with risk level and output paths.
 
 You're now using Spec-driven development. Your AI understands the methodology and will follow it.
 
-**Key insight:** You don't "use kse" - your project "follows Spec-driven methodology" and kse helps enforce it.
+**Key insight:** You don't "use sce" - your project "follows Spec-driven methodology" and sce helps enforce it.
 
 ---
 
 ## Next Steps
 
-- **[Integration Modes](integration-modes.md)** - Understand how AI tools work with kse
+- **[Integration Modes](integration-modes.md)** - Understand how AI tools work with sce
 - **[Spec Workflow](spec-workflow.md)** - Deep dive into Spec creation
 - **[Tool Guides](tools/)** - Tool-specific tips
 

package/docs/release-checklist.md

@@ -1,6 +1,6 @@
 # Release Checklist
 
-> Minimal, repeatable checklist before publishing a new kse version.
+> Minimal, repeatable checklist before publishing a new sce version.
 
 ---
 
@@ -20,8 +20,8 @@ npm run test:skip-audit
 npm test -- tests/unit/commands/value-metrics.test.js
 
 # CLI smoke checks
-node bin/kiro-spec-engine.js --help
-node bin/kiro-spec-engine.js value metrics --help
+node bin/scene-capability-engine.js --help
+node bin/scene-capability-engine.js value metrics --help
 ```
 
 ---
@@ -29,8 +29,8 @@ node bin/kiro-spec-engine.js value metrics --help
 ## 2. Value Observability Smoke Flow
 
 ```bash
-kse value metrics sample --out ./kpi-input.json --json
-kse value metrics snapshot --input ./kpi-input.json --json
+sce value metrics sample --out ./kpi-input.json --json
+sce value metrics snapshot --input ./kpi-input.json --json
 ```
 
 Expected:
@@ -70,7 +70,7 @@ Optional sanity scan:
 rg -n "yourusername|support@example.com" README.md README.zh.md docs docs/zh -S
 
 # Canonical repository link check (should return no matches)
-rg -n "github.com/kiro-spec-engine/kse" README.md README.zh.md docs START_HERE.txt INSTALL_OFFLINE.txt -S -g "!docs/release-checklist.md" -g "!docs/zh/release-checklist.md"
+rg -n "github.com/scene-capability-engine/sce" README.md README.zh.md docs START_HERE.txt INSTALL_OFFLINE.txt -S -g "!docs/release-checklist.md" -g "!docs/zh/release-checklist.md"
 ```
 
 ---
@@ -116,6 +116,6 @@ Ensure:
   - `KSE_RELEASE_DRIFT_HARD_GATE_BLOCK_STREAK_MIN`: minimum consecutive hard-gate preflight blocked streak (latest window, default `2`)
   - `KSE_RELEASE_DRIFT_PREFLIGHT_UNAVAILABLE_STREAK_MIN`: minimum consecutive release preflight unavailable streak (latest window, default `2`)
 - Optional local dry-run for gate history index artifact:
-  - `kse auto handoff gate-index --dir .kiro/reports/release-evidence --out .kiro/reports/release-evidence/release-gate-history.json --json`
+  - `sce auto handoff gate-index --dir .kiro/reports/release-evidence --out .kiro/reports/release-evidence/release-gate-history.json --json`
 
 Then proceed with your release workflow (tag, push, npm publish, GitHub release).

package/docs/releases/v1.46.2-validation.md

@@ -34,7 +34,7 @@ npm pack --dry-run
 
 Result:
 
-- Tarball name: `kiro-spec-engine-1.46.2.tgz`
+- Tarball name: `scene-capability-engine-1.46.2.tgz`
 - Package size: ~889.8 kB
 - Total files: 317
 - No transient Python bytecode artifacts observed in listing.

package/docs/releases/v1.46.2.md

@@ -5,15 +5,15 @@ Release date: 2026-02-14
 ## Highlights
 
 - Added KPI observability commands for real delivery measurement:
-  - `kse value metrics snapshot`
-  - `kse value metrics baseline`
-  - `kse value metrics trend`
+  - `sce value metrics snapshot`
+  - `sce value metrics baseline`
+  - `sce value metrics trend`
 - Added first-run scaffold command:
-  - `kse value metrics sample`
+  - `sce value metrics sample`
 - Improved operator experience:
   - Actionable failure guidance now points to concrete next commands.
 - Strengthened product positioning:
-  - README, quick-start, and docs index now clearly express kse advantages.
+  - README, quick-start, and docs index now clearly express sce advantages.
 - Refreshed onboarding consistency:
   - `START_HERE.txt`, `INSTALL_OFFLINE.txt`, and `docs/OFFLINE_INSTALL.md` now align with current version and workflow.
 - Improved package hygiene:
@@ -21,7 +21,7 @@ Release date: 2026-02-14
 
 ## Why This Release Matters
 
-This release shifts kse from "workflow tooling" to "measurable delivery system":
+This release shifts sce from "workflow tooling" to "measurable delivery system":
 
 - You can now produce weekly, machine-readable KPI evidence.
 - You can compare baseline vs trend for risk review.
@@ -30,10 +30,10 @@ This release shifts kse from "workflow tooling" to "measurable delivery system":
 ## Quick Verification
 
 ```bash
-kse adopt
-kse spec bootstrap --name 01-00-demo-feature --non-interactive
-kse value metrics sample --out ./kpi-input.json --json
-kse value metrics snapshot --input ./kpi-input.json --json
+sce adopt
+sce spec bootstrap --name 01-00-demo-feature --non-interactive
+sce value metrics sample --out ./kpi-input.json --json
+sce value metrics snapshot --input ./kpi-input.json --json
 ```
 
 ## Upgrade Notes

package/docs/scene-runtime-guide.md

@@ -1,6 +1,6 @@
 # Scene Runtime Guide
 
-> Complete guide to kse Scene features: Template Engine, Quality Pipeline, Ontology, and Moqui ERP Integration
+> Complete guide to sce Scene features: Template Engine, Quality Pipeline, Ontology, and Moqui ERP Integration
 
 ---
 
@@ -11,7 +11,7 @@
 
 ## Overview
 
-The kse Scene Runtime is a suite of features for building, validating, scoring, and analyzing reusable scene template packages. Scene packages describe business capabilities (e.g., ERP inventory management) as structured templates that AI agents can understand and instantiate.
+The sce Scene Runtime is a suite of features for building, validating, scoring, and analyzing reusable scene template packages. Scene packages describe business capabilities (e.g., ERP inventory management) as structured templates that AI agents can understand and instantiate.
 
 ### Feature Timeline
 
@@ -76,16 +76,16 @@ Each layer can extend the parent's variable schema and template files. The `temp
 
 ```bash
 # Validate variable schema
-kse scene template-validate --package <path>
-kse scene template-validate --package ./my-package --json
+sce scene template-validate --package <path>
+sce scene template-validate --package ./my-package --json
 
 # Resolve inheritance chain
-kse scene template-resolve --package <name>
-kse scene template-resolve --package scene-erp-inventory --json
+sce scene template-resolve --package <name>
+sce scene template-resolve --package scene-erp-inventory --json
 
 # Render templates with variable values
-kse scene template-render --package <name> --values <json-or-path> --out <dir>
-kse scene template-render --package scene-erp --values '{"entity_name":"Order"}' --out ./output --json
+sce scene template-render --package <name> --values <json-or-path> --out <dir>
+sce scene template-render --package scene-erp --values '{"entity_name":"Order"}' --out ./output --json
 ```
 
 ---
@@ -125,17 +125,17 @@ Analyzes Moqui ERP resources and generates reusable scene templates:
 
 ```bash
 # Test connectivity
-kse scene connect --config <path>
-kse scene connect --config ./moqui-config.json --json
+sce scene connect --config <path>
+sce scene connect --config ./moqui-config.json --json
 
 # Discover entities, services, screens
-kse scene discover --config <path>
-kse scene discover --config ./moqui-config.json --type entities --json
+sce scene discover --config <path>
+sce scene discover --config ./moqui-config.json --type entities --json
 
 # Extract scene templates
-kse scene extract --config <path> --out <dir>
-kse scene extract --config ./moqui-config.json --type entities --pattern crud --out ./templates --json
-kse scene extract --config ./moqui-config.json --dry-run --json
+sce scene extract --config <path> --out <dir>
+sce scene extract --config ./moqui-config.json --type entities --pattern crud --out ./templates --json
+sce scene extract --config ./moqui-config.json --dry-run --json
 ```
 
 ### Configuration File
@@ -190,30 +190,30 @@ One-stop workflow: validate → lint → score → preview → publish.
 
 ```bash
 # Full pipeline
-kse scene contribute --package <path>
+sce scene contribute --package <path>
 
 # With registry target
-kse scene contribute --package ./my-package --registry ./registry --json
+sce scene contribute --package ./my-package --registry ./registry --json
 
 # Dry-run (preview only)
-kse scene contribute --package ./my-package --dry-run
+sce scene contribute --package ./my-package --dry-run
 
 # Skip lint step
-kse scene contribute --package ./my-package --skip-lint --json
+sce scene contribute --package ./my-package --skip-lint --json
 ```
 
 ### CLI Commands
 
 ```bash
 # Lint
-kse scene lint --package <path>
-kse scene lint --package ./my-package --json
-kse scene lint --package ./my-package --strict
+sce scene lint --package <path>
+sce scene lint --package ./my-package --json
+sce scene lint --package ./my-package --strict
 
 # Score
-kse scene score --package <path>
-kse scene score --package ./my-package --json
-kse scene score --package ./my-package --strict
+sce scene score --package <path>
+sce scene score --package ./my-package --json
+sce scene score --package ./my-package --strict
 ```
 
 ---
@@ -301,36 +301,36 @@ Quality scoring bonus dimension (max +10 points) based on:
 
 ```bash
 # Show ontology graph
-kse scene ontology show --package <path>
-kse scene ontology show --package ./my-package --json
+sce scene ontology show --package <path>
+sce scene ontology show --package ./my-package --json
 
 # Query dependency chain
-kse scene ontology deps --package <path> --ref <node-ref>
-kse scene ontology deps --package ./my-package --ref entity:Order --json
+sce scene ontology deps --package <path> --ref <node-ref>
+sce scene ontology deps --package ./my-package --ref entity:Order --json
 
 # Query reverse impact radius
-kse scene ontology impact --package <path> --ref <node-ref>
-kse scene ontology impact --package ./my-package --ref service:createOrder --relation depends_on,composes --max-depth 2 --json
+sce scene ontology impact --package <path> --ref <node-ref>
+sce scene ontology impact --package ./my-package --ref service:createOrder --relation depends_on,composes --max-depth 2 --json
 
 # Query shortest relation path between two refs
-kse scene ontology path --package <path> --from <source-ref> --to <target-ref>
-kse scene ontology path --package ./my-package --from service:createOrder --to entity:Order --undirected --json
+sce scene ontology path --package <path> --from <source-ref> --to <target-ref>
+sce scene ontology path --package ./my-package --from service:createOrder --to entity:Order --undirected --json
 
 # Validate graph (dangling edges, cycles)
-kse scene ontology validate --package <path>
-kse scene ontology validate --package ./my-package --json
+sce scene ontology validate --package <path>
+sce scene ontology validate --package ./my-package --json
 
 # Show action abstraction
-kse scene ontology actions --package <path>
-kse scene ontology actions --package ./my-package --ref service:createOrder --json
+sce scene ontology actions --package <path>
+sce scene ontology actions --package ./my-package --ref service:createOrder --json
 
 # Show data lineage
-kse scene ontology lineage --package <path>
-kse scene ontology lineage --package ./my-package --ref entity:Order --json
+sce scene ontology lineage --package <path>
+sce scene ontology lineage --package ./my-package --ref entity:Order --json
 
 # Show agent hints
-kse scene ontology agent-info --package <path>
-kse scene ontology agent-info --package ./my-package --json
+sce scene ontology agent-info --package <path>
+sce scene ontology agent-info --package ./my-package --json
 ```
 
 ---
@@ -339,7 +339,7 @@ kse scene ontology agent-info --package ./my-package --json
 
 - [Command Reference](command-reference.md) — Complete CLI command documentation
 - [Architecture](architecture.md) — System architecture overview
-- [Developer Guide](developer-guide.md) — Contributing and extending kse
+- [Developer Guide](developer-guide.md) — Contributing and extending sce
 
 ---