expo-harmony-toolkit 1.6.0 → 1.7.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.6.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.7.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-059669?style=flat-square">
   </p>
@@ -24,7 +24,7 @@
 </div>
 
 > [!IMPORTANT]
-> Starting with `v1.6`, the toolkit exposes `verified + preview + experimental` support tiers. `expo55-rnoh082-ui-stack` remains the only `verified` public matrix, while `expo-file-system` and `expo-image-picker` move into `preview`. This is still not a claim that arbitrary Expo apps can be published to HarmonyOS unchanged.
+> `v1.7` keeps the `verified + preview + experimental` model and moves `expo-location` and `expo-camera` into `preview`. The public path is still "Core Expo Full Coverage first, long-tail third-party native modules second"; this is still not a claim that arbitrary Expo apps can be published to HarmonyOS unchanged.
 
 > [!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.
@@ -47,13 +47,13 @@
 
 | Item | Status |
 | --- | --- |
-| Current version | `v1.6.0` |
+| Current version | `v1.7.0` |
 | Support model | `verified + preview + experimental` |
 | Public `verified` matrix | `expo55-rnoh082-ui-stack` |
 | Supported input | Managed/CNG Expo projects |
 | `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` |
-| `experimental` capabilities | `expo-location`, `expo-camera`, `expo-notifications`, `react-native-gesture-handler` |
+| `preview` native capabilities | `expo-file-system`, `expo-image-picker`, `expo-location`, `expo-camera` |
+| `experimental` capabilities | `expo-notifications`, `react-native-gesture-handler` |
 | Build path | `doctor -> init -> bundle -> build-hap` |
 | Primary sample | `examples/official-ui-stack-sample` |
 | Preview sample | `examples/official-native-capabilities-sample` |
@@ -63,10 +63,9 @@
 <summary><strong>Still outside the verified public promise</strong></summary>
 
 - bare Expo
-- `expo-file-system` and `expo-image-picker` remain `preview`
-- `expo-location`
-- `expo-camera`
+- `expo-file-system`, `expo-image-picker`, `expo-location`, and `expo-camera` remain `preview`
 - `expo-notifications`
+- `react-native-gesture-handler`
 - multiple public matrices
 
 </details>
@@ -169,11 +168,11 @@ Common decision points:
 
 ## Support Matrix
 
-`v1.6` moves to tiered support:
+`v1.7` keeps tiered support:
 
 - `verified`: the only public matrix remains `expo55-rnoh082-ui-stack`
-- `preview`: `expo-file-system`, `expo-image-picker`
-- `experimental`: `expo-location`, `expo-camera`, `expo-notifications`, `react-native-gesture-handler`
+- `preview`: `expo-file-system`, `expo-image-picker`, `expo-location`, `expo-camera`
+- `experimental`: `expo-notifications`, `react-native-gesture-handler`
 
 `doctor --strict` still means `verified` only. `doctor --target-tier preview` allows the same runtime matrix plus preview-tier capabilities, but that does not promote them into the formal public promise.
 
@@ -184,7 +183,7 @@ See [docs/support-matrix.md](./docs/support-matrix.md) for the full allowlist, p
 - `examples/official-ui-stack-sample`
   The primary public sample for `v1.5.0`, covering router, linking, constants, SVG, reanimated, and Harmony sidecar build flow.
 - `examples/official-native-capabilities-sample`
-  The new preview sample for `v1.6`, covering the `expo-file-system` and `expo-image-picker` bridge, permission generation, and bundle-time alias flow.
+  The `v1.7` Batch A+B preview sample, covering `expo-file-system`, `expo-image-picker`, `expo-location`, and `expo-camera` bridge, permission, bundle, and debug-build validation.
 - `examples/official-app-shell-sample`
   The `v1.1` App Shell regression baseline that protects router behavior while UI-stack support is finalized.
 - `examples/official-minimal-sample`
@@ -247,7 +246,7 @@ Manual Harmony acceptance still requires:
 - pressing the home-screen motion rail triggers visible animation
 - routing still works after the animation completes
 - `Build Debug Hap(s)` succeeds
-- `official-native-capabilities-sample` at least proves preview route bundling and generated Harmony permissions
+- `official-native-capabilities-sample` at least proves Batch A+B preview route bundling, generated Harmony permissions, and the debug build path
 
 See [docs/npm-release.md](./docs/npm-release.md) and [docs/signing-and-release.md](./docs/signing-and-release.md).
 
@@ -261,6 +260,7 @@ See [docs/npm-release.md](./docs/npm-release.md) and [docs/signing-and-release.m
 - [Official Minimal Sample Guide](./docs/official-minimal-sample.md)
 - [npm Release Notes](./docs/npm-release.md)
 - [Signing and Release Notes](./docs/signing-and-release.md)
+- [v1.7.0 Acceptance Log (In Progress)](./docs/v1.7.0-acceptance.md)
 - [Roadmap](./docs/roadmap.md)
 
 ## License

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.6.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.7.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-059669?style=flat-square">
   </p>
@@ -24,7 +24,7 @@
 </div>
 
 > [!IMPORTANT]
-> `v1.6` 开始，toolkit 采用 `verified + preview + experimental` 三层支持模型。`expo55-rnoh082-ui-stack` 仍是唯一 `verified` 公开矩阵；`expo-file-system` 与 `expo-image-picker` 进入 `preview`，但这仍然不是“任意 Expo 项目都能原样发布到 HarmonyOS”的声明。
+> `v1.7` 延续 `verified + preview + experimental` 三层支持模型，并把 `expo-location`、`expo-camera` 推进到 `preview`。当前对外路线仍然是先做到 `Core Expo Full Coverage`，再去覆盖长尾第三方 native module；这依然不是“任意 Expo 项目都能原样发布到 HarmonyOS”的声明。
 
 > [!TIP]
 > 由于当前公开矩阵内的两套 `@react-native-oh-tpl/*` adapter 依赖以 Git URL + exact commit 形式接入，仓库开发和官方 UI-stack sample 推荐使用 `pnpm install --ignore-scripts`，避免 Git adapter 在 prepare 阶段拉取私有资源而中断安装。
@@ -47,13 +47,13 @@
 
 | 项目 | 说明 |
 | --- | --- |
-| 当前版本 | `v1.6.0` |
+| 当前版本 | `v1.7.0` |
 | 支持模型 | `verified + preview + experimental` |
 | 唯一 `verified` 公开矩阵 | `expo55-rnoh082-ui-stack` |
 | 输入范围 | Managed/CNG Expo 项目 |
 | `verified` JS/UI 能力 | `expo-router`、`expo-linking`、`expo-constants`、`react-native-reanimated`、`react-native-svg` |
-| `preview` 原生能力 | `expo-file-system`、`expo-image-picker` |
-| `experimental` 能力 | `expo-location`、`expo-camera`、`expo-notifications`、`react-native-gesture-handler` |
+| `preview` 原生能力 | `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera` |
+| `experimental` 能力 | `expo-notifications`、`react-native-gesture-handler` |
 | 构建链 | `doctor -> init -> bundle -> build-hap` |
 | 主 sample | `examples/official-ui-stack-sample` |
 | preview sample | `examples/official-native-capabilities-sample` |
@@ -63,10 +63,9 @@
 <summary><strong>当前仍不在 verified 正式承诺范围</strong></summary>
 
 - bare Expo
-- `expo-file-system`、`expo-image-picker` 仍只属于 `preview`
-- `expo-location`
-- `expo-camera`
+- `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera` 仍只属于 `preview`
 - `expo-notifications`
+- `react-native-gesture-handler`
 - 多矩阵并行支持
 
 </details>
@@ -169,11 +168,11 @@ pnpm exec expo-harmony build-hap --mode release
 
 ## 支持矩阵
 
-`v1.6` 开始改成支持分层：
+`v1.7` 继续采用支持分层：
 
 - `verified`：唯一公开矩阵仍是 `expo55-rnoh082-ui-stack`
-- `preview`：`expo-file-system`、`expo-image-picker`
-- `experimental`：`expo-location`、`expo-camera`、`expo-notifications`、`react-native-gesture-handler`
+- `preview`：`expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera`
+- `experimental`：`expo-notifications`、`react-native-gesture-handler`
 
 `doctor --strict` 继续只代表 `verified`。`doctor --target-tier preview` 会在同一 runtime matrix 下额外放行 preview 能力，但这不等于它们已经进入正式承诺。
 
@@ -184,7 +183,7 @@ pnpm exec expo-harmony build-hap --mode release
 - `examples/official-ui-stack-sample`
   当前唯一对外主 sample，同时覆盖 router、linking、constants、SVG、reanimated 和 Harmony sidecar 构建链。
 - `examples/official-native-capabilities-sample`
-  v1.6 新增的 preview sample，用来承接 `expo-file-system` 与 `expo-image-picker` 的 bridge、permission 与 bundle 骨架验收。
+  `v1.7` 的 Batch A+B preview sample，用来承接 `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera` 的 bridge、permission、bundle 与 debug build 验收。
 - `examples/official-app-shell-sample`
   `v1.1` App Shell 回归基线，用来防止 UI-stack 收口引入 router 退化。
 - `examples/official-minimal-sample`
@@ -247,7 +246,7 @@ pnpm exec expo-harmony build-hap --mode release
 - 点击首页 motion rail 后能触发可见动画
 - 动画完成后路由跳转仍正常
 - `Build Debug Hap(s)` 成功
-- `official-native-capabilities-sample` 至少完成 preview route 的 bundle 与 permission 产物检查
+- `official-native-capabilities-sample` 至少完成 Batch A+B preview route 的 bundle、permission 与 debug build 检查
 
 详见 [docs/npm-release.md](./docs/npm-release.md) 与 [docs/signing-and-release.md](./docs/signing-and-release.md)。
 
@@ -261,6 +260,7 @@ pnpm exec expo-harmony build-hap --mode release
 - [官方最小 sample 指南](./docs/official-minimal-sample.md)
 - [npm 发布说明](./docs/npm-release.md)
 - [签名与 Release 说明](./docs/signing-and-release.md)
+- [v1.7.0 验收记录（进行中）](./docs/v1.7.0-acceptance.md)
 - [路线图](./docs/roadmap.md)
 
 ## License

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.6.0";
+export declare const TOOLKIT_VERSION = "1.7.0";
 export declare const TEMPLATE_VERSION = "rnoh-0.82.18";
 export declare const RNOH_VERSION = "0.82.18";
 export declare const RNOH_CLI_VERSION = "0.82.18";

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.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.6.0';
+exports.TOOLKIT_VERSION = '1.7.0';
 exports.TEMPLATE_VERSION = 'rnoh-0.82.18';
 exports.RNOH_VERSION = '0.82.18';
 exports.RNOH_CLI_VERSION = '0.82.18';

package/build/core/template.js

@@ -717,6 +717,10 @@ function renderCapabilityModuleShim(capability) {
             return renderExpoFileSystemPreviewShim(capability);
         case 'expo-image-picker':
             return renderExpoImagePickerPreviewShim(capability);
+        case 'expo-location':
+            return renderExpoLocationPreviewShim(capability);
+        case 'expo-camera':
+            return renderExpoCameraPreviewShim(capability);
         default:
             return renderUnsupportedCapabilityShim(capability);
     }
@@ -1074,6 +1078,177 @@ module.exports = {
 };
 `;
 }
+function renderExpoLocationPreviewShim(capability) {
+    return `'use strict';
+
+const { CodedError } = require('expo-modules-core');
+
+const PREVIEW_MESSAGE =
+  '${capability.packageName} is routed through the Expo Harmony ${capability.supportTier} bridge. Bundling is supported, but foreground permission, current-position, and watch flows still need device-side validation.';
+const DEFAULT_PERMISSION_RESPONSE = {
+  status: 'undetermined',
+  granted: false,
+  canAskAgain: true,
+  expires: 'never',
+};
+
+function createPreviewError(operationName) {
+  return new CodedError(
+    'ERR_EXPO_HARMONY_PREVIEW',
+    PREVIEW_MESSAGE + ' Attempted operation: ' + operationName + '.',
+  );
+}
+
+async function unavailable(operationName) {
+  throw createPreviewError(operationName);
+}
+
+function getPermissionResponse() {
+  return { ...DEFAULT_PERMISSION_RESPONSE };
+}
+
+module.exports = {
+  Accuracy: {
+    Lowest: 1,
+    Low: 2,
+    Balanced: 3,
+    High: 4,
+    Highest: 5,
+    BestForNavigation: 6,
+  },
+  PermissionStatus: {
+    DENIED: 'denied',
+    GRANTED: 'granted',
+    UNDETERMINED: 'undetermined',
+  },
+  requestForegroundPermissionsAsync() {
+    return unavailable('requestForegroundPermissionsAsync');
+  },
+  getForegroundPermissionsAsync() {
+    return Promise.resolve(getPermissionResponse());
+  },
+  requestBackgroundPermissionsAsync() {
+    return unavailable('requestBackgroundPermissionsAsync');
+  },
+  getBackgroundPermissionsAsync() {
+    return Promise.resolve(getPermissionResponse());
+  },
+  hasServicesEnabledAsync() {
+    return Promise.resolve(false);
+  },
+  getCurrentPositionAsync(options) {
+    return unavailable('getCurrentPositionAsync(' + JSON.stringify(options ?? {}) + ')');
+  },
+  getLastKnownPositionAsync(options) {
+    return unavailable('getLastKnownPositionAsync(' + JSON.stringify(options ?? {}) + ')');
+  },
+  watchPositionAsync(options) {
+    return unavailable('watchPositionAsync(' + JSON.stringify(options ?? {}) + ')');
+  },
+};
+`;
+}
+function renderExpoCameraPreviewShim(capability) {
+    return `'use strict';
+
+const React = require('react');
+const { Text, View } = require('react-native');
+const { CodedError } = require('expo-modules-core');
+
+const PREVIEW_MESSAGE =
+  '${capability.packageName} is routed through the Expo Harmony ${capability.supportTier} bridge. Bundling is supported, and a managed preview surface can render, but device-side camera permission and capture flows still need validation.';
+const DEFAULT_PERMISSION_RESPONSE = {
+  status: 'undetermined',
+  granted: false,
+  canAskAgain: true,
+  expires: 'never',
+};
+
+function createPreviewError(operationName) {
+  return new CodedError(
+    'ERR_EXPO_HARMONY_PREVIEW',
+    PREVIEW_MESSAGE + ' Attempted operation: ' + operationName + '.',
+  );
+}
+
+async function unavailable(operationName) {
+  throw createPreviewError(operationName);
+}
+
+function getPermissionResponse() {
+  return { ...DEFAULT_PERMISSION_RESPONSE };
+}
+
+const CameraView = React.forwardRef(function ExpoHarmonyCameraPreview(props, ref) {
+  React.useImperativeHandle(ref, () => ({
+    takePictureAsync(options) {
+      return unavailable('CameraView.takePictureAsync(' + JSON.stringify(options ?? {}) + ')');
+    },
+  }));
+
+  return React.createElement(
+    View,
+    {
+      style: [
+        {
+          minHeight: 220,
+          alignItems: 'center',
+          justifyContent: 'center',
+          borderRadius: 20,
+          borderWidth: 1,
+          borderStyle: 'dashed',
+          borderColor: '#14b8a6',
+          backgroundColor: '#ccfbf1',
+          padding: 20,
+        },
+        props.style,
+      ],
+      accessibilityLabel: 'Expo Harmony preview camera surface',
+    },
+    React.createElement(
+      Text,
+      {
+        style: {
+          color: '#0f766e',
+          fontSize: 14,
+          fontWeight: '600',
+          textAlign: 'center',
+        },
+      },
+      'Expo Harmony preview camera surface',
+    ),
+  );
+});
+
+CameraView.displayName = 'ExpoHarmonyCameraPreview';
+
+module.exports = {
+  CameraType: {
+    front: 'front',
+    back: 'back',
+  },
+  FlashMode: {
+    off: 'off',
+    on: 'on',
+    auto: 'auto',
+    torch: 'torch',
+  },
+  CameraView,
+  requestCameraPermissionsAsync() {
+    return unavailable('requestCameraPermissionsAsync');
+  },
+  getCameraPermissionsAsync() {
+    return Promise.resolve(getPermissionResponse());
+  },
+  requestMicrophonePermissionsAsync() {
+    return unavailable('requestMicrophonePermissionsAsync');
+  },
+  getMicrophonePermissionsAsync() {
+    return Promise.resolve(getPermissionResponse());
+  },
+};
+`;
+}
 function renderExpoModulesCoreHarmonyShim(expoConfig, identifiers) {
     const embeddedExpoConfig = buildExpoConfigForShim(expoConfig, identifiers);
     const serializedExpoConfig = JSON.stringify(embeddedExpoConfig, null, 2);

package/build/data/capabilities.js

@@ -43,8 +43,8 @@ exports.CAPABILITY_DEFINITIONS = [
         id: 'expo-location',
         packageName: 'expo-location',
         status: 'manual',
-        supportTier: 'experimental',
-        note: 'Location hooks are planned on top of the shared permission bridge, but no verified runtime path is shipped yet.',
+        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.',
         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'],
@@ -59,8 +59,8 @@ exports.CAPABILITY_DEFINITIONS = [
         id: 'expo-camera',
         packageName: 'expo-camera',
         status: 'manual',
-        supportTier: 'experimental',
-        note: 'Camera preview and capture remain experimental until a stable Harmony-native implementation is wired into the managed bridge.',
+        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.',
         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'],

package/docs/cli-build.md

@@ -1,6 +1,6 @@
 # CLI 构建指南
 
-`v1.6.0` 开始，toolkit 的公开叙事升级为 `verified + preview + experimental` 支持分层，其中 `expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
+`v1.7.0` 延续 `verified + preview + experimental` 支持分层，并把 Batch B 设备能力推进到 preview 接入路径，其中 `expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
 
 CLI 命令集合不变：
 
@@ -33,6 +33,13 @@ expo-harmony build-hap --mode debug
 - `bundle` 负责 `bundle.harmony.js`
 - `build-hap` 负责串起 bundle、`ohpm`、`hvigor`
 
+当前 preview capability onboarding 范围：
+
+- `expo-file-system`
+- `expo-image-picker`
+- `expo-location`
+- `expo-camera`
+
 ## UI stack 依赖安装注意事项
 
 当前公开矩阵里的两项 Harmony adapter 依赖都固定为 Git URL + exact commit：

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

@@ -2,27 +2,31 @@
 
 路径：`examples/official-native-capabilities-sample`
 
-这个 sample 从 `v1.6` 开始承担 preview 能力的官方入口。它不是新的 `verified` 主 sample，而是专门用来验证：
+这个 sample 从 `v1.7` 开始承担 Batch A+B preview 能力的统一官方入口。它不是新的 `verified` 主 sample，而是专门用来验证：
 
 - `doctor --target-tier preview`
 - managed Harmony permission 生成
 - preview capability Metro alias / shim
-- `bundle` 阶段对原生能力 import path 的稳定接管
+- `bundle` 与 `build-hap --mode debug` 阶段对原生能力 import path 的稳定接管
 
 ## 当前覆盖
 
 - `expo-file-system`
 - `expo-image-picker`
+- `expo-location`
+- `expo-camera`
 
 当前 route：
 
 - `/file-system`
 - `/image-picker`
+- `/location`
+- `/camera`
 
 说明：
 
 - 这些 route 的目标是承接 preview bridge，而不是宣称运行时已经完全可用
-- 当前 sample 仍然强调“可分析、可生成 sidecar、可 bundle、可观察 permission/shim 产物”
+- 当前 sample 强调“可分析、可生成 sidecar、可 bundle、可 debug build、可观察 permission/shim 产物”
 - 只有当设备侧 runtime、debug HAP、人工验收都完成后，对应能力才可以从 `preview` 晋升到 `verified`
 
 ## 推荐命令
@@ -32,6 +36,7 @@ cd examples/official-native-capabilities-sample
 pnpm run harmony:doctor:preview
 pnpm run harmony:sync-template
 pnpm run harmony:bundle
+pnpm run harmony:build:debug
 ```
 
 如果要确认它为什么不能进入 `verified`：
@@ -43,15 +48,18 @@ pnpm run harmony:doctor:strict
 预期结果：
 
 - `doctor --target-tier preview`：通过
-- `doctor --strict`：失败，因为 `expo-file-system` / `expo-image-picker` 仍然不在 verified allowlist
-- `sync-template`：产出 preview shims 与 Harmony permissions
+- `doctor --strict`：失败，因为 preview 能力仍然不在 verified allowlist
+- `sync-template`：产出 Batch A+B 对应 preview shims 与 Harmony permissions
 - `bundle`：成功产出 `bundle.harmony.js`
+- `build-hap --mode debug`：可进入 debug HAP 构建路径
 
 ## 关键受管产物
 
 - `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`
 
 ## 晋升条件
@@ -60,5 +68,5 @@ pnpm run harmony:doctor:strict
 
 - 真机或模拟器运行时功能通过
 - debug `build-hap` 成功
-- 拒权限、取消流程、异常路径完成记录
+- 权限拒绝、取消流程、异常路径完成记录
 - support matrix、README、roadmap、acceptance 记录同 PR 更新

package/docs/roadmap.md

@@ -30,50 +30,74 @@
 - `official-ui-stack-sample` 升级为主 sample
 - npm 首次公开发布准备：`release:check`、tarball smoke、release workflow
 
-## 当前主线
-
 ### v1.6 Support Tiers + Core Native Bridge
 
-目标：在不放弃单一 verified 矩阵的前提下，把能力扩张路径产品化。
-
-- 保留 `expo55-rnoh082-ui-stack` 作为唯一 `verified` 公开矩阵
 - 新增 `preview` 与 `experimental` 支持层级
 - `doctor --target-tier <verified|preview|experimental>`
 - `DoctorReport` 增加 `supportTier`、`supportSummary`、`capabilities`
-- 建立 Expo 原生能力桥接骨架，沿用受管 Metro alias 与 `expo-modules-core` shim
 - 首批 `preview` 能力：`expo-file-system`、`expo-image-picker`
 - 共享 Harmony permission 生成链
 - 新增 `official-native-capabilities-sample`
 
-### v1.7 Device APIs Batch B
+## 当前主线
 
-目标：在同一套桥接与权限模型上补齐第二批高频设备能力。
+### v1.7 Device APIs Batch B + Capability Onboarding
 
-- `expo-location`
-- `expo-camera`
-- 前台定位权限、当前定位、watchPosition
-- 相机权限、预览、拍照验收
-- 将已完成端到端验收的 `preview` 能力提升为 `verified`
+目标：把第二批高频设备能力推进到 `preview`，并把 capability 接入、验证、晋升流程产品化。
 
-### v1.8 Delivery Hardening
+- `expo-location`、`expo-camera` 进入 `preview`
+- 共用 managed capability bridge 行为：
+  可 `doctor`、可 `sync-template`、可 `bundle`、可 `build-hap --mode debug`
+- `expo-location` 至少覆盖：
+  前台权限、当前定位、`watchPosition`
+- `expo-camera` 至少覆盖：
+  相机权限、预览 surface、单次拍照入口
+- `official-native-capabilities-sample` 扩成 Batch A+B 统一验证入口
+- 为 Batch A+B 维护 fixture、sample、文档、验收记录同步更新
+- `expo-file-system`、`expo-image-picker` 只有在同版补齐完整证据时才晋升 `verified`
 
-目标：把“能 bundle / 能 debug build”推进到“交付路径可依赖”。
+### v1.8 Verification and Release Hardening
+
+目标：把 capability coverage 与 release reliability 合并成可重复执行的 gate。
 
 - 完整 deep link lifecycle 验收
 - 更强的 signing / profile / release lint
 - 快速 smoke 与 capability acceptance 双层验证
 - 具备 Harmony 工具链的 runner 上增加 debug HAP 真构建 gate
+- capability promotion gate 固化到 sample、fixture、build、device acceptance 流程
 - release gate 只放在有签名环境的专用流程
 
-### v2.0 Practical Full Coverage
+### v1.9 Core Expo Production Modules
+
+目标：优先补齐能解锁最多真实项目的 Expo 官方生产能力，而不是先追长尾第三方 native package。
+
+- 存储、安全、设备信息、资产、多媒体、剪贴板、触感等高频官方模块
+- 每个能力都必须沿用 v1.7 建立的 onboarding / acceptance 模型
+- 继续保持单一 `verified` runtime matrix，对外承诺不膨胀
 
-定义：不是 Expo / React Native 全生态的绝对 100% 覆盖，而是 Managed/CNG Expo 项目的“实用全兼容”。
+### v2.0 Core Expo Full Coverage
 
-- 大多数 Expo 生产项目可通过 `doctor -> init -> bundle -> build-hap`
-- 常见 UI stack、常见设备 API、常见交付链至少达到 `preview`
+定义：在单一 `verified` runtime matrix 下，把“核心 Expo 生产项目”推进到完整可用、可构建、可交付。
+
+- 官方 Expo 常用能力达到明确公开支持
+- 主流 UI stack、常见设备 API、常见交付链形成完整故事
 - 高频能力达到 `verified`
-- 明确 release readiness 路径
-- `expo-notifications` 在端到端服务故事未打通前继续停留在 `preview` 或更低层级
+- 具备明确 release readiness 路径
+- roadmap 对外叙事从“能跑 sample”升级为“核心 Expo 项目可稳定交付”
+
+### v2.x Long-tail Native Module Extension
+
+目标：在完成核心 Expo 全覆盖后，再去逼近“任何 Expo 项目都能打包成鸿蒙 APP”的长期目标。
+
+- 引入长尾第三方 native module 的 extension / onboarding 模型
+- 为第三方适配建立 capability registry、adapter、fixture、acceptance 规范
+- 不对未知或未验证 native package 提前给出正式可用承诺
+
+## 长期方向
+
+- 先做到 `Core Expo Full Coverage`
+- 再做到 `Long-tail Native Module Coverage`
+- “推进速度”与“完全可用”并行，而不是先扩承诺再补证据
 
 ## 路线约束
 

package/docs/support-matrix.md

@@ -1,6 +1,6 @@
-# v1.6 支持矩阵
+# v1.7 支持矩阵
 
-`v1.6` 开始，toolkit 不再只暴露“单一 allowlist”这一种语言，而是同时公开：
+`v1.7` 延续并扩张 tiered support model：
 
 - 一条 `verified` 正式承诺矩阵
 - 一组 `preview` 预览能力
@@ -30,7 +30,7 @@
 | 层级 | 含义 | `doctor --strict` | `doctor --target-tier <tier>` |
 | --- | --- | --- | --- |
 | `verified` | 已进入正式公开承诺，要求完整样例、构建、人工验收 | 允许 | 允许 |
-| `preview` | 已具备 managed bridge / bundle 路径，但运行时仍待完整验收 | 阻断 | `preview` / `experimental` 允许 |
+| `preview` | 已具备 managed bridge / bundle / debug build 路径，但运行时仍待完整验收 | 阻断 | `preview` / `experimental` 允许 |
 | `experimental` | 允许继续探索，但预期会有 bridge 漂移或设备侧缺口 | 阻断 | 仅 `experimental` 允许 |
 | `unsupported` | 不在 catalog 内，toolkit 无法给出可靠承诺 | 阻断 | 阻断 |
 
@@ -60,19 +60,19 @@
 | --- | --- | --- | --- | --- |
 | `expo-file-system` | `preview` | `react-native-fs` | 无新增必需权限 | `/file-system` |
 | `expo-image-picker` | `preview` | `react-native-image-picker` + `react-native-permissions` | `ohos.permission.CAMERA`、`ohos.permission.READ_IMAGEVIDEO` | `/image-picker` |
+| `expo-location` | `preview` | `@react-native-community/geolocation` + `react-native-permissions` | `ohos.permission.LOCATION`、`ohos.permission.APPROXIMATELY_LOCATION` | `/location` |
+| `expo-camera` | `preview` | `react-native-camera-kit` + `react-native-permissions` | `ohos.permission.CAMERA` | `/camera` |
 
 说明：
 
 - preview 能力会进入 `DoctorReport.capabilities`
-- toolkit 会生成对应 Metro alias shim，确保 preview 项目能稳定 bundle
+- toolkit 会生成对应 Metro alias shim，确保 preview 项目能稳定 `bundle` 与 `build-hap --mode debug`
 - preview 不等于 verified；没有运行时与设备侧证据前，不可对外宣称完全可用
 
 ## Experimental 能力
 
 | Expo 能力 / 依赖 | 当前层级 | 说明 |
 | --- | --- | --- |
-| `expo-location` | `experimental` | 规划走共享 permission bridge + geolocation 方案 |
-| `expo-camera` | `experimental` | 相机预览与拍照仍需稳定 Harmony 原生桥 |
 | `expo-notifications` | `experimental` | 服务链路与交付故事未打通 |
 | `react-native-gesture-handler` | `experimental` | 继续保留本地探索 shim，但不在公开 verified 矩阵内 |
 
@@ -144,7 +144,7 @@ toolkit 受管的核心产物仍包括：
 - `harmony/entry/src/main/module.json5`
 - `.expo-harmony/shims/*`
 
-新增约束：
+当前约束：
 
 - `entry/src/main/module.json5` 的 `requestPermissions` 由 toolkit 根据已启用能力自动补齐
 - preview / experimental 能力的 Metro import path 通过 `.expo-harmony/shims/<package>` 接管
@@ -163,7 +163,8 @@ toolkit 受管的核心产物仍包括：
 
 - `official-native-capabilities-sample` 在 `--target-tier preview` 下通过 `doctor`
 - `sync-template` 生成对应 preview shims 与 Harmony permissions
-- `bundle` 成功产出 `bundle.harmony.js`
+- Batch A+B route 成功产出 `bundle.harmony.js`
+- Batch A+B route 可进入 `build-hap --mode debug`
 
 ### Verified promotion gate
 

package/docs/v1.7.0-acceptance.md

@@ -0,0 +1,142 @@
+# v1.7.0 验收记录（已完成）
+
+日期：2026-03-31
+
+基线：
+
+- 仓库：`Expo-Harmony-Toolkit`
+- 版本：`1.7.0`
+- 发布目标：Batch B capability onboarding baseline
+
+## 当前结论
+
+`v1.7.0` 的 Batch B capability onboarding baseline 已完成验收。
+
+这一轮完成了代码与文档基线同步，把 `expo-location`、`expo-camera` 正式推进到 `preview` 接入路径，并把 roadmap 重写为：
+
+- `v1.7 Device APIs Batch B + Capability Onboarding`
+- `v1.8 Verification and Release Hardening`
+- `v1.9 Core Expo Production Modules`
+- `v2.0 Core Expo Full Coverage`
+- `v2.x Long-tail Native Module Extension`
+
+本轮验收结论是：
+
+- `expo-location`、`expo-camera` 的 preview-tier 接入链路已经完成基线验收
+- `expo-file-system`、`expo-image-picker` 的 Batch A preview route 已完成回归验收
+- `doctor --strict` 仍然会正确阻挡全部 preview capability；这条规则没有变化
+- `preview` 验收完成不代表这些能力已经晋升到 `verified`
+
+## 本轮实现范围
+
+- `expo-location`、`expo-camera` 调整为 `preview`
+- `doctor --target-tier preview` 放行 Batch A+B preview capability
+- managed Harmony permission / shim / Metro alias 生成扩展到 Batch A+B
+- `official-native-capabilities-sample` 扩充到 `/file-system`、`/image-picker`、`/location`、`/camera`
+- roadmap、support matrix、README、sample 指南同步更新
+
+## 自动化检查结果
+
+- `pnpm build`
+- `pnpm test`
+- `official-native-capabilities-sample` 在 preview tier 下完成 `doctor`
+- `sync-template` 生成 Batch A+B preview shims 与 Harmony permissions
+- `bundle` 成功产出 `bundle.harmony.js`
+- `build-hap --mode debug` 成功走完构建路径
+
+结果：
+
+- `pnpm build`：通过
+- `pnpm test`：通过，`11` suites / `58` tests
+- `doctor --target-tier preview`：通过，`Eligibility: eligible`
+- `doctor --strict`：按预期失败，`STRICT_EXIT=2`
+- `init --force`：通过，`written: 42`
+- `bundle`：通过，产物位于 `examples/official-native-capabilities-sample/harmony/entry/src/main/resources/rawfile/bundle.harmony.js`
+- `build-hap --mode debug`：通过，产物位于 `examples/official-native-capabilities-sample/harmony/entry/build/default/outputs/default/entry-default-unsigned.hap`
+
+额外说明：
+
+- `build-hap --mode debug` 期间仍会提示 `env.signing.missing`
+- 这是预期结果；debug HAP 可构建，但 release signing 仍未配置
+
+## 模拟器设备侧验收
+
+环境：
+
+- 模拟器 target：`127.0.0.1:5555`
+- 安装产物：`examples/official-native-capabilities-sample/harmony/entry/build/default/outputs/default/entry-default-unsigned.hap`
+- 安装结果：`install bundle successfully`
+- 启动结果：`start ability successfully`
+
+首页：
+
+- `Official Native Capabilities Sample` 成功渲染
+- `/file-system`、`/image-picker`、`/location`、`/camera` 四条 route 入口全部可见
+
+### File System
+
+- `/file-system` route 成功打开
+- `Attempt preview write` 可触发 preview bridge
+- 页面返回 `expo-file-system is routed through the Expo Harmony preview bridge...`
+- 路由切换与返回首页过程中未发生 crash
+
+### Image Picker
+
+- `/image-picker` route 成功打开
+- `Attempt preview pick` 可触发 preview bridge
+- 页面返回 `expo-image-picker is routed through the Expo Harmony preview bridge...`
+- 路由切换与返回首页过程中未发生 crash
+
+### Location
+
+- `/location` route 成功打开
+- `Attempt foreground permission` 可触发 preview bridge
+- `Attempt current position` 可触发 preview bridge
+- `Attempt watch start` 可触发 preview bridge
+- `Clear watch state` 可正常清理本地 watcher 状态
+- 页面可观察到 `requestForegroundPermissionsAsync`、`getCurrentPositionAsync(`、`watchPositionAsync(` 与 `Preview watch state cleared.`
+- 路由切换与返回首页过程中未发生 crash
+
+### Camera
+
+- `/camera` route 成功打开
+- `Expo Harmony preview camera surface` 成功渲染
+- `Attempt camera permission` 可触发 preview bridge
+- `Attempt preview capture` 可触发 preview bridge
+- 页面可观察到 `requestCameraPermissionsAsync` 与 `CameraView.takePictureAsync(`
+- 路由切换与返回首页过程中未发生 crash
+
+### 权限声明检查
+
+- `ohos.permission.LOCATION`
+- `ohos.permission.APPROXIMATELY_LOCATION`
+- `ohos.permission.CAMERA`
+- `ohos.permission.READ_IMAGEVIDEO`
+
+以上权限已在 `bm dump -n com.blackishgreen.expoharmonynativepreview` 中确认存在。
+
+## 晋升规则
+
+- `preview` 能力只有在 sample、fixture、bundle、debug HAP、设备侧验收、文档记录都完成后，才允许晋升到 `verified`
+- `expo-file-system`、`expo-image-picker` 不作为本轮发版阻塞；若证据不足则继续停留在 `preview`
+
+## 本轮已完成与未完成的边界
+
+已完成：
+
+- preview-tier capability onboarding 基线
+- managed shim / permission / Metro alias / route / debug build / emulator walkthrough
+- Batch A+B unified sample 的可安装、可启动、可点击、可观察 preview bridge 验收
+
+未完成：
+
+- `expo-location` 的真实权限 grant / deny 与真实坐标结果验收
+- `expo-camera` 的真实权限 grant / deny 与真实拍照文件结果验收
+- release signing / release HAP 验收
+- 任何 preview capability 的 `verified` 晋升
+
+因此，`v1.7.0` 的结论不是“location/camera 已经原生完全可用”，而是：
+
+- 它们已经完成 preview baseline 验收
+- 工具链已经可以稳定支撑分析、生成、bundle、build、install、launch、route、bridge
+- 它们仍然留在 `preview`，直到真实 Harmony-native runtime 证据补齐为止

package/package.json

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