expo-harmony-toolkit 1.7.0 → 1.7.2

package/build/data/capabilities.js

@@ -6,21 +6,35 @@ exports.isSupportTierAllowed = isSupportTierAllowed;
 exports.getCapabilityDefinitionsForProject = getCapabilityDefinitionsForProject;
 exports.collectCapabilityHarmonyPermissions = collectCapabilityHarmonyPermissions;
 const project_1 = require("../core/project");
+const PREVIEW_BASELINE_EVIDENCE = {
+    bundle: true,
+    debugBuild: true,
+    device: true,
+    release: false,
+};
+const EXPLORATORY_EVIDENCE = {
+    bundle: false,
+    debugBuild: false,
+    device: false,
+    release: false,
+};
 exports.CAPABILITY_DEFINITIONS = [
     {
         id: 'expo-file-system',
         packageName: 'expo-file-system',
         status: 'manual',
         supportTier: 'preview',
-        note: 'Preview bridge scaffolding is available through the managed Harmony shim path, but device persistence is not verified yet.',
+        runtimeMode: 'adapter',
+        evidence: PREVIEW_BASELINE_EVIDENCE,
+        note: 'Toolkit-managed Harmony native file-system adapters cover the v1.7.2 preview subset: UTF-8/base64 sandbox I/O, append and partial reads, md5 metadata, and direct downloads into the app sandbox.',
         docsUrl: 'https://github.com/react-native-oh-library/usage-docs/blob/master/en/react-native-fs.md',
         nativePackageNames: ['react-native-fs'],
         harmonyPermissions: [],
         sampleRoute: '/file-system',
         acceptanceChecklist: [
-            'Write a UTF-8 file into the app sandbox.',
-            'Read the file back and verify content.',
-            'Delete the file and verify the entry disappears.',
+            'Write UTF-8 and base64 content into the app sandbox.',
+            'Read back full and partial content and verify md5 metadata.',
+            'Download a remote file into the sandbox and clean up generated entries.',
         ],
     },
     {
@@ -28,15 +42,21 @@ exports.CAPABILITY_DEFINITIONS = [
         packageName: 'expo-image-picker',
         status: 'manual',
         supportTier: 'preview',
-        note: 'Preview bridge scaffolding is available, but image selection and camera capture still require device-side validation before promotion.',
+        runtimeMode: 'adapter',
+        evidence: PREVIEW_BASELINE_EVIDENCE,
+        note: 'Toolkit-managed Harmony adapters cover the v1.7.2 preview subset: media and camera permissions, single/multi-select library flows, system photo/video capture, pending-result restore, and richer video asset metadata.',
         docsUrl: 'https://github.com/react-native-oh-library/usage-docs/blob/master/en/react-native-image-picker.md',
         nativePackageNames: ['react-native-image-picker', 'react-native-permissions'],
-        harmonyPermissions: ['ohos.permission.CAMERA', 'ohos.permission.READ_IMAGEVIDEO'],
+        harmonyPermissions: [
+            'ohos.permission.CAMERA',
+            'ohos.permission.MICROPHONE',
+            'ohos.permission.READ_IMAGEVIDEO',
+        ],
         sampleRoute: '/image-picker',
         acceptanceChecklist: [
-            'Request media-library permissions and surface denied/cancel states.',
-            'Launch the image library flow and return one selected asset.',
-            'Launch the camera flow and surface denied/cancel states.',
+            'Request media-library and camera permissions and surface denied/cancel states.',
+            'Launch single, multi-select, and mixed library flows and return asset metadata.',
+            'Launch photo/video camera capture and restore one pending result when the JS side resumes.',
         ],
     },
     {
@@ -44,15 +64,22 @@ exports.CAPABILITY_DEFINITIONS = [
         packageName: 'expo-location',
         status: 'manual',
         supportTier: 'preview',
-        note: 'Preview bridge scaffolding is available for foreground permissions, current-position probes, and watch flows, but device-side runtime behavior is still pending verified promotion.',
+        runtimeMode: 'adapter',
+        evidence: PREVIEW_BASELINE_EVIDENCE,
+        note: 'Toolkit-managed Harmony adapters cover the v1.7.2 preview subset: foreground/background permission flows, current and last-known fixes, geocoding, continuous watch subscriptions, and sensor-backed heading updates.',
         docsUrl: 'https://github.com/react-native-oh-library/usage-docs/blob/master/en/%40react-native-community-geolocation.md',
         nativePackageNames: ['@react-native-community/geolocation', 'react-native-permissions'],
-        harmonyPermissions: ['ohos.permission.LOCATION', 'ohos.permission.APPROXIMATELY_LOCATION'],
+        harmonyPermissions: [
+            'ohos.permission.LOCATION',
+            'ohos.permission.APPROXIMATELY_LOCATION',
+            'ohos.permission.LOCATION_IN_BACKGROUND',
+            'ohos.permission.ACCELEROMETER',
+        ],
         sampleRoute: '/location',
         acceptanceChecklist: [
-            'Request foreground location permission.',
-            'Resolve one current position fix.',
-            'Start and stop a watchPosition subscription cleanly.',
+            'Request foreground and background location permissions.',
+            'Resolve current and last-known fixes plus one active watch update.',
+            'Resolve heading snapshot/watch updates and reverse-geocoded results.',
         ],
     },
     {
@@ -60,15 +87,17 @@ exports.CAPABILITY_DEFINITIONS = [
         packageName: 'expo-camera',
         status: 'manual',
         supportTier: 'preview',
-        note: 'Preview bridge scaffolding is available for permission, preview-surface, and capture-entry flows, but a verified Harmony-native runtime path is not public yet.',
+        runtimeMode: 'adapter',
+        evidence: PREVIEW_BASELINE_EVIDENCE,
+        note: 'Toolkit-managed Harmony adapters cover the v1.7.2 preview subset: embedded camera preview, still capture, preview pause/resume, microphone permission, and in-session video recording controls.',
         docsUrl: 'https://github.com/react-native-oh-library/usage-docs/blob/master/en/react-native-camera-kit.md',
         nativePackageNames: ['react-native-camera-kit', 'react-native-permissions'],
-        harmonyPermissions: ['ohos.permission.CAMERA'],
+        harmonyPermissions: ['ohos.permission.CAMERA', 'ohos.permission.MICROPHONE'],
         sampleRoute: '/camera',
         acceptanceChecklist: [
-            'Request camera permission.',
-            'Render a live preview without crashing the Harmony runtime.',
-            'Capture one photo and surface the asset metadata back to JS.',
+            'Request camera and microphone permissions.',
+            'Capture one photo and one embedded video result and surface metadata back to JS.',
+            'Exercise preview pause/resume plus denied or canceled outcomes without crashing the Harmony runtime.',
         ],
     },
     {
@@ -76,6 +105,8 @@ exports.CAPABILITY_DEFINITIONS = [
         packageName: 'expo-notifications',
         status: 'manual',
         supportTier: 'experimental',
+        runtimeMode: 'shim',
+        evidence: EXPLORATORY_EVIDENCE,
         note: 'Notifications stay below the public promise until a complete Harmony delivery story is validated end to end.',
         docsUrl: 'https://github.com/react-native-oh-library',
         nativePackageNames: [],

package/build/types.d.ts

@@ -2,6 +2,7 @@ export type CompatibilityStatus = 'supported' | 'manual' | 'unknown';
 export type EligibilityStatus = 'eligible' | 'ineligible';
 export type SupportTier = 'verified' | 'preview' | 'experimental' | 'unsupported';
 export type DoctorTargetTier = Exclude<SupportTier, 'unsupported'>;
+export type CapabilityRuntimeMode = 'shim' | 'adapter' | 'verified';
 export type DependencySource = 'dependency' | 'devDependency' | 'peerDependency' | 'expo-plugin';
 export interface ExpoHarmonyPluginProps {
     bundleName?: string;
@@ -82,11 +83,19 @@ export interface SupportTierSummary {
     experimental: number;
     unsupported: number;
 }
+export interface CapabilityEvidence {
+    bundle: boolean;
+    debugBuild: boolean;
+    device: boolean;
+    release: boolean;
+}
 export interface CapabilityDefinition {
     id: string;
     packageName: string;
     status: CompatibilityStatus;
     supportTier: DoctorTargetTier;
+    runtimeMode: CapabilityRuntimeMode;
+    evidence: CapabilityEvidence;
     note: string;
     docsUrl?: string;
     nativePackageNames: string[];
@@ -99,6 +108,8 @@ export interface ProjectCapabilityReport {
     packageName: string;
     status: CompatibilityStatus;
     supportTier: DoctorTargetTier;
+    runtimeMode: CapabilityRuntimeMode;
+    evidence: CapabilityEvidence;
     note: string;
     docsUrl?: string;
     nativePackageNames: string[];
@@ -106,6 +117,13 @@ export interface ProjectCapabilityReport {
     sampleRoute: string;
     acceptanceChecklist: string[];
 }
+export interface ManagedCapabilityRecord {
+    id: string;
+    packageName: string;
+    supportTier: DoctorTargetTier;
+    runtimeMode: CapabilityRuntimeMode;
+    evidence: CapabilityEvidence;
+}
 export interface DoctorReport {
     generatedAt: string;
     projectRoot: string;
@@ -200,7 +218,7 @@ export interface ToolkitConfig {
     rnohCliVersion: string;
     bundleName: string;
     entryModuleName: string;
-    capabilities: string[];
+    capabilities: ManagedCapabilityRecord[];
     requestedHarmonyPermissions: string[];
     project: {
         name: string;

package/docs/cli-build.md

@@ -1,6 +1,6 @@
 # CLI 构建指南
 
-`v1.7.0` 延续 `verified + preview + experimental` 支持分层，并把 Batch B 设备能力推进到 preview 接入路径，其中 `expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
+`v1.7.2` 延续 `verified + preview + experimental` 支持分层，并把四项 preview capability 的现有 `🟠` 缺口收口到明确 `🟡` 子集，其中 `expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
 
 CLI 命令集合不变：
 

package/docs/npm-release.md

@@ -1,14 +1,29 @@
 # npm 发布说明
 
-`v1.5.0` 是 `expo-harmony-toolkit` 首个面向外部用户的 npm 正式公开版本。
+`expo-harmony-toolkit` 继续公开发布到 npm，但从现在开始明确区分两条发布轨：
+
+- `latest`
+  - 只发布完整验收的 `verified` 能力
+  - 面向正式公开承诺
+- `next`
+  - 承接 preview fast track
+  - 面向更快的集成反馈，不等于 verified 或 release-ready
+
+## 发布轨策略
 
 固定策略：
 
 - 包名：`expo-harmony-toolkit`
-- dist-tag：`latest`
-- provenance：GitHub 自动发布开启；本地手动发布不要求
+- 稳定轨 dist-tag：`latest`
+- 快速轨 dist-tag：`next`
+- provenance：GitHub 自动发布开启；本地手动发布不强制
 - 自动发布：hosted CI only
 
+推荐理解：
+
+- `latest` 解决“可以公开承诺什么”
+- `next` 解决“怎样更快收敛 preview 能力”
+
 ## 发布前检查
 
 统一执行：
@@ -20,47 +35,72 @@ npm pack --dry-run
 pnpm release:check
 ```
 
-`release:check` 固定覆盖：
+`release:check` 会根据发布轨选择 smoke sample 与 doctor gate：
+
+- `latest`
+  - smoke sample：`examples/official-ui-stack-sample`
+  - doctor gate：`expo-harmony doctor --strict`
+- `next`
+  - smoke sample：`examples/official-native-capabilities-sample`
+  - doctor gate：`expo-harmony doctor --target-tier preview`
+
+固定覆盖：
 
 - `pnpm build`
 - `pnpm test`
 - `npm pack --dry-run`
 - tarball 文件清单检查，不允许包含 `examples/`、`fixtures/`、`tests/`
 - tarball 安装 smoke：
-  - `expo-harmony doctor --strict`
-  - `expo-harmony init --force`
-  - `expo-harmony bundle`
+  - `doctor`
+  - `init --force`
+  - `bundle`
+- `next` 轨额外要求 preview sample 作为 smoke 根目录
 
 说明：
 
-- hosted CI 默认不阻塞 `build-hap --mode debug`
-- `build-hap` 继续作为本地或有 DevEco 工具链环境时的附加验证
+- hosted CI 默认仍可通过 `EXPO_HARMONY_RELEASE_SKIP_HAP=1` 跳过真实 DevEco HAP 构建
+- debug / release HAP gate 继续由 capability acceptance、带工具链环境的 CI 或本地验收补齐
 
 ## 手动发布
 
-本地执行：
+发布 `latest`：
 
 ```bash
 pnpm release:check
 npm publish --tag latest --access public
 ```
 
+发布 `next`：
+
+```bash
+EXPO_HARMONY_RELEASE_CHANNEL=next pnpm release:check
+npm publish --tag next --access public
+```
+
 前提：
 
 - 已登录 npm
-- 包名 `expo-harmony-toolkit` 仍可用
+- 当前包版本与预期发布轨一致
+- `next` 版本建议使用 prerelease version，例如 `1.8.0-next.1`
 
 ## GitHub 自动发布
 
 默认触发：
 
-- push version tag，例如 `v1.5.2`
+- push version tag，例如 `v1.8.0`
+- push prerelease tag，例如 `v1.8.0-next.1`
 
 工作流行为：
 
 - 安装依赖
-- 执行 `pnpm release:check`
-- 使用 npm Trusted Publisher 发布到 npm
+- 判断发布轨
+- 执行对应轨道的 `release:check`
+- 使用 npm Trusted Publisher 发布到对应 dist-tag
+
+约定：
+
+- 普通版本 tag 发布到 `latest`
+- 包含 `-next.`、`-beta.` 或 `-alpha.` 的 tag 发布到 `next`
 
 要求：
 
@@ -69,27 +109,34 @@ npm publish --tag latest --access public
 - workflow 具备 `id-token: write`
 - 使用 GitHub-hosted runner
 - GitHub 自动发布命令包含 `--provenance`
-- 本地手动发布只要求 `latest` dist-tag，不强制 provenance
-
-`workflow_dispatch` 仅用于 rehearsal / dry-run，不会直接 publish。
 
 ## tarball smoke 的安装注意事项
 
-当前官方 UI-stack sample 依赖两项 Git adapter：
+当前公开矩阵内的两套 Git adapter 依赖仍是：
 
 - `@react-native-oh-tpl/react-native-reanimated`
 - `@react-native-oh-tpl/react-native-svg`
 
-为了避免 Git adapter prepare 阶段拉取私有上游资源，tarball smoke 固定使用：
+为了避免 adapter prepare 阶段拉取私有上游资源，tarball smoke 固定使用：
 
 ```bash
 pnpm install --ignore-scripts
 pnpm add --ignore-scripts <tarball>
 ```
 
-这不会影响 toolkit 的公开发布验证，因为 tarball smoke 只要求 `doctor`、`init`、`bundle`。
+这不会影响公开发布验证，因为 smoke 只要求：
+
+- `doctor`
+- `init`
+- `bundle`
 
-补充：
+## 发布边界
 
-- `react-native-gesture-handler` 目前不在公开 release gate 里
-- 如需继续尝试它，请按矩阵外的手动探索项处理，而不是把它当作 `doctor --strict` 通过条件
+- `latest` 不承接 preview capability 的公开承诺
+- `next` 可以承接 preview fast track，但不得替代 capability promotion gate
+- 任何声称 verified 的能力都必须具备：
+  - `bundle`
+  - debug `build-hap`
+  - device acceptance
+  - release acceptance
+  - 文档与 acceptance 记录

package/docs/official-app-shell-sample.md

@@ -2,13 +2,13 @@
 
 这份指南适用于仓库内的 `examples/official-app-shell-sample`。
 
-从 `v1.5.0` 开始，它不再是对外主 sample，而是 App Shell 回归基线，主要用于确认：
+从 `v1.7.x` 开始，它的定位不再只是“回归基线”，而是最小可理解的 App Shell 开发者 sample。它专门展示：
 
 - `expo-router`
 - `expo-linking`
 - `expo-constants`
-- router sidecar 入口和 bundle 行为
-- UI-stack 收口没有破坏原有 App Shell 路径
+- 当前 pathname / observed URL / generated URL
+- router push、`Link` 组件、generated deep link 三条最核心入口
 
 ## 使用方式
 
@@ -19,21 +19,42 @@ pnpm run harmony:doctor:strict
 pnpm run harmony:init
 pnpm run harmony:sync-template
 pnpm run harmony:bundle
+pnpm run harmony:build:debug
 ```
 
-如果本机 DevEco 环境已就绪，也可以继续：
+## 运行时成功标准
+
+打开 App 后，至少确认：
+
+- 首页能看到 `Constants.expoConfig?.name`
+- 首页能看到当前 pathname、observed URL、generated details URL
+- 点击 `Push /details with router` 后能进入 `/details`
+- 点击 `Open details with Link component` 后能进入 `/details`
+- 点击 `Open generated deep link` 后，也能把同一个 App 壳子解析到 `/details`
+- 在 `/details` 点击返回后能回首页
+
+## Release 路径
+
+如果要继续验证 release 构建，先准备本地签名覆盖文件：
 
 ```bash
-pnpm run harmony:build:debug
+mkdir -p .expo-harmony
+$EDITOR .expo-harmony/signing.local.json
+pnpm run harmony:env
+pnpm run harmony:build:release
 ```
 
-## 回归关注点
+说明：
+
+- `.expo-harmony/signing.local.json` 是本地 signing 入口
+- signing 缺失时，`harmony:env` 和 `harmony:build:release` 会明确提示，不会静默跳过
+
+## 边界
 
-这个 sample 不引入 UI adapters。它的价值在于：
+这个 sample 只负责 App Shell 入门路径，不负责：
 
-- `doctor` 仍然判定在 `expo55-rnoh082-ui-stack` 公开矩阵内
-- `index.harmony.js` 与 router sidecar 入口仍然正确
-- `autolinking.cmake` 在无 UI adapters 时保持空 stub，不被 UI-stack 逻辑污染
-- `bundle.harmony.js` 仍能正确产出 router 页面
+- `react-native-svg`
+- `react-native-reanimated`
+- preview native capability
 
-如果需要对外展示 UI-stack 能力，请改用 [官方 UI Stack sample 指南](./official-ui-stack-sample.md)。
+如果你要看 verified UI-stack 主线，请改用 [官方 UI Stack sample 指南](./official-ui-stack-sample.md)。

package/docs/official-minimal-sample.md

@@ -2,11 +2,11 @@
 
 这份指南适用于仓库内的 `examples/official-minimal-sample`。
 
-它在 `v1.5.0` 中继续作为最小 smoke baseline，用于回归：
+它仍然是仓库里最小的官方 sample，但从 `v1.7.x` 开始不再把自己描述成“空白 smoke baseline”。它的定位是：
 
-- 最短 `doctor -> init -> bundle` 链路
-- sidecar 模板稳定性
-- 非 router、非 UI adapter 的最小输入
+- 让新开发者一眼看懂最短 `doctor -> init -> bundle -> build-hap` 链路
+- 验证受管 Harmony sidecar 的最小稳定产物
+- 明确说明它不覆盖 router、UI-stack、native capability
 
 ## 使用方式
 
@@ -17,16 +17,49 @@ pnpm run harmony:doctor:strict
 pnpm run harmony:init
 pnpm run harmony:sync-template
 pnpm run harmony:bundle
+pnpm run harmony:build:debug
 ```
 
-## 预期
+## 运行时成功标准
 
-- `doctor --strict` 通过
-- `harmony:init` 与 `harmony:sync-template` 冪等
-- `bundle.harmony.js` 产出成功
-- 生成的 `RNOHPackagesFactory.*` 与 `autolinking.cmake` 保持空 baseline，不被 UI-stack 逻辑污染
+打开 App 后，至少确认：
 
-如果你要验证 router 或 UI 能力，请改用：
+- 页面能正常启动
+- 页面清楚显示这条 sample 验证的是最短构建链路
+- 页面清楚区分“验证什么”和“故意不包含什么”
+- `bundle.harmony.js` 成功产出
+- 生成的 Harmony sidecar 保持最小且稳定，不被 router 或 UI-stack 逻辑污染
+
+## Release 路径
+
+如果要继续验证 release 构建，先准备本地签名覆盖文件：
+
+```bash
+mkdir -p .expo-harmony
+$EDITOR .expo-harmony/signing.local.json
+pnpm run harmony:env
+pnpm run harmony:build:release
+```
+
+说明：
+
+- `.expo-harmony/signing.local.json` 是本地 signing 入口
+- toolkit 会把本地 signing 合并进 `harmony/build-profile.json5`
+- 如果 signing 没配置，`harmony:env` 会明确报缺失；这属于预期阻断
+
+## 不覆盖的内容
+
+这个 sample 故意不包含：
+
+- `expo-router`
+- `expo-linking`
+- `expo-constants`
+- `react-native-svg`
+- `react-native-reanimated`
+- 任意 preview native capability
+
+如果你要验证这些内容，请改用：
 
 - [官方 App Shell sample 指南](./official-app-shell-sample.md)
 - [官方 UI Stack sample 指南](./official-ui-stack-sample.md)
+- [官方 Native Capabilities sample 指南](./official-native-capabilities-sample.md)

package/docs/official-native-capabilities-sample.md

@@ -2,12 +2,11 @@
 
 路径：`examples/official-native-capabilities-sample`
 
-这个 sample 从 `v1.7` 开始承担 Batch A+B preview 能力的统一官方入口。它不是新的 `verified` 主 sample，而是专门用来验证：
+这个 sample 是 `v1.7.2` 的官方 preview native-capability walkthrough。它的目标不是把 preview 能力包装成 `verified`，而是把四项能力当前真实可承诺的 `🟡` 子集集中演示出来，并把 preview 边界收敛到真机 / release 证据，而不是接口缺口。
 
-- `doctor --target-tier preview`
-- managed Harmony permission 生成
-- preview capability Metro alias / shim
-- `bundle` 与 `build-hap --mode debug` 阶段对原生能力 import path 的稳定接管
+标记说明：
+
+- `🟡` 当前可用子集：这部分已经有可信实现，样例和模拟器路径可用；下一步主要缺真机 / release 证据
 
 ## 当前覆盖
 
@@ -23,11 +22,62 @@
 - `/location`
 - `/camera`
 
+## 每条 route 的真实范围
+
+### `/file-system`
+
+`🟡 当前可用子集`：
+
+- sandbox 目录创建
+- UTF-8 写入 / 读回
+- base64 roundtrip
+- append / partial read
+- `getInfoAsync({ md5: true })`
+- `downloadAsync`
+- 清理生成产物
+
+### `/image-picker`
+
+`🟡 当前可用子集`：
+
+- media permission
+- camera permission
+- 单选图库选择
+- 多选图库选择
+- mixed image+video library selection
+- system photo capture
+- system video capture
+- pending result 恢复
+- image / video asset metadata 展示
+
+### `/location`
+
+`🟡 当前可用子集`：
+
+- foreground permission
+- background permission
+- `getCurrentPositionAsync`
+- `watchPositionAsync`
+- `getHeadingAsync`
+- `watchHeadingAsync`
+- `geocodeAsync`
+- `reverseGeocodeAsync`
+
 说明：
 
-- 这些 route 的目标是承接 preview bridge，而不是宣称运行时已经完全可用
-- 当前 sample 强调“可分析、可生成 sidecar、可 bundle、可 debug build、可观察 permission/shim 产物”
-- 只有当设备侧 runtime、debug HAP、人工验收都完成后，对应能力才可以从 `preview` 晋升到 `verified`
+- 背景权限按 Harmony 的独立后台权限契约暴露，不伪装成 Expo 的完全同构平台行为
+- heading 使用 Harmony 传感器方向语义，属于最接近 Expo 的等价语义，不复用 GPS `direction`
+
+### `/camera`
+
+`🟡 当前可用子集`：
+
+- embedded `CameraView` preview
+- `pausePreview` / `resumePreview`
+- still photo capture
+- video recording start / stop / toggle
+- microphone permission snapshot
+- denied / canceled / successful result 展示
 
 ## 推荐命令
 
@@ -48,25 +98,31 @@ pnpm run harmony:doctor:strict
 预期结果：
 
 - `doctor --target-tier preview`：通过
-- `doctor --strict`：失败，因为 preview 能力仍然不在 verified allowlist
-- `sync-template`：产出 Batch A+B 对应 preview shims 与 Harmony permissions
+- `doctor --strict`：失败，因为 preview capability 仍然不在 verified allowlist
+- `sync-template`：产出 preview shims、Harmony permissions、toolkit telemetry
 - `bundle`：成功产出 `bundle.harmony.js`
 - `build-hap --mode debug`：可进入 debug HAP 构建路径
 
-## 关键受管产物
+## Release 路径
+
+如果要继续验证 release 构建，先准备本地签名覆盖文件：
 
-- `harmony/entry/src/main/module.json5`
-- `.expo-harmony/shims/expo-file-system/index.js`
-- `.expo-harmony/shims/expo-image-picker/index.js`
-- `.expo-harmony/shims/expo-location/index.js`
-- `.expo-harmony/shims/expo-camera/index.js`
-- `metro.harmony.config.js`
+```bash
+mkdir -p .expo-harmony
+$EDITOR .expo-harmony/signing.local.json
+pnpm run harmony:env
+pnpm run harmony:build:release
+```
+
+说明：
 
-## 晋升条件
+- `.expo-harmony/signing.local.json` 是本地 signing 入口
+- toolkit 会把本地 signing 合并进 `harmony/build-profile.json5`
+- 即使 release 构建可走通，在没有真机前，这四项能力也仍保持 `preview`
 
-当以下条件都具备时，相关能力才可以从这个 sample 迁移到 verified 主叙事：
+## 当前结论
 
-- 真机或模拟器运行时功能通过
-- debug `build-hap` 成功
-- 权限拒绝、取消流程、异常路径完成记录
-- support matrix、README、roadmap、acceptance 记录同 PR 更新
+- 这个 sample 属于 `preview` 主线，不等于已经进入 `verified`
+- `doctor-report.json` 与 `toolkit-config.json` 中的 `runtimeMode` / `evidence.*` 会如实反映这些能力距离 verified 还缺哪些证据
+- 当前重点是“模拟器下真正可用、核心流清楚、文档一致”
+- 等未来补齐真机 gate 后，才讨论 capability promotion