expo-harmony-toolkit 1.7.2 → 1.8.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.7.2-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.8.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.7` keeps the `verified + preview + experimental` model and moves `expo-location` and `expo-camera` into `preview`. Starting with this documentation refresh, the public promise is tighter: `latest` only carries fully accepted `verified` capabilities, while `next` is reserved for preview fast-track work. The roadmap still targets `Managed/CNG Core Expo Coverage` first and long-tail extension coverage second.
+> `v1.8` keeps the `verified + preview + experimental` model and continues to keep `expo-location` and `expo-camera` in `preview`. The public promise remains tighter: `latest` only carries fully accepted `verified` capabilities, while `next` is reserved for preview fast-track work. The roadmap now defines `v2.0.0` itself as “reliable Harmony packaging for any Expo project”, so the intermediate versions will keep getting split smaller, but that still does not widen the current `verified` boundary 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.
@@ -45,9 +45,10 @@
 
 ## Current Status
 
+<!-- GENERATED:readme-current-status:start -->
 | Item | Status |
 | --- | --- |
-| Current version | `v1.7.2` |
+| Current version | `v1.8.0` |
 | Support model | `verified + preview + experimental` |
 | Public `verified` matrix | `expo55-rnoh082-ui-stack` |
 | Supported input | Managed/CNG Expo projects |
@@ -55,11 +56,12 @@
 | `preview` native capabilities | `expo-file-system`, `expo-image-picker`, `expo-location`, `expo-camera` |
 | `experimental` capabilities | `expo-notifications`, `react-native-gesture-handler` |
 | Release tracks | `latest` = fully accepted `verified` only; `next` = preview fast track |
-| Capability telemetry | `runtimeMode` + `evidence(bundle/debugBuild/device/release)` |
+| Capability telemetry | `runtimeMode` + `evidence(...)` + `evidenceSource(...)` + `coverageProfile` + `nextActions` |
 | Build path | `doctor -> init -> bundle -> build-hap` |
 | Primary sample | `examples/official-ui-stack-sample` |
 | Preview sample | `examples/official-native-capabilities-sample` |
 | Supporting onboarding samples | `examples/official-app-shell-sample`, `examples/official-minimal-sample` |
+<!-- GENERATED:readme-current-status:end -->
 
 <details>
 <summary><strong>Still outside the verified public promise</strong></summary>
@@ -170,28 +172,33 @@ Common decision points:
 
 ## Support Matrix
 
-`v1.7` keeps tiered support and now exposes capability promotion distance in public reports:
-
+<!-- GENERATED:readme-support-matrix:start -->
 - `verified`: the only public matrix remains `expo55-rnoh082-ui-stack`
 - `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.
 
-Starting in this refresh:
-
 - `doctor-report.json` exposes `capabilities[].runtimeMode`
 - `doctor-report.json` and `toolkit-config.json` expose `evidence.bundle`, `evidence.debugBuild`, `evidence.device`, and `evidence.release`
+- `doctor-report.json` and `toolkit-config.json` expose `evidenceSource.bundle`, `evidenceSource.debugBuild`, `evidenceSource.device`, and `evidenceSource.release`
+- `doctor-report.json` and `toolkit-config.json` also expose `coverageProfile` plus ordered `nextActions`
 - `runtimeMode=shim` means the capability still has not reached a verified runtime path even if bundling and debug-build scaffolding already exist
+- `evidenceSource.device=manual-doc` means the current device signal comes from manual acceptance records, not automated verification
+<!-- GENERATED:readme-support-matrix:end -->
+
+Starting in this refresh, `doctor` also emits `buildabilityRisk`, `coverageProfile`, `gapCategory`, and ordered `nextActions` so matrix drift, official-module gaps, third-party native blockers, and bare-workflow tracks no longer get described the same way. This does not relax any gate; it only improves diagnosis.
 
 See [docs/support-matrix.md](./docs/support-matrix.md) for the full allowlist, pairing rules, exact specifiers, issue codes, and release gates.
 
+If you want the `v1.8.x` promotion board directly, use [acceptance/v1.8.x-capability-board.md](./acceptance/v1.8.x-capability-board.md).
+
 ## Official Samples
 
 - `examples/official-ui-stack-sample`
   The current public main sample, covering router, linking, constants, SVG, reanimated, and the Harmony sidecar build flow.
 - `examples/official-native-capabilities-sample`
-  The `v1.7.x` Batch A+B preview walkthrough sample, covering the supported core subsets for `expo-file-system`, `expo-image-picker`, `expo-location`, and `expo-camera` plus permission, bundle, and debug-build validation.
+  The `v1.8.x` preview walkthrough sample, covering the supported core subsets for `expo-file-system`, `expo-image-picker`, `expo-location`, and `expo-camera` plus permission, bundle, debug-build validation, and per-capability acceptance tracking.
 - `examples/official-app-shell-sample`
   The minimal App Shell onboarding sample that demonstrates router, linking, constants, pathname, observed URL, and a generated deep-link flow.
 - `examples/official-minimal-sample`
@@ -226,10 +233,10 @@ Key managed outputs include:
 - `harmony/entry/src/main/cpp/autolinking.cmake`
 - `metro.harmony.config.js`
 - `.expo-harmony/manifest.json`
+- `.expo-harmony/toolkit-config.json`
 - `.expo-harmony/doctor-report.json`
 - `.expo-harmony/env-report.json`
 - `.expo-harmony/build-report.json`
-- `.expo-harmony/toolkit-config.json`
 
 ## Release And Validation
 
@@ -249,6 +256,12 @@ Automatic publishing still defaults to hosted CI only, but now splits into two t
 - GitHub auto-publish selects `latest` or `next` based on the tag and keeps provenance enabled
 - `build-hap --mode debug` still does not block hosted npm publishing
 
+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
+
 Manual Harmony acceptance still requires:
 
 - `official-ui-stack-sample` launches successfully
@@ -276,9 +289,10 @@ 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.2 Acceptance Log](./docs/v1.7.2-acceptance.md)
 - [Roadmap](./docs/roadmap.md)
 
+Acceptance logs stay in the repo-only [`acceptance/`](./acceptance/) directory and are not shipped inside the npm tarball.
+
 ## License
 
 Released under the [MIT License](./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.7.2-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.8.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.7` 延续 `verified + preview + experimental` 三层支持模型，并把 `expo-location`、`expo-camera` 推进到 `preview`。从这版文档开始，对外承诺进一步收紧为：`latest` 只承诺完整验收的 `verified` 能力，`next` 用于 preview fast track；路线仍然是先做到 `Managed/CNG Core Expo Coverage`，再通过 extension model 逼近“任意 Expo 项目”。
+> `v1.8` 延续 `verified + preview + experimental` 三层支持模型，并把 `expo-location`、`expo-camera` 继续保持在 `preview`。当前公开承诺仍然收紧为：`latest` 只承诺完整验收的 `verified` 能力，`next` 用于 preview fast track。最新 roadmap 已把 `v2.0.0` 直接定义成“任何 Expo 项目都能可靠打包成鸿蒙 App”，因此中间版本会继续拆小，但这不等于当前 `verified` 边界已经放宽。
 
 > [!TIP]
 > 由于当前公开矩阵内的两套 `@react-native-oh-tpl/*` adapter 依赖以 Git URL + exact commit 形式接入，仓库开发和官方 UI-stack sample 推荐使用 `pnpm install --ignore-scripts`，避免 Git adapter 在 prepare 阶段拉取私有资源而中断安装。
@@ -45,9 +45,10 @@
 
 ## 当前状态
 
+<!-- GENERATED:readme-current-status:start -->
 | 项目 | 说明 |
 | --- | --- |
-| 当前版本 | `v1.7.2` |
+| 当前版本 | `v1.8.0` |
 | 支持模型 | `verified + preview + experimental` |
 | 唯一 `verified` 公开矩阵 | `expo55-rnoh082-ui-stack` |
 | 输入范围 | Managed/CNG Expo 项目 |
@@ -55,11 +56,12 @@
 | `preview` 原生能力 | `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera` |
 | `experimental` 能力 | `expo-notifications`、`react-native-gesture-handler` |
 | 发布轨 | `latest` = fully accepted verified only；`next` = preview fast track |
-| capability 遥测 | `runtimeMode` + `evidence(bundle/debugBuild/device/release)` |
+| capability 遥测 | `runtimeMode` + `evidence(...)` + `evidenceSource(...)` + `coverageProfile` + `nextActions` |
 | 构建链 | `doctor -> init -> bundle -> build-hap` |
 | 主 sample | `examples/official-ui-stack-sample` |
 | preview sample | `examples/official-native-capabilities-sample` |
 | 辅助 onboarding samples | `examples/official-app-shell-sample`、`examples/official-minimal-sample` |
+<!-- GENERATED:readme-current-status:end -->
 
 <details>
 <summary><strong>当前仍不在 verified 正式承诺范围</strong></summary>
@@ -170,19 +172,22 @@ pnpm exec expo-harmony build-hap --mode release
 
 ## 支持矩阵
 
-`v1.7` 继续采用支持分层，并开始把 capability 晋升距离写进公开报告：
-
+<!-- GENERATED:readme-support-matrix:start -->
 - `verified`：唯一公开矩阵仍是 `expo55-rnoh082-ui-stack`
-- `preview`：`expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera`
-- `experimental`：`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 能力，但这不等于它们已经进入正式承诺。
 
-从本版开始：
-
 - `doctor-report.json` 的 `capabilities[]` 会带出 `runtimeMode`
 - `doctor-report.json` 与 `toolkit-config.json` 会带出 `evidence.bundle`、`evidence.debugBuild`、`evidence.device`、`evidence.release`
+- `doctor-report.json` 与 `toolkit-config.json` 会带出 `evidenceSource.bundle`、`evidenceSource.debugBuild`、`evidenceSource.device`、`evidenceSource.release`
+- `doctor-report.json` 与 `toolkit-config.json` 也会带出 `coverageProfile` 与按顺序排列的 `nextActions`
 - `runtimeMode=shim` 说明当前仍未进入 verified runtime path，即使 bundle / debug build 已经可走通
+- `evidenceSource.device=manual-doc` 表示当前只有人工设备验收记录，不代表机器自动验证
+<!-- GENERATED:readme-support-matrix:end -->
+
+从本版开始，`doctor` 还会额外输出 `buildabilityRisk`、`coverageProfile`、`gapCategory` 与有序 `nextActions`，把“矩阵漂移”“官方模块缺口”“第三方 native blocker”“bare workflow 轨道”分开描述；这不会放宽 gate，只是让构建可诊断性更强。
 
 文档里的状态标记额外约定为：
 
@@ -192,12 +197,14 @@ pnpm exec expo-harmony build-hap --mode release
 
 完整白名单、配对规则、exact specifier、issue code 与 release gate 见 [docs/support-matrix.md](./docs/support-matrix.md)。
 
+如果你要跟进 `v1.8.x` 的并行晋升节奏，可直接看 [acceptance/v1.8.x-capability-board.md](./acceptance/v1.8.x-capability-board.md)。
+
 ## 官方 Samples
 
 - `examples/official-ui-stack-sample`
   当前唯一对外主 sample，同时覆盖 router、linking、constants、SVG、reanimated 和 Harmony sidecar 构建链。
 - `examples/official-native-capabilities-sample`
-  `v1.7.x` 的 Batch A+B preview walkthrough sample，用来承接 `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera` 的核心支持子集、permission、bundle 与 debug build 验收。
+  `v1.8.x` 的 preview walkthrough sample，用来承接 `expo-file-system`、`expo-image-picker`、`expo-location`、`expo-camera` 的核心支持子集、permission、bundle、debug build 与逐 capability 验收追踪。
 - `examples/official-app-shell-sample`
   最小可理解的 App Shell onboarding sample，用来展示 router、linking、constants、pathname、observed URL 与 generated deep link。
 - `examples/official-minimal-sample`
@@ -233,9 +240,9 @@ pnpm exec expo-harmony build-hap --mode release
 - `metro.harmony.config.js`
 - `.expo-harmony/manifest.json`
 - `.expo-harmony/doctor-report.json`
+- `.expo-harmony/toolkit-config.json`
 - `.expo-harmony/env-report.json`
 - `.expo-harmony/build-report.json`
-- `.expo-harmony/toolkit-config.json`
 
 ## 发布与验收
 
@@ -255,6 +262,12 @@ pnpm exec expo-harmony build-hap --mode release
 - GitHub 自动发布按 tag 选择 `latest` 或 `next` dist-tag，并保留 provenance
 - `build-hap --mode debug` 继续不作为 hosted npm publish 的硬阻塞条件
 
+preview 证据的额外说明：
+
+- `bundle/debugBuild` 标记为 `automated`
+- `device` 标记为 `manual-doc`，表示已有人工验收记录，不等于 CI 自动验收
+- `release` 标记为 `none`，表示当前仍没有 release 证据
+
 手动 Harmony 验收继续要求：
 
 - `official-ui-stack-sample` 成功启动
@@ -282,9 +295,10 @@ verified capability 晋升还必须补齐：
 - [官方最小 sample 指南](./docs/official-minimal-sample.md)
 - [npm 发布说明](./docs/npm-release.md)
 - [签名与 Release 说明](./docs/signing-and-release.md)
-- [v1.7.2 验收记录](./docs/v1.7.2-acceptance.md)
 - [路线图](./docs/roadmap.md)
 
+验收记录继续保留在 repo-only 的 [`acceptance/`](./acceptance/) 目录中，不随 npm tarball 一起发布。
+
 ## License
 
 本项目基于 [MIT License](./LICENSE) 发布。

package/build/core/autolinking.d.ts

@@ -0,0 +1,10 @@
+import { TemplateFileDefinition } from '../types';
+export declare const AUTOLINKED_FILE_PATHS: readonly [string, string, string, string];
+export declare class AutolinkingFailureError extends Error {
+    constructor(stage: string, command: string, options?: {
+        cause?: string;
+        missingFiles?: string[];
+    });
+}
+export declare function buildAutolinkedManagedFiles(projectRoot: string, harmonyRootPackageContents: string): Promise<TemplateFileDefinition[]>;
+export declare function normalizeKnownHarmonyPackageJsons(projectRoot: string): Promise<() => Promise<void>>;