scene-capability-engine 3.6.36 → 3.6.37

package/CHANGELOG.md

@@ -1,4 +1,4 @@
-# Changelog
+# Changelog
 
 All notable changes to this project will be documented in this file.
 
@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.6.37] - 2026-03-12
+
+### Added
+- Added explicit release-environment guidance that clarifies this project publishes only from `v*` tag pushes, requires GitHub Actions secret `NPM_TOKEN`, and must bump `package.json.version` before tagging.
+- Added release notes for `v3.6.37` under `docs/releases/` and `docs/zh/releases/`.
+
+### Changed
+- Removed legacy `kse` command/content references across active code paths, templates, fixtures, watch configuration, version metadata, steering, and release documentation without preserving compatibility aliases.
+- Renamed the multi-workspace directory validation API from `isValidKseDirectory` to `isValidSceDirectory` and updated the related tests.
+- Renamed historical spec/template fixture paths from `kse` identifiers to `sce` identifiers, including scene package template IDs and spec-scene override references.
+- Updated the branding consistency gate to fail on legacy `kse` aliases and stale social handles instead of allowing them to linger in tracked content.
+- Fixed `scripts/git-managed-gate.js` on Windows by falling back to `git.cmd` / `git.exe` resolution, so `prepublishOnly` and release preflight no longer misreport a valid repository as missing git metadata.
+
 ### Added
 - Added `lib/auto/handoff-release-gate-history-loaders-service.js` for release-gate history entry normalization, report discovery, seed loading, and merge selection.
 - Added `lib/auto/handoff-run-service.js` for full auto-handoff orchestration outside the command layer.
@@ -278,7 +291,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `state-reconcile-<tag>.json`
 
 ### Changed
-- Release workflow state reconciliation gate is now enforce-by-default (`KSE_RELEASE_STATE_MIGRATION_ENFORCE` defaults to `true`).
+- Release workflow state reconciliation gate is now enforce-by-default (`SCE_RELEASE_STATE_MIGRATION_ENFORCE` defaults to `true`).
 - Release workflow Node runtime updated to `22.x` so sqlite-backed reconciliation can run in release pipeline.
 
 ## [3.6.7] - 2026-03-05
@@ -856,7 +869,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Interactive runtime policy + work-order default pipeline**: Added `interactive-runtime-policy-evaluate` and `interactive-work-order-build`, integrated both into `interactive-customization-loop` and `interactive-flow` (including `sce scene interactive-loop/interactive-flow` passthrough), with default `runtime_mode=ops-fix`, `runtime_environment=staging`, runtime non-allow fail gate option, and auditable work-order artifacts.
 - **Release weekly ops closed-loop summary**: Added `node scripts/release-ops-weekly-summary.js` (npm alias `npm run report:release-ops-weekly`) to aggregate handoff evidence, release-gate history, interactive governance, and matrix signals into one weekly risk/recommendation card (`weekly-ops-summary.json|.md`).
 - **Release workflow weekly ops asset publication**: `release.yml` now exports and publishes `weekly-ops-summary-<tag>.json|.md` alongside governance snapshot and Moqui release evidence assets.
-- **Release weekly ops hard gate**: Added `node scripts/release-weekly-ops-gate.js` (npm alias `npm run gate:release-ops-weekly`) and wired release workflow defaults to block publish when weekly ops summary risk exceeds `medium` (configurable via `KSE_RELEASE_WEEKLY_OPS_*` variables).
+- **Release weekly ops hard gate**: Added `node scripts/release-weekly-ops-gate.js` (npm alias `npm run gate:release-ops-weekly`) and wired release workflow defaults to block publish when weekly ops summary risk exceeds `medium` (configurable via `SCE_RELEASE_WEEKLY_OPS_*` variables).
 - **Unified weekly+drift remediation bundle**: Added `node scripts/release-risk-remediation-bundle.js` (npm alias `npm run report:release-risk-remediation`) and wired release workflow to publish `release-risk-remediation-<tag>.json|.md|.lines` assets derived from merged gate signals.
 - **Release asset integrity hard gate**: Added `node scripts/release-asset-integrity-check.js` (npm alias `npm run gate:release-asset-integrity`) and wired `release.yml` to block publish on missing/empty core release-evidence assets, while exporting `release-asset-integrity-<tag>.json|.md`.
 - **Interactive dialogue governance baseline**: Added `node scripts/interactive-dialogue-governance.js`, baseline policy `docs/interactive-customization/dialogue-governance-policy-baseline.json`, and loop/flow integration so embedded assistants emit `allow|clarify|deny` dialogue decisions with clarification prompts before planning.
@@ -878,7 +891,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Interactive matrix signal closed-loop defaultization**: `interactive-flow` now runs a default matrix snapshot stage (`moqui-template-baseline-report`) after loop execution, persists session matrix artifacts, appends `.sce/reports/interactive-matrix-signals.jsonl`, and exposes matrix controls (`--no-matrix`, thresholds, compare baseline, signal path, fail-on-portfolio/regression/error) in both script and `sce scene interactive-flow`.
 - **Interactive approval workflow state machine**: Added `node scripts/interactive-approval-workflow.js` (status alias `npm run report:interactive-approval-status`) covering `draft/submitted/approved/rejected/executed/verified/archived` transitions, with high-risk execute blocking and append-only approval event audit JSONL.
 - **Interactive Moqui adapter stage-C baseline**: Added `lib/interactive-customization/moqui-interactive-adapter.js` plus `node scripts/interactive-moqui-adapter.js` (alias `npm run report:interactive-adapter-capabilities`) to implement unified adapter contract `capabilities/plan/validate/apply/rollback`, low-risk one-click apply (`low-risk-apply`), policy-aware controlled execution, and append-only execution records with validation snapshot + rollback reference.
-- **Interactive template matrix stage-D baseline**: Added `kse.scene--moqui-interactive-customization-loop--0.1.0` scene package assets (scene-package/scene manifest/template manifest), plus template sedimentation playbook, adapter extension contract schema/sample, and Domain_Pack extension flow docs for cross-stack replication.
+- **Interactive template matrix stage-D baseline**: Added `sce.scene--moqui-interactive-customization-loop--0.1.0` scene package assets (scene-package/scene manifest/template manifest), plus template sedimentation playbook, adapter extension contract schema/sample, and Domain_Pack extension flow docs for cross-stack replication.
 - **Interactive governance observability + alerting**: Added `node scripts/interactive-governance-report.js` (alias `npm run report:interactive-governance`) to compute adoption/success/rollback/security-intercept/satisfaction KPIs, apply threshold alerts, and emit JSON/Markdown governance reports with `--fail-on-alert` gate behavior.
 - **Interactive governance matrix telemetry integration**: `interactive-governance-report` now consumes matrix signals by default, computes matrix pass/regression/stage-error metrics, and enforces threshold alerts for matrix trend degradation.
 - **Matrix regression gate + remediation queue automation**: Added `scripts/matrix-regression-gate.js` and `scripts/moqui-matrix-remediation-queue.js` with npm aliases (`gate:matrix-regression`, `report:matrix-remediation-queue`) so CI/release can enforce configurable regression limits and export close-loop remediation lines from matrix regressions.
@@ -901,8 +914,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Capability matrix recommendations upgrade**: `sce auto handoff capability-matrix` now also recommends baseline-driven phased one-shot remediation commands when Moqui matrix regressions appear in baseline trend comparison.
 - **Handoff profile policy abstraction (`default|moqui|enterprise`)**: `sce auto handoff run` and `sce auto handoff capability-matrix` now support `--profile` preset policies with explicit option override precedence, plus external integration contract guidance in `docs/handoff-profile-integration-guide.md`.
 - **Regression/governance recommendation unification**: `sce auto handoff regression`, `sce auto governance stats`, and governance close-loop release-gate blockers now include baseline-driven phased one-shot remediation guidance for Moqui matrix regressions.
-- **Release workflow matrix evidence hardening**: `test.yml` and `release.yml` now archive matrix/governance artifacts by default and support configurable matrix regression hard-gate controls via `KSE_MATRIX_REGRESSION_GATE_ENFORCE` + `KSE_MATRIX_REGRESSION_GATE_MAX`.
-- **Release workflow Moqui summary alignment**: `release.yml` now explicitly generates and publishes `moqui-release-summary.{json,md}` from baseline + interactive governance + evidence inputs, with optional hard-gate flag `KSE_MOQUI_RELEASE_SUMMARY_ENFORCE`.
+- **Release workflow matrix evidence hardening**: `test.yml` and `release.yml` now archive matrix/governance artifacts by default and support configurable matrix regression hard-gate controls via `SCE_MATRIX_REGRESSION_GATE_ENFORCE` + `SCE_MATRIX_REGRESSION_GATE_MAX`.
+- **Release workflow Moqui summary alignment**: `release.yml` now explicitly generates and publishes `moqui-release-summary.{json,md}` from baseline + interactive governance + evidence inputs, with optional hard-gate flag `SCE_MOQUI_RELEASE_SUMMARY_ENFORCE`.
 - **Release governance snapshot standalone assets**: Added `scripts/release-governance-snapshot-export.js` and wired `release.yml` to publish `governance-snapshot-<tag>.json|.md` as independent governance audit artifacts (with unavailable placeholders when evidence summary is missing).
 - **331-poc integration checklist baseline**: Added `docs/interactive-customization/331-poc-sce-integration-checklist.md` to define minimal runtime contract, default commands, gate defaults, and pass criteria for Moqui + SCE deployment.
 - **Interactive feedback ingestion helper**: Added `node scripts/interactive-feedback-log.js` (alias `npm run log:interactive-feedback`) to append structured business-user feedback events into `.sce/reports/interactive-user-feedback.jsonl` for governance sample coverage and trend stability.
@@ -1285,7 +1298,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [1.39.0] - 2026-02-10
 
 ### Added
-- **Moqui ERP Adapter**: Integrate Moqui ERP instance into KSE scene runtime
+- **Moqui ERP Adapter**: Integrate Moqui ERP instance into SCE scene runtime
   - `MoquiClient` — HTTP client with JWT auth lifecycle (login, refresh, re-login, logout), retry logic using Node.js built-in `http`/`https`
   - `MoquiAdapter` — Binding handler for `spec.erp.*` and `moqui.*` refs, entity CRUD, service invocation, screen discovery
   - `sce scene connect` — Test connectivity and authentication to Moqui ERP instance
@@ -2089,7 +2102,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Template management: `sce templates update`, `sce templates cache`, `sce templates guide`
   - Custom sources: `sce templates add-source <name> <url>`, `sce templates remove-source <name>`, `sce templates sources`
   - Create Spec from template: `sce spec create <name> --template <template-id>`
-  - Local caching for offline use (~/.kse/templates/)
+  - Local caching for offline use (~/.sce/templates/)
   - Multi-source support with conflict resolution (source:template-id format)
   - Automatic variable substitution ({{SPEC_NAME}}, {{DATE}}, {{AUTHOR}}, etc.)
   - YAML frontmatter removal in applied templates
@@ -2186,10 +2199,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - **Multi-user support**: Detects and respects `contexts/` multi-user collaboration setup
   - Differential backup: Only backs up violating files/directories (not entire .sce/)
   - Backup location: `.sce/backups/steering-cleanup-{timestamp}/`
-  - Version-based caching (~/.kse/steering-check-cache.json) to avoid repeated checks
+  - Version-based caching (~/.sce/steering-check-cache.json) to avoid repeated checks
   - Performance target: <50ms per check
   - Clear progress messages during auto-fix
-  - Bypass options: `--skip-steering-check` flag and `KSE_SKIP_STEERING_CHECK` environment variable
+  - Bypass options: `--skip-steering-check` flag and `SCE_SKIP_STEERING_CHECK` environment variable
   - Force check option: `--force-steering-check` flag
   - Comprehensive documentation in `.sce/README.md`
 
@@ -2227,7 +2240,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Critical Principle**: Added "测试失败零容忍原则" (Zero Tolerance for Test Failures) to CORE_PRINCIPLES.md
   - Emphasizes "千里之堤溃于蚁穴" - never ignore any test failure
   - Provides clear execution standards and rationale
-  - Aligns with Ultrawork spirit and KSE core values
+  - Aligns with Ultrawork spirit and SCE core values
 
 ### Changed
 - **Documentation Optimization**: Refactored CORE_PRINCIPLES.md for clarity and value density
@@ -2414,7 +2427,7 @@ rm -rf .sce/steering/workspaces
   - `sce workspace remove <name>` - Remove workspace from registry
   - `sce workspace info [name]` - Display workspace details
 - **Data Atomicity Architecture**
-  - Single source of truth: `~/.kse/workspace-state.json`
+  - Single source of truth: `~/.sce/workspace-state.json`
   - Atomic operations for all workspace state changes
   - Automatic migration from legacy format
   - Cross-platform path handling with PathUtils

package/bin/scene-capability-engine.js

@@ -1118,7 +1118,7 @@ async function updateProjectConfig(projectName) {
   const skipAutoTakeover = isTakeoverAutoApplySkippedCommand(args);
   const skipCheck = isNoMutationCommand(args) ||
                     args.includes('--skip-steering-check') || 
-                    process.env.KSE_SKIP_STEERING_CHECK === '1';
+                    process.env.SCE_SKIP_STEERING_CHECK === '1';
   const forceCheck = args.includes('--force-steering-check');
 
   if (!isLegacyAllowlistedCommand) {

package/docs/331-poc-adaptation-roadmap.md

@@ -54,7 +54,7 @@
    - tag 发布时自动将 release notes 草稿、evidence 审阅 markdown、summary JSON 作为 GitHub Release 资产上传。
    - 无 evidence 时至少上传 fallback notes，保证发布资产结构稳定。
 20. 新增可配置发布门禁（workflow 级）：
-   - 支持通过 `KSE_RELEASE_*` 仓库变量配置 success rate/risk/ontology 阈值。
+   - 支持通过 `SCE_RELEASE_*` 仓库变量配置 success rate/risk/ontology 阈值。
    - 支持 advisory（默认）与 enforce（阻断发布）两种模式，且门禁在 `npm publish` 前执行。
 21. 新增 release gate 审计产物：
    - 每次 tag 发布生成 `release-gate-<tag>.json`，记录阈值、观测信号、违规项和判定结果。
@@ -87,10 +87,10 @@
    - 自动检测连续 gate 失败、高风险占比过高、短期风险占比上升。
    - 在 Release Notes 中显式给出 drift alerts，提前暴露质量恶化趋势。
 31. 漂移告警阈值参数化：
-   - 支持通过 `KSE_RELEASE_DRIFT_*` 仓库变量调节 fail streak/high-risk share/delta 阈值。
+   - 支持通过 `SCE_RELEASE_DRIFT_*` 仓库变量调节 fail streak/high-risk share/delta 阈值。
    - 不同项目可按发布策略调整灵敏度，减少误报或漏报。
 32. 漂移告警阻断模式：
-   - 新增 `KSE_RELEASE_DRIFT_ENFORCE`，可在漂移告警触发时阻断发布。
+   - 新增 `SCE_RELEASE_DRIFT_ENFORCE`，可在漂移告警触发时阻断发布。
    - 保留默认 advisory 模式，确保历史数据不足时不误阻断。
 33. 漂移告警审计写回 gate 报告：
    - `release.yml` 将 drift 评估结果回写到 `release-gate-<tag>.json` 的 `drift` 字段。

package/docs/command-reference.md

@@ -1574,7 +1574,7 @@ Moqui template library lexicon audit (script-level governance helper):
 - `node scripts/moqui-lexicon-audit.js [--manifest <path>] [--template-dir <path>] [--lexicon <path>] [--out <path>] [--markdown-out <path>] [--fail-on-gap] [--json]`: audit manifest/template capability names against canonical Moqui lexicon; reports unknown aliases and uncovered expected capabilities.
   - Expected capability scope uses `manifest.capabilities` first; when empty, it infers canonical expected capabilities from `manifest.templates` and emits `expected_scope` metadata (`source`, `inferred_*`, `unresolved_templates`).
   - By default, template capability auditing is scoped to `manifest.templates` (when matched), reducing noise from unrelated templates.
-  - Template scope matching normalizes `sce.scene--*` / `kse.scene--*` prefixes, so renamed template namespaces still map correctly.
+  - Template scope matching normalizes `sce.scene--*` / `sce.scene--*` prefixes, so renamed template namespaces still map correctly.
 
 Moqui release summary helper (script-level consolidated gate view):
 - `node scripts/moqui-release-summary.js [--evidence <path>] [--baseline <path>] [--lexicon <path>] [--capability-matrix <path>] [--interactive-governance <path>] [--matrix-remediation-plan <path>] [--out <path>] [--markdown-out <path>] [--fail-on-gate-fail] [--json]`: merge handoff release-evidence + baseline + lexicon + capability-matrix + interactive-governance into one Moqui release gate summary (`passed | failed | incomplete`) with executable remediation recommendations.
@@ -2126,10 +2126,10 @@ Release workflow default:
 - Runs interactive flow smoke (`npm run test:interactive-flow-smoke`) in test/release test jobs.
 - Runs interactive governance gate by default (`interactive-governance-report --period weekly --fail-on-alert`) in test and release pipelines.
 - Evaluates matrix regression gate in CI/release with configurable policy:
-  - `KSE_MATRIX_REGRESSION_GATE_ENFORCE` (`true|false`, default advisory/disabled)
-  - `KSE_MATRIX_REGRESSION_GATE_MAX` (default `0`)
+  - `SCE_MATRIX_REGRESSION_GATE_ENFORCE` (`true|false`, default advisory/disabled)
+  - `SCE_MATRIX_REGRESSION_GATE_MAX` (default `0`)
 - Optional release summary hard-gate:
-  - `KSE_MOQUI_RELEASE_SUMMARY_ENFORCE` (`true|false`, default advisory/disabled)
+  - `SCE_MOQUI_RELEASE_SUMMARY_ENFORCE` (`true|false`, default advisory/disabled)
 - Publishes `moqui-template-baseline.json` + `moqui-template-baseline.md` as release assets.
 - Publishes `moqui-release-summary.json` + `moqui-release-summary.md` as release review assets.
 - Publishes `interactive-governance-<tag>.json` + `interactive-governance-<tag>.md` as release evidence assets.
@@ -2138,7 +2138,7 @@ Release workflow default:
 - Evaluates weekly ops risk gate by default (`release-weekly-ops-gate`; default block when `risk > medium` or summary missing).
 - Publishes `release-risk-remediation-<tag>.json|.md|.lines` derived from unified weekly+drift gate signals.
 - Evaluates and publishes release asset integrity audit (`release-asset-integrity-<tag>.json|.md`) before `npm publish`.
-- Enforces baseline portfolio gate by default (`KSE_MOQUI_BASELINE_ENFORCE` defaults to `true` when unset).
+- Enforces baseline portfolio gate by default (`SCE_MOQUI_BASELINE_ENFORCE` defaults to `true` when unset).
 
 ### Moqui ERP Integration
 

package/docs/faq.md

@@ -682,7 +682,7 @@ sce spec bootstrap --name 03-00-ci-cd-pipeline --non-interactive
 **Ask the community:**
 - GitHub Discussions: https://github.com/heguangyong/scene-capability-engine/discussions
 - Discord: [Join our Discord](https://discord.gg/sce)
-- Twitter: [@kse_dev](https://twitter.com/kse_dev)
+- Twitter: [@sce_dev](https://twitter.com/sce_dev)
 
 **Report issues:**
 - GitHub Issues: https://github.com/heguangyong/scene-capability-engine/issues

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

@@ -71,9 +71,9 @@ node scripts/matrix-regression-gate.js \
 
 Recommended GitHub Variables:
 
-- `KSE_MATRIX_REGRESSION_GATE_ENFORCE=true`
-- `KSE_MATRIX_REGRESSION_GATE_MAX=0`
-- `KSE_MOQUI_RELEASE_SUMMARY_ENFORCE=true` (optional hard gate for release summary `failed` state)
+- `SCE_MATRIX_REGRESSION_GATE_ENFORCE=true`
+- `SCE_MATRIX_REGRESSION_GATE_MAX=0`
+- `SCE_MOQUI_RELEASE_SUMMARY_ENFORCE=true` (optional hard gate for release summary `failed` state)
 
 Security baseline:
 

package/docs/interactive-customization/moqui-interactive-template-playbook.md

@@ -20,10 +20,10 @@ This playbook defines how to turn validated Moqui interactive customization flow
 
 Primary package for the interactive loop:
 
-- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
-- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
-- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/custom/scene.yaml`
-- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/template.manifest.json`
+- `.sce/templates/scene-packages/sce.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
+- `.sce/templates/scene-packages/sce.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
+- `.sce/templates/scene-packages/sce.scene--moqui-interactive-customization-loop--0.1.0/custom/scene.yaml`
+- `.sce/templates/scene-packages/sce.scene--moqui-interactive-customization-loop--0.1.0/template.manifest.json`
 
 ## Capability Matrix Mapping
 

package/docs/interactive-customization/phase-acceptance-evidence.md

@@ -90,8 +90,8 @@ Scope:
 
 Evidence:
 
-- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
-- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
+- `.sce/templates/scene-packages/sce.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
+- `.sce/templates/scene-packages/sce.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
 - `docs/interactive-customization/moqui-interactive-template-playbook.md`
 - `docs/interactive-customization/adapter-extension-contract.schema.json`
 - `docs/interactive-customization/domain-pack-extension-flow.md`

package/docs/moqui-standard-rebuild-guide.md

@@ -84,12 +84,12 @@ Defaults: `ready>=6`, `partial<=0`, `gap<=0`.
 
 ## Default Moqui Template Matrix
 
-- `kse.scene--moqui-entity-model-core--0.1.0`
-- `kse.scene--moqui-service-contract-core--0.1.0`
-- `kse.scene--moqui-screen-flow-core--0.1.0`
-- `kse.scene--moqui-form-interaction-core--0.1.0`
-- `kse.scene--moqui-rule-decision-core--0.1.0`
-- `kse.scene--moqui-page-copilot-dialog--0.1.0`
+- `sce.scene--moqui-entity-model-core--0.1.0`
+- `sce.scene--moqui-service-contract-core--0.1.0`
+- `sce.scene--moqui-screen-flow-core--0.1.0`
+- `sce.scene--moqui-form-interaction-core--0.1.0`
+- `sce.scene--moqui-rule-decision-core--0.1.0`
+- `sce.scene--moqui-page-copilot-dialog--0.1.0`
 
 ## Next Step for Business Project
 

package/docs/moqui-template-core-library-playbook.md

@@ -201,7 +201,7 @@ sce auto close-loop-batch .sce/auto/ontology-remediation.lines --format lines --
 
 Stage-D baseline package for the interactive business customization loop:
 
-- `kse.scene--moqui-interactive-customization-loop--0.1.0`
+- `sce.scene--moqui-interactive-customization-loop--0.1.0`
 
 This package captures:
 

package/docs/release-checklist.md

@@ -115,41 +115,48 @@ Verify:
 
 Ensure:
 
+- Release automation is tag-driven, not commit-driven:
+  - `.github/workflows/release.yml` only triggers on `push.tags: v*`
+  - plain `git push` runs normal CI and does not publish npm/GitHub release
+- GitHub Actions publish prerequisites are in place:
+  - repository secret `NPM_TOKEN` must exist and remain valid for `npm publish --access public`
+  - `GITHUB_TOKEN` is used by workflow for release asset/readback steps
 - `package.json` version is correct.
+- `package.json` version must be greater than the currently published npm version.
 - `CHANGELOG.md` includes release-relevant entries.
 - Release notes draft exists (for example `docs/releases/vX.Y.Z.md`).
 - Optional: configure release evidence gate with repository variables (`Settings -> Secrets and variables -> Actions -> Variables`):
-  - `KSE_RELEASE_GATE_ENFORCE`: `true|false` (default advisory, non-blocking)
-  - `KSE_RELEASE_GATE_REQUIRE_EVIDENCE`: require `handoff-runs.json` summary
-  - `KSE_RELEASE_GATE_REQUIRE_GATE_PASS`: require evidence gate `passed=true` (default true when evidence exists)
-  - `KSE_RELEASE_GATE_MIN_SPEC_SUCCESS_RATE`: minimum allowed success rate percent
-  - `KSE_RELEASE_GATE_MAX_RISK_LEVEL`: `low|medium|high|unknown` (default `unknown`)
-  - `KSE_RELEASE_GATE_MAX_UNMAPPED_RULES`: maximum allowed unmapped ontology business rules
-  - `KSE_RELEASE_GATE_MAX_UNDECIDED_DECISIONS`: maximum allowed undecided ontology decisions
-  - `KSE_RELEASE_GATE_REQUIRE_SCENE_BATCH_PASS`: require scene package publish-batch gate passed (`true|false`, default `true`)
-  - `KSE_RELEASE_GATE_MAX_SCENE_BATCH_FAILURES`: maximum allowed scene package batch failure count (default `0`)
+  - `SCE_RELEASE_GATE_ENFORCE`: `true|false` (default advisory, non-blocking)
+  - `SCE_RELEASE_GATE_REQUIRE_EVIDENCE`: require `handoff-runs.json` summary
+  - `SCE_RELEASE_GATE_REQUIRE_GATE_PASS`: require evidence gate `passed=true` (default true when evidence exists)
+  - `SCE_RELEASE_GATE_MIN_SPEC_SUCCESS_RATE`: minimum allowed success rate percent
+  - `SCE_RELEASE_GATE_MAX_RISK_LEVEL`: `low|medium|high|unknown` (default `unknown`)
+  - `SCE_RELEASE_GATE_MAX_UNMAPPED_RULES`: maximum allowed unmapped ontology business rules
+  - `SCE_RELEASE_GATE_MAX_UNDECIDED_DECISIONS`: maximum allowed undecided ontology decisions
+  - `SCE_RELEASE_GATE_REQUIRE_SCENE_BATCH_PASS`: require scene package publish-batch gate passed (`true|false`, default `true`)
+  - `SCE_RELEASE_GATE_MAX_SCENE_BATCH_FAILURES`: maximum allowed scene package batch failure count (default `0`)
 - Optional: tune release drift alerts in release notes:
   - Drift evaluation is executed by `scripts/release-drift-evaluate.js` in CI (history load, alert calc, gate report writeback, enforce exit code).
-  - `KSE_RELEASE_DRIFT_ENFORCE`: `true|false` (default `false`), block publish when drift alerts are triggered
-  - `KSE_RELEASE_DRIFT_FAIL_STREAK_MIN`: minimum consecutive failed gates to trigger alert (default `2`)
-  - `KSE_RELEASE_DRIFT_HIGH_RISK_SHARE_MIN_PERCENT`: minimum high-risk share in latest 5 versions (default `60`)
-  - `KSE_RELEASE_DRIFT_HIGH_RISK_SHARE_DELTA_MIN_PERCENT`: minimum short-vs-long high-risk share delta (default `25`)
-  - `KSE_RELEASE_DRIFT_PREFLIGHT_BLOCK_RATE_MIN_PERCENT`: minimum release preflight blocked rate in latest 5 known runs (default `40`)
-  - `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`)
+  - `SCE_RELEASE_DRIFT_ENFORCE`: `true|false` (default `false`), block publish when drift alerts are triggered
+  - `SCE_RELEASE_DRIFT_FAIL_STREAK_MIN`: minimum consecutive failed gates to trigger alert (default `2`)
+  - `SCE_RELEASE_DRIFT_HIGH_RISK_SHARE_MIN_PERCENT`: minimum high-risk share in latest 5 versions (default `60`)
+  - `SCE_RELEASE_DRIFT_HIGH_RISK_SHARE_DELTA_MIN_PERCENT`: minimum short-vs-long high-risk share delta (default `25`)
+  - `SCE_RELEASE_DRIFT_PREFLIGHT_BLOCK_RATE_MIN_PERCENT`: minimum release preflight blocked rate in latest 5 known runs (default `40`)
+  - `SCE_RELEASE_DRIFT_HARD_GATE_BLOCK_STREAK_MIN`: minimum consecutive hard-gate preflight blocked streak (latest window, default `2`)
+  - `SCE_RELEASE_DRIFT_PREFLIGHT_UNAVAILABLE_STREAK_MIN`: minimum consecutive release preflight unavailable streak (latest window, default `2`)
 - Optional: tune weekly ops release gate:
-  - `KSE_RELEASE_WEEKLY_OPS_ENFORCE`: `true|false` (default `true`)
-  - `KSE_RELEASE_WEEKLY_OPS_REQUIRE_SUMMARY`: require weekly summary artifact (`true|false`, default `true`)
-  - `KSE_RELEASE_WEEKLY_OPS_MAX_RISK_LEVEL`: `low|medium|high|unknown` (default `medium`)
-  - `KSE_RELEASE_WEEKLY_OPS_MAX_GOVERNANCE_BREACHES`: optional max breach count
-  - `KSE_RELEASE_WEEKLY_OPS_MAX_AUTHORIZATION_TIER_BLOCK_RATE_PERCENT`: max authorization-tier deny/review block rate percent (default `40`)
-  - `KSE_RELEASE_WEEKLY_OPS_MAX_DIALOGUE_AUTHORIZATION_BLOCK_RATE_PERCENT`: max dialogue-authorization block rate percent (default `40`)
-  - `KSE_RELEASE_WEEKLY_OPS_MAX_MATRIX_REGRESSION_RATE_PERCENT`: optional max regression-positive rate percent
+  - `SCE_RELEASE_WEEKLY_OPS_ENFORCE`: `true|false` (default `true`)
+  - `SCE_RELEASE_WEEKLY_OPS_REQUIRE_SUMMARY`: require weekly summary artifact (`true|false`, default `true`)
+  - `SCE_RELEASE_WEEKLY_OPS_MAX_RISK_LEVEL`: `low|medium|high|unknown` (default `medium`)
+  - `SCE_RELEASE_WEEKLY_OPS_MAX_GOVERNANCE_BREACHES`: optional max breach count
+  - `SCE_RELEASE_WEEKLY_OPS_MAX_AUTHORIZATION_TIER_BLOCK_RATE_PERCENT`: max authorization-tier deny/review block rate percent (default `40`)
+  - `SCE_RELEASE_WEEKLY_OPS_MAX_DIALOGUE_AUTHORIZATION_BLOCK_RATE_PERCENT`: max dialogue-authorization block rate percent (default `40`)
+  - `SCE_RELEASE_WEEKLY_OPS_MAX_MATRIX_REGRESSION_RATE_PERCENT`: optional max regression-positive rate percent
   - Invalid numeric values are reported as gate `config_warnings` and default threshold fallback is applied.
 - Optional: tune release asset integrity gate:
-  - `KSE_RELEASE_ASSET_INTEGRITY_ENFORCE`: `true|false` (default `true`)
-  - `KSE_RELEASE_ASSET_INTEGRITY_REQUIRE_NON_EMPTY`: `true|false` (default `true`)
-  - `KSE_RELEASE_ASSET_INTEGRITY_REQUIRED_FILES`: override required asset list (comma-separated, supports `{tag}`)
+  - `SCE_RELEASE_ASSET_INTEGRITY_ENFORCE`: `true|false` (default `true`)
+  - `SCE_RELEASE_ASSET_INTEGRITY_REQUIRE_NON_EMPTY`: `true|false` (default `true`)
+  - `SCE_RELEASE_ASSET_INTEGRITY_REQUIRED_FILES`: override required asset list (comma-separated, supports `{tag}`)
 - Optional release-asset 0-byte guard (enabled in workflow by default):
   - `scripts/release-asset-nonempty-normalize.js` auto-fills placeholder content for optional assets such as `.lines` and `.jsonl` before GitHub Release upload.
   - Local dry-run example:
@@ -159,4 +166,20 @@ Ensure:
 - Optional local dry-run for gate history index artifact:
   - `sce auto handoff gate-index --dir .sce/reports/release-evidence --out .sce/reports/release-evidence/release-gate-history.json --json`
 
-Then proceed with your release workflow (tag, push, npm publish, GitHub release).
+Then proceed with your release workflow:
+
+```bash
+# 1. bump version + commit first
+# 2. push branch changes
+git push origin main
+
+# 3. create and push release tag
+git tag vX.Y.Z
+git push origin vX.Y.Z
+```
+
+Expected:
+
+- `git push origin main` only runs normal CI.
+- `git push origin vX.Y.Z` triggers GitHub Actions `Release` workflow.
+- workflow publishes npm package and creates GitHub Release if all release gates pass.

package/docs/releases/README.md

@@ -9,6 +9,7 @@ This directory stores release-facing documents:
 ## Archived Versions
 
 - [Release checklist](../release-checklist.md)
+- [v3.6.37 release notes](./v3.6.37.md)
 - [v1.46.2 release notes](./v1.46.2.md) (historical)
 - [v1.46.2 validation report](./v1.46.2-validation.md) (historical)
 - [GitHub Releases](https://github.com/heguangyong/scene-capability-engine/releases) (latest)

package/docs/releases/v3.6.37.md

@@ -0,0 +1,22 @@
+# v3.6.37 Release Notes
+
+Release date: 2026-03-12
+
+## Highlights
+
+- Removed legacy `kse` command/content references from active runtime paths, templates, fixtures, and release-facing documentation without keeping a compatibility bridge.
+- Standardized scene package/template metadata and fixture paths on `sce` naming so generated artifacts no longer leak old `kse` identifiers.
+- Fixed Windows release preflight for `scripts/git-managed-gate.js` by adding `git.cmd` / `git.exe` fallback resolution.
+- Documented the actual release trigger model: only `v*` tag pushes trigger GitHub Actions release publishing, and workflow publishing depends on repository secret `NPM_TOKEN`.
+
+## Verification
+
+- `npx jest tests/unit/workspace/workspace-context-resolver.test.js tests/unit/workspace/workspace-state-manager.test.js tests/unit/steering/compliance-cache.test.js tests/unit/scripts/moqui-lexicon-audit.test.js tests/unit/scripts/moqui-standard-rebuild.test.js tests/unit/scripts/moqui-metadata-extract.test.js tests/unit/task/task-claimer.test.js tests/unit/commands/auto.test.js tests/integration/auto-close-loop-cli.integration.test.js --runInBand`
+- `node scripts/check-branding-consistency.js`
+- `npx jest tests/unit/scripts/git-managed-gate.test.js --runInBand`
+
+## Release Notes
+
+- Plain `git push` does not publish this project.
+- Release automation starts only when `git push origin vX.Y.Z` triggers `.github/workflows/release.yml`.
+- GitHub Actions publish requires repository secret `NPM_TOKEN`.

package/docs/steering-strategy-guide.md

@@ -64,14 +64,14 @@ Detect existing steering files
     │
     └─ Steering files found → Prompt for strategy
            ↓
-           ├─ use-kse → Backup existing → Install sce steering
+           ├─ use-sce → Backup existing → Install sce steering
            │
            └─ use-project → Keep existing → Skip sce steering
 ```
 
 ## Rollback
 
-If you chose "use-kse" and want to restore your original steering files:
+If you chose "use-sce" and want to restore your original steering files:
 
 ```bash
 # List available backups
@@ -100,7 +100,7 @@ Your steering strategy choice is saved in `.sce/adoption-config.json`:
 {
   "version": "1.0.0",
   "adoptedAt": "2026-01-23T10:00:00.000Z",
-  "steeringStrategy": "use-kse",
+  "steeringStrategy": "use-sce",
   "steeringBackupId": "steering-2026-01-23T10-00-00-000Z",
   "multiUserMode": false,
   "lastUpdated": "2026-01-23T10:00:00.000Z"
@@ -111,7 +111,7 @@ Your steering strategy choice is saved in `.sce/adoption-config.json`:
 
 ### For New sce Users
 
-1. **Choose "use-kse"** to get the full experience
+1. **Choose "use-sce"** to get the full experience
 2. Review the installed steering files to understand sce workflow
 3. Customize `ENVIRONMENT.md` for your project specifics
 4. Update `CURRENT_CONTEXT.md` as you work on different Specs
@@ -123,7 +123,7 @@ Your steering strategy choice is saved in `.sce/adoption-config.json`:
 3. Consider creating a hybrid approach:
    - Keep your core steering rules
    - Add sce-specific rules in separate files
-   - Use file naming to control load order (e.g., `00-core.md`, `10-kse.md`)
+   - Use file naming to control load order (e.g., `00-core.md`, `10-sce.md`)
 
 ### For Teams
 
@@ -138,13 +138,13 @@ Your steering strategy choice is saved in `.sce/adoption-config.json`:
 
 **Solution:**
 - Check which steering strategy you chose: `cat .sce/adoption-config.json`
-- If "use-kse", verify sce steering files are present
+- If "use-sce", verify sce steering files are present
 - If "use-project", ensure your steering files are compatible with sce
 
 ### Problem: Want to switch strategies after adoption
 
 **Solution:**
-1. If currently "use-kse":
+1. If currently "use-sce":
    ```bash
    sce rollback {steering-backup-id}
    ```

package/docs/troubleshooting.md

@@ -1045,7 +1045,7 @@ ls -la .sce/
 
 **4. Community:**
 - Discord: [Join our Discord](https://discord.gg/sce)
-- Twitter: [@kse_dev](https://twitter.com/kse_dev)
+- Twitter: [@sce_dev](https://twitter.com/sce_dev)
 
 ### Creating a Good Issue Report
 

package/docs/zh/release-checklist.md

@@ -100,28 +100,35 @@ node scripts/git-managed-gate.js --fail-on-violation --json
 
 确认：
 
+- 发布自动化是基于 tag，而不是普通 commit：
+  - `.github/workflows/release.yml` 只在 `push.tags: v*` 时触发
+  - 普通 `git push` 只会跑常规 CI，不会发布 npm 包，也不会创建 GitHub Release
+- GitHub Actions 发版前置条件已配置：
+  - 仓库 Secret `NPM_TOKEN` 必须存在且有效，workflow 会用它执行 `npm publish --access public`
+  - workflow 的 release 资产/回读步骤依赖 `GITHUB_TOKEN`
 - `package.json` 版本号正确；
+- `package.json` 版本号必须大于 npm 当前已发布版本；
 - `CHANGELOG.md` 已记录发布相关变化；
 - 发布说明草稿已就绪（如 `docs/releases/vX.Y.Z.md`）。
 - 可选：通过仓库变量配置 release evidence 门禁（`Settings -> Secrets and variables -> Actions -> Variables`）：
-  - `KSE_RELEASE_GATE_ENFORCE`：`true|false`（默认 advisory，不阻断发布）
-  - `KSE_RELEASE_GATE_REQUIRE_EVIDENCE`：是否要求存在 `handoff-runs.json` 摘要
-  - `KSE_RELEASE_GATE_REQUIRE_GATE_PASS`：是否要求 evidence gate `passed=true`（有 evidence 时默认要求）
-  - `KSE_RELEASE_GATE_MIN_SPEC_SUCCESS_RATE`：最小允许成功率（百分比）
-  - `KSE_RELEASE_GATE_MAX_RISK_LEVEL`：`low|medium|high|unknown`（默认 `unknown`）
-  - `KSE_RELEASE_GATE_MAX_UNMAPPED_RULES`：ontology 业务规则未映射最大允许值
-  - `KSE_RELEASE_GATE_MAX_UNDECIDED_DECISIONS`：ontology 决策未定最大允许值
-  - `KSE_RELEASE_GATE_REQUIRE_SCENE_BATCH_PASS`：是否要求 scene package publish-batch gate 必须通过（`true|false`，默认 `true`）
-  - `KSE_RELEASE_GATE_MAX_SCENE_BATCH_FAILURES`：scene package batch 失败数量最大允许值（默认 `0`）
+  - `SCE_RELEASE_GATE_ENFORCE`：`true|false`（默认 advisory，不阻断发布）
+  - `SCE_RELEASE_GATE_REQUIRE_EVIDENCE`：是否要求存在 `handoff-runs.json` 摘要
+  - `SCE_RELEASE_GATE_REQUIRE_GATE_PASS`：是否要求 evidence gate `passed=true`（有 evidence 时默认要求）
+  - `SCE_RELEASE_GATE_MIN_SPEC_SUCCESS_RATE`：最小允许成功率（百分比）
+  - `SCE_RELEASE_GATE_MAX_RISK_LEVEL`：`low|medium|high|unknown`（默认 `unknown`）
+  - `SCE_RELEASE_GATE_MAX_UNMAPPED_RULES`：ontology 业务规则未映射最大允许值
+  - `SCE_RELEASE_GATE_MAX_UNDECIDED_DECISIONS`：ontology 决策未定最大允许值
+  - `SCE_RELEASE_GATE_REQUIRE_SCENE_BATCH_PASS`：是否要求 scene package publish-batch gate 必须通过（`true|false`，默认 `true`）
+  - `SCE_RELEASE_GATE_MAX_SCENE_BATCH_FAILURES`：scene package batch 失败数量最大允许值（默认 `0`）
 - 可选：通过仓库变量调节 Release Notes 中的漂移告警阈值：
   - CI 中漂移评估由 `scripts/release-drift-evaluate.js` 执行（历史读取、告警计算、gate 报告写回、enforce 退出码）。
-  - `KSE_RELEASE_DRIFT_ENFORCE`：`true|false`（默认 `false`），触发 drift alert 时阻断发布
-  - `KSE_RELEASE_DRIFT_FAIL_STREAK_MIN`：触发告警的最小连续失败次数（默认 `2`）
-  - `KSE_RELEASE_DRIFT_HIGH_RISK_SHARE_MIN_PERCENT`：近 5 版 high 风险占比告警阈值（默认 `60`）
-  - `KSE_RELEASE_DRIFT_HIGH_RISK_SHARE_DELTA_MIN_PERCENT`：短期相对长期 high 风险占比增量阈值（默认 `25`）
-  - `KSE_RELEASE_DRIFT_PREFLIGHT_BLOCK_RATE_MIN_PERCENT`：近 5 版（有 preflight 信号）blocked 占比告警阈值（默认 `40`）
-  - `KSE_RELEASE_DRIFT_HARD_GATE_BLOCK_STREAK_MIN`：hard-gate preflight 连续 blocked 告警阈值（最近窗口，默认 `2`）
-  - `KSE_RELEASE_DRIFT_PREFLIGHT_UNAVAILABLE_STREAK_MIN`：release preflight 连续 unavailable 告警阈值（最近窗口，默认 `2`）
+  - `SCE_RELEASE_DRIFT_ENFORCE`：`true|false`（默认 `false`），触发 drift alert 时阻断发布
+  - `SCE_RELEASE_DRIFT_FAIL_STREAK_MIN`：触发告警的最小连续失败次数（默认 `2`）
+  - `SCE_RELEASE_DRIFT_HIGH_RISK_SHARE_MIN_PERCENT`：近 5 版 high 风险占比告警阈值（默认 `60`）
+  - `SCE_RELEASE_DRIFT_HIGH_RISK_SHARE_DELTA_MIN_PERCENT`：短期相对长期 high 风险占比增量阈值（默认 `25`）
+  - `SCE_RELEASE_DRIFT_PREFLIGHT_BLOCK_RATE_MIN_PERCENT`：近 5 版（有 preflight 信号）blocked 占比告警阈值（默认 `40`）
+  - `SCE_RELEASE_DRIFT_HARD_GATE_BLOCK_STREAK_MIN`：hard-gate preflight 连续 blocked 告警阈值（最近窗口，默认 `2`）
+  - `SCE_RELEASE_DRIFT_PREFLIGHT_UNAVAILABLE_STREAK_MIN`：release preflight 连续 unavailable 告警阈值（最近窗口，默认 `2`）
 - 可选：发布资产 0 字节防护（workflow 默认开启）
   - `scripts/release-asset-nonempty-normalize.js` 会在上传 GitHub Release 资产前，为可选 `.lines` / `.jsonl` 资产自动补齐占位内容，避免 422。
   - 本地 dry-run 示例：
@@ -131,4 +138,20 @@ node scripts/git-managed-gate.js --fail-on-violation --json
 - 可选本地预演 release gate 历史索引产物：
   - `sce auto handoff gate-index --dir .sce/reports/release-evidence --out .sce/reports/release-evidence/release-gate-history.json --json`
 
-然后再执行你的正式发布流程（打 tag、push、npm publish、GitHub Release）。
+然后再执行正式发布流程：
+
+```bash
+# 1. 先升级版本并提交
+# 2. 先 push 分支代码
+git push origin main
+
+# 3. 再创建并 push 发版 tag
+git tag vX.Y.Z
+git push origin vX.Y.Z
+```
+
+预期：
+
+- `git push origin main` 只跑常规 CI；
+- `git push origin vX.Y.Z` 才会触发 GitHub Actions `Release` workflow；
+- 只有 release workflow 全部门禁通过后，才会自动发布 npm 包并创建 GitHub Release。

package/docs/zh/releases/README.md

@@ -9,6 +9,7 @@
 ## 历史版本归档
 
 - [发布检查清单](../release-checklist.md)
+- [v3.6.37 发布说明](./v3.6.37.md)
 - [v1.46.2 发布说明](./v1.46.2.md)（历史归档）
 - [v1.46.2 验证报告](./v1.46.2-validation.md)（历史归档）
 - [GitHub Releases](https://github.com/heguangyong/scene-capability-engine/releases)（最新）

package/docs/zh/releases/v3.6.37.md

@@ -0,0 +1,22 @@
+# v3.6.37 发布说明
+
+发布日期：2026-03-12
+
+## 重点变化
+
+- 彻底移除了运行路径、模板、夹具和对外文档中的旧 `kse` 命令与内容，不再保留兼容桥接。
+- 将 scene package / template 元数据与 fixture 路径统一到 `sce` 命名，避免新产物继续泄漏旧 `kse` 标识。
+- 修复了 Windows 下 `scripts/git-managed-gate.js` 的 git 可执行文件解析问题，新增 `git.cmd` / `git.exe` 回退，避免发布前置门禁误判。
+- 明确记录了真实发布方式：只有 `v*` tag push 才会触发 GitHub Actions 发版，且 workflow 发布依赖仓库 Secret `NPM_TOKEN`。
+
+## 验证
+
+- `npx jest tests/unit/workspace/workspace-context-resolver.test.js tests/unit/workspace/workspace-state-manager.test.js tests/unit/steering/compliance-cache.test.js tests/unit/scripts/moqui-lexicon-audit.test.js tests/unit/scripts/moqui-standard-rebuild.test.js tests/unit/scripts/moqui-metadata-extract.test.js tests/unit/task/task-claimer.test.js tests/unit/commands/auto.test.js tests/integration/auto-close-loop-cli.integration.test.js --runInBand`
+- `node scripts/check-branding-consistency.js`
+- `npx jest tests/unit/scripts/git-managed-gate.test.js --runInBand`
+
+## 发布说明
+
+- 普通 `git push` 不会发布本项目。
+- 只有 `git push origin vX.Y.Z` 触发 `.github/workflows/release.yml` 后，才会进入自动发布流程。
+- GitHub Actions 发版依赖仓库 Secret `NPM_TOKEN`。

package/lib/auto/governance-summary.js

@@ -1,4 +1,4 @@
-const { parseAutoHandoffGateBoolean, normalizeHandoffText } = require('./governance-signals');
+const { parseAutoHandoffGateBoolean, normalizeHandoffText } = require('./governance-signals');
 const { buildMoquiRegressionRecoverySequenceLines } = require('./moqui-recovery-sequence');
 
 function deriveGovernanceRiskLevel(summary) {
@@ -575,7 +575,7 @@ function buildGovernanceRecommendations(summary) {
     }
     if (Number.isFinite(weeklyOpsConfigWarningsTotal) && weeklyOpsConfigWarningsTotal > 0) {
       recommendations.push(
-        'Fix invalid weekly ops threshold variables (`KSE_RELEASE_WEEKLY_OPS_*`) and rerun release gates ' +
+        'Fix invalid weekly ops threshold variables (`SCE_RELEASE_WEEKLY_OPS_*`) and rerun release gates ' +
         'to clear config warnings.'
       );
     }

package/lib/commands/adopt.js

@@ -449,7 +449,7 @@ async function adoptInteractive(projectPath, options) {
       // Prompt for strategy
       steeringStrategy = await steeringManager.promptStrategy(detection.steeringDetection);
       
-      if (steeringStrategy === 'use-kse') {
+      if (steeringStrategy === 'use-sce') {
         // Backup existing steering files
         console.log(chalk.blue('📦 Backing up existing steering files...'));
         const backupResult = await steeringManager.backupSteering(projectPath);
@@ -460,7 +460,7 @@ async function adoptInteractive(projectPath, options) {
           
           // Install sce steering files
           console.log(chalk.blue('📝 Installing sce steering files...'));
-          const installResult = await steeringManager.installKseSteering(projectPath);
+          const installResult = await steeringManager.installSceSteering(projectPath);
           
           if (installResult.success) {
             console.log(chalk.green(`✅ Installed ${installResult.filesInstalled} sce steering file(s)`));
@@ -711,7 +711,7 @@ async function adoptInteractive(projectPath, options) {
  * 
  * @param {string} projectPath - Project root path
  */
-async function setupKiroMcpConfig(projectPath) {
+async function setupSceMcpConfig(projectPath) {
   const mcpConfigPath = path.join(projectPath, '.sce', 'settings', 'mcp.json');
   
   // Don't overwrite existing config
@@ -767,7 +767,7 @@ async function offerAutomationSetup(projectPath) {
     
     // If AI IDE detected, create default MCP settings
     if (toolDetection.primaryTool === 'SCE') {
-      await setupKiroMcpConfig(projectPath);
+      await setupSceMcpConfig(projectPath);
     }
   } catch (toolError) {
     // Tool detection is optional, don't fail adoption if it errors

package/lib/commands/auto.js

@@ -1,4 +1,4 @@
-/**
+/**
  * Autonomous Control CLI Commands
  */
 
@@ -8615,7 +8615,7 @@ function buildAutoHandoffRunRecommendations(projectPath, result) {
       observabilityWeeklyOps.config_warning_positive_sessions > 0
     ) {
       push(
-        'Fix invalid weekly ops threshold variables (`KSE_RELEASE_WEEKLY_OPS_*`) and rerun release gates ' +
+        'Fix invalid weekly ops threshold variables (`SCE_RELEASE_WEEKLY_OPS_*`) and rerun release gates ' +
         'to clear config warnings.'
       );
     }
@@ -13073,7 +13073,7 @@ function buildGovernanceCloseLoopRecommendations(finalAssessment, stopReason, st
   }
   if (reasons.some(item => `${item}`.includes('weekly-ops-config-warnings'))) {
     base.push(
-      'Fix invalid weekly ops threshold variables (`KSE_RELEASE_WEEKLY_OPS_*`) and rerun release gates ' +
+      'Fix invalid weekly ops threshold variables (`SCE_RELEASE_WEEKLY_OPS_*`) and rerun release gates ' +
       'to clear config warnings.'
     );
   }

package/lib/spec/bootstrap/context-collector.js

@@ -35,7 +35,7 @@ class ContextCollector {
   }
 
   _detectLanguagePreference() {
-    const lang = `${process.env.KSE_LANG || process.env.LANG || ''}`.toLowerCase();
+    const lang = `${process.env.SCE_LANG || process.env.LANG || ''}`.toLowerCase();
     if (lang.includes('zh')) {
       return 'zh';
     }

package/lib/steering/adoption-config.js

@@ -60,7 +60,7 @@ class AdoptionConfig {
   /**
    * 更新 steering 策略配置
    * 
-   * @param {string} strategy - 策略 ('use-kse' | 'use-project')
+   * @param {string} strategy - 策略 ('use-sce' | 'use-project')
    * @param {string|null} backupId - 备份 ID（如果有）
    * @returns {Promise<boolean>} 是否成功
    */
@@ -152,7 +152,7 @@ class AdoptionConfig {
     const config = {
       version: '1.0.0',
       adoptedAt: new Date().toISOString(),
-      steeringStrategy: options.steeringStrategy || 'use-kse',
+      steeringStrategy: options.steeringStrategy || 'use-sce',
       multiUserMode: options.multiUserMode || false,
       ...options
     };

package/lib/steering/compliance-cache.js

@@ -21,11 +21,11 @@ class ComplianceCache {
   /**
    * Get the default cache file path
    * 
-   * @returns {string} Path to ~/.kse/steering-check-cache.json
+   * @returns {string} Path to ~/.sce/steering-check-cache.json
    */
   getDefaultCachePath() {
     const homeDir = os.homedir();
-    return path.join(homeDir, '.kse', 'steering-check-cache.json');
+    return path.join(homeDir, '.sce', 'steering-check-cache.json');
   }
 
   /**

package/lib/steering/steering-manager.js

@@ -65,12 +65,12 @@ class SteeringManager {
    * 提示用户选择 steering 策略
    * 
    * @param {Object} detection - detectSteering 的返回结果
-   * @returns {Promise<string>} 选择的策略 ('use-kse' | 'use-project')
+   * @returns {Promise<string>} 选择的策略 ('use-sce' | 'use-project')
    */
   async promptStrategy(detection) {
     if (!detection.hasExistingSteering) {
       // 没有现有 steering 文件，默认使用 sce
-      return 'use-kse';
+      return 'use-sce';
     }
 
     console.log('\n⚠️  Steering Conflict Detected');
@@ -94,7 +94,7 @@ class SteeringManager {
       choices: [
         {
           name: 'Use sce steering (backup existing files) - Recommended for new sce users',
-          value: 'use-kse'
+          value: 'use-sce'
         },
         {
           name: 'Keep existing steering (skip sce steering) - For projects with custom steering rules',
@@ -167,7 +167,7 @@ class SteeringManager {
    * @param {string} projectPath - 项目根目录路径
    * @returns {Promise<Object>} 安装结果
    */
-  async installKseSteering(projectPath) {
+  async installSceSteering(projectPath) {
     const steeringPath = path.join(projectPath, this.steeringDir);
     const templatePath = path.join(__dirname, '../../template/.sce/steering');
 

package/lib/task/task-claimer.js

@@ -97,8 +97,7 @@ class TaskClaimer {
       return [];
     }
 
-    // Accept both legacy and current section headers to keep existing specs readable.
-    const markerHeaderRegex = /^\s*##\s+(?:(?:sce|kse)\s+)?Status\s+Markers\s*$/i;
+    const markerHeaderRegex = /^\s*##\s+(?:sce\s+)?Status\s+Markers\s*$/i;
     const sectionHeaderRegex = /^\s*##\s+/;
 
     const markerLine = lines.findIndex((line) => markerHeaderRegex.test(String(line || '')));

package/lib/workspace/multi/workspace-context-resolver.js

@@ -92,7 +92,7 @@ class WorkspaceContextResolver {
    * @param {string} dirPath - Directory path to check
    * @returns {Promise<boolean>} True if directory contains .sce/ structure
    */
-  async isValidKseDirectory(dirPath) {
+  async isValidSceDirectory(dirPath) {
     try {
       const kiroPath = path.join(dirPath, '.sce');
       const exists = await fs.pathExists(kiroPath);
@@ -184,7 +184,7 @@ class WorkspaceContextResolver {
     const targetDir = currentDir || process.cwd();
 
     // Check if it's a valid sce directory
-    const isValid = await this.isValidKseDirectory(targetDir);
+    const isValid = await this.isValidSceDirectory(targetDir);
     if (!isValid) {
       return false;
     }
@@ -210,7 +210,7 @@ class WorkspaceContextResolver {
     
     if (!workspace) {
       const targetDir = currentDir || process.cwd();
-      const isValid = await this.isValidKseDirectory(targetDir);
+      const isValid = await this.isValidSceDirectory(targetDir);
       
       if (isValid) {
         throw new Error(

package/lib/workspace/multi/workspace-state-manager.js

@@ -48,62 +48,20 @@ class WorkspaceStateManager {
     return path.join(homeDir, '.sce', 'workspace-state.json');
   }
 
-  /**
-   * Get the legacy state file path used by prior versions
-   *
-   * @returns {string} Path to ~/.kse/workspace-state.json
-   */
-  getLegacyStatePath() {
-    const homeDir = os.homedir();
-    return path.join(homeDir, '.kse', 'workspace-state.json');
-  }
-
-  /**
-   * Whether state manager is operating on the default state path.
-   *
-   * Automatic legacy migration should only run in this mode.
-   *
-   * @returns {boolean}
-   */
-  isDefaultStatePath() {
-    return path.resolve(this.statePath) === path.resolve(this.getDefaultStatePath());
-  }
-
   /**
    * Load workspace state from disk
    * 
-   * Supports automatic migration from legacy format (workspaces.json + config.json)
-   * 
    * @returns {Promise<boolean>} True if loaded successfully
    */
   async load() {
     try {
-      // Try loading new format
       const exists = await fs.pathExists(this.statePath);
-      
       if (exists) {
         await this.loadNewFormat();
         this.loaded = true;
         return true;
       }
 
-      // Migrate legacy single-file state from ~/.kse/workspace-state.json
-      if (await this.hasLegacyStateFile()) {
-        console.log('Migrating workspace state to new .sce directory...');
-        await this.migrateFromLegacyStateFile();
-        await this.loadNewFormat();
-        this.loaded = true;
-        return true;
-      }
-
-      // Check for legacy format and migrate
-      if (await this.hasLegacyFiles()) {
-        console.log('Migrating workspace configuration to new format...');
-        await this.migrateFromLegacy();
-        this.loaded = true;
-        return true;
-      }
-
       // Initialize empty state
       this.state = {
         version: '1.0',
@@ -160,128 +118,6 @@ class WorkspaceStateManager {
     };
   }
 
-  /**
-   * Check if legacy configuration files exist
-   * 
-   * @private
-   * @returns {Promise<boolean>}
-   */
-  async hasLegacyFiles() {
-    if (!this.isDefaultStatePath()) {
-      return false;
-    }
-
-    const homeDir = os.homedir();
-    const legacyWorkspacesPath = path.join(homeDir, '.kse', 'workspaces.json');
-    const legacyConfigPath = path.join(homeDir, '.kse', 'config.json');
-    
-    const workspacesExists = await fs.pathExists(legacyWorkspacesPath);
-    const configExists = await fs.pathExists(legacyConfigPath);
-    
-    return workspacesExists || configExists;
-  }
-
-  /**
-   * Check whether legacy single-file state exists
-   *
-   * @private
-   * @returns {Promise<boolean>}
-   */
-  async hasLegacyStateFile() {
-    if (!this.isDefaultStatePath()) {
-      return false;
-    }
-
-    const legacyStatePath = this.getLegacyStatePath();
-    return fs.pathExists(legacyStatePath);
-  }
-
-  /**
-   * Copy legacy single-file state into the new default location.
-   *
-   * @private
-   * @returns {Promise<void>}
-   */
-  async migrateFromLegacyStateFile() {
-    const legacyStatePath = this.getLegacyStatePath();
-    const stateDir = path.dirname(this.statePath);
-    await fs.ensureDir(stateDir);
-    await fs.copy(legacyStatePath, this.statePath);
-  }
-
-  /**
-   * Migrate from legacy format (workspaces.json + config.json)
-   * 
-   * @private
-   */
-  async migrateFromLegacy() {
-    const homeDir = os.homedir();
-    const legacyWorkspacesPath = path.join(homeDir, '.kse', 'workspaces.json');
-    const legacyConfigPath = path.join(homeDir, '.kse', 'config.json');
-
-    // Load legacy workspaces
-    let legacyWorkspaces = [];
-    if (await fs.pathExists(legacyWorkspacesPath)) {
-      const content = await fs.readFile(legacyWorkspacesPath, 'utf8');
-      const data = JSON.parse(content);
-      legacyWorkspaces = data.workspaces || [];
-    }
-
-    // Load legacy config
-    let legacyActiveWorkspace = null;
-    let legacyPreferences = {};
-    if (await fs.pathExists(legacyConfigPath)) {
-      const content = await fs.readFile(legacyConfigPath, 'utf8');
-      const data = JSON.parse(content);
-      legacyActiveWorkspace = data.active_workspace || null;
-      legacyPreferences = data.preferences || {};
-    }
-
-    // Merge into new format
-    this.state.activeWorkspace = legacyActiveWorkspace;
-    this.state.workspaces = new Map();
-    
-    for (const workspaceData of legacyWorkspaces) {
-      const workspace = Workspace.fromDict(workspaceData);
-      this.state.workspaces.set(workspace.name, workspace);
-    }
-
-    this.state.preferences = {
-      autoDetectWorkspace: legacyPreferences.auto_detect_workspace ?? true,
-      confirmDestructiveOperations: legacyPreferences.confirm_destructive_operations ?? true
-    };
-
-    // Save to new format
-    await this.save();
-
-    // Backup legacy files
-    await this.backupLegacyFiles();
-  }
-
-  /**
-   * Backup legacy configuration files
-   * 
-   * @private
-   */
-  async backupLegacyFiles() {
-    const homeDir = os.homedir();
-    const legacyWorkspacesPath = path.join(homeDir, '.kse', 'workspaces.json');
-    const legacyConfigPath = path.join(homeDir, '.kse', 'config.json');
-    const timestamp = new Date().toISOString().replace(/[:.]/g, '-');
-
-    if (await fs.pathExists(legacyWorkspacesPath)) {
-      const backupPath = path.join(homeDir, '.kse', `workspaces.json.backup-${timestamp}`);
-      await fs.copy(legacyWorkspacesPath, backupPath);
-      await fs.remove(legacyWorkspacesPath);
-    }
-
-    if (await fs.pathExists(legacyConfigPath)) {
-      const backupPath = path.join(homeDir, '.kse', `config.json.backup-${timestamp}`);
-      await fs.copy(legacyConfigPath, backupPath);
-      await fs.remove(legacyConfigPath);
-    }
-  }
-
   /**
    * Save workspace state to disk (atomic operation)
    * 

package/lib/workspace/sce-tracking-audit.js

@@ -4,7 +4,7 @@ const FIXTURE_ROOT = 'tests/fixtures/moqui-core-regression/workspace/.sce';
 const REQUIRED_TRACKED_FILES = [
   `${FIXTURE_ROOT}/specs/60-10-moqui-core-order-query/custom/scene-package.json`,
   `${FIXTURE_ROOT}/specs/60-10-moqui-core-order-query/custom/scene.yaml`,
-  `${FIXTURE_ROOT}/templates/scene-packages/kse.scene--erp-order-query-read--0.1.0/scene-package.json`,
+  `${FIXTURE_ROOT}/templates/scene-packages/sce.scene--erp-order-query-read--0.1.0/scene-package.json`,
 ];
 const DISALLOWED_TRACKED_PREFIXES = [
   `${FIXTURE_ROOT}/reports/`,

package/lib/workspace/takeover-baseline.js

@@ -303,7 +303,7 @@ function _buildAdoptionConfig(existing, nowIso, sceVersion) {
     adoptedAt,
     steeringStrategy: typeof base.steeringStrategy === 'string' && base.steeringStrategy.trim()
       ? base.steeringStrategy
-      : 'use-kse',
+      : 'use-sce',
     multiUserMode: base.multiUserMode === true,
     runtimePolicy: {
       agent_parity_permissions: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scene-capability-engine",
-  "version": "3.6.36",
+  "version": "3.6.37",
   "description": "SCE (Scene Capability Engine) - A CLI tool and npm package for spec-driven development with AI coding assistants.",
   "main": "index.js",
   "bin": {

package/template/.sce/README.md

@@ -45,7 +45,7 @@ This project uses **Spec-driven development** - a structured approach where:
 
 ### Workspace Management
 - `sce workspace create/list/switch/info/remove` — Manage multiple sce projects
-- Global state: `~/.kse/workspace-state.json`
+- Global state: `~/.sce/workspace-state.json`
 
 ### Environment Configuration
 - `sce env list/switch/info/register/unregister/rollback/verify/run` — Multi-environment management

package/template/.sce/steering/CORE_PRINCIPLES.md

@@ -16,7 +16,7 @@
 
 ## ⚠️ 核心原则
 
-### 0. KSE 项目接管声明 🎯
+### 0. SCE 项目接管声明 🎯
 
 **核心**: 项目已由 sce 接管，AI 拥有完全开发和管理权限
 

package/bin/kse.js

@@ -1,3 +0,0 @@
-#!/usr/bin/env node
-
-require('./scene-capability-engine');