scene-capability-engine 3.6.51 → 3.6.53

package/CHANGELOG.md

@@ -7,6 +7,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.6.53] - 2026-03-16
+
+### Added
+- Added a tracked project-shared high-value errorbook projection at `.sce/knowledge/errorbook/project-shared-registry.json`, seeded by default in template/takeover baselines so same-project work on another computer can recover curated `verified` and `promoted` knowledge through Git without committing raw `.sce/errorbook/**`.
+
+### Changed
+- Errorbook mutation commands now auto-refresh the tracked project-shared projection, and registry-inclusive lookup can search that local file in `remote` mode without requiring an index.
+- Co-work governance auditing now treats the project-shared errorbook projection as a required closure artifact: config must stay enabled, the project-shared source must exist, the projection file must parse, and it must be Git-tracked.
+
+## [3.6.52] - 2026-03-16
+
+### Added
+- Added `sce app runtime uninstall` with active-release protection, explicit installed-vs-active runtime projection fields, and MagicBall-facing runtime uninstall/auth documentation.
+- Extended co-work governance auditing so shared `errorbook` registry baseline and managed `errorbook_convergence` defaults are now checked alongside multi-agent/runtime-state drift.
+
 ## [3.6.51] - 2026-03-15
 
 ### Changed

package/README.md

@@ -165,7 +165,7 @@ MagicBall-specific integration surfaces now also include:
 
 - `sce app bundle list|show|register`
 - `sce app registry status|configure|sync*`
-- `sce app runtime show|releases|install|activate`
+- `sce app runtime show|releases|install|activate|uninstall`
 - `sce app engineering show|attach|hydrate|activate`
 - `sce mode application|ontology|engineering home`
 - `sce pm requirement|tracking|planning|change|issue ... --json`
@@ -218,5 +218,5 @@ MIT. See [LICENSE](LICENSE).
 
 ---
 
-**Version**: 3.6.51
-**Last Updated**: 2026-03-15
+**Version**: 3.6.53
+**Last Updated**: 2026-03-16

package/README.zh.md

@@ -170,7 +170,7 @@ SCE 默认是强治理的。
 
 - `sce app bundle list|show|register`
 - `sce app registry status|configure|sync*`
-- `sce app runtime show|releases|install|activate`
+- `sce app runtime show|releases|install|activate|uninstall`
 - `sce app engineering show|attach|hydrate|activate`
 - `sce mode application|ontology|engineering home`
 - `sce pm requirement|tracking|planning|change|issue ... --json`
@@ -223,5 +223,5 @@ MIT，见 [LICENSE](LICENSE)。
 
 ---
 
-**版本**：3.6.51
-**最后更新**：2026-03-15
+**版本**：3.6.53
+**最后更新**：2026-03-16

package/docs/command-reference.md

@@ -2,8 +2,8 @@
 
 > Quick reference for all `sce` commands
 
-**Version**: 3.6.51
-**Last Updated**: 2026-03-15
+**Version**: 3.6.52
+**Last Updated**: 2026-03-16
 
 ---
 
@@ -135,7 +135,7 @@ Timeline policy:
 - default enabled with local retention under `.sce/timeline/snapshots/`
 - stage/key-event checkpoints are automatically captured for `studio` and `session` commands
 - interval auto-checkpoints are integrated in the same flow via timeline checkpoint capture
-- `timeline push` now blocks before snapshot/push when collaboration governance drifts, so tracked runtime state, missing co-work ignore rules, legacy `.kiro*` references, invalid multi-agent config, or steering boundary drift cannot pass through managed push flow
+- `timeline push` now blocks before snapshot/push when collaboration governance drifts, so tracked runtime state, missing co-work ignore rules, missing shared `errorbook` registry baseline, missing tracked project-shared errorbook projection, invalid multi-agent config, legacy `.kiro*` references, or steering boundary drift cannot pass through managed push flow
 
 ### Value Metrics
 
@@ -348,7 +348,7 @@ sce workspace legacy-migrate --dry-run --json
 sce workspace tracking-audit
 sce workspace tracking-audit --json
 
-# Audit collaboration governance boundaries and legacy naming drift
+# Audit collaboration governance boundaries, shared errorbook closure, and legacy naming drift
 sce workspace collab-governance-audit
 sce workspace collab-governance-audit --json
 sce workspace collab-governance-audit --strict
@@ -393,6 +393,7 @@ sce app runtime show --app customer-order-demo --json
 sce app runtime releases --app customer-order-demo --json
 sce app runtime install --app customer-order-demo --release <release-id> --json
 sce app runtime activate --app customer-order-demo --release <release-id> --json
+sce app runtime uninstall --app customer-order-demo --release <release-id> --json
 
 # Engineering projection
 sce app engineering show --app customer-order-demo --json
@@ -637,8 +638,10 @@ Curated quality policy (`宁缺毋滥，优胜略汰`) defaults:
   - missing exit/cleanup/deadline metadata
   - expired mitigation deadline
 - `export` outputs a machine-readable registry bundle from curated local entries (recommended default: `promoted`, `quality>=75`).
+- managed same-project sharing now uses a tracked projection file at `.sce/knowledge/errorbook/project-shared-registry.json`, refreshed automatically after `record`, `promote`, `deprecate`, and `requalify`
 - `sync-registry` pulls external registry JSON into local cache (`.sce/errorbook/registry-cache.json`) for unified `find` retrieval.
 - `find --include-registry --registry-mode remote` supports direct remote query for large registries (no full local sync required).
+- registry-inclusive lookup can also search the tracked project-shared local file in `remote` mode without a shard index.
 - Recommended for large registries: maintain a remote index file (`registry/errorbook-registry.index.json`) and shard files, then provide `index_url` in registry config.
 - Since `v3.3.23`, `sce init` / `sce adopt` default baseline includes enabled central registry config in `.sce/config/errorbook-registry.json`.
 - `health-registry` validates config readability, source/index accessibility, and index-to-shard resolution before release.

package/docs/errorbook-registry.md

@@ -72,12 +72,23 @@ Create `.sce/config/errorbook-registry.json`:
   "enabled": true,
   "search_mode": "remote",
   "cache_file": ".sce/errorbook/registry-cache.json",
+  "project_shared_projection": {
+    "enabled": true,
+    "file": ".sce/knowledge/errorbook/project-shared-registry.json",
+    "statuses": ["verified", "promoted"],
+    "min_quality": 75
+  },
   "sources": [
     {
       "name": "central",
       "enabled": true,
       "url": "https://raw.githubusercontent.com/heguangyong/sce-errorbook-registry/main/registry/errorbook-registry.json",
       "index_url": "https://raw.githubusercontent.com/heguangyong/sce-errorbook-registry/main/registry/errorbook-registry.index.json"
+    },
+    {
+      "name": "project-shared",
+      "enabled": true,
+      "file": ".sce/knowledge/errorbook/project-shared-registry.json"
     }
   ]
 }
@@ -87,23 +98,30 @@ Notes:
 - `url` must be a raw JSON URL (`raw.githubusercontent.com`) or use a local file path.
 - `search_mode` supports `cache|remote|hybrid` (recommended: `remote` for very large registries).
 - Local cache file is used by cache/hybrid mode.
-- Since `v3.3.23`, `sce init` / `sce adopt` template baselines include this config by default (central source enabled).
+- `project_shared_projection` is the Git-tracked same-project sharing path used for cross-computer co-work continuity.
+- Since `v3.3.23`, `sce init` / `sce adopt` template baselines include registry config by default; current baseline also seeds the tracked project-shared projection file.
 
 ## 4) Daily Workflow
 
-1. Export curated local entries:
+1. Keep project-shared same-project knowledge current:
+```bash
+# SCE refreshes this automatically after record/promote/deprecate/requalify
+.sce/knowledge/errorbook/project-shared-registry.json
+```
+
+2. Export curated local entries for central cross-project publication:
 ```bash
 sce errorbook export --status promoted --min-quality 75 --out .sce/errorbook/exports/registry.json --json
 ```
 
-2. Merge approved entries into central repo `registry/errorbook-registry.json`.
+3. Merge approved entries into central repo `registry/errorbook-registry.json`.
 
-3. Sync central registry into local cache:
+4. Sync central registry into local cache:
 ```bash
 sce errorbook sync-registry --source https://raw.githubusercontent.com/heguangyong/sce-errorbook-registry/main/registry/errorbook-registry.json --json
 ```
 
-4. Search local + shared entries:
+5. Search local + shared entries:
 ```bash
 sce errorbook find --query "approve order timeout" --include-registry --json
 sce errorbook find --query "approve order timeout" --include-registry --registry-mode remote --json
@@ -116,6 +134,7 @@ SCE_REGISTRY_HEALTH_STRICT=1 node scripts/errorbook-registry-health-gate.js --js
 
 ## 5) Governance Rules
 
+- Same-project co-work should rely on the tracked project-shared projection instead of committing raw `.sce/errorbook/**`.
 - Publish to central registry only curated entries (recommended: `status=promoted` and `quality>=75`).
 - Do not publish sensitive tenant/customer data.
 - Temporary mitigation entries must remain bounded and governed (exit criteria, cleanup task, deadline).

package/docs/magicball-adaptation-task-checklist-v1.md

@@ -70,6 +70,8 @@ Important fields:
 - `summary.app_name`
 - `summary.runtime_version`
 - `summary.install_status`
+- `summary.installed_release_id`
+- `summary.active_release_id`
 - `summary.release_count`
 - `view_model.current_release`
 - `view_model.entrypoint`
@@ -84,6 +86,7 @@ sce app runtime releases --app customer-order-demo --json
 Expected UI:
 - release table/list
 - active/default release marker
+- installed marker
 - runtime version
 - release status
 - entrypoint
@@ -113,6 +116,19 @@ Done when:
 - active release changes in UI
 - `mode application home` reflects the new active release after refresh
 
+### Task 2.5
+Wire uninstall action for installed-but-not-active release.
+
+Command:
+```bash
+sce app runtime uninstall --app customer-order-demo --release <release-id> --json
+```
+
+Done when:
+- uninstall button is shown only for installed and non-active release
+- uninstall removes local installed state after refresh
+- the same release can be installed again through existing install flow
+
 ## Phase 3: Ontology Mode
 
 ### Task 3.1
@@ -288,6 +304,7 @@ Commands that matter now:
 - `sce app engineering activate`
 - `sce app runtime install`
 - `sce app runtime activate`
+- `sce app runtime uninstall`
 - `sce pm * upsert`
 - `sce ontology * upsert`
 
@@ -371,7 +388,7 @@ MagicBall can be considered adapted to the current SCE version when:
 4. Ontology Mode reads `sce ontology *`
 5. Assurance tabs read `sce assurance *`
 6. write actions pass `--auth-lease`
-7. install / activate / attach / hydrate actions work from the UI
+7. install / activate / uninstall / attach / hydrate actions work from the UI
 
 ## Practical Conclusion
 

package/docs/magicball-cli-invocation-examples.md

@@ -55,6 +55,8 @@ Typical fields MagicBall cares about:
 - `summary.app_name`
 - `summary.runtime_version`
 - `summary.install_status`
+- `summary.installed_release_id`
+- `summary.active_release_id`
 - `summary.release_count`
 - `view_model.current_release`
 
@@ -73,6 +75,11 @@ sce app runtime install --app customer-order-demo --release rel-2026-03 --json
 sce app runtime activate --app customer-order-demo --release rel-2026-03 --json
 ```
 
+### 2.5 Uninstall a non-active installed release
+```bash
+sce app runtime uninstall --app customer-order-demo --release rel-2026-03 --json
+```
+
 ## 3. Ontology Mode Examples
 
 ### 3.1 Read ontology home

package/docs/magicball-integration-issue-tracker.md

@@ -22,7 +22,7 @@ SCE changes completed and now available for MagicBall:
 - `mode ontology home --app ... --json`
 - `mode engineering home --app ... --json`
 - `app registry status/configure/sync*`
-- `app runtime show/releases/install/activate`
+- `app runtime show/releases/install/activate/uninstall`
 - `app engineering show/attach/hydrate/activate`
 - `pm requirement/tracking/planning/change/issue` data plane
 - `ontology er/br/dl` + `ontology triad summary`
@@ -33,7 +33,7 @@ SCE changes completed and now available for MagicBall:
 ### Current recommended MagicBall consumption order
 1. consume `mode * home` as the top-level source for the three modes
 2. consume `pm`, `ontology`, and `assurance` table payloads
-3. wire runtime install/activate and engineering attach/hydrate/activate actions
+3. wire runtime install/activate/uninstall and engineering attach/hydrate/activate actions
 4. use demo app: `customer-order-demo`
 
 ### Related SCE docs

package/docs/magicball-sce-adaptation-guide.md

@@ -25,7 +25,7 @@ Use these documents together:
 SCE currently provides MagicBall-facing support for:
 1. `app bundle registry`
 2. `application / ontology / engineering home projections`
-3. `app runtime install / activate`
+3. `app runtime install / activate / uninstall`
 4. `app engineering attach / hydrate / activate`
 5. `pm` delivery data plane
 6. `ontology` triad data plane
@@ -100,7 +100,7 @@ Use `docs/magicball-cli-invocation-examples.md` for copy-ready commands.
 - `sce app engineering show`
 
 ### Runtime and engineering control
-- `sce app runtime show/releases/install/activate`
+- `sce app runtime show/releases/install/activate/uninstall`
 - `sce app engineering show/attach/hydrate/activate`
 - `sce app registry status/configure/sync*`
 

package/docs/magicball-write-auth-adaptation-guide.md

@@ -67,6 +67,7 @@ Current implemented write flows in SCE imply these practical action families:
 - `app:engineering:activate`
 - `app:runtime:install`
 - `app:runtime:activate`
+- `app:runtime:uninstall`
 
 ### Engineering mode PM data plane
 - `pm:requirement:upsert`
@@ -176,6 +177,7 @@ Recommended UI steps:
 | Activate engineering workspace | `sce app engineering activate` | `app:engineering:activate` |
 | Install runtime release | `sce app runtime install` | `app:runtime:install` |
 | Activate runtime release | `sce app runtime activate` | `app:runtime:activate` |
+| Uninstall runtime release | `sce app runtime uninstall` | `app:runtime:uninstall` |
 | Save requirement | `sce pm requirement upsert` | `pm:requirement:upsert` |
 | Save tracking item | `sce pm tracking upsert` | `pm:tracking:upsert` |
 | Save plan | `sce pm planning upsert` | `pm:planning:upsert` |
@@ -196,6 +198,11 @@ Recommended UI steps:
 sce auth grant --scope app:runtime:activate --reason "activate selected runtime release" --json
 ```
 
+### Runtime uninstall lease
+```bash
+sce auth grant --scope app:runtime:uninstall --reason "remove non-active installed runtime release" --json
+```
+
 ### Multiple scopes if one workflow batches mutations
 ```bash
 sce auth grant --scope app:engineering:attach,app:engineering:hydrate,app:engineering:activate --reason "initialize engineering workspace" --json

package/docs/multi-agent-coordination-guide.md

@@ -2,8 +2,8 @@
 
 > Enable multiple AI agents to work on the same sce project simultaneously without conflicts.
 
-**Version**: 3.6.51  
-**Last Updated**: 2026-03-15
+**Version**: 3.6.52  
+**Last Updated**: 2026-03-16
 
 ---
 

package/docs/releases/v3.6.52.md

@@ -0,0 +1,20 @@
+# v3.6.52 Release Notes
+
+Release date: 2026-03-16
+
+## Highlights
+
+- Added `sce app runtime uninstall` so MagicBall and CLI users can remove a non-active installed runtime release without editing local SCE state by hand.
+- Split runtime projection semantics so installed release and active release are exposed separately in runtime/app-home payloads.
+- Extended co-work governance auditing to enforce shared `errorbook` registry availability and managed `errorbook_convergence` defaults as part of the default collaboration baseline.
+
+## Validation
+
+- `npx jest tests/unit/commands/app-mode.test.js --runInBand`
+- `npx jest tests/unit/workspace/collab-governance-audit.test.js tests/unit/scripts/collab-governance-gate.test.js --runInBand`
+- `node scripts/collab-governance-gate.js --json`
+
+## Release Notes
+
+- This patch closes two integration gaps: MagicBall can now offer uninstall/reinstall flows cleanly, and co-work governance now treats shared failure-learning resources as a real default baseline instead of a merely available optional capability.
+- The runtime model is still a single-installation-slot design; multiple release selection is supported, but multiple local installed runtime versions per app are not introduced in this patch.

package/docs/releases/v3.6.53.md

@@ -0,0 +1,19 @@
+# v3.6.53 Release Notes
+
+Release date: 2026-03-16
+
+## Highlights
+
+- Closed the co-work loop for same-project high-value `errorbook` knowledge by adding a tracked shared projection at `.sce/knowledge/errorbook/project-shared-registry.json`.
+- Baseline/template projects now seed the shared projection source by default, so another computer can recover historical specs and curated project errorbook knowledge after normal Git sync.
+- Collaboration governance now blocks managed push/publish when the shared project errorbook projection is missing, disabled, invalid, or not Git-tracked.
+
+## Validation
+
+- `npx jest tests/unit/commands/errorbook.test.js tests/unit/workspace/takeover-baseline.test.js tests/unit/workspace/collab-governance-audit.test.js tests/integration/takeover-baseline-cli.integration.test.js --runInBand`
+- `node scripts/release-doc-version-audit.js --fail-on-error`
+- `node scripts/collab-governance-gate.js --fail-on-violation --json`
+
+## Release Notes
+
+- This patch turns “shared errorbook experience” from a config-level promise into a real same-project continuity path. Historical specs stay Git-shared as before, while high-value `verified/promoted` errorbook knowledge now has a dedicated tracked projection instead of leaking raw `.sce/errorbook/**` runtime state into version control.

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

@@ -0,0 +1,20 @@
+# v3.6.52 发布说明
+
+发布日期：2026-03-16
+
+## 重点变化
+
+- 新增 `sce app runtime uninstall`，MagicBall 和 CLI 现在都可以在不手改本地状态的前提下卸载“已安装但未激活”的运行时版本。
+- 运行时投影语义已拆分为“已安装版本”和“当前激活版本”，前端不再需要自行猜测 installed / active 状态。
+- co-work 治理审计已扩展为默认检查共享 `errorbook` registry 是否可用，以及 managed 项目的 `errorbook_convergence` 基线是否漂移。
+
+## 验证
+
+- `npx jest tests/unit/commands/app-mode.test.js --runInBand`
+- `npx jest tests/unit/workspace/collab-governance-audit.test.js tests/unit/scripts/collab-governance-gate.test.js --runInBand`
+- `node scripts/collab-governance-gate.js --json`
+
+## 发布说明
+
+- 这个补丁版补上了两个真实缺口：一是 MagicBall 运行时版本管理终于具备卸载/重装闭环，二是 co-work 默认协作基线开始真正把共享错题经验资源视为必备能力，而不是“仓库里有这个功能就算支持”。
+- 当前运行时仍然是“单安装槽位”模型；本次支持多版本选择，但不引入同一 app 多个本地安装版本并存。

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

@@ -0,0 +1,19 @@
+# v3.6.53 发布说明
+
+发布日期：2026-03-16
+
+## 重点变化
+
+- 补齐了同一项目 co-work 下高价值 `errorbook` 经验的闭环，新增 Git 跟踪投影文件 `.sce/knowledge/errorbook/project-shared-registry.json`。
+- baseline / template 现在默认带上这个共享投影源，另一台电脑正常 `git pull` 后即可同时拿到历史 spec 和项目级高价值错题经验。
+- 协作治理现在会阻断缺失、禁用、损坏或未纳入 Git 跟踪的项目共享错题投影，避免“能力存在但默认不生效”。
+
+## 验证
+
+- `npx jest tests/unit/commands/errorbook.test.js tests/unit/workspace/takeover-baseline.test.js tests/unit/workspace/collab-governance-audit.test.js tests/integration/takeover-baseline-cli.integration.test.js --runInBand`
+- `node scripts/release-doc-version-audit.js --fail-on-error`
+- `node scripts/collab-governance-gate.js --fail-on-violation --json`
+
+## 发布说明
+
+- 这个补丁版把“共享错题经验”从配置层能力补成了真正可落地的同项目跨电脑延续机制。历史 spec 仍按原方式走 Git 共享，而高价值 `verified/promoted` 错题经验则通过单独的受控投影文件同步，不再把 `.sce/errorbook/**` 运行态数据直接带入版本库。

package/lib/commands/app.js

@@ -89,17 +89,77 @@ function buildBundleSummary(graph = {}) {
   };
 }
 
-function buildRuntimeSummary(graph = {}) {
+function getRuntimeProjectionState(graph = {}) {
   const bundle = graph.bundle || {};
   const runtimeRelease = graph.runtime_release || {};
   const metadata = bundle.metadata && typeof bundle.metadata === 'object' ? bundle.metadata : {};
   const installation = metadata.runtime_installation && typeof metadata.runtime_installation === 'object'
     ? metadata.runtime_installation
     : {};
+  const runtimeActivation = metadata.runtime_activation && typeof metadata.runtime_activation === 'object'
+    ? metadata.runtime_activation
+    : {};
   const serviceCatalog = metadata.service_catalog && typeof metadata.service_catalog === 'object'
     ? metadata.service_catalog
     : {};
   const releases = Array.isArray(serviceCatalog.releases) ? serviceCatalog.releases : [];
+  const installStatus = normalizeString(installation.status) || 'not-installed';
+  const installedReleaseId = installStatus === 'installed'
+    ? (normalizeString(installation.release_id) || null)
+    : null;
+  const activeReleaseId = normalizeString(
+    bundle.runtime_release_id
+    || runtimeRelease.release_id
+    || runtimeActivation.active_release_id
+  ) || null;
+
+  return {
+    metadata,
+    installation,
+    runtimeActivation,
+    serviceCatalog,
+    releases,
+    installStatus,
+    installedReleaseId,
+    activeReleaseId
+  };
+}
+
+function buildRuntimeReleaseItems(graph = {}) {
+  const state = getRuntimeProjectionState(graph);
+  return state.releases.map((item) => {
+    const releaseId = normalizeString(item && item.release_id) || null;
+    const installed = Boolean(releaseId && state.installedReleaseId && releaseId === state.installedReleaseId);
+    const active = Boolean(releaseId && state.activeReleaseId && releaseId === state.activeReleaseId);
+    const availableActions = [];
+
+    if (!installed) {
+      availableActions.push('install');
+    }
+    if (!active) {
+      availableActions.push('activate');
+    }
+    if (installed && !active) {
+      availableActions.push('uninstall');
+    }
+
+    return {
+      ...item,
+      installed,
+      active,
+      installation_status: installed ? state.installStatus : 'not-installed',
+      can_install: !installed,
+      can_activate: !active,
+      can_uninstall: installed && !active,
+      available_actions: availableActions
+    };
+  });
+}
+
+function buildRuntimeSummary(graph = {}) {
+  const bundle = graph.bundle || {};
+  const runtimeRelease = graph.runtime_release || {};
+  const state = getRuntimeProjectionState(graph);
   return {
     app_id: bundle.app_id || null,
     app_name: bundle.app_name || null,
@@ -107,10 +167,11 @@ function buildRuntimeSummary(graph = {}) {
     runtime_version: runtimeRelease.runtime_version || null,
     release_status: runtimeRelease.release_status || null,
     runtime_status: runtimeRelease.runtime_status || null,
-    install_status: installation.status || 'not-installed',
-    install_root: installation.install_root || null,
-    release_count: releases.length,
-    active_release_id: installation.release_id || bundle.runtime_release_id || runtimeRelease.release_id || null
+    install_status: state.installStatus,
+    install_root: state.installation.install_root || null,
+    release_count: state.releases.length,
+    installed_release_id: state.installedReleaseId,
+    active_release_id: state.activeReleaseId
   };
 }
 
@@ -564,8 +625,7 @@ async function runAppRuntimeShowCommand(options = {}, dependencies = {}) {
     throw new Error('--app is required');
   }
   const { graph } = await requireAppGraph(appRef, dependencies);
-  const metadata = graph.bundle && graph.bundle.metadata && typeof graph.bundle.metadata === 'object' ? graph.bundle.metadata : {};
-  const serviceCatalog = metadata.service_catalog && typeof metadata.service_catalog === 'object' ? metadata.service_catalog : {};
+  const state = getRuntimeProjectionState(graph);
   const payload = {
     mode: 'app-runtime-show',
     generated_at: new Date().toISOString(),
@@ -575,12 +635,14 @@ async function runAppRuntimeShowCommand(options = {}, dependencies = {}) {
     summary: buildRuntimeSummary(graph),
     bundle: graph.bundle,
     runtime_release: graph.runtime_release,
-    runtime_installation: metadata.runtime_installation || null,
+    runtime_installation: Object.keys(state.installation).length > 0 ? state.installation : null,
+    runtime_activation: Object.keys(state.runtimeActivation).length > 0 ? state.runtimeActivation : null,
     service_catalog: {
-      default_release_id: serviceCatalog.default_release_id || null,
-      release_count: Array.isArray(serviceCatalog.releases) ? serviceCatalog.releases.length : 0,
-      source: serviceCatalog.source || null
-    }
+      default_release_id: state.serviceCatalog.default_release_id || null,
+      release_count: state.releases.length,
+      source: state.serviceCatalog.source || null
+    },
+    releases: buildRuntimeReleaseItems(graph)
   };
   printPayload(payload, options, 'App Runtime Show');
   return payload;
@@ -592,9 +654,8 @@ async function runAppRuntimeReleasesCommand(options = {}, dependencies = {}) {
     throw new Error('--app is required');
   }
   const { graph } = await requireAppGraph(appRef, dependencies);
-  const metadata = graph.bundle && graph.bundle.metadata && typeof graph.bundle.metadata === 'object' ? graph.bundle.metadata : {};
-  const serviceCatalog = metadata.service_catalog && typeof metadata.service_catalog === 'object' ? metadata.service_catalog : {};
-  const releases = Array.isArray(serviceCatalog.releases) ? serviceCatalog.releases : [];
+  const state = getRuntimeProjectionState(graph);
+  const releases = buildRuntimeReleaseItems(graph);
   const payload = {
     mode: 'app-runtime-releases',
     generated_at: new Date().toISOString(),
@@ -603,12 +664,14 @@ async function runAppRuntimeReleasesCommand(options = {}, dependencies = {}) {
     },
     summary: {
       total: releases.length,
-      default_release_id: serviceCatalog.default_release_id || null
+      default_release_id: state.serviceCatalog.default_release_id || null,
+      installed_release_id: state.installedReleaseId,
+      active_release_id: state.activeReleaseId
     },
     items: releases,
     view_model: {
       type: 'table',
-      columns: ['release_id', 'runtime_version', 'release_channel', 'release_status', 'runtime_status', 'published_at']
+      columns: ['release_id', 'runtime_version', 'release_channel', 'release_status', 'runtime_status', 'installed', 'active', 'published_at']
     },
     mb_status: graph.runtime_release && graph.runtime_release.runtime_status ? graph.runtime_release.runtime_status : (graph.bundle && graph.bundle.status ? graph.bundle.status : 'unknown')
   };
@@ -704,6 +767,58 @@ async function runAppRuntimeActivateCommand(options = {}, dependencies = {}) {
   return payload;
 }
 
+async function runAppRuntimeUninstallCommand(options = {}, dependencies = {}) {
+  const appRef = normalizeString(options.app);
+  if (!appRef) {
+    throw new Error('--app is required');
+  }
+  await ensureAuthorized('app:runtime:uninstall', options, dependencies);
+  const fileSystem = dependencies.fileSystem || fs;
+  const { store, graph } = await requireAppGraph(appRef, dependencies);
+  const nextPayload = graphToRegisterPayload(graph);
+  const state = getRuntimeProjectionState(graph);
+  const installedReleaseId = state.installedReleaseId;
+  const targetReleaseId = normalizeString(options.release) || installedReleaseId;
+
+  if (!installedReleaseId) {
+    throw new Error('no installed runtime release found for this app');
+  }
+  if (!targetReleaseId || targetReleaseId !== installedReleaseId) {
+    throw new Error(`runtime release is not installed: ${targetReleaseId || '<unknown>'}`);
+  }
+  if (state.activeReleaseId && targetReleaseId === state.activeReleaseId) {
+    throw new Error(`cannot uninstall active runtime release ${targetReleaseId}; activate another release first`);
+  }
+
+  const installRoot = normalizeString(state.installation.install_root);
+  if (installRoot) {
+    await fileSystem.remove(installRoot);
+  }
+
+  nextPayload.metadata = nextPayload.metadata || {};
+  nextPayload.metadata.runtime_installation = {
+    status: 'not-installed',
+    release_id: null,
+    install_root: null,
+    uninstalled_at: new Date().toISOString(),
+    source: 'sce app runtime uninstall',
+    previous_release_id: targetReleaseId
+  };
+
+  const updated = await store.registerAppBundle(nextPayload);
+  const updatedState = getRuntimeProjectionState(updated);
+  const payload = {
+    mode: 'app-runtime-uninstall',
+    success: true,
+    summary: buildRuntimeSummary(updated),
+    uninstalled_release_id: targetReleaseId,
+    removed_install_root: installRoot || null,
+    runtime_installation: updatedState.installation
+  };
+  printPayload(payload, options, 'App Runtime Uninstall');
+  return payload;
+}
+
 function safeRun(handler, options = {}, context = 'app command') {
   Promise.resolve(handler(options))
     .catch((error) => {
@@ -839,6 +954,17 @@ function registerAppCommands(program) {
     .option('--json', 'Print machine-readable JSON output')
     .action((options) => safeRun(runAppRuntimeActivateCommand, options, 'app runtime activate'));
 
+  runtime
+    .command('uninstall')
+    .description('Uninstall runtime release for one app bundle')
+    .requiredOption('--app <app-id-or-key>', 'App id or app key')
+    .option('--release <release-id>', 'Installed runtime release id')
+    .option('--auth-lease <lease-id>', 'Write authorization lease id')
+    .option('--auth-password <password>', 'Inline auth password if policy allows')
+    .option('--actor <actor>', 'Audit actor override')
+    .option('--json', 'Print machine-readable JSON output')
+    .action((options) => safeRun(runAppRuntimeUninstallCommand, options, 'app runtime uninstall'));
+
   const engineering = app
     .command('engineering')
     .description('Manage engineering project projection for one app bundle');
@@ -903,6 +1029,7 @@ module.exports = {
   runAppRuntimeReleasesCommand,
   runAppRuntimeInstallCommand,
   runAppRuntimeActivateCommand,
+  runAppRuntimeUninstallCommand,
   runAppEngineeringShowCommand,
   runAppEngineeringAttachCommand,
   runAppEngineeringHydrateCommand,