expo-harmony-toolkit 1.9.3 → 1.10.0

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.9.3-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.10.0-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.9.3` keeps the `v1.9.2` Wave A baseline and brings ccnubox-first `react-native-webview`, JPush runtime, `expo-media-library`, `lottie-react-native`, and `@shopify/react-native-skia` into Third-party Native Wave B formal experimental onboarding. The public promise remains tighter: `latest` only carries fully accepted `verified` capabilities, and Wave B does not widen the current `verified` boundary.
+> `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.
 
 > [!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,10 +48,10 @@
 <!-- GENERATED:readme-current-status:start -->
 | Item | Status |
 | --- | --- |
-| Current version | `v1.9.3` |
+| Current version | `v1.10.0` |
 | Support model | `verified + preview + experimental` |
 | Public `verified` matrix | `expo55-rnoh082-ui-stack` |
-| Supported input | Managed/CNG Expo projects; bare workflow intake baseline |
+| 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` |

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.9.3-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.10.0-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.9.3` 延续 `v1.9.2` 的 Wave A 基线，并把 ccnubox 优先的 `react-native-webview`、JPush runtime、`expo-media-library`、`lottie-react-native` 与 `@shopify/react-native-skia` 纳入 Third-party Native Wave B formal experimental onboarding。当前公开承诺仍然收紧为：`latest` 只承诺完整验收的 `verified` 能力，Wave B 不放宽当前 `verified` 边界。
+> `v1.10.0` 冻结 Any-project Intake：任何 Expo 项目进入 `doctor` 后都应得到 `coverageProfile`、明确 `gapCategory` 与有序 `nextActions`。当前公开承诺仍然收紧为：`latest` 只承诺完整验收的 `verified` 能力；v1.10.0 不是 verified 扩容，也不承诺 catalog 外项目都能可靠打包。
 
 > [!TIP]
 > 由于当前公开矩阵内的两套 `@react-native-oh-tpl/*` adapter 依赖以 Git URL + exact commit 形式接入，仓库开发和官方 UI-stack sample 推荐使用 `pnpm install --ignore-scripts`，避免 Git adapter 在 prepare 阶段拉取私有资源而中断安装。
@@ -48,10 +48,10 @@
 <!-- GENERATED:readme-current-status:start -->
 | 项目 | 说明 |
 | --- | --- |
-| 当前版本 | `v1.9.3` |
+| 当前版本 | `v1.10.0` |
 | 支持模型 | `verified + preview + experimental` |
 | 唯一 `verified` 公开矩阵 | `expo55-rnoh082-ui-stack` |
-| 输入范围 | Managed/CNG Expo 项目；bare workflow intake baseline |
+| 输入范围 | 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` |

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.9.3";
+export declare const TOOLKIT_VERSION = "1.10.0";
 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.9.3';
+exports.TOOLKIT_VERSION = '1.10.0';
 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

@@ -499,51 +499,44 @@ function buildNextActions(input) {
         'config.scheme.missing',
         'config.bundle_script.mismatch',
     ].includes(issue.code));
+    const hasThirdPartyWaveA = dependencies.some((dependency) => THIRD_PARTY_WAVE_A_PACKAGE_NAMES.has(dependency.name));
+    const hasThirdPartyWaveB = dependencies.some((dependency) => THIRD_PARTY_WAVE_B_PACKAGE_NAMES.has(dependency.name));
     if (hasBlockingIssueCode(blockingIssues, 'matrix.expo_sdk.unsupported') ||
         hasBlockingIssueCode(blockingIssues, 'dependency.version_mismatch') ||
         hasBlockingIssueCode(blockingIssues, 'dependency.specifier_mismatch') ||
         hasBlockingIssueCode(blockingIssues, 'dependency.required_missing')) {
         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.');
+    }
+    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.');
+    }
+    if (hasBlockingIssueCode(blockingIssues, 'config.native_identifier.missing')) {
+        actions.push('Set `android.package` or `ios.bundleIdentifier` in Expo config before expecting a strict Harmony build path.');
+    }
     if (targetTier === 'verified' && hasPreviewCapabilities) {
         actions.push('Use `expo-harmony doctor --project-root . --target-tier preview` to measure the current preview-capability baseline while keeping `latest` pinned to verified-only releases.');
     }
     if (hasPreviewCapabilities) {
         actions.push('Keep combined sample smoke for regression coverage, but track bundle/debug/device/release evidence separately for each preview capability before promotion.');
     }
-    switch (coverageProfile) {
-        case 'managed-core':
-            actions.push('Stay on the verified lane: rerun `expo-harmony sync-template --project-root .`, `expo-harmony bundle --project-root .`, and `expo-harmony build-hap --project-root . --mode debug` before claiming release readiness.');
-            break;
-        case 'managed-native-heavy':
-            actions.push('After every native-capability change, rerun `expo-harmony sync-template --project-root .`, `expo-harmony bundle --project-root .`, and `expo-harmony build-hap --project-root . --mode debug` to keep the managed sidecar and preview evidence aligned.');
-            break;
-        case '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.');
-            break;
-        case 'third-party-native-heavy':
-            if (dependencies.some((dependency) => THIRD_PARTY_WAVE_A_PACKAGE_NAMES.has(dependency.name))) {
-                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.');
-            }
-            if (dependencies.some((dependency) => THIRD_PARTY_WAVE_B_PACKAGE_NAMES.has(dependency.name))) {
-                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.');
-            }
-            if (!dependencies.some((dependency) => THIRD_PARTY_WAVE_A_PACKAGE_NAMES.has(dependency.name)) &&
-                !dependencies.some((dependency) => THIRD_PARTY_WAVE_B_PACKAGE_NAMES.has(dependency.name))) {
-                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.');
-            }
-            break;
-    }
-    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.');
-    }
     if (blockingIssues.some((issue) => issue.code === 'dependency.not_allowed' &&
         (issue.subject === 'react-native-gesture-handler' ||
             issue.subject === '@react-native-oh-tpl/react-native-gesture-handler'))) {
         actions.push('Keep `react-native-gesture-handler` on the formal experimental slice until its Harmony adapter path closes device and release evidence.');
     }
-    if (hasBlockingIssueCode(blockingIssues, 'config.native_identifier.missing')) {
-        actions.push('Set `android.package` or `ios.bundleIdentifier` in Expo config before expecting a strict Harmony build path.');
+    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.');
+        }
+        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.');
+        }
+        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.');
+        }
     }
     if (dependencies.some((dependency) => dependency.buildabilityRisk === 'native-risk')) {
         actions.push('Inspect unknown native-looking dependencies and either replace them, gate them behind preview work, or onboard them explicitly before promising Harmony portability.');
@@ -551,6 +544,12 @@ function buildNextActions(input) {
     if (dependencies.some((dependency) => dependency.buildabilityRisk === 'js-only-unknown')) {
         actions.push('Unknown JavaScript-only packages still sit outside the public matrix; verify bundling manually, but prioritize native gaps first.');
     }
+    if (coverageProfile === 'managed-core') {
+        actions.push('Stay on the verified lane: rerun `expo-harmony sync-template --project-root .`, `expo-harmony bundle --project-root .`, and `expo-harmony build-hap --project-root . --mode debug` before claiming release readiness.');
+    }
+    if (coverageProfile === 'managed-native-heavy') {
+        actions.push('After every native-capability change, rerun `expo-harmony sync-template --project-root .`, `expo-harmony bundle --project-root .`, and `expo-harmony build-hap --project-root . --mode debug` to keep the managed sidecar and preview evidence aligned.');
+    }
     return dedupeStrings(actions);
 }
 function hasBlockingIssueCode(issues, code) {

package/build/data/publicDocs.d.ts

@@ -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.9.3";
+export declare const PUBLIC_CURRENT_VERSION = "1.10.0";

package/build/docs/render.js

@@ -35,8 +35,8 @@ function renderReadmeCurrentStatus(locale) {
         ? `\`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}`;
     const inputValue = locale === 'zh'
-        ? 'Managed/CNG Expo 项目；bare workflow intake baseline'
-        : 'Managed/CNG Expo projects; bare workflow intake baseline';
+        ? 'Managed/CNG Expo 项目；bare 与 catalog 外项目 intake 分类'
+        : 'Managed/CNG Expo projects; bare and catalog-out intake classification';
     const listJoiner = locale === 'zh' ? '、' : ', ';
     return [
         `| ${headers[0]} | ${headers[1]} |`,

package/docs/cli-build.md

@@ -1,6 +1,6 @@
 # CLI 构建指南
 
-`v1.9.3` 延续 `verified + preview + experimental` 支持分层，把 ccnubox-first Third-party Native Wave B 纳入 formal experimental onboarding；`expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
+`v1.10.0` 延续 `verified + preview + experimental` 支持分层，并冻结 Any-project Intake：`doctor` 必须能分类任意 Expo 项目、标出 blocker 类型并给出有序下一步；`expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
 
 CLI 命令集合不变：
 

package/docs/roadmap.md

@@ -204,7 +204,7 @@
 
 目标日期：`2026-10-31`
 
-状态：implementation baseline complete；simulator delivery gate pending target；device / release evidence carryover。
+状态：implementation baseline complete；simulator delivery gate complete on ccnubox_rn；device / release evidence carryover。
 
 目标：扩大第三方 native 覆盖，并把 `v1.9.0` 建好的最小 regression farm 扩容成持续回归面。
 
@@ -229,6 +229,8 @@
 
 目标日期：`2026-11-15`
 
+状态：`implementation target`，本阶段首个正式发布版本直接使用 `1.10.0` / `v1.10.0`；发布动作另行执行。
+
 目标：先冻结“任何 Expo 项目”入口面的产品故事，确保不存在无法分类、无法给下一步、无法明确阻断原因的项目。
 
 - `doctor` 对任意 Expo 项目必须满足：
@@ -238,6 +240,14 @@
 - roadmap / support matrix / acceptance board 与实际 catalog 保持零漂移
 - 对外叙事从“更多项目开始进入主线”升级成“任何项目都有明确处理路径”
 
+Acceptance checklist：
+
+- 新增 `fixtures/v110-*` 覆盖 catalog managed、bare、unknown JS-only、unknown native-looking、mixed intake
+- `nextActions[]` 固定按版本矩阵问题 -> 项目形态问题 -> native blocker -> unknown JS/native 依赖 -> build gate 排序
+- `acceptance/v1.10.0-acceptance.md` 记录 repo-only gate 与边界
+- 不提升任何 capability 到 `verified`
+- 不要求真机 device evidence
+
 ### v1.11.0 Final Blocker Burn-down
 
 目标日期：`2026-11-30`

package/docs/support-matrix.md

@@ -1,6 +1,6 @@
-# v1.9 支持矩阵
+# v1.10 支持矩阵
 
-`v1.9` 继续采用 tiered support model，并把“层级”与“晋升距离”拆开表达：
+`v1.10` 继续采用 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.9.3` 新增的是 ccnubox-first Third-party Native Wave B formal experimental onboarding，不是 verified 扩容
+- `v1.10.0` 新增的是 Any-project Intake Freeze：任何 Expo 项目进入 `doctor` 后都应有分类、明确 blocker 类型与有序 `nextActions`
+- 这不是 verified 扩容；`latest` 仍只承诺完整验收的 `verified` 能力，catalog 外项目只承诺可诊断路径
 
 `doctor --strict` 继续只代表 `verified`。
 
@@ -208,7 +209,7 @@ expo-harmony doctor --project-root /path/to/app --target-tier preview
 - `runtimeMode !== verified`，表示即使已有部分证据，也仍不属于正式承诺
 - `coverageProfile=bare`，表示当前项目已落入 bare workflow 主线规划，但不等于当前 matrix 已正式支持 bare
 - `gapCategory=third-party-native-gap`，表示问题不应再被模糊描述成普通 matrix drift，而是主线 blocker
-- `nextActions[]` 的顺序即 toolkit 当前建议的处理顺序
+- `nextActions[]` 的顺序即 toolkit 当前建议的处理顺序：版本矩阵问题 -> 项目形态问题 -> native blocker -> unknown JS/native 依赖 -> build gate
 
 当前公开阻断 issue code 继续包括：
 
@@ -247,7 +248,7 @@ toolkit 受管的核心产物仍包括：
 
 ## Release Tracks
 
-从 `v1.8` 开始，发布节奏按双轨设计；`v1.9.0` 继续沿用同一规则：
+从 `v1.8` 开始，发布节奏按双轨设计；`v1.10.0` 继续沿用同一规则：
 
 <!-- GENERATED:support-matrix-release-tracks:start -->
 - `latest`

package/package.json

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