expo-harmony-toolkit 1.10.0 → 1.11.2

package/README.en.md

@@ -9,7 +9,7 @@
   <p>
     <a href="https://github.com/BlackishGreen33/Expo-Harmony-Toolkit/actions/workflows/ci.yml"><img alt="Checks" src="https://img.shields.io/badge/checks-passing-16a34a?style=flat-square&logo=githubactions&logoColor=white"></a>
     <a href="./LICENSE"><img alt="License" src="https://img.shields.io/badge/license-MIT-0f766e?style=flat-square"></a>
-    <a href="https://github.com/BlackishGreen33/Expo-Harmony-Toolkit/releases"><img alt="Version" src="https://img.shields.io/badge/version-v1.10.0-111827?style=flat-square"></a>
+    <a href="https://github.com/BlackishGreen33/Expo-Harmony-Toolkit/releases"><img alt="Version" src="https://img.shields.io/badge/version-v1.11.2-111827?style=flat-square"></a>
     <a href="./docs/support-matrix.md"><img alt="Matrix" src="https://img.shields.io/badge/matrix-expo55--rnoh082--ui--stack-2563eb?style=flat-square"></a>
     <img alt="Input" src="https://img.shields.io/badge/input-Managed%2FCNG%20%2B%20bare%20intake-059669?style=flat-square">
   </p>
@@ -24,7 +24,7 @@
 </div>
 
 > [!IMPORTANT]
-> `v1.10.0` freezes Any-project Intake: any Expo project entering `doctor` should receive a `coverageProfile`, explicit `gapCategory`, and ordered `nextActions`. The public promise remains tighter: `latest` only carries fully accepted `verified` capabilities; v1.10.0 is not a verified expansion and does not promise reliable packaging for catalog-out projects.
+> `v1.11.2` has completed the pre-release non-device closeout: release HAP/runtime, bare workflow, and Third-party Native Wave A/B gaps stay explicit, and the ccnubox_rn signed simulator app-shell gate has passed. `v1.11.1` remains the first published public `v1.11.x`; the public promise stays tight: `latest` only carries fully accepted `verified` capabilities, and v1.11.2 is not a verified expansion and has not been published yet.
 
 > [!TIP]
 > The two validated `@react-native-oh-tpl/*` adapters in the public matrix are currently consumed via exact Git URLs and commits. For repository development and the official UI-stack sample, prefer `pnpm install --ignore-scripts` so adapter prepare hooks do not fail on private upstream resources.
@@ -48,14 +48,14 @@
 <!-- GENERATED:readme-current-status:start -->
 | Item | Status |
 | --- | --- |
-| Current version | `v1.10.0` |
+| Current version | `v1.11.2` |
 | Support model | `verified + preview + experimental` |
 | Public `verified` matrix | `expo55-rnoh082-ui-stack` |
 | Supported input | Managed/CNG Expo projects; bare and catalog-out intake classification |
 | `verified` JS/UI capabilities | `expo-router`, `expo-linking`, `expo-constants`, `react-native-reanimated`, `react-native-svg` |
 | `preview` native capabilities | `expo-file-system`, `expo-image-picker`, `expo-location`, `expo-camera`, `expo-secure-store`, `expo-asset`, `expo-device`, `expo-clipboard`, `expo-haptics` |
 | `experimental` capabilities | `expo-notifications`, `react-native-gesture-handler`, `@react-native-async-storage/async-storage`, `react-native-screens`, `react-native-safe-area-context`, `react-native-webview`, `jpush-react-native`, `expo-media-library`, `lottie-react-native`, `@shopify/react-native-skia` |
-| Release tracks | `latest` = fully accepted `verified` only; `next` = preview fast track |
+| Release tracks | `latest` = verified commitments plus stable toolkit patches; `next` = preview fast track |
 | Capability telemetry | `runtimeMode` + `evidence(...)` + `evidenceSource(...)` + `coverageProfile` + `nextActions` |
 | Build path | `doctor -> init -> bundle -> build-hap` |
 | Primary sample | `examples/official-ui-stack-sample` |
@@ -264,7 +264,7 @@ Additional preview evidence semantics:
 - `bundle/debugBuild` are marked as `automated`
 - `device` is marked as `manual-doc`, which means a human acceptance record exists rather than CI automation
 - `release` is marked as `none`, which means no release evidence exists yet
-- `v1.8.2` additionally records local signing plus simulator install/start evidence for the ccnubox release HAP; this only proves the minimal app-shell release-HAP path and does not close per-capability release acceptance
+- `v1.11.2` additionally records the current local ccnubox_rn dirty checkout signed simulator install/start gate; this only proves the app-shell non-device smoke and does not close per-capability release acceptance
 - `v1.8.3` aligns the RNOH runtime / CLI to the current latest `0.82.x` patch (`0.82.29`) while keeping the buildable `react-native@0.82.1` matrix boundary
 
 Manual Harmony acceptance still requires:

package/README.md

@@ -9,7 +9,7 @@
   <p>
     <a href="https://github.com/BlackishGreen33/Expo-Harmony-Toolkit/actions/workflows/ci.yml"><img alt="Checks" src="https://img.shields.io/badge/checks-passing-16a34a?style=flat-square&logo=githubactions&logoColor=white"></a>
     <a href="./LICENSE"><img alt="License" src="https://img.shields.io/badge/license-MIT-0f766e?style=flat-square"></a>
-    <a href="https://github.com/BlackishGreen33/Expo-Harmony-Toolkit/releases"><img alt="Version" src="https://img.shields.io/badge/version-v1.10.0-111827?style=flat-square"></a>
+    <a href="https://github.com/BlackishGreen33/Expo-Harmony-Toolkit/releases"><img alt="Version" src="https://img.shields.io/badge/version-v1.11.2-111827?style=flat-square"></a>
     <a href="./docs/support-matrix.md"><img alt="Matrix" src="https://img.shields.io/badge/matrix-expo55--rnoh082--ui--stack-2563eb?style=flat-square"></a>
     <img alt="Input" src="https://img.shields.io/badge/input-Managed%2FCNG%20%2B%20bare%20intake-059669?style=flat-square">
   </p>
@@ -24,7 +24,7 @@
 </div>
 
 > [!IMPORTANT]
-> `v1.10.0` 冻结 Any-project Intake：任何 Expo 项目进入 `doctor` 后都应得到 `coverageProfile`、明确 `gapCategory` 与有序 `nextActions`。当前公开承诺仍然收紧为：`latest` 只承诺完整验收的 `verified` 能力；v1.10.0 不是 verified 扩容，也不承诺 catalog 外项目都能可靠打包。
+> `v1.11.2` 已完成发布前非实机 closeout：release HAP/runtime、bare workflow 与 Third-party Native Wave A/B 的缺口继续被明确记录，ccnubox_rn 的 signed simulator app-shell gate 已通过。`v1.11.1` 仍是已发布的第一个公开 `v1.11.x`；当前公开承诺仍然收紧为：`latest` 只承诺完整验收的 `verified` 能力，v1.11.2 不是 verified 扩容，也尚未发布。
 
 > [!TIP]
 > 由于当前公开矩阵内的两套 `@react-native-oh-tpl/*` adapter 依赖以 Git URL + exact commit 形式接入，仓库开发和官方 UI-stack sample 推荐使用 `pnpm install --ignore-scripts`，避免 Git adapter 在 prepare 阶段拉取私有资源而中断安装。
@@ -48,14 +48,14 @@
 <!-- GENERATED:readme-current-status:start -->
 | 项目 | 说明 |
 | --- | --- |
-| 当前版本 | `v1.10.0` |
+| 当前版本 | `v1.11.2` |
 | 支持模型 | `verified + preview + experimental` |
 | 唯一 `verified` 公开矩阵 | `expo55-rnoh082-ui-stack` |
 | 输入范围 | Managed/CNG Expo 项目；bare 与 catalog 外项目 intake 分类 |
 | `verified` JS/UI 能力 | `expo-router`、`expo-linking`、`expo-constants`、`react-native-reanimated`、`react-native-svg` |
 | `preview` 原生能力 | `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera`、`expo-secure-store`、`expo-asset`、`expo-device`、`expo-clipboard`、`expo-haptics` |
 | `experimental` 能力 | `expo-notifications`、`react-native-gesture-handler`、`@react-native-async-storage/async-storage`、`react-native-screens`、`react-native-safe-area-context`、`react-native-webview`、`jpush-react-native`、`expo-media-library`、`lottie-react-native`、`@shopify/react-native-skia` |
-| 发布轨 | `latest` = fully accepted verified only；`next` = preview fast track |
+| 发布轨 | `latest` = 已验收 verified 承诺 + 不放宽承诺的稳定工具链 patch；`next` = preview fast track |
 | capability 遥测 | `runtimeMode` + `evidence(...)` + `evidenceSource(...)` + `coverageProfile` + `nextActions` |
 | 构建链 | `doctor -> init -> bundle -> build-hap` |
 | 主 sample | `examples/official-ui-stack-sample` |
@@ -270,7 +270,7 @@ preview 证据的额外说明：
 - `bundle/debugBuild` 标记为 `automated`
 - `device` 标记为 `manual-doc`，表示已有人工验收记录，不等于 CI 自动验收
 - `release` 标记为 `none`，表示当前仍没有 release 证据
-- `v1.8.2` 额外记录了 ccnubox release HAP 的本地签名、模拟器安装与启动证据；这只证明 app-shell release HAP 最低链路，不关闭单 capability release acceptance
+- `v1.11.2` 额外记录了当前本地 ccnubox_rn dirty checkout 的 signed simulator install/start gate；这只证明 app-shell 非实机 smoke，不关闭单 capability release acceptance
 - `v1.8.3` 将 RNOH runtime / CLI 对齐到当前 `0.82.x` 最新 patch（`0.82.29`），继续保留 `react-native@0.82.1` 的可构建矩阵边界
 
 手动 Harmony 验收继续要求：

package/build/core/constants.d.ts

@@ -1,6 +1,6 @@
 export declare const TOOLKIT_PACKAGE_NAME = "expo-harmony-toolkit";
 export declare const CLI_NAME = "expo-harmony";
-export declare const TOOLKIT_VERSION = "1.10.0";
+export declare const TOOLKIT_VERSION = "1.11.2";
 export declare const TEMPLATE_VERSION = "rnoh-0.82.29";
 export declare const RNOH_VERSION = "0.82.29";
 export declare const RNOH_CLI_VERSION = "0.82.29";

package/build/core/constants.js

@@ -3,7 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.DESIRED_PACKAGE_SCRIPTS = exports.HARMONY_RUNTIME_PRELUDE_RELATIVE_PATH = exports.HARMONY_ROUTER_ENTRY_FILENAME = exports.STRICT_ENV_EXIT_CODE = exports.STRICT_DOCTOR_EXIT_CODE = exports.DEFAULT_HVIGOR_PLUGIN_FILENAME = exports.PREBUILD_METADATA_FILENAME = exports.TOOLKIT_CONFIG_FILENAME = exports.BUILD_REPORT_FILENAME = exports.ENV_REPORT_FILENAME = exports.DOCTOR_REPORT_FILENAME = exports.MANIFEST_FILENAME = exports.SIGNING_LOCAL_EXAMPLE_FILENAME = exports.SIGNING_LOCAL_FILENAME = exports.GENERATED_SHIMS_DIR = exports.GENERATED_DIR = exports.SUPPORTED_EXPO_SDKS = exports.RNOH_CLI_VERSION = exports.RNOH_VERSION = exports.TEMPLATE_VERSION = exports.TOOLKIT_VERSION = exports.CLI_NAME = exports.TOOLKIT_PACKAGE_NAME = void 0;
 exports.TOOLKIT_PACKAGE_NAME = 'expo-harmony-toolkit';
 exports.CLI_NAME = 'expo-harmony';
-exports.TOOLKIT_VERSION = '1.10.0';
+exports.TOOLKIT_VERSION = '1.11.2';
 exports.TEMPLATE_VERSION = 'rnoh-0.82.29';
 exports.RNOH_VERSION = '0.82.29';
 exports.RNOH_CLI_VERSION = '0.82.29';

package/build/core/report.js

@@ -508,7 +508,7 @@ function buildNextActions(input) {
         actions.push(`Align Expo SDK, React Native, RNOH, and validated adapter versions to ${validatedMatrices_1.DEFAULT_VALIDATED_MATRIX_ID}, then rerun \`expo-harmony doctor --project-root . --strict\`.`);
     }
     if (coverageProfile === 'bare') {
-        actions.push('Keep this project on the bare workflow track for now: preserve the native directories, use `expo-harmony doctor --project-root .` for classification, and only claim verified support after bare workflow support lands in the mainline capability catalog.');
+        actions.push('Keep this project on the bare workflow track for now: preserve the native directories, use `expo-harmony doctor --project-root .` for classification, keep release HAP/runtime evidence as the v1.11.x blocker, and do not call it release-ready until that evidence closes.');
     }
     if (hasRouterBlockingIssues) {
         actions.push('Add the missing expo-router peers/plugin/scheme or update the Harmony bundle script to use `expo-harmony bundle`, then rerun doctor before trusting router builds.');
@@ -529,10 +529,10 @@ function buildNextActions(input) {
     }
     if (coverageProfile === 'third-party-native-heavy') {
         if (hasThirdPartyWaveA) {
-            actions.push('Keep Third-party Native Wave A on `doctor --target-tier experimental`: pair async-storage and screens with their Harmony adapters, keep safe-area on the toolkit shim, and close device/release evidence before any promotion.');
+            actions.push('Keep Third-party Native Wave A on `doctor --target-tier experimental`: pair async-storage and screens with their Harmony adapters, keep safe-area on the toolkit shim, and record fallback paths before any promotion when device/release evidence cannot close in v1.11.x.');
         }
         if (hasThirdPartyWaveB) {
-            actions.push('Keep Third-party Native Wave B on `doctor --target-tier experimental`: pair ccnubox WebView, media-library, Lottie, and Skia surfaces with their Harmony adapters, keep JPush runtime evidence separate, and require debug/release simulator delivery gates before shipping.');
+            actions.push('Keep Third-party Native Wave B on `doctor --target-tier experimental`: pair ccnubox WebView, media-library, Lottie, and Skia surfaces with their Harmony adapters, keep JPush runtime evidence separate, and record fallback paths if release/runtime evidence cannot close in v1.11.x.');
         }
         if (!hasThirdPartyWaveA && !hasThirdPartyWaveB) {
             actions.push('Isolate third-party native packages and onboard them through the mainline capability catalog one by one; start with `react-native-gesture-handler` if it is present, and treat unknown native surfaces as explicit unblockers rather than matrix drift.');

package/build/core/template.js

@@ -58,6 +58,7 @@ const TEMPLATE_FILE_PATHS = [
     'entry/src/main/resources/rawfile/.gitkeep',
 ];
 const RNOH_GENERATED_TS_SHIM_RELATIVE_PATH = path_1.default.join('harmony', 'oh_modules', '@rnoh', 'react-native-openharmony', 'ts.ts');
+const SIDECAR_DRIFT_REQUIRES_FORCE_WARNING_CODE = 'sidecar.drift.requires-force';
 exports.BUILD_REQUIRED_MANAGED_FILE_PATHS = [
     ...autolinking_1.AUTOLINKED_FILE_PATHS,
     RNOH_GENERATED_TS_SHIM_RELATIVE_PATH,
@@ -109,7 +110,7 @@ async function syncProjectTemplate(projectRoot, force = false, options = {}) {
             const shouldForce = force || forceManagedPaths.has(file.relativePath);
             if (!shouldForce && !managedByToolkit) {
                 result.skippedFiles.push(file.relativePath);
-                result.warnings.push(`Skipped ${file.relativePath} because it drifted from the last generated version. Re-run with --force to overwrite it.`);
+                result.warnings.push(renderSidecarDriftRequiresForceWarning(file.relativePath));
                 continue;
             }
         }
@@ -133,6 +134,9 @@ async function syncProjectTemplate(projectRoot, force = false, options = {}) {
     await fs_extra_1.default.writeJson(result.manifestPath, manifest, { spaces: 2 });
     return result;
 }
+function renderSidecarDriftRequiresForceWarning(relativePath) {
+    return `[${SIDECAR_DRIFT_REQUIRES_FORCE_WARNING_CODE}] Skipped managed sidecar file ${relativePath} because it drifted from the last generated version. Re-run expo-harmony sync-template --force or expo-harmony init --force to overwrite it.`;
+}
 async function buildManagedFiles(loadedProject, identifiers, previousToolkitConfig, doctorReport) {
     const hasExpoRouter = (0, support_1.usesExpoRouter)(loadedProject.packageJson);
     const doctorConfig = (0, project_1.resolveExpoHarmonyDoctorConfig)(loadedProject.expoConfig);

package/build/data/publicDocs.d.ts

@@ -1,5 +1,5 @@
 export declare const PUBLIC_RELEASE_TRACKS: {
-    readonly latest: "fully accepted verified only";
+    readonly latest: "verified commitments plus stable toolkit patches";
     readonly next: "preview fast track";
 };
 export declare const PRIMARY_SAMPLE_PATH = "examples/official-ui-stack-sample";
@@ -8,4 +8,4 @@ export declare const SUPPORTING_SAMPLE_PATHS: readonly ["examples/official-app-s
 export declare const VERIFIED_JS_UI_CAPABILITY_NAMES: readonly ["expo-router", "expo-linking", "expo-constants", ...("react-native-reanimated" | "react-native-svg")[]];
 export declare const PREVIEW_CAPABILITY_DEFINITIONS: import("..").CapabilityDefinition[];
 export declare const EXPERIMENTAL_CAPABILITY_NAMES: readonly string[];
-export declare const PUBLIC_CURRENT_VERSION = "1.10.0";
+export declare const PUBLIC_CURRENT_VERSION = "1.11.2";

package/build/data/publicDocs.js

@@ -5,7 +5,7 @@ const constants_1 = require("../core/constants");
 const capabilities_1 = require("./capabilities");
 const uiStack_1 = require("./uiStack");
 exports.PUBLIC_RELEASE_TRACKS = {
-    latest: 'fully accepted verified only',
+    latest: 'verified commitments plus stable toolkit patches',
     next: 'preview fast track',
 };
 exports.PRIMARY_SAMPLE_PATH = 'examples/official-ui-stack-sample';

package/build/docs/render.js

@@ -32,8 +32,8 @@ function renderReadmeCurrentStatus(locale) {
     const previewSampleLabel = locale === 'zh' ? 'preview sample' : 'Preview sample';
     const supportingSamplesLabel = locale === 'zh' ? '辅助 onboarding samples' : 'Supporting onboarding samples';
     const releaseTracksValue = locale === 'zh'
-        ? `\`latest\` = ${publicDocs_1.PUBLIC_RELEASE_TRACKS.latest}；\`next\` = ${publicDocs_1.PUBLIC_RELEASE_TRACKS.next}`
-        : `\`latest\` = fully accepted \`verified\` only; \`next\` = ${publicDocs_1.PUBLIC_RELEASE_TRACKS.next}`;
+        ? `\`latest\` = 已验收 verified 承诺 + 不放宽承诺的稳定工具链 patch；\`next\` = ${publicDocs_1.PUBLIC_RELEASE_TRACKS.next}`
+        : `\`latest\` = ${publicDocs_1.PUBLIC_RELEASE_TRACKS.latest}; \`next\` = ${publicDocs_1.PUBLIC_RELEASE_TRACKS.next}`;
     const inputValue = locale === 'zh'
         ? 'Managed/CNG Expo 项目；bare 与 catalog 外项目 intake 分类'
         : 'Managed/CNG Expo projects; bare and catalog-out intake classification';
@@ -134,6 +134,7 @@ function renderSupportMatrixCapabilityTelemetry(locale) {
             '- `runtimeMode=shim`：说明当前还在桥接或占位阶段，即使 bundle / debug build 已完成，也不应宣称 verified',
             '- `runtimeMode=adapter`：说明已经进入真实适配路径，但仍缺少某些验收证据',
             '- `runtimeMode=verified`：说明能力已进入正式承诺，且证据闭环完成',
+            '- `release=no[none]`：说明 release HAP/runtime evidence 尚未关闭，不能写成 release-ready',
         ]
         : [
             'All capabilities now publish the following fields together:',
@@ -154,6 +155,7 @@ function renderSupportMatrixCapabilityTelemetry(locale) {
             '- `runtimeMode=shim`: the capability is still on a bridge or placeholder path and must not be described as verified',
             '- `runtimeMode=adapter`: the capability is on a real adapter path but still lacks part of the evidence needed for verified promotion',
             '- `runtimeMode=verified`: the capability has entered the formal public promise and closed the evidence loop',
+            '- `release=no[none]`: release HAP/runtime evidence is still open and must not be described as release-ready',
         ];
     return lines.join('\n');
 }
@@ -241,8 +243,8 @@ function renderSupportMatrixReleaseTracks(locale) {
     return locale === 'zh'
         ? [
             '- `latest`',
-            '  - 只承接完整验收的 `verified` 能力',
-            '  - 只允许 verified sample / gate 作为发布依据',
+            '  - 承接完整验收的 `verified` 能力与不放宽承诺的稳定工具链 patch',
+            '  - 只允许 verified sample / gate、稳定工具链 gate 与明确 acceptance 作为发布依据',
             '- `next`',
             '  - 承接 preview fast track',
             '  - 必须至少通过 preview sample、bundle、debug build gate',
@@ -250,8 +252,8 @@ function renderSupportMatrixReleaseTracks(locale) {
         ].join('\n')
         : [
             '- `latest`',
-            '  - only carries fully accepted `verified` capabilities',
-            '  - only verified samples and gates may justify a release',
+            '  - carries fully accepted `verified` capabilities plus stable toolkit patches that do not widen the public promise',
+            '  - only verified samples/gates, stable toolkit gates, and explicit acceptance records may justify a release',
             '- `next`',
             '  - carries preview fast-track work',
             '  - must at least pass the preview sample, bundle, and debug-build gates',

package/docs/cli-build.md

@@ -1,6 +1,6 @@
 # CLI 构建指南
 
-`v1.10.0` 延续 `verified + preview + experimental` 支持分层，并冻结 Any-project Intake：`doctor` 必须能分类任意 Expo 项目、标出 blocker 类型并给出有序下一步；`expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
+`v1.11.2` 延续 `verified + preview + experimental` 支持分层，并完成发布前非实机 closeout：v1.11.x 剩余 blocker 继续写成 burn-down 台账与降级策略，ccnubox_rn signed simulator app-shell gate 已通过；`doctor` 继续分类任意 Expo 项目、标出 blocker 类型并给出有序下一步；`expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
 
 CLI 命令集合不变：
 

package/docs/npm-release.md

@@ -3,8 +3,8 @@
 `expo-harmony-toolkit` 继续公开发布到 npm，但从现在开始明确区分两条发布轨：
 
 - `latest`
-  - 只发布完整验收的 `verified` 能力
-  - 面向正式公开承诺
+  - 发布完整验收的 `verified` 能力，或不放宽公开承诺的稳定工具链 patch
+  - 面向正式公开承诺与稳定工具链修复
 - `next`
   - 承接 preview fast track
   - 面向更快的集成反馈，不等于 verified 或 release-ready
@@ -21,7 +21,7 @@
 
 推荐理解：
 
-- `latest` 解决“可以公开承诺什么”
+- `latest` 解决“可以公开承诺什么”，也承接不扩大承诺边界的稳定工具链 patch
 - `next` 解决“怎样更快收敛 preview 能力”
 
 ## 发布前检查
@@ -60,7 +60,9 @@ pnpm release:check
 
 - hosted CI 默认仍可通过 `EXPO_HARMONY_RELEASE_SKIP_HAP=1` 跳过真实 DevEco HAP 构建
 - debug / release HAP gate 继续由 capability acceptance、带工具链环境的 CI 或本地验收补齐
-- `v1.8.2` 已补一条 ccnubox release HAP 的本地签名、模拟器安装与启动记录；该记录不替代真机 device acceptance，也不把 preview capability 标为 release-ready
+- `v1.11.0` 是未发布的 burn-down ledger checkpoint；`v1.11.1` 是第一个公开 `v1.11.x`，发布到 `latest` 只代表 sidecar drift 工具链行为收口，不代表 verified/capability 边界放宽
+- `v1.11.2` 已完成发布前非实机 closeout 与 ccnubox signed simulator app-shell gate；不发布 tag/npm/GitHub Release 前，远端公开状态仍以已发布版本为准
+- `v1.11.2` 的 ccnubox signed simulator install/start 记录不替代真机 device acceptance，也不把 preview capability 标为 release-ready
 - `v1.8.3` 只刷新 RNOH runtime / CLI 到 `0.82.29`，仍不宣称 RN `0.83.x` 已进入公开 Harmony 矩阵
 - preview capability 若在报告里显示 `device=yes`，必须同时以 `evidenceSource.device=manual-doc` 对外说明其来源，不得表述成 CI 自动设备验证
 
@@ -135,7 +137,7 @@ pnpm add --ignore-scripts <tarball>
 
 ## 发布边界
 
-- `latest` 不承接 preview capability 的公开承诺
+- `latest` 不承接 preview capability 的公开承诺，但可以发布不扩大 verified 边界的稳定工具链 patch
 - `next` 可以承接 preview fast track，但不得替代 capability promotion gate
 - 任何声称 verified 的能力都必须具备：
   - `bundle`

package/docs/roadmap.md

@@ -229,7 +229,7 @@
 
 目标日期：`2026-11-15`
 
-状态：`implementation target`，本阶段首个正式发布版本直接使用 `1.10.0` / `v1.10.0`；发布动作另行执行。
+状态：released / complete；`1.10.0` / `v1.10.0` 已发布到 `latest`。
 
 目标：先冻结“任何 Expo 项目”入口面的产品故事，确保不存在无法分类、无法给下一步、无法明确阻断原因的项目。
 
@@ -248,10 +248,12 @@ Acceptance checklist：
 - 不提升任何 capability 到 `verified`
 - 不要求真机 device evidence
 
-### v1.11.0 Final Blocker Burn-down
+### v1.11.x Final Blocker Burn-down
 
 目标日期：`2026-11-30`
 
+状态：`v1.11.0` 是未发布的 burn-down ledger checkpoint；`v1.11.1` 是第一个公开 `v1.11.x`，发布到 `latest`，只收口 sidecar drift 工具链行为；`v1.11.2` 已完成发布前非实机 closeout 与 ccnubox signed simulator app-shell gate，不提升任何 capability 到 `verified`，且尚未发布。
+
 目标：把还会阻止“任何 Expo 项目可靠打包”的剩余高频 blocker 清到只剩极少数明确已知例外。
 
 - 逐项清掉剩余高频 blocker：
@@ -262,6 +264,29 @@ Acceptance checklist：
 - 对仍无法在 `v2.0.0` 前关闭的项，必须提前明确降级策略与替代路径
 - `v2.0.0` 不接受“先宣布完成，再慢慢补长尾”
 
+Burn-down ledger：
+
+- `release-evidence`：preview adapter capability 必须逐项补 per-capability release HAP runtime evidence；combined sample smoke 不能替代单项 release 验收
+- `bare-release-gap`：bare workflow 继续保留 intake / debug baseline，只有 release HAP 与 runtime evidence 补齐后才允许宣称 release-ready
+- `third-party-native`：Wave A / Wave B 继续停留在 `experimental`，先关闭 device / release evidence 或写明降级策略
+- `sidecar-drift`：所有 catalog-covered managed 项目都必须能重复执行 `sync-template -> bundle -> build-hap --mode debug`，drift 必须被明确报出或被可验证修复
+
+Sidecar drift audit：
+
+- `detected`：非 build-required managed sidecar drift 必须输出稳定 warning code：`sidecar.drift.requires-force`
+- `auto-refreshed build-required files`：bundle/build gate 必需的 autolinking 与 RNOH shim drift 可以自动刷新，不能误报 unresolved drift
+- `requires --force`：其他 managed sidecar drift 默认保留用户改动，并提示 `expo-harmony sync-template --force` 或 `expo-harmony init --force`
+- `accepted exception`：无法在 v1.11.x 关闭的真实项目 drift 必须写入 acceptance，不得扩写成 build/device/runtime pass
+
+Acceptance checklist：
+
+- 新增 `acceptance/v1.11.0-burn-down-ledger.md` 记录 v1.11.x 起始台账
+- 新增 `acceptance/v1.11.1-acceptance.md` 记录第一个公开 v1.11.x release、`v1.11.0` 不发布决策与 sidecar drift 收口结果
+- 更新 `acceptance/v1.11.2-acceptance.md` 记录非实机 closeout、ccnubox signed simulator app-shell gate、bare release gap 与 third-party fallback 策略
+- 明确本阶段不改变 `latest` / `verified` 边界
+- 不把 debug/release HAP build pass 表述为真机 device 或 runtime pass
+- 对每个无法在 v1.11.x 关闭的 blocker 写出降级或替代路径
+
 ### v2.0.0 Catalog-covered Expo Project Reliable Packaging
 
 原 `Any Expo Project Reliable Packaging` 叙事保留为 intake 目标，但可靠打包承诺明确收敛到 catalog-covered 项目。

package/docs/support-matrix.md

@@ -1,6 +1,6 @@
-# v1.10 支持矩阵
+# v1.11 支持矩阵
 
-`v1.10` 继续采用 tiered support model，并把“层级”“晋升距离”与“intake 分类”拆开表达：
+`v1.11` 继续采用 tiered support model，并把“层级”“晋升距离”与“intake 分类”拆开表达：
 
 - `supportTier` 表示公开承诺层级
 - `runtimeMode` 表示当前运行时接入形态：`shim`、`adapter`、`verified`
@@ -14,7 +14,8 @@
 - bare workflow 与第三方 native package 不再被描述成“收官后才考虑的另一条 extension 终局”
 - `v2.0.0` 本身被定义成“任何 Expo 项目都能可靠打包成鸿蒙 App”的目标版本
 - 但当前公开承诺依旧没有放宽；它们只是进入同一主线 backlog，而不是已经进入 `verified`
-- `v1.10.0` 新增的是 Any-project Intake Freeze：任何 Expo 项目进入 `doctor` 后都应有分类、明确 blocker 类型与有序 `nextActions`
+- `v1.10.0` 已冻结 Any-project Intake：任何 Expo 项目进入 `doctor` 后都应有分类、明确 blocker 类型与有序 `nextActions`
+- `v1.11.2` 已完成发布前非实机 closeout 与 ccnubox signed simulator app-shell gate；`v1.11.1` 是第一个公开 `v1.11.x`，只收口 sidecar drift 的可诊断行为；`v1.11.0` 保留为未发布的 burn-down ledger checkpoint
 - 这不是 verified 扩容；`latest` 仍只承诺完整验收的 `verified` 能力，catalog 外项目只承诺可诊断路径
 
 `doctor --strict` 继续只代表 `verified`。
@@ -92,6 +93,7 @@
 - `runtimeMode=shim`：说明当前还在桥接或占位阶段，即使 bundle / debug build 已完成，也不应宣称 verified
 - `runtimeMode=adapter`：说明已经进入真实适配路径，但仍缺少某些验收证据
 - `runtimeMode=verified`：说明能力已进入正式承诺，且证据闭环完成
+- `release=no[none]`：说明 release HAP/runtime evidence 尚未关闭，不能写成 release-ready
 <!-- GENERATED:support-matrix-capability-telemetry:end -->
 
 为了避免把“只差真机”与“当前子 API 还没实现到位”混在一起，`v1.8.x` 文档额外使用以下标记：
@@ -121,7 +123,7 @@
 - 四项 preview capability 都已经进入 `adapter` 路径；`device=yes[manual-doc]` 只表示已有人工设备验收记录，仍不代表 verified 或 release-ready
 - 当前原生 adapter preview baseline 的默认 evidenceSource 固定为：`bundle/debugBuild=automated`、`device=manual-doc`、`release=none`
 - `v1.9.0` 新增的 app foundation modules 当前是 `runtimeMode=shim`，`bundle/debugBuild=automated`，`device/release=none`
-- `v1.8.2` 的 ccnubox release HAP 模拟器安装/启动记录只证明 app-shell release 构建链路，不改变上述 per-capability `release=no[none]`
+- `v1.8.2` 的 ccnubox release HAP 模拟器安装/启动记录与 `v1.11.2` 的 ccnubox_rn signed simulator app-shell gate 都只证明 app-shell 非实机链路，不改变上述 per-capability `release=no[none]`
 - `v1.8.x` 开始，combined sample smoke 只负责总回归；每项 capability 还必须单独维护 device / release acceptance 记录，见 [acceptance/v1.8.x-capability-board.md](../acceptance/v1.8.x-capability-board.md)
 - `v1.8.x` repo 内可完成的 closeout 已完成；剩余 carryover 只包括单 capability 真机 device record 与 release HAP runtime acceptance
 - `expo-file-system`
@@ -248,12 +250,12 @@ toolkit 受管的核心产物仍包括：
 
 ## Release Tracks
 
-从 `v1.8` 开始，发布节奏按双轨设计；`v1.10.0` 继续沿用同一规则：
+从 `v1.8` 开始，发布节奏按双轨设计；`v1.11.2` 继续沿用同一规则：
 
 <!-- GENERATED:support-matrix-release-tracks:start -->
 - `latest`
-  - 只承接完整验收的 `verified` 能力
-  - 只允许 verified sample / gate 作为发布依据
+  - 承接完整验收的 `verified` 能力与不放宽承诺的稳定工具链 patch
+  - 只允许 verified sample / gate、稳定工具链 gate 与明确 acceptance 作为发布依据
 - `next`
   - 承接 preview fast track
   - 必须至少通过 preview sample、bundle、debug build gate
@@ -272,7 +274,7 @@ toolkit 受管的核心产物仍包括：
 - release signing / release HAP 验收完成
 - 文档、矩阵、roadmap、acceptance 记录同 PR 更新
 
-`v1.8.2` 记录的 simulator release-HAP evidence 只覆盖 ccnubox app-shell 的 signed HAP 构建、安装和启动；单 capability 的 release acceptance 仍必须按各自记录单独关闭。
+`v1.11.2` 记录的 simulator evidence 只覆盖当前本地 ccnubox_rn dirty checkout 的 signed HAP 构建、安装和启动；单 capability 的 release acceptance 仍必须按各自记录单独关闭。
 
 `v1.8.x` repo-only closeout 不改变 capability evidence source：`device=yes[manual-doc]` 仍只代表既有人工基线，`release=no[none]` 仍表示没有单 capability release HAP runtime evidence。
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expo-harmony-toolkit",
-  "version": "1.10.0",
+  "version": "1.11.2",
   "description": "面向 Managed/CNG Expo 项目的 HarmonyOS 迁移、准入检查与 UI-stack 构建工具链",
   "main": "app.plugin.js",
   "types": "build/index.d.ts",