[PR #4411] docs(android): correct public fixture metadata path #6222

New issue

Open

opened 2026-10-31 01:12:49 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:12:49 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4411
Author: @dajiaohuang
Created: 10/16/2026
Status: 🔄 Open

Base: main ← Head: docs/android-fixture-metadata-path-20261016

📝 Commits (2)

7d399b1 docs(android): correct public fixture metadata path
9dfebca Merge branch 'main' into docs/android-fixture-metadata-path-20261016

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 third_party/README.md (+1 -1)

📄 Description

Summary

Correct the public APK fixture metadata path in third_party/README.md.

Problem and expected behavior

The instructions point readers to scripts/fixtures/android-apidemos.json, which does not exist. The tracked provenance record and fixture fetcher use scripts/fixtures/android/apidemos.json. No companion issue: this is a directly verifiable documentation error.

Change and scope

Change only that path. This is within the existing static Android fixture workflow; a separate maintainer capability/scope decision is not applicable.

Contract and boundary impact

Semantic owner: third-party fixture instructions.
CLI/MCP, provider, evidence, packaging and installation behavior: unchanged.
Documentation or usability only; no target interaction.

Evidence and regression coverage

Source inspection confirms the corrected JSON exists, contains the ApiDemos 6.0.18 provenance, and the former path is absent. No APK/JAR or generated file is included.

Validation performed

Current base 2c7583599b9ac1c847bd77b1940930fd8d4594c7: git diff --check, pre-commit formatting and pre-push npm run check:fast passed (typecheck/lint: 2 successful tasks), using Node 24.18.0.
npm run docs:check attempted on this revision, but blocked before tasks by the clean Windows checkout's missing native/windows/build/manifest.json and native addon. It is not a current-head pass.
Earlier validation on unchanged affected documentation at base 4135c911d3a3414b17fcd8954a15f6c7ec6ae8f4: npm run docs:check passed (6 tasks; README consistency 5/5). This is prior evidence, not a rerun on this head.

Compatibility, safety, and release

No runtime change, breaking change, migration or release metadata change. No engine or APK execution was needed for this correction. Full npm run check and current-head docs validation remain outstanding; CI has not been claimed as passed.

Author readiness

Human owner: @dajiaohuang (PR author by default). AI-assisted draft submitted for the author's review; no human review or readiness declaration is asserted.

I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
I declare this PR ready for initial maintainer review.

Before merge

Human review/readiness and applicable current-head checks are complete.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/4411 **Author:** [@dajiaohuang](https://github.com/dajiaohuang) **Created:** 10/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/android-fixture-metadata-path-20261016` --- ### 📝 Commits (2) - [`7d399b1`](https://github.com/morluto/rea/commit/7d399b189cc754949438aa2edf1d8329c1c9a319) docs(android): correct public fixture metadata path - [`9dfebca`](https://github.com/morluto/rea/commit/9dfebcae66601e5edf87d6045a138b51c93ecb12) Merge branch 'main' into docs/android-fixture-metadata-path-20261016 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `third_party/README.md` (+1 -1) </details> ### 📄 Description ## Summary Correct the public APK fixture metadata path in `third_party/README.md`. ## Problem and expected behavior The instructions point readers to `scripts/fixtures/android-apidemos.json`, which does not exist. The tracked provenance record and fixture fetcher use `scripts/fixtures/android/apidemos.json`. No companion issue: this is a directly verifiable documentation error. ## Change and scope Change only that path. This is within the existing static Android fixture workflow; a separate maintainer capability/scope decision is not applicable. ## Contract and boundary impact - Semantic owner: third-party fixture instructions. - CLI/MCP, provider, evidence, packaging and installation behavior: unchanged. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage Source inspection confirms the corrected JSON exists, contains the ApiDemos 6.0.18 provenance, and the former path is absent. No APK/JAR or generated file is included. ## Validation performed - Current base `2c7583599b9ac1c847bd77b1940930fd8d4594c7`: `git diff --check`, pre-commit formatting and pre-push `npm run check:fast` passed (typecheck/lint: 2 successful tasks), using Node 24.18.0. - `npm run docs:check` attempted on this revision, but blocked before tasks by the clean Windows checkout's missing `native/windows/build/manifest.json` and native addon. It is **not** a current-head pass. - Earlier validation on unchanged affected documentation at base `4135c911d3a3414b17fcd8954a15f6c7ec6ae8f4`: `npm run docs:check` passed (6 tasks; README consistency 5/5). This is prior evidence, not a rerun on this head. ## Compatibility, safety, and release No runtime change, breaking change, migration or release metadata change. No engine or APK execution was needed for this correction. Full `npm run check` and current-head docs validation remain outstanding; CI has not been claimed as passed. ## Author readiness Human owner: @dajiaohuang (PR author by default). AI-assisted draft submitted for the author's review; no human review or readiness declaration is asserted. - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] Human review/readiness and applicable current-head checks are complete. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-31 01:12:49 +00:00

bsakaguchi referenced this issue

2026-11-01 21:46:11 +00:00

[PR #6222] [CLOSED] fix(discovery): classify host-gated Linux-only tools as unsupported_host #7211