scene-capability-engine 3.6.36 → 3.6.38

package/CHANGELOG.md

@@ -1,4 +1,4 @@
-# Changelog
+# Changelog
 
 All notable changes to this project will be documented in this file.
 
@@ -7,6 +7,31 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.6.38] - 2026-03-12
+
+### Added
+- Added `scripts/steering-content-audit.js` to audit steering content budgets, stale history, checklist leakage, stable-layer spec leakage, and non-canonical governance aliases.
+- Added weekly scheduled workflow `.github/workflows/steering-hygiene.yml` and project guidance in `docs/steering-governance.md` for recurring steering review and cleanup.
+- Added Spec `119-00-steering-self-governance` to document the steering self-governance model, audit scope, and CI rollout.
+
+### Changed
+- Refactored `.sce/steering/` and `template/.sce/steering/` so baseline steering content stays lean, layered, and free of long history or task-state drift.
+- Extended steering manifest governance metadata with file budgets, relocation targets, review cadence, and canonical mechanism rules.
+- Wired `npm run audit:steering` into CI and `prepublishOnly`, making steering hygiene part of normal validation and release flow.
+
+## [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 +303,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 +881,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 +903,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 +926,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 +1310,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 +2114,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 +2211,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 +2252,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 +2439,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,8 @@ This directory stores release-facing documents:
 ## Archived Versions
 
 - [Release checklist](../release-checklist.md)
+- [v3.6.38 release notes](./v3.6.38.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/releases/v3.6.38.md

@@ -0,0 +1,19 @@
+# v3.6.38 Release Notes
+
+Release date: 2026-03-12
+
+## Highlights
+
+- Added a steering self-governance audit that checks content budgets, stale history, checklist leakage, stable-layer Spec leakage, and non-canonical governance aliases.
+- Refactored the live steering baseline and template steering files so they stay lean, layered, and easier to refresh over time.
+- Added recurring steering hygiene enforcement in normal CI, `prepublishOnly`, and a weekly GitHub Actions schedule.
+
+## Verification
+
+- `npm run audit:steering`
+- `npx jest tests/unit/steering/steering-compliance-checker.test.js tests/unit/scripts/steering-content-audit.test.js tests/unit/scripts/git-managed-gate.test.js --runInBand`
+
+## Release Notes
+
+- Steering is now expected to self-correct through recurring audit rather than rely on ad hoc cleanup.
+- Stable steering layers should remain short-lived in content size but long-lived in principle quality.

package/docs/steering-governance.md

@@ -0,0 +1,112 @@
+# Steering 治理与净化
+
+## 目标
+
+让 `.sce/steering/` 长期保持三种品质：
+
+- 健壮：长期规则稳定，不被短期任务污染
+- 活力：随着项目演进持续校正，不靠历史惯性堆积
+- 节制：只保留最小必要上下文，其他内容迁回更合适的位置
+
+## 分层标准
+
+| 位置 | 应放什么 | 不应放什么 |
+|------|---------|-----------|
+| `.sce/steering/CORE_PRINCIPLES.md` | 长期原则、跨 Spec 仍成立的默认行为 | 任务项、历史版本、阶段流水、短期战术 |
+| `.sce/steering/ENVIRONMENT.md` | 项目环境、目录约定、发布触发方式、长期运行约束 | Spec 进度、问题清单、临时 workaround |
+| `.sce/steering/CURRENT_CONTEXT.md` | 当前阶段最小必要上下文、近期优先级 | 长历史、完整日志、旧阶段总结 |
+| `.sce/steering/RULES_GUIDE.md` | 职责边界、迁移规则、审计入口 | 详细制度、示例、长篇解释 |
+| `.sce/specs/<spec>/` | 任务、证据、诊断、阶段记录、报告 | 不应再回写到 steering 的长历史 |
+| `docs/` | 详细制度、示例、方法论、治理说明 | 当前 session 的即时状态 |
+
+## 审查周期
+
+- 每周一次
+- 每次发布前一次
+- 每次重大 Spec 收尾后一次
+- 接管老项目或大规模文档迁移后，再补一次
+
+## 审查动作
+
+每次审查只做四类决定：
+
+1. 保留
+   条件：内容长期有效，且放在当前层是正确的
+2. 合并
+   条件：多条规则表达同一个约束，只是换了说法
+3. 迁移
+   条件：内容有效，但层级错了
+4. 删除
+   条件：短期价值已结束、已有现成机制承接、或已经被文档/系统能力覆盖
+
+## 防腐重点
+
+### 1. 不允许平行机制
+
+steering 不能因为“想提醒 AI”就再造一套并行机制。
+
+典型案例：
+
+- 缺陷经验、临时兜底、发布阻断：统一复用 `errorbook`
+- Scene / session 生命周期：复用现有 close-loop / scene 运行时
+- release gate：复用现有 release workflow 与 gate 脚本
+
+如果某条 steering 规则本质上是在说“再搞一套模式”，应先问两件事：
+
+1. 现有 SCE 是否已经有能力承接？
+2. 这条内容应该写成机制引用，而不是重新定义机制吗？
+
+### 2. 不允许长历史驻留
+
+历史记录、阶段流水、版本脚注、完成纪要不应长期留在 steering。
+
+迁移目标：
+
+- 当前阶段以外的推进历史 -> 对应 Spec `custom/` 或 `reports/`
+- 发布历史 -> `CHANGELOG.md` / `docs/releases/`
+- 详细治理说明 -> `docs/steering-governance.md`
+
+### 3. 不允许任务态混入
+
+steering 不是待办清单。
+
+以下内容应迁出：
+
+- checklist
+- “下一个动作”
+- 具体执行命令流水
+- 某个 Spec 的进行中任务状态
+
+### 4. 不允许错层
+
+判断标准很简单：
+
+- 跨项目、跨阶段仍成立？放 `CORE_PRINCIPLES.md`
+- 仅对当前项目成立？放 `ENVIRONMENT.md`
+- 仅对当前阶段成立？放 `CURRENT_CONTEXT.md`
+- 需要示例和长解释？放 `docs/`
+
+## 审计入口
+
+本项目提供自动审计：
+
+```bash
+npm run audit:steering
+```
+
+当前会检查：
+
+- 文件预算是否超线
+- 长期层是否混入历史版本脚注
+- 长期层是否混入 Spec 引用
+- steering 中是否混入 checklist / 任务态
+- `CURRENT_CONTEXT.md` 是否与当前包版本脱节
+- 是否出现“错题 / 错题本”这类非规范机制别名
+
+## 通过标准
+
+- `CORE_PRINCIPLES.md` 能在短时间读完并说明默认行为
+- `CURRENT_CONTEXT.md` 不依赖长历史也能让 Agent 开工
+- steering 中不再出现任务态和阶段流水
+- 已有机制统一复用，不再出现平行命名
+- 周期性审计可稳定通过

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