scene-capability-engine 3.0.0 → 3.0.2

package/docs/README.md

@@ -1,6 +1,6 @@
-# kse Documentation Index
+# sce Documentation Index
 
-> Complete guide to kse (Kiro Spec Engine)
+> Complete guide to sce (Scene Capability Engine)
 
 ---
 
@@ -11,30 +11,30 @@
 
 ## 🚀 Getting Started
 
-**New to kse?** Start here:
+**New to sce?** Start here:
 
 - **[Quick Start Guide](quick-start.md)** - Get up and running in 5 minutes
 - **[FAQ](faq.md)** - Frequently asked questions
 - **[Troubleshooting](troubleshooting.md)** - Common issues and solutions
 
-## ⭐ Why Teams Choose kse
+## ⭐ Why Teams Choose sce
 
 - **Structured AI delivery**: Specs enforce Requirements → Design → Tasks before implementation.
 - **Parallel execution at scale**: Orchestrate multiple Specs with dependency-aware scheduling.
-- **Dual-track handoff closure**: `kse auto handoff run` executes plan/queue/batch/observability in one closed loop, supports `--continue-from` resume, and emits executable follow-up recommendations.
+- **Dual-track handoff closure**: `sce auto handoff run` executes plan/queue/batch/observability in one closed loop, supports `--continue-from` resume, and emits executable follow-up recommendations.
 - **Measurable outcomes**: KPI snapshot/baseline/trend commands make delivery quality auditable.
-- **Tool-agnostic workflow**: Works across Claude, Cursor, Windsurf, Copilot, and Kiro.
+- **Tool-agnostic workflow**: Works across Claude, Cursor, Windsurf, Copilot, and SCE.
 - **Built-in governance**: Locks, document governance, environment/workspace controls, and audit trails.
 
 ---
 
 ## 📖 Core Concepts
 
-Understand how kse works:
+Understand how sce works:
 
 - **[Spec Workflow](spec-workflow.md)** - Understanding the Spec-driven development process
-- **[Integration Modes](integration-modes.md)** - Three ways to integrate kse with AI tools
-- **[Command Reference](command-reference.md)** - Complete list of all kse commands
+- **[Integration Modes](integration-modes.md)** - Three ways to integrate sce with AI tools
+- **[Command Reference](command-reference.md)** - Complete list of all sce commands
 
 ---
 
@@ -43,18 +43,18 @@ Understand how kse works:
 Choose your AI tool and learn how to integrate:
 
 ### Native Integration
-- **[Kiro IDE Guide](tools/kiro-guide.md)** - Fully automatic integration
+- **[AI IDE Guide](tools/SCE-guide.md)** - Fully automatic integration
 
 ### Manual Export Integration
-- **[Cursor Guide](tools/cursor-guide.md)** - Using kse with Cursor IDE
-- **[Claude Code Guide](tools/claude-guide.md)** - Using kse with Claude Code
-- **[VS Code + Copilot Guide](tools/vscode-guide.md)** - Using kse with VS Code and GitHub Copilot
+- **[Cursor Guide](tools/cursor-guide.md)** - Using sce with Cursor IDE
+- **[Claude Code Guide](tools/claude-guide.md)** - Using sce with Claude Code
+- **[VS Code + Copilot Guide](tools/vscode-guide.md)** - Using sce with VS Code and GitHub Copilot
 
 ### Watch Mode Integration
-- **[Windsurf Guide](tools/windsurf-guide.md)** - Using kse with Windsurf (supports watch mode)
+- **[Windsurf Guide](tools/windsurf-guide.md)** - Using sce with Windsurf (supports watch mode)
 
 ### Universal Integration
-- **[Generic AI Tools Guide](tools/generic-guide.md)** - Using kse with any AI tool
+- **[Generic AI Tools Guide](tools/generic-guide.md)** - Using sce with any AI tool
 
 ---
 
@@ -86,14 +86,14 @@ Learn by example with complete Spec demonstrations:
 
 Detailed technical documentation:
 
-- **[Command Reference](command-reference.md)** - All kse commands with examples
+- **[Command Reference](command-reference.md)** - All sce commands with examples
 - **[Environment Management Guide](environment-management-guide.md)** - Multi-environment configuration management
 - **[Multi-Repository Management Guide](multi-repo-management-guide.md)** - Managing multiple Git repositories
 - **[Value Observability Guide](value-observability-guide.md)** - KPI snapshot, baseline, trend, and gate evidence workflow
 - **[Scene Runtime Guide](scene-runtime-guide.md)** - Scene template engine, quality pipeline, ontology, and Moqui ERP integration
-- **[Moqui Template Core Library Playbook](moqui-template-core-library-playbook.md)** - Default-gated intake flow for absorbing Moqui capabilities into KSE templates
-- **[331-poc Dual-Track Integration Guide](331-poc-dual-track-integration-guide.md)** - Handoff contract and integration playbook between 331-poc and kse
-- **[331-poc Adaptation Roadmap](331-poc-adaptation-roadmap.md)** - Ongoing KSE-side adaptation backlog and rollout phases
+- **[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
 - **[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
@@ -102,8 +102,8 @@ Detailed technical documentation:
 
 ## 📋 Additional Guides
 
-- **[Adoption Guide](adoption-guide.md)** - Adopting kse in existing projects
-- **[Upgrade Guide](upgrade-guide.md)** - Upgrading kse to newer versions
+- **[Adoption Guide](adoption-guide.md)** - Adopting sce in existing projects
+- **[Upgrade Guide](upgrade-guide.md)** - Upgrading sce to newer versions
 - **[Release Checklist](release-checklist.md)** - Repeatable pre-release verification flow
 - **[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
@@ -112,8 +112,8 @@ Detailed technical documentation:
 - **[Multi-Repository Management Guide](multi-repo-management-guide.md)** - Managing multiple Git repositories
 - **[Scene Runtime Guide](scene-runtime-guide.md)** - Scene template engine, quality pipeline, ontology, and Moqui ERP integration
 - **[Multi-Agent Coordination Guide](multi-agent-coordination-guide.md)** - Multi-agent parallel coordination for concurrent development
-- **[Developer Guide](developer-guide.md)** - Contributing to kse development
-- **[Architecture](architecture.md)** - kse system architecture
+- **[Developer Guide](developer-guide.md)** - Contributing to sce development
+- **[Architecture](architecture.md)** - sce system architecture
 
 ---
 
@@ -139,7 +139,7 @@ Detailed technical documentation:
 4. [Troubleshooting](troubleshooting.md) - Solve problems
 
 ### For Advanced Users
-1. [Developer Guide](developer-guide.md) - Contribute to kse
+1. [Developer Guide](developer-guide.md) - Contribute to sce
 2. [Architecture](architecture.md) - Understand internals
 3. [Manual Workflows Guide](manual-workflows-guide.md) - Advanced workflows
 

package/docs/adopt-migration-guide.md

@@ -21,10 +21,10 @@ This guide helps users transition from the old interactive adoption mode to the
 
 ### Old Behavior (v1.8.x and earlier)
 
-The `kse adopt` command was **interactive** and required user input:
+The `sce adopt` command was **interactive** and required user input:
 
 ```bash
-$ kse adopt
+$ sce adopt
 
 📦 Analyzing project structure...
 
@@ -51,12 +51,12 @@ $ kse adopt
 
 ### New Behavior (v1.9.0+)
 
-The `kse adopt` command is now **smart and automatic**:
+The `sce adopt` command is now **smart and automatic**:
 
 ```bash
-$ kse adopt
+$ sce adopt
 
-🔥 Kiro Spec Engine - Project Adoption
+🔥 Scene Capability Engine - Project Adoption
 
 📦 Analyzing project structure... ✅
 📋 Creating adoption plan... ✅
@@ -82,7 +82,7 @@ Adoption Plan:
   Preserved: 3 specs, 2 custom files
   
 💡 Your original files are safely backed up.
-   To restore: kse rollback backup-20260128-143022
+   To restore: sce rollback backup-20260128-143022
 ```
 
 **Characteristics**:
@@ -162,15 +162,15 @@ Automatic resolution based on file type:
 **Old Behavior**:
 ```bash
 # Backup was optional
-kse adopt              # No backup
-kse adopt --backup     # With backup
+sce adopt              # No backup
+sce adopt --backup     # With backup
 ```
 
 **New Behavior**:
 ```bash
 # Backup is mandatory
-kse adopt              # Always creates backup
-kse adopt --no-backup  # Requires confirmation (dangerous)
+sce adopt              # Always creates backup
+sce adopt --no-backup  # Requires confirmation (dangerous)
 ```
 
 ---
@@ -179,26 +179,26 @@ kse adopt --no-backup  # Requires confirmation (dangerous)
 
 ### For Individual Users
 
-**Step 1**: Upgrade KSE
+**Step 1**: Upgrade sce
 ```bash
-npm install -g kiro-spec-engine@latest
+npm install -g scene-capability-engine@latest
 ```
 
 **Step 2**: Test with dry-run (optional)
 ```bash
 cd your-project
-kse adopt --dry-run
+sce adopt --dry-run
 ```
 
 **Step 3**: Run adoption
 ```bash
-kse adopt
+sce adopt
 ```
 
 **Step 4**: Verify results
 ```bash
-kse status
-kse version-info
+sce status
+sce version-info
 ```
 
 ### For Teams
@@ -211,8 +211,8 @@ kse version-info
 **Step 2**: Test on non-critical project
 ```bash
 cd test-project
-kse adopt --dry-run
-kse adopt
+sce adopt --dry-run
+sce adopt
 ```
 
 **Step 3**: Roll out gradually
@@ -232,16 +232,16 @@ kse adopt
 **Old Script**:
 ```bash
 # Old: Required --auto flag
-kse adopt --auto
+sce adopt --auto
 ```
 
 **New Script**:
 ```bash
 # New: No flag needed (already automatic)
-kse adopt
+sce adopt
 
 # Or with verbose logging
-kse adopt --verbose
+sce adopt --verbose
 ```
 
 ---
@@ -261,7 +261,7 @@ You might prefer interactive mode if:
 Simply add the `--interactive` flag:
 
 ```bash
-kse adopt --interactive
+sce adopt --interactive
 ```
 
 This enables the old behavior:
@@ -272,7 +272,7 @@ This enables the old behavior:
 ### Example
 
 ```bash
-$ kse adopt --interactive
+$ sce adopt --interactive
 
 📦 Analyzing project structure...
 
@@ -301,7 +301,7 @@ $ kse adopt --interactive
 
 **A**: Use the `--interactive` flag:
 ```bash
-kse adopt --interactive
+sce adopt --interactive
 ```
 
 ---
@@ -320,12 +320,12 @@ kse adopt --interactive
 
 **A**: You can easily rollback:
 ```bash
-kse rollback backup-20260128-143022
+sce rollback backup-20260128-143022
 ```
 
 Then use interactive mode:
 ```bash
-kse adopt --interactive
+sce adopt --interactive
 ```
 
 ---
@@ -334,7 +334,7 @@ kse adopt --interactive
 
 **A**: Use dry-run mode:
 ```bash
-kse adopt --dry-run
+sce adopt --dry-run
 ```
 
 ---
@@ -343,7 +343,7 @@ kse adopt --dry-run
 
 **A**: Yes, use the `--force` flag:
 ```bash
-kse adopt --force
+sce adopt --force
 ```
 
 This will:
@@ -375,7 +375,7 @@ This will:
 
 For more details, use verbose mode:
 ```bash
-kse adopt --verbose
+sce adopt --verbose
 ```
 
 ---
@@ -384,7 +384,7 @@ kse adopt --verbose
 
 **A**: Not recommended, but possible:
 ```bash
-kse adopt --no-backup
+sce adopt --no-backup
 ```
 
 ⚠️ **Warning**: This is dangerous and requires confirmation.
@@ -403,12 +403,12 @@ kse adopt --no-backup
 
 **Old**:
 ```bash
-kse adopt --auto
+sce adopt --auto
 ```
 
 **New**:
 ```bash
-kse adopt
+sce adopt
 ```
 
 ---
@@ -430,7 +430,7 @@ Problem: Unable to create backup
 Solutions:
   1. Free up disk space
   2. Check permissions
-  3. Run kse doctor
+  3. Run sce doctor
 ```
 
 ---
@@ -442,7 +442,7 @@ Solutions:
 ```bash
 for dir in project1 project2 project3; do
   cd $dir
-  kse adopt
+  sce adopt
   cd ..
 done
 ```
@@ -452,7 +452,7 @@ done
 ### Q: How do I report issues?
 
 **A**: 
-1. Run with verbose mode: `kse adopt --verbose`
+1. Run with verbose mode: `sce adopt --verbose`
 2. Check the logs
 3. Report at: https://github.com/heguangyong/scene-capability-engine/issues
 
@@ -464,7 +464,7 @@ done
 
 **Solution**: Use interactive mode:
 ```bash
-kse adopt --interactive
+sce adopt --interactive
 ```
 
 ---
@@ -473,7 +473,7 @@ kse adopt --interactive
 
 **Solution**: Use verbose mode:
 ```bash
-kse adopt --verbose
+sce adopt --verbose
 ```
 
 ---
@@ -482,7 +482,7 @@ kse adopt --verbose
 
 **Solution**: Use rollback:
 ```bash
-kse rollback backup-20260128-143022
+sce rollback backup-20260128-143022
 ```
 
 ---
@@ -493,7 +493,7 @@ kse rollback backup-20260128-143022
 
 1. Rollback immediately:
    ```bash
-   kse rollback backup-20260128-143022
+   sce rollback backup-20260128-143022
    ```
 
 2. Report the issue:
@@ -510,8 +510,8 @@ kse rollback backup-20260128-143022
 Always test on a non-critical project first:
 ```bash
 cd test-project
-kse adopt --dry-run
-kse adopt
+sce adopt --dry-run
+sce adopt
 ```
 
 ### 2. Use Version Control
@@ -519,8 +519,8 @@ kse adopt
 Commit before adopting:
 ```bash
 git add -A
-git commit -m "Before KSE v1.9.0 adoption"
-kse adopt
+git commit -m "Before sce v1.9.0 adoption"
+sce adopt
 ```
 
 ### 3. Keep Backups
@@ -535,8 +535,8 @@ ls .kiro/backups/
 
 After adoption, verify:
 ```bash
-kse status
-kse version-info
+sce status
+sce version-info
 npm test  # If you have tests
 ```
 
@@ -567,22 +567,22 @@ If you customize files, document it:
 For most users:
 ```bash
 # Just run it!
-kse adopt
+sce adopt
 ```
 
 For cautious users:
 ```bash
 # Preview first
-kse adopt --dry-run
+sce adopt --dry-run
 
 # Then apply
-kse adopt
+sce adopt
 ```
 
 For advanced users:
 ```bash
 # Use interactive mode
-kse adopt --interactive
+sce adopt --interactive
 ```
 
 ---
@@ -590,8 +590,8 @@ kse adopt --interactive
 ## Getting Help
 
 - **Documentation**: [Adoption Guide](adoption-guide.md)
-- **System Check**: `kse doctor`
-- **Version Info**: `kse version-info`
+- **System Check**: `sce doctor`
+- **Version Info**: `sce version-info`
 - **Issues**: https://github.com/heguangyong/scene-capability-engine/issues
 
 ---