expo-harmony-toolkit 1.7.3 → 1.8.1

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.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.8.1-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.
@@ -48,7 +48,7 @@
 <!-- GENERATED:readme-current-status:start -->
 | Item | Status |
 | --- | --- |
-| Current version | `v1.7.3` |
+| Current version | `v1.8.1` |
 | Support model | `verified + preview + experimental` |
 | Public `verified` matrix | `expo55-rnoh082-ui-stack` |
 | Supported input | Managed/CNG Expo projects |
@@ -56,7 +56,7 @@
 | `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(...)` + `evidenceSource(...)` |
+| 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` |
@@ -182,20 +182,23 @@ Common decision points:
 - `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` so matrix-out dependencies that still look JavaScript-only no longer get described the same way as packages with clear native risk. This does not relax any gate; it only improves diagnosis.
+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`

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.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.8.1-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 阶段拉取私有资源而中断安装。
@@ -48,7 +48,7 @@
 <!-- GENERATED:readme-current-status:start -->
 | 项目 | 说明 |
 | --- | --- |
-| 当前版本 | `v1.7.3` |
+| 当前版本 | `v1.8.1` |
 | 支持模型 | `verified + preview + experimental` |
 | 唯一 `verified` 公开矩阵 | `expo55-rnoh082-ui-stack` |
 | 输入范围 | Managed/CNG Expo 项目 |
@@ -56,7 +56,7 @@
 | `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(...)` + `evidenceSource(...)` |
+| capability 遥测 | `runtimeMode` + `evidence(...)` + `evidenceSource(...)` + `coverageProfile` + `nextActions` |
 | 构建链 | `doctor -> init -> bundle -> build-hap` |
 | 主 sample | `examples/official-ui-stack-sample` |
 | preview sample | `examples/official-native-capabilities-sample` |
@@ -182,11 +182,12 @@ pnpm exec expo-harmony build-hap --mode release
 - `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`，把“超出公开矩阵但看起来更像纯 JS 层”的依赖，与“存在明确原生风险”的依赖区分开来；这不会放宽 gate，只是让构建可诊断性更强。
+从本版开始，`doctor` 还会额外输出 `buildabilityRisk`、`coverageProfile`、`gapCategory` 与有序 `nextActions`，把“矩阵漂移”“官方模块缺口”“第三方 native blocker”“bare workflow 轨道”分开描述；这不会放宽 gate，只是让构建可诊断性更强。
 
 文档里的状态标记额外约定为：
 
@@ -196,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`

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.7.3";
+export declare const TOOLKIT_VERSION = "1.8.1";
 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.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.7.3';
+exports.TOOLKIT_VERSION = '1.8.1';
 exports.TEMPLATE_VERSION = 'rnoh-0.82.18';
 exports.RNOH_VERSION = '0.82.18';
 exports.RNOH_CLI_VERSION = '0.82.18';

package/build/core/dependencyInspection.js

@@ -46,7 +46,7 @@ async function resolveDependencyBuildabilityRisk(projectRoot, dependency) {
     if (dependency.status !== 'unknown') {
         return 'known';
     }
-    const packageJsonPath = resolveInstalledDependencyPackageJson(projectRoot, dependency.name);
+    const packageJsonPath = resolveInstalledDependencyPackageJson(projectRoot, dependency.name, dependency.version);
     if (!packageJsonPath || !(await fs_extra_1.default.pathExists(packageJsonPath))) {
         return 'unresolved';
     }
@@ -60,7 +60,11 @@ async function resolveDependencyBuildabilityRisk(projectRoot, dependency) {
     }
     return 'js-only-unknown';
 }
-function resolveInstalledDependencyPackageJson(projectRoot, dependencyName) {
+function resolveInstalledDependencyPackageJson(projectRoot, dependencyName, dependencyVersion) {
+    const localPackageJsonPath = resolveLocalDependencyPackageJson(projectRoot, dependencyVersion);
+    if (localPackageJsonPath) {
+        return localPackageJsonPath;
+    }
     try {
         const projectRequire = (0, node_module_1.createRequire)(path_1.default.join(projectRoot, 'package.json'));
         return projectRequire.resolve(`${dependencyName}/package.json`);
@@ -69,6 +73,20 @@ function resolveInstalledDependencyPackageJson(projectRoot, dependencyName) {
         return null;
     }
 }
+function resolveLocalDependencyPackageJson(projectRoot, dependencyVersion) {
+    const trimmedVersion = dependencyVersion.trim();
+    for (const prefix of ['file:', 'link:', 'portal:']) {
+        if (!trimmedVersion.startsWith(prefix)) {
+            continue;
+        }
+        const relativeTarget = trimmedVersion.slice(prefix.length).trim();
+        if (!relativeTarget) {
+            return null;
+        }
+        return path_1.default.resolve(projectRoot, relativeTarget, 'package.json');
+    }
+    return null;
+}
 function looksLikeNativeDependencyByPackageName(dependencyName) {
     return PACKAGE_NAME_NATIVE_PATTERNS.some((pattern) => pattern.test(dependencyName));
 }

package/build/core/project.d.ts

@@ -1,4 +1,4 @@
-import { DependencySource, ExpoHarmonyPluginProps, HarmonyIdentifiers, LoadedProject, PackageJson } from '../types';
+import { DependencySource, ExpoHarmonyResolvedDoctorConfig, ExpoHarmonyPluginProps, HarmonyIdentifiers, LoadedProject, PackageJson } from '../types';
 export declare function resolveProjectRoot(projectRoot?: string): Promise<string>;
 export declare function loadProject(projectRoot: string): Promise<LoadedProject>;
 export declare function ensureProjectPackageJsonPath(projectRoot: string): Promise<string>;
@@ -10,6 +10,8 @@ export declare function collectDeclaredDependencies(packageJson: PackageJson): A
 }>;
 export declare function hasDeclaredDependency(packageJson: PackageJson, dependencyName: string): boolean;
 export declare function collectExpoPlugins(expoConfig: Record<string, any>): string[];
+export declare function resolveExpoHarmonyDoctorConfig(expoConfig: Record<string, any>): ExpoHarmonyResolvedDoctorConfig;
+export declare function applyDependencyExclusions(packageJson: PackageJson, excludedDependencies: readonly string[]): PackageJson;
 export declare function collectExpoSchemes(expoConfig: Record<string, any>): string[];
 export declare function deriveHarmonyIdentifiers(expoConfig: Record<string, any>, packageJson?: PackageJson, props?: ExpoHarmonyPluginProps): HarmonyIdentifiers;
 export declare function detectExpoSdkVersion(packageJson: PackageJson): number | null;

package/build/core/project.js

@@ -10,6 +10,8 @@ exports.findAppConfigPath = findAppConfigPath;
 exports.collectDeclaredDependencies = collectDeclaredDependencies;
 exports.hasDeclaredDependency = hasDeclaredDependency;
 exports.collectExpoPlugins = collectExpoPlugins;
+exports.resolveExpoHarmonyDoctorConfig = resolveExpoHarmonyDoctorConfig;
+exports.applyDependencyExclusions = applyDependencyExclusions;
 exports.collectExpoSchemes = collectExpoSchemes;
 exports.deriveHarmonyIdentifiers = deriveHarmonyIdentifiers;
 exports.detectExpoSdkVersion = detectExpoSdkVersion;
@@ -100,6 +102,27 @@ function collectExpoPlugins(expoConfig) {
     }
     return [...names].sort((left, right) => left.localeCompare(right));
 }
+function resolveExpoHarmonyDoctorConfig(expoConfig) {
+    const rawDoctorConfig = expoConfig.extra?.expoHarmony?.doctor;
+    const coverageProfile = normalizeCoverageProfile(rawDoctorConfig?.coverageProfile);
+    return {
+        excludeDependencies: normalizeStringArray(rawDoctorConfig?.excludeDependencies),
+        excludePlugins: normalizeStringArray(rawDoctorConfig?.excludePlugins),
+        coverageProfile,
+    };
+}
+function applyDependencyExclusions(packageJson, excludedDependencies) {
+    if (excludedDependencies.length === 0) {
+        return packageJson;
+    }
+    const excludedDependencySet = new Set(excludedDependencies);
+    return {
+        ...packageJson,
+        dependencies: filterDependencySection(packageJson.dependencies, excludedDependencySet),
+        devDependencies: filterDependencySection(packageJson.devDependencies, excludedDependencySet),
+        peerDependencies: filterDependencySection(packageJson.peerDependencies, excludedDependencySet),
+    };
+}
 function collectExpoSchemes(expoConfig) {
     const rawScheme = expoConfig.scheme;
     if (typeof rawScheme === 'string' && rawScheme.trim().length > 0) {
@@ -204,3 +227,27 @@ function sanitizeIdentifierSegment(value) {
         .replace(/^_+/, '');
     return cleaned.length > 0 ? cleaned : 'entry';
 }
+function normalizeStringArray(value) {
+    if (!Array.isArray(value)) {
+        return [];
+    }
+    return [...new Set(value
+            .filter((entry) => typeof entry === 'string')
+            .map((entry) => entry.trim())
+            .filter((entry) => entry.length > 0))].sort((left, right) => left.localeCompare(right));
+}
+function normalizeCoverageProfile(value) {
+    if (value === 'managed-core' ||
+        value === 'managed-native-heavy' ||
+        value === 'bare' ||
+        value === 'third-party-native-heavy') {
+        return value;
+    }
+    return null;
+}
+function filterDependencySection(section, excludedDependencies) {
+    if (!section) {
+        return section;
+    }
+    return Object.fromEntries(Object.entries(section).filter(([dependencyName]) => !excludedDependencies.has(dependencyName)));
+}

package/build/core/report.js

@@ -23,15 +23,20 @@ const DEFAULT_RECORD = {
     supportTier: 'unsupported',
     note: 'This dependency is not in the current compatibility catalog yet.',
 };
+const BARE_WORKFLOW_DIRECTORY_NAMES = ['android', 'ios'];
+const BARE_WORKFLOW_DEPENDENCIES = new Set(['expo-build-properties', 'expo-dev-client']);
 async function buildDoctorReport(projectRoot, options = {}) {
     const loadedProject = await (0, project_1.loadProject)(projectRoot);
+    const doctorConfig = (0, project_1.resolveExpoHarmonyDoctorConfig)(loadedProject.expoConfig);
+    const filteredPackageJson = (0, project_1.applyDependencyExclusions)(loadedProject.packageJson, doctorConfig.excludeDependencies);
     const expoSdkVersion = (0, project_1.detectExpoSdkVersion)(loadedProject.packageJson);
     const matrix = validatedMatrices_1.VALIDATED_RELEASE_MATRICES[validatedMatrices_1.DEFAULT_VALIDATED_MATRIX_ID];
     const targetTier = options.targetTier ?? 'verified';
-    const expoPlugins = (0, project_1.collectExpoPlugins)(loadedProject.expoConfig);
+    const excludedPlugins = new Set(doctorConfig.excludePlugins);
+    const expoPlugins = (0, project_1.collectExpoPlugins)(loadedProject.expoConfig).filter((pluginName) => !excludedPlugins.has(pluginName));
     const expoSchemes = (0, project_1.collectExpoSchemes)(loadedProject.expoConfig);
     const dependencyRecords = new Map();
-    const declaredDependencies = (0, project_1.collectDeclaredDependencies)(loadedProject.packageJson);
+    const declaredDependencies = (0, project_1.collectDeclaredDependencies)(filteredPackageJson);
     for (const dependency of declaredDependencies) {
         dependencyRecords.set(dependency.name, createDependencyRecord(dependency.name, dependency.version, dependency.source));
     }
@@ -41,8 +46,11 @@ async function buildDoctorReport(projectRoot, options = {}) {
         }
     }
     const dependencies = await (0, dependencyInspection_1.annotateDependencyBuildability)(loadedProject.projectRoot, [...dependencyRecords.values()].sort((left, right) => left.name.localeCompare(right.name)));
-    const blockingIssues = await collectBlockingIssues(loadedProject.projectRoot, loadedProject.expoConfig, loadedProject.packageJson, expoPlugins, expoSchemes, expoSdkVersion, dependencies, matrix, targetTier);
-    const capabilities = (0, capabilities_1.getCapabilityDefinitionsForProject)(loadedProject.packageJson).map((definition) => ({
+    const blockingIssues = await collectBlockingIssues(loadedProject.projectRoot, loadedProject.expoConfig, filteredPackageJson, expoPlugins, expoSchemes, expoSdkVersion, dependencies, matrix, targetTier);
+    const excludedDependencies = new Set(doctorConfig.excludeDependencies);
+    const capabilities = (0, capabilities_1.getCapabilityDefinitionsForProject)(filteredPackageJson, {
+        excludedDependencies,
+    }).map((definition) => ({
         id: definition.id,
         packageName: definition.packageName,
         status: definition.status,
@@ -57,15 +65,24 @@ async function buildDoctorReport(projectRoot, options = {}) {
         sampleRoute: definition.sampleRoute,
         acceptanceChecklist: [...definition.acceptanceChecklist],
     }));
+    const coverageProfile = await detectCoverageProfile(loadedProject.projectRoot, filteredPackageJson, dependencies, doctorConfig.coverageProfile);
     const blockingDependencyNames = new Set(blockingIssues
         .filter((issue) => issue.code.startsWith('dependency.') && issue.subject)
         .map((issue) => issue.subject));
     const resolvedDependencies = dependencies.map((dependency) => ({
         ...dependency,
+        gapCategory: resolveDependencyGapCategory(dependency, coverageProfile),
         blocking: blockingDependencyNames.has(dependency.name),
     }));
+    const nextActions = buildNextActions({
+        targetTier,
+        coverageProfile,
+        blockingIssues,
+        dependencies: resolvedDependencies,
+        capabilities,
+    });
     const warnings = buildWarnings(loadedProject.expoConfig, expoSdkVersion, resolvedDependencies);
-    const advisories = buildAdvisories(loadedProject.expoConfig);
+    const advisories = buildAdvisories(loadedProject.expoConfig, doctorConfig);
     return {
         generatedAt: new Date().toISOString(),
         projectRoot: loadedProject.projectRoot,
@@ -78,6 +95,7 @@ async function buildDoctorReport(projectRoot, options = {}) {
         rnohCliVersion: constants_1.RNOH_CLI_VERSION,
         expoSdkVersion,
         targetTier,
+        coverageProfile,
         expoConfig: {
             name: loadedProject.expoConfig.name ?? null,
             slug: loadedProject.expoConfig.slug ?? null,
@@ -102,6 +120,7 @@ async function buildDoctorReport(projectRoot, options = {}) {
         },
         capabilities,
         blockingIssues,
+        nextActions,
         advisories,
         warnings,
     };
@@ -120,6 +139,7 @@ function renderDoctorReport(report) {
         `Expo SDK: ${report.expoSdkVersion ?? 'unknown'} (recognized ${constants_1.SUPPORTED_EXPO_SDKS.join(', ')})`,
         `Matrix: ${report.matrixId ?? 'none'}`,
         `Target tier: ${report.targetTier}`,
+        `Coverage profile: ${report.coverageProfile}`,
         `Eligibility: ${report.eligibility}`,
         `Schemes: ${report.expoConfig.schemes.join(', ') || 'none'}`,
         `Plugins: ${report.expoConfig.plugins.join(', ') || 'none'}`,
@@ -131,7 +151,7 @@ function renderDoctorReport(report) {
         ...report.dependencies.map((dependency) => {
             const replacement = dependency.replacement ? ` | replacement: ${dependency.replacement}` : '';
             const blocking = dependency.blocking ? ' | blocking: yes' : '';
-            return `- [${dependency.status}/${dependency.supportTier}] ${dependency.name}@${dependency.version} (${dependency.source}) - ${dependency.note} | buildability: ${renderDependencyBuildabilityRisk(dependency.buildabilityRisk)}${replacement}${blocking}`;
+            return `- [${dependency.status}/${dependency.supportTier}] ${dependency.name}@${dependency.version} (${dependency.source}) - ${dependency.note} | buildability: ${renderDependencyBuildabilityRisk(dependency.buildabilityRisk)} | gap: ${dependency.gapCategory}${replacement}${blocking}`;
         }),
     ];
     if (report.capabilities.length > 0) {
@@ -151,6 +171,9 @@ function renderDoctorReport(report) {
     if (report.blockingIssues.length > 0) {
         sections.push('', 'Blocking issues:', ...report.blockingIssues.map((issue) => `- ${issue.code}: ${issue.message}${issue.subject ? ` (${issue.subject})` : ''}`));
     }
+    if (report.nextActions.length > 0) {
+        sections.push('', 'Next actions:', ...report.nextActions.map((action, index) => `${index + 1}. ${action}`));
+    }
     if (report.advisories.length > 0) {
         sections.push('', 'Advisories:', ...report.advisories.map((advisory) => `- ${advisory}`));
     }
@@ -188,6 +211,7 @@ function createDependencyRecord(name, version, source) {
         status: matrixRecord.status,
         supportTier: matrixRecord.supportTier,
         buildabilityRisk: 'known',
+        gapCategory: 'matrix-drift',
         blocking: false,
         note: matrixRecord.note,
         replacement: matrixRecord.replacement,
@@ -335,6 +359,117 @@ async function collectBlockingIssues(projectRoot, expoConfig, packageJson, expoP
     }
     return dedupeIssues(issues);
 }
+async function detectCoverageProfile(projectRoot, packageJson, dependencies, coverageProfileOverride) {
+    if (coverageProfileOverride) {
+        return coverageProfileOverride;
+    }
+    for (const directoryName of BARE_WORKFLOW_DIRECTORY_NAMES) {
+        if (await fs_extra_1.default.pathExists(path_1.default.join(projectRoot, directoryName))) {
+            return 'bare';
+        }
+    }
+    if (dependencies.some((dependency) => isThirdPartyNativeGapDependency(dependency))) {
+        return 'third-party-native-heavy';
+    }
+    if ((0, capabilities_1.getCapabilityDefinitionsForProject)(packageJson).length > 0 ||
+        dependencies.some((dependency) => isOfficialExpoDependencyName(dependency.name) && dependency.supportTier !== 'verified')) {
+        return 'managed-native-heavy';
+    }
+    return 'managed-core';
+}
+function resolveDependencyGapCategory(dependency, coverageProfile) {
+    if (coverageProfile === 'bare' &&
+        (BARE_WORKFLOW_DEPENDENCIES.has(dependency.name) ||
+            dependency.name === 'expo' ||
+            dependency.name === 'react-native')) {
+        return 'bare-workflow-gap';
+    }
+    if (isOfficialExpoDependencyName(dependency.name) || capabilities_1.CAPABILITY_BY_PACKAGE[dependency.name]) {
+        return dependency.supportTier === 'verified' && dependency.status === 'supported'
+            ? 'matrix-drift'
+            : 'official-module-gap';
+    }
+    if (isThirdPartyNativeGapDependency(dependency)) {
+        return 'third-party-native-gap';
+    }
+    if (coverageProfile === 'bare') {
+        return 'bare-workflow-gap';
+    }
+    return 'matrix-drift';
+}
+function isOfficialExpoDependencyName(dependencyName) {
+    return dependencyName === 'expo' || dependencyName.startsWith('expo-') || dependencyName.startsWith('@expo/');
+}
+function isThirdPartyNativeGapDependency(dependency) {
+    if (dependency.name === 'react-native-gesture-handler' ||
+        dependency.name === '@react-native-oh-tpl/react-native-gesture-handler') {
+        return true;
+    }
+    if (dependency.buildabilityRisk === 'native-risk') {
+        return true;
+    }
+    return (dependency.supportTier !== 'verified' &&
+        !isOfficialExpoDependencyName(dependency.name) &&
+        dependency.name.startsWith('react-native'));
+}
+function buildNextActions(input) {
+    const actions = [];
+    const { targetTier, coverageProfile, blockingIssues, dependencies, capabilities } = input;
+    const hasPreviewCapabilities = capabilities.some((capability) => capability.supportTier === 'preview');
+    const hasRouterBlockingIssues = blockingIssues.some((issue) => [
+        'dependency.router_peer_missing',
+        'config.router_plugin.missing',
+        'config.scheme.missing',
+        'config.bundle_script.mismatch',
+    ].includes(issue.code));
+    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 (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':
+            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` out of the verified lane until its Harmony adapter path has stable doctor, sample, and build coverage.');
+    }
+    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 (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.');
+    }
+    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.');
+    }
+    return dedupeStrings(actions);
+}
+function hasBlockingIssueCode(issues, code) {
+    return issues.some((issue) => issue.code === code);
+}
 function buildWarnings(expoConfig, expoSdkVersion, dependencies) {
     const warnings = [];
     const expoSdkWarning = (0, project_1.getExpoSdkWarning)(expoSdkVersion);
@@ -364,8 +499,17 @@ function buildWarnings(expoConfig, expoSdkVersion, dependencies) {
     }
     return warnings;
 }
-function buildAdvisories(expoConfig) {
+function buildAdvisories(expoConfig, doctorConfig) {
     const advisories = [];
+    if (doctorConfig.excludeDependencies.length > 0) {
+        advisories.push(`Expo Harmony doctor excluded dependencies: ${doctorConfig.excludeDependencies.join(', ')}.`);
+    }
+    if (doctorConfig.excludePlugins.length > 0) {
+        advisories.push(`Expo Harmony doctor excluded plugins: ${doctorConfig.excludePlugins.join(', ')}.`);
+    }
+    if (doctorConfig.coverageProfile) {
+        advisories.push(`Expo Harmony doctor forced coverage profile to ${doctorConfig.coverageProfile}.`);
+    }
     if (!expoConfig.android?.package && expoConfig.ios?.bundleIdentifier) {
         advisories.push('The project is using ios.bundleIdentifier as the only explicit native identifier. Prefer setting android.package as well before claiming release readiness.');
     }
@@ -375,11 +519,12 @@ function isDependencyAllowedForTargetTier(dependencyName, matrix, targetTier) {
     if (matrix.allowedDependencies.includes(dependencyName)) {
         return true;
     }
-    const capability = capabilities_1.CAPABILITY_BY_PACKAGE[dependencyName];
-    if (!capability) {
-        return false;
+    const catalogRecord = dependencyCatalog_1.DEPENDENCY_CATALOG[dependencyName];
+    if (catalogRecord) {
+        return (0, capabilities_1.isSupportTierAllowed)(catalogRecord.supportTier, targetTier);
     }
-    return (0, capabilities_1.isSupportTierAllowed)(capability.supportTier, targetTier);
+    const capability = capabilities_1.CAPABILITY_BY_PACKAGE[dependencyName];
+    return capability ? (0, capabilities_1.isSupportTierAllowed)(capability.supportTier, targetTier) : false;
 }
 function matchesVersionRange(rawVersion, range) {
     const coerced = semver_1.default.coerce(rawVersion);
@@ -418,3 +563,6 @@ function dedupeIssues(issues) {
         return true;
     });
 }
+function dedupeStrings(values) {
+    return [...new Set(values)];
+}

package/build/core/template.d.ts

@@ -1,9 +1,10 @@
-import { InitResult, SyncResult } from '../types';
+import { InitResult, DoctorReport, SyncResult } from '../types';
 export { buildDesiredPackageScripts, resolveHarmonyBundleEntryFile, usesExpoRouter, } from './template/support';
 export declare const BUILD_REQUIRED_MANAGED_FILE_PATHS: readonly [string, string, string, string, string];
 interface SyncProjectTemplateOptions {
     forceManagedPaths?: readonly string[];
     skipJavaScriptDependencyNormalization?: boolean;
+    doctorReport?: DoctorReport;
 }
 export declare function initProject(projectRoot: string, force?: boolean): Promise<InitResult>;
 export declare function syncProjectTemplate(projectRoot: string, force?: boolean, options?: SyncProjectTemplateOptions): Promise<SyncResult>;

package/build/core/template.js

@@ -64,7 +64,9 @@ exports.BUILD_REQUIRED_MANAGED_FILE_PATHS = [
 ];
 async function initProject(projectRoot, force = false) {
     const report = await (0, report_1.buildDoctorReport)(projectRoot);
-    const sync = await syncProjectTemplate(projectRoot, force);
+    const sync = await syncProjectTemplate(projectRoot, force, {
+        doctorReport: report,
+    });
     const packageWarnings = await syncPackageScripts(projectRoot, force);
     const doctorReportPath = await (0, report_1.writeDoctorReport)(projectRoot, report);
     return {
@@ -78,7 +80,8 @@ async function syncProjectTemplate(projectRoot, force = false, options = {}) {
     const loadedProject = await (0, project_1.loadProject)(projectRoot);
     const identifiers = (0, project_1.deriveHarmonyIdentifiers)(loadedProject.expoConfig, loadedProject.packageJson);
     const previousToolkitConfig = await (0, metadata_1.readToolkitConfig)(loadedProject.projectRoot);
-    const desiredFiles = await buildManagedFiles(loadedProject, identifiers, previousToolkitConfig);
+    const doctorReport = options.doctorReport ?? (await (0, report_1.buildDoctorReport)(loadedProject.projectRoot));
+    const desiredFiles = await buildManagedFiles(loadedProject, identifiers, previousToolkitConfig, doctorReport);
     const previousManifest = await (0, metadata_1.readManifest)(loadedProject.projectRoot);
     const forceManagedPaths = new Set(options.forceManagedPaths ?? []);
     const result = {
@@ -130,11 +133,14 @@ async function syncProjectTemplate(projectRoot, force = false, options = {}) {
     await fs_extra_1.default.writeJson(result.manifestPath, manifest, { spaces: 2 });
     return result;
 }
-async function buildManagedFiles(loadedProject, identifiers, previousToolkitConfig) {
+async function buildManagedFiles(loadedProject, identifiers, previousToolkitConfig, doctorReport) {
     const hasExpoRouter = (0, support_1.usesExpoRouter)(loadedProject.packageJson);
-    const enabledCapabilities = (0, capabilities_1.getCapabilityDefinitionsForProject)(loadedProject.packageJson);
+    const doctorConfig = (0, project_1.resolveExpoHarmonyDoctorConfig)(loadedProject.expoConfig);
+    const enabledCapabilities = doctorReport.capabilities;
     const hasManagedExpoHarmonyPackage = enabledCapabilities.some((capability) => capability.runtimeMode !== 'shim');
-    const requestedHarmonyPermissions = (0, capabilities_1.collectCapabilityHarmonyPermissions)(loadedProject.packageJson);
+    const requestedHarmonyPermissions = (0, capabilities_1.collectCapabilityHarmonyPermissions)(loadedProject.packageJson, {
+        excludedDependencies: new Set(doctorConfig.excludeDependencies),
+    });
     const signingLocalConfig = await (0, signing_1.readSigningLocalConfig)(loadedProject.projectRoot);
     const hvigorPluginFilename = await (0, project_1.resolveRnohHvigorPluginFilename)(loadedProject.projectRoot);
     const renderedHarmonyRootPackage = renderTemplate(await fs_extra_1.default.readFile(path_1.default.join(TEMPLATE_ROOT, 'oh-package.json5'), 'utf8'), loadedProject, identifiers, hvigorPluginFilename);
@@ -175,6 +181,8 @@ async function buildManagedFiles(loadedProject, identifiers, previousToolkitConf
         rnohCliVersion: constants_1.RNOH_CLI_VERSION,
         bundleName: identifiers.bundleName,
         entryModuleName: identifiers.entryModuleName,
+        coverageProfile: doctorReport.coverageProfile,
+        doctorConfig,
         capabilities: enabledCapabilities.map((capability) => ({
             id: capability.id,
             packageName: capability.packageName,
@@ -184,6 +192,7 @@ async function buildManagedFiles(loadedProject, identifiers, previousToolkitConf
             evidenceSource: { ...capability.evidenceSource },
         })),
         requestedHarmonyPermissions,
+        nextActions: [...doctorReport.nextActions],
         project: {
             name: loadedProject.expoConfig.name ?? identifiers.appName,
             slug: loadedProject.expoConfig.slug ?? identifiers.slug,

package/build/data/capabilities.d.ts

@@ -3,5 +3,9 @@ export declare const CAPABILITY_DEFINITIONS: readonly CapabilityDefinition[];
 export declare const CAPABILITY_BY_PACKAGE: Record<string, CapabilityDefinition>;
 export declare function compareSupportTiers(left: SupportTier, right: SupportTier): number;
 export declare function isSupportTierAllowed(dependencyTier: SupportTier, targetTier: DoctorTargetTier): boolean;
-export declare function getCapabilityDefinitionsForProject(packageJson: PackageJson): CapabilityDefinition[];
-export declare function collectCapabilityHarmonyPermissions(packageJson: PackageJson): string[];
+export declare function getCapabilityDefinitionsForProject(packageJson: PackageJson, options?: {
+    excludedDependencies?: ReadonlySet<string>;
+}): CapabilityDefinition[];
+export declare function collectCapabilityHarmonyPermissions(packageJson: PackageJson, options?: {
+    excludedDependencies?: ReadonlySet<string>;
+}): string[];

package/build/data/capabilities.js

@@ -39,7 +39,7 @@ exports.CAPABILITY_DEFINITIONS = [
         runtimeMode: 'adapter',
         evidence: PREVIEW_BASELINE_EVIDENCE,
         evidenceSource: PREVIEW_BASELINE_EVIDENCE_SOURCE,
-        note: 'Toolkit-managed Harmony native file-system adapters cover the v1.7.3 preview subset: UTF-8/base64 sandbox I/O, append and partial reads, md5 metadata, and direct downloads into the app sandbox.',
+        note: 'Toolkit-managed Harmony native file-system adapters cover the v1.8.0 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: [],
@@ -58,7 +58,7 @@ exports.CAPABILITY_DEFINITIONS = [
         runtimeMode: 'adapter',
         evidence: PREVIEW_BASELINE_EVIDENCE,
         evidenceSource: PREVIEW_BASELINE_EVIDENCE_SOURCE,
-        note: 'Toolkit-managed Harmony adapters cover the v1.7.3 preview subset: media and camera permissions, single/multi-select library flows, system photo/video capture, pending-result restore, and richer video asset metadata.',
+        note: 'Toolkit-managed Harmony adapters cover the v1.8.0 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: [
@@ -81,7 +81,7 @@ exports.CAPABILITY_DEFINITIONS = [
         runtimeMode: 'adapter',
         evidence: PREVIEW_BASELINE_EVIDENCE,
         evidenceSource: PREVIEW_BASELINE_EVIDENCE_SOURCE,
-        note: 'Toolkit-managed Harmony adapters cover the v1.7.3 preview subset: foreground/background permission flows, current and last-known fixes, geocoding, continuous watch subscriptions, and sensor-backed heading updates.',
+        note: 'Toolkit-managed Harmony adapters cover the v1.8.0 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: [
@@ -105,7 +105,7 @@ exports.CAPABILITY_DEFINITIONS = [
         runtimeMode: 'adapter',
         evidence: PREVIEW_BASELINE_EVIDENCE,
         evidenceSource: PREVIEW_BASELINE_EVIDENCE_SOURCE,
-        note: 'Toolkit-managed Harmony adapters cover the v1.7.3 preview subset: embedded camera preview, still capture, preview pause/resume, microphone permission, and in-session video recording controls.',
+        note: 'Toolkit-managed Harmony adapters cover the v1.8.0 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', 'ohos.permission.MICROPHONE'],
@@ -149,9 +149,11 @@ function compareSupportTiers(left, right) {
 function isSupportTierAllowed(dependencyTier, targetTier) {
     return compareSupportTiers(dependencyTier, targetTier) <= 0;
 }
-function getCapabilityDefinitionsForProject(packageJson) {
-    return exports.CAPABILITY_DEFINITIONS.filter((definition) => (0, project_1.hasDeclaredDependency)(packageJson, definition.packageName)).sort((left, right) => left.packageName.localeCompare(right.packageName));
+function getCapabilityDefinitionsForProject(packageJson, options = {}) {
+    const excludedDependencies = options.excludedDependencies ?? new Set();
+    return exports.CAPABILITY_DEFINITIONS.filter((definition) => !excludedDependencies.has(definition.packageName) &&
+        (0, project_1.hasDeclaredDependency)(packageJson, definition.packageName)).sort((left, right) => left.packageName.localeCompare(right.packageName));
 }
-function collectCapabilityHarmonyPermissions(packageJson) {
-    return Array.from(new Set(getCapabilityDefinitionsForProject(packageJson).flatMap((definition) => definition.harmonyPermissions))).sort((left, right) => left.localeCompare(right));
+function collectCapabilityHarmonyPermissions(packageJson, options = {}) {
+    return Array.from(new Set(getCapabilityDefinitionsForProject(packageJson, options).flatMap((definition) => definition.harmonyPermissions))).sort((left, right) => left.localeCompare(right));
 }

package/build/data/dependencyCatalog.js

@@ -112,6 +112,30 @@ exports.DEPENDENCY_CATALOG = {
         supportTier: 'verified',
         note: 'File-based routing is treated as part of the validated App Shell matrix when router peers, scheme, and plugin config are present.',
     },
+    '@react-native-async-storage/async-storage': {
+        status: 'manual',
+        supportTier: 'experimental',
+        note: 'Async storage is a high-frequency startup dependency. Treat it as an experimental Harmony intake dependency until the managed adapter path has stable doctor, sample, and build coverage.',
+        docsUrl: 'https://github.com/react-native-oh-library',
+    },
+    'react-native-safe-area-context': {
+        status: 'supported',
+        supportTier: 'experimental',
+        note: 'Safe-area handling is shimmed by the toolkit for Harmony so App Shell layouts can keep rendering while the native path remains outside the verified matrix.',
+        docsUrl: 'https://github.com/react-native-oh-library',
+    },
+    'react-native-screens': {
+        status: 'manual',
+        supportTier: 'experimental',
+        note: 'Navigation stacks frequently depend on react-native-screens. Keep it on the experimental lane until the Harmony adapter path has repeatable sample and device coverage.',
+        docsUrl: 'https://github.com/react-native-oh-library',
+    },
+    'react-native-webview': {
+        status: 'manual',
+        supportTier: 'experimental',
+        note: 'WebView is a common app-shell blocker. Treat it as an experimental intake dependency until the Harmony runtime path is validated on device.',
+        docsUrl: 'https://github.com/react-native-oh-library',
+    },
     ...UI_STACK_COMPATIBILITY_RECORDS,
     'react-native-gesture-handler': {
         status: 'manual',

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[], "react-native-gesture-handler"];
-export declare const PUBLIC_CURRENT_VERSION = "1.7.3";
+export declare const PUBLIC_CURRENT_VERSION = "1.8.1";

package/build/docs/render.js

@@ -45,7 +45,7 @@ function renderReadmeCurrentStatus(locale) {
         `| ${previewLabel} | ${joinInlineCode(publicDocs_1.PREVIEW_CAPABILITY_DEFINITIONS.map((definition) => definition.packageName), listJoiner)} |`,
         `| ${experimentalLabel} | ${joinInlineCode(publicDocs_1.EXPERIMENTAL_CAPABILITY_NAMES, listJoiner)} |`,
         `| ${releaseTracksLabel} | ${releaseTracksValue} |`,
-        `| ${telemetryLabel} | \`runtimeMode\` + \`evidence(...)\` + \`evidenceSource(...)\` |`,
+        `| ${telemetryLabel} | \`runtimeMode\` + \`evidence(...)\` + \`evidenceSource(...)\` + \`coverageProfile\` + \`nextActions\` |`,
         `| ${buildPathLabel} | \`doctor -> init -> bundle -> build-hap\` |`,
         `| ${primarySampleLabel} | \`${publicDocs_1.PRIMARY_SAMPLE_PATH}\` |`,
         `| ${previewSampleLabel} | \`${publicDocs_1.PREVIEW_SAMPLE_PATH}\` |`,
@@ -70,6 +70,7 @@ function renderReadmeSupportMatrixSection(locale) {
             '- `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` 表示当前只有人工设备验收记录，不代表机器自动验证',
         ]
@@ -77,6 +78,7 @@ function renderReadmeSupportMatrixSection(locale) {
             '- `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',
         ];

package/build/plugin.js

@@ -16,9 +16,13 @@ const project_2 = require("./core/project");
 const withExpoHarmony = (config, props = {}) => {
     validatePluginProps(props);
     const identifiers = (0, project_1.deriveHarmonyIdentifiers)(config, undefined, props);
+    const existingExpoHarmonyConfig = config.extra && typeof config.extra.expoHarmony === 'object' && config.extra.expoHarmony
+        ? config.extra.expoHarmony
+        : {};
     config.extra = {
         ...(config.extra ?? {}),
         expoHarmony: {
+            ...existingExpoHarmonyConfig,
             bundleName: identifiers.bundleName,
             entryModuleName: identifiers.entryModuleName,
             templateVersion: props.templateVersion ?? constants_1.TEMPLATE_VERSION,

package/build/types.d.ts

@@ -5,7 +5,19 @@ export type DoctorTargetTier = Exclude<SupportTier, 'unsupported'>;
 export type CapabilityRuntimeMode = 'shim' | 'adapter' | 'verified';
 export type CapabilityEvidenceSource = 'automated' | 'manual-doc' | 'none';
 export type DependencyBuildabilityRisk = 'known' | 'js-only-unknown' | 'native-risk' | 'unresolved';
+export type CoverageProfile = 'managed-core' | 'managed-native-heavy' | 'bare' | 'third-party-native-heavy';
+export type GapCategory = 'matrix-drift' | 'official-module-gap' | 'third-party-native-gap' | 'bare-workflow-gap';
 export type DependencySource = 'dependency' | 'devDependency' | 'peerDependency' | 'expo-plugin';
+export interface ExpoHarmonyDoctorConfig {
+    excludeDependencies?: string[];
+    excludePlugins?: string[];
+    coverageProfile?: CoverageProfile;
+}
+export interface ExpoHarmonyResolvedDoctorConfig {
+    excludeDependencies: string[];
+    excludePlugins: string[];
+    coverageProfile: CoverageProfile | null;
+}
 export interface ExpoHarmonyPluginProps {
     bundleName?: string;
     entryModuleName?: string;
@@ -69,6 +81,7 @@ export interface DetectedDependency {
     status: CompatibilityStatus;
     supportTier: SupportTier;
     buildabilityRisk: DependencyBuildabilityRisk;
+    gapCategory: GapCategory;
     blocking: boolean;
     note: string;
     replacement?: string;
@@ -148,6 +161,7 @@ export interface DoctorReport {
     rnohCliVersion: string;
     expoSdkVersion: number | null;
     targetTier: DoctorTargetTier;
+    coverageProfile: CoverageProfile;
     expoConfig: {
         name: string | null;
         slug: string | null;
@@ -162,6 +176,7 @@ export interface DoctorReport {
     supportSummary: SupportTierSummary;
     capabilities: ProjectCapabilityReport[];
     blockingIssues: BlockingIssue[];
+    nextActions: string[];
     advisories: string[];
     warnings: string[];
 }
@@ -230,8 +245,11 @@ export interface ToolkitConfig {
     rnohCliVersion: string;
     bundleName: string;
     entryModuleName: string;
+    coverageProfile: CoverageProfile;
+    doctorConfig: ExpoHarmonyResolvedDoctorConfig;
     capabilities: ManagedCapabilityRecord[];
     requestedHarmonyPermissions: string[];
+    nextActions: string[];
     project: {
         name: string;
         slug: string;

package/docs/cli-build.md

@@ -1,6 +1,6 @@
 # CLI 构建指南
 
-`v1.7.3` 延续 `verified + preview + experimental` 支持分层，并把四项 preview capability 的现有 `🟠` 缺口收口到明确 `🟡` 子集，其中 `expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
+`v1.8.0` 延续 `verified + preview + experimental` 支持分层，并把四项 preview capability 的现有 `🟠` 缺口收口到明确 `🟡` 子集，其中 `expo55-rnoh082-ui-stack` 仍是唯一 verified 矩阵。
 
 CLI 命令集合不变：
 

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

@@ -2,7 +2,12 @@
 
 路径：`examples/official-native-capabilities-sample`
 
-这个 sample 是 `v1.7.3` 的官方 preview native-capability walkthrough。它的目标不是把 preview 能力包装成 `verified`，而是把四项能力当前真实可承诺的 `🟡` 子集集中演示出来，并把 preview 边界收敛到真机 / release 证据，而不是接口缺口。
+这个 sample 是 `v1.8.0` 的官方 preview native-capability walkthrough。它的目标不是把 preview 能力包装成 `verified`，而是把四项能力当前真实可承诺的 `🟡` 子集集中演示出来，并把 preview 边界收敛到真机 / release 证据，而不是接口缺口。
+
+从 `v1.8.x` 开始，这个 sample 的角色会固定成两层：
+
+- combined smoke：负责四项 preview capability 的总回归
+- per-capability acceptance：每条 route 继续单独维护 device / release 记录，不再让 combined smoke 代替单项证据
 
 标记说明：
 
@@ -22,6 +27,10 @@
 - `/location`
 - `/camera`
 
+对应的逐 capability 追踪板见：
+
+- [v1.8.x capability board](../acceptance/v1.8.x-capability-board.md)
+
 ## 每条 route 的真实范围
 
 ### `/file-system`

package/docs/roadmap.md

@@ -2,18 +2,19 @@
 
 ## 收官定义
 
-这个项目的“完美落幕”不再定义为“一次性完美支持任意 Expo 项目”。
+这个项目的终局重新定义为：
 
-新的收官定义是：
+- 所有 Expo project types 与 package categories，最终都进入同一条 `mainline capability catalog`
+- `v2.0.0` 本身就要接近最完美、最最终的交付形态，而不是“还差最后一段 extension”
+- 公开承诺仍然按 evidence gate 逐步放开，而不是因为目标扩大就提前放宽 `latest`
+- `latest` 继续只承接完整验收的 `verified`
+- `next` 继续承接 fast track，用来加速收敛，但不伪装成 `verified`
 
-- 在 `Managed/CNG Expo` 主线下，主流官方 Expo 能力可稳定分析、可 bundle、可 debug/release 验证、可交付
-- `latest` 只承诺已经完成完整验收的 `verified` 能力
-- 长尾第三方 native module 不再挤进同一条公开承诺，而是进入 `extension model`
+这意味着：
 
-因此，路线会分成两段：
-
-- `Core Expo Coverage`：主线收官点
-- `Long-tail Extension`：收官后的持续扩展模型
+- `Managed/CNG` 仍是当前最成熟的已验证输入
+- bare workflow、高频第三方 native packages、长尾第三方依赖，不再被定义成“收官后才考虑的另一条扩展路线”
+- 它们会被逐步拉回同一条公开主线，只是进入主线的时间点和 evidence gate 不同
 
 ## 已完成里程碑
 
@@ -59,77 +60,171 @@
 - `expo-location`、`expo-camera` 进入 `preview`
 - Batch A+B preview capability 进入统一 sample / fixture / 文档 / 验收模型
 - 形成 `doctor -> sync-template -> bundle -> build-hap --mode debug` 的 preview onboarding baseline
-- 公开结论保持保守：可接入，不等于已 verified
+- `doctor` 增加 `buildabilityRisk`
+- 文档生成链收口到 marker block + renderer source data
 
 ## 当前主线
 
-### v1.8 Capability Graduation + Fast Track Release
+### v1.8.0 Intake Hardening + Parallel Promotion
 
 目标日期：`2026-05-15`
 
-目标：优先把“已经接入的 preview 能力”推进到可晋升状态，而不是只继续堆新模块数量。
+目标：先把“任何 Expo 项目都能被正确分类并拿到下一步”做硬，再把现有 preview 能力和主线阻塞项并行推进。
+
+- `doctor` 增加：
+  - `coverageProfile`
+  - `gapCategory`
+  - `nextActions`
+- 先把任意项目分进四类：
+  - `managed-core`
+  - `managed-native-heavy`
+  - `bare`
+  - `third-party-native-heavy`
+- 四项 preview capability 进入同一个 graduation board：
+  - `expo-file-system`
+  - `expo-image-picker`
+  - `expo-location`
+  - `expo-camera`
+- `react-native-gesture-handler` 从“矩阵外模糊探索”拉回主线：
+  - 必须可被 `doctor` 明确识别
+  - 必须有独立 fixture
+  - 必须有独立 sample / build / test coverage
+  - 来不及 verified 也不能继续停留在灰区
+- sample 策略升级成双层：
+  - combined smoke
+  - per-capability acceptance
+
+### v1.8.x Capability Board Closeout
+
+目标日期：`2026-06-15`
+
+目标：把 v1.8.0 建好的 intake + promotion 架子收口到可持续执行的证据节奏。
+
+- 每个 preview capability 必须单独维护：
+  - bundle evidence
+  - debug build evidence
+  - device acceptance record
+  - release acceptance record
+- combined sample 只负责回归烟测，不再替代单 capability 证据
+- `toolkit-config.json`、`doctor-report.json`、roadmap、support matrix、acceptance board 保持同源同步
+- `latest` 仍不承接任何证据未闭环的 capability
+
+### v1.9.0 Bare Workflow Baseline + App Foundation Modules
+
+目标日期：`2026-08-31`
+
+目标：先把 bare workflow 拉进主线，并补齐最容易卡死真实项目的官方基础模块。
+
+- bare workflow 正式进入主线里程碑
+- 优先补齐：
+  - `expo-secure-store`
+  - `expo-asset`
+  - `expo-device`
+  - `expo-clipboard`
+  - `expo-haptics`
+- 高频第三方 native dependencies 开始进入同一 capability catalog
+- 对每个新能力继续坚持：
+  - fixture
+  - sample route
+  - doctor
+  - sync-template
+  - bundle
+  - debug build
+  - acceptance 记录
+
+### v1.9.1 Third-party Native Wave A
+
+目标日期：`2026-09-30`
+
+目标：优先清掉最容易挡住“任何 Expo 项目”的高频第三方 native blocker。
+
+- 第一批高频第三方 native blocker 进入正式 onboarding：
+  - `react-native-gesture-handler`
+  - `react-native-safe-area-context`
+  - `react-native-screens`
+  - `@react-native-async-storage/async-storage`
+- 建立第三方 native capability onboarding checklist：
+  - catalog entry
+  - shim / adapter strategy
+  - doctor diagnostics
+  - sample / fixture
+  - debug + release evidence
+- 任何进入 Wave A 的 blocker，都不允许继续停留在“矩阵外模糊探索”
+
+### v1.9.2 Third-party Native Wave B + Regression Farm
+
+目标日期：`2026-10-31`
 
-- 建立 capability graduation 流水线：
-  `doctor --strict`、`doctor --target-tier preview`、`sync-template`、`bundle`、`build-hap --mode debug`、device acceptance、release acceptance
-- `DoctorReport`、`toolkit-config.json`、support matrix 全部引入 `runtimeMode` 与 `evidence`
-- `expo-file-system`、`expo-image-picker` 优先冲刺 verified 所需的真 runtime 与 device 证据
-- `expo-location`、`expo-camera` 从 throw-only shim 推进到可验证的 adapter-backed preview
-- 发布节奏改成双轨：
-  `latest` 只承接完整验收的 verified 能力，`next` 承接 preview fast track
+目标：扩大第三方 native 覆盖，并建立“任何 Expo 项目”目标需要的持续回归面。
 
-### v1.9 App Foundation Modules
+- 第二批高频第三方 native 依赖进入主线
+- 引入 project-shape regression farm：
+  - managed core
+  - managed native heavy
+  - bare
+  - third-party native heavy
+- 至少维护一组“未知项目导入 -> doctor 分类 -> nextActions -> sample/build gate”的持续回归案例
+- 继续收口 preview capability 的 release evidence，尽量减少 `v2.0.0` 前的残留灰区
 
-目标日期：`2026-07-31`
+### v1.10.0 Any-project Intake Freeze
 
-目标：优先补齐最能解锁真实 Managed/CNG Expo 项目的基础官方模块。
+目标日期：`2026-11-15`
 
-- 依序接入：`expo-secure-store`、`expo-device`、`expo-asset`、`expo-clipboard`、`expo-haptics`
-- 每个能力都必须同时具备：
-  fixture、sample route、doctor、sync-template、bundle、debug build、acceptance 记录
-- 完成 `expo-location`、`expo-camera` verified 晋升
-- 如果某项能力无法在同版晋升，则必须明确记录阻塞点与缺失证据，而不是模糊停留
+目标：先冻结“任何 Expo 项目”入口面的产品故事，确保不存在无法分类、无法给下一步、无法明确阻断原因的项目。
 
-### v2.0 Managed/CNG Core Expo Coverage
+- `doctor` 对任意 Expo 项目必须满足：
+  - 能分类
+  - 能指出 blocker 属于官方模块、bare workflow、还是第三方 native gap
+  - 能输出有顺序的 remediation actions
+- roadmap / support matrix / acceptance board 与实际 catalog 保持零漂移
+- 对外叙事从“更多项目开始进入主线”升级成“任何项目都有明确处理路径”
 
-目标日期：`2026-10-31`
+### v1.11.0 Final Blocker Burn-down
 
-定义：在单一 `verified` runtime matrix 下，把主流 `Managed/CNG Expo` 生产项目推进到完整可用、可构建、可交付。
+目标日期：`2026-11-30`
 
-- 官方高频 Expo 能力覆盖达到可交付水平
-- `latest` 只包含完整验收能力
-- release readiness 路径完整闭环
-- roadmap 对外叙事从“sample 可跑”升级为“核心 Managed/CNG Expo 项目可稳定交付”
+目标：把还会阻止“任何 Expo 项目可靠打包”的剩余高频 blocker 清到只剩极少数明确已知例外。
 
-这是最早可以对外宣告“主目标收官”的时间点。
+- 逐项清掉剩余高频 blocker：
+  - adapter 不稳定
+  - bare workflow release gap
+  - 高频第三方 native 缺失 release evidence
+  - 自动生成 sidecar 与真实项目 drift
+- 对仍无法在 `v2.0.0` 前关闭的项，必须提前明确降级策略与替代路径
+- `v2.0.0` 不接受“先宣布完成，再慢慢补长尾”
 
-### v2.x Long-tail Native Module Extension
+### v2.0.0 Any Expo Project Reliable Packaging
 
-目标日期：`2027-03-31` 前启动
+目标日期：`2026-12-31`
 
-目标：把“任何 Expo 项目都能打包成鸿蒙 APP”从内建承诺，转成有边界、可扩展、可持续维护的 extension model。
+定义：任何 Expo 项目，只要依赖已经存在于主线 capability catalog 内，就能可靠打包成鸿蒙 App；`v2.0.0` 本身就是基本接近最完美、最最终的形态。
 
-- 引入第三方 native module extension / onboarding 模型
-- 建立 capability registry、adapter、fixture、acceptance 规范
-- 把未知或未验证第三方包从“公开承诺”切换为“显式扩展”
-- 不对未验证长尾模块提前给出正式可用声明
+- 不再只覆盖“主流项目”，而是把“任何 Expo 项目都能可靠打包成鸿蒙 App”作为正式版本定义
+- `Managed/CNG` 与 bare workflow 都必须进入稳定交付路径
+- 高频官方 Expo 模块与高频第三方 native blockers 必须已经进入同一公开 capability catalog
+- `doctor -> sync-template -> bundle -> build-hap --mode debug|release` 必须对主线 catalog 内项目形成稳定闭环
+- 只允许极少数、明确列名、已有替代策略的已知例外存在；不允许存在大类空白地带
 
 ## 长期方向
 
-- 先做到 `Managed/CNG Core Expo Coverage`
-- 再通过 `Long-tail Native Module Extension` 逼近“任意 Expo 项目”
-- 推进速度依赖 `next` 快速收敛反馈，但公开承诺继续由 `latest` 控制
+- 所有输入最终都进入同一个 `mainline capability catalog`
+- `v2.0.0` 就是“任何 Expo 项目可靠打包成鸿蒙 App”的正式目标版本
+- `latest` 只由完整验收能力驱动
+- `next` 用来加速收敛主线 backlog，而不是制造伪 verified 叙事
+- roadmap 的关键问题不再是“要不要把某类项目算进主线”，而是“它何时进入主线、当前缺哪格 evidence、下一步怎么 unblock”
 
 ## 路线约束
 
-- `v2.0` 前继续坚持单一 verified runtime matrix
-- `v2.0` 前不把 bare Expo 拉进主线，只保留 `Managed/CNG`
+- 当前公开 `verified` runtime matrix 仍然只有 `expo55-rnoh082-ui-stack`
 - `doctor --strict` 继续只代表 `verified`
-- `latest` 只承诺完整验收的 `verified` 能力
+- `latest` 只承诺完整验收的 `verified`
 - `next` 可以承接 preview fast track，但不得伪装成 verified
+- 没有 fixture、sample、文档、构建证据、人工验收记录的能力，不得晋升到 `verified`
 - roadmap、support matrix、README、acceptance 记录必须在同一 PR 同步更新
-- 没有 sample、fixture、文档、构建证据、人工验收记录的能力，不得晋升到 `verified`
+- 目标扩大不等于当前对外承诺扩大；任何公开边界放宽都必须先有证据闭环
 
 ## 风险与顺延条件
 
-- 收官前提是从 `2026-03-31` 起持续具备 Harmony 模拟器或真机验证条件，并保持周级别验收节奏
-- 如果 Expo SDK / RNOH 在 `2026-05-15` 前发生大矩阵漂移，`v2.0` 收官点应顺延到 `2026-12-31` 左右
+- 继续依赖 Harmony 模拟器或真机的稳定验证条件
+- 继续依赖周级别的 acceptance 节奏，而不是只做 sample 展示
+- 如果 Expo SDK / RNOH 在 `2026-05-15` 前发生较大矩阵漂移，`v1.8.x` 收口和 `v2.0.0` 时间点都需要相应顺延

package/docs/support-matrix.md

@@ -1,11 +1,19 @@
-# v1.7 支持矩阵
+# v1.8 支持矩阵
 
-`v1.7` 继续采用 tiered support model，但从现在开始把“层级”与“晋升距离”拆开表达：
+`v1.8` 继续采用 tiered support model，但从现在开始把“层级”与“晋升距离”拆开表达：
 
 - `supportTier` 表示公开承诺层级
 - `runtimeMode` 表示当前运行时接入形态：`shim`、`adapter`、`verified`
 - `evidence` 表示距离 verified 还缺哪些证据格
 - `evidenceSource` 表示每个证据格来自自动化、人工记录，还是当前无证据
+- `coverageProfile` 表示当前项目属于哪条主线输入形态
+- `nextActions` 表示 toolkit 为当前项目生成的有序下一步
+
+同时，`v1.8.x` 的 roadmap 已经改成单一 `mainline capability catalog` 方向：
+
+- bare workflow 与第三方 native package 不再被描述成“收官后才考虑的另一条 extension 终局”
+- `v2.0.0` 本身被定义成“任何 Expo 项目都能可靠打包成鸿蒙 App”的目标版本
+- 但当前公开承诺依旧没有放宽；它们只是进入同一主线 backlog，而不是已经进入 `verified`
 
 `doctor --strict` 继续只代表 `verified`。
 
@@ -84,7 +92,7 @@
 - `runtimeMode=verified`：说明能力已进入正式承诺，且证据闭环完成
 <!-- GENERATED:support-matrix-capability-telemetry:end -->
 
-为了避免把“只差真机”与“当前子 API 还没实现到位”混在一起，`v1.7.x` 文档额外使用以下标记：
+为了避免把“只差真机”与“当前子 API 还没实现到位”混在一起，`v1.8.x` 文档额外使用以下标记：
 
 - `🟡 可用待晋升`：当前子集已经有可信实现，样例和模拟器路径可用；下一步主要缺真机 / release 证据
 - `⛔ 完全不支持`：能力仍在 catalog 外，或根本不在当前公开承诺范围
@@ -105,6 +113,7 @@
 - 当前四项 preview capability 都已经完成 preview baseline 的 bundle / debug build / route walkthrough
 - 四项 preview capability 都已经进入 `adapter` 路径；`device=yes[manual-doc]` 只表示已有人工设备验收记录，仍不代表 verified 或 release-ready
 - 当前 preview baseline 的默认 evidenceSource 固定为：`bundle/debugBuild=automated`、`device=manual-doc`、`release=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)
 - `expo-file-system`
   - `🟡` 当前主路径是 UTF-8/base64 sandbox I/O、append/partial read、`getInfoAsync({ md5: true })` 与 `downloadAsync`
 - `expo-image-picker`
@@ -169,12 +178,18 @@ expo-harmony doctor --project-root /path/to/app --target-tier preview
 - `capabilities[].evidenceSource.debugBuild`
 - `capabilities[].evidenceSource.device`
 - `capabilities[].evidenceSource.release`
+- `coverageProfile`
+- `dependencies[].gapCategory`
+- `nextActions[]`
 
 判读方式：
 
 - 任一 `evidence.* = false`，表示晋升到 verified 前仍缺证据
 - `evidenceSource.device = manual-doc`，表示该证据来自人工验收记录，不应被表述成自动化设备验证
 - `runtimeMode !== verified`，表示即使已有部分证据，也仍不属于正式承诺
+- `coverageProfile=bare`，表示当前项目已落入 bare workflow 主线规划，但不等于当前 matrix 已正式支持 bare
+- `gapCategory=third-party-native-gap`，表示问题不应再被模糊描述成普通 matrix drift，而是主线 blocker
+- `nextActions[]` 的顺序即 toolkit 当前建议的处理顺序
 
 当前公开阻断 issue code 继续包括：
 
@@ -208,6 +223,7 @@ toolkit 受管的核心产物仍包括：
 - `entry/src/main/module.json5` 的 `requestPermissions` 由 toolkit 根据已启用能力自动补齐
 - preview / experimental 能力的 Metro import path 通过 `.expo-harmony/shims/<package>` 接管
 - `toolkit-config.json` 会记录 capability 的 `runtimeMode`、`evidence` 与 `evidenceSource`
+- `toolkit-config.json` 也会记录当前项目的 `coverageProfile` 与有序 `nextActions`
 - verified UI stack 依赖继续走现有 autolinking + `.har` 管理逻辑
 
 ## Release Tracks
@@ -236,8 +252,13 @@ toolkit 受管的核心产物仍包括：
 - release signing / release HAP 验收完成
 - 文档、矩阵、roadmap、acceptance 记录同 PR 更新
 
-## 当前不在短期输入范围
+## 当前仍未进入正式公开承诺
 
 - bare Expo
 - 多 Expo / RNOH 并行 verified 矩阵
 - 任意第三方 native package 的即时正式承诺
+
+说明：
+
+- 上述项目并没有从 roadmap 消失；它们会逐步进入同一条主线 capability catalog
+- 这份 support matrix 只记录当前已经公开验证到哪一步，而不是未来愿景本身

package/package.json

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