Skip to content

docs+ci: sync trust surfaces with the actually-gated RN range and engine reality#69

Open
danfry1 wants to merge 1 commit into
mainfrom
fix/trust-surface-drift
Open

docs+ci: sync trust surfaces with the actually-gated RN range and engine reality#69
danfry1 wants to merge 1 commit into
mainfrom
fix/trust-surface-drift

Conversation

@danfry1

@danfry1 danfry1 commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Problem

Three drift classes on the project's trust surfaces:

  1. The published fidelity page understated CI coverage. The lockfile has shipped React Native 0.86 since fix(compat): mock react-native 0.86 top-level exports #38, so the full gate runs it on every push — but native-rn-matrix.yml (which fidelity-report.mjs derives the published range from, by design) still stopped at 0.85. The fidelity page, both READMEs, and five website pages all claimed 0.81–0.85.
  2. The fidelity page never said which RN version produced the committed probe numbers. The crosscheck report captures reactNativeVersion; the page template dropped it.
  3. Website pages taught code that throws under the default engine. The quick start's "Control device state" example used setPlatform('android'), which throws under engine: 'native' (the platform is fixed when the real module graph loads). Three more pages carried the same unqualified claim, setInsets() was undocumented on the website, and the mocks option page lacked its mock-engine-only caveat (the plugin throws a configuration error when it's set under native).

Change

  • Add the RN 0.86 row to the matrix, with a header note documenting the matrix→fidelity-page coupling so the newest row stays in sync with the lockfile.
  • Render the generating RN version into the fidelity summary; regenerate the page and badge (fidelity:check passes).
  • Update the supported-range claim to 0.81–0.86 across both READMEs and the website.
  • Quick start now demonstrates setDimensions/setColorScheme (engine-agnostic) and explains the config/projects route for platform testing; helpers.md gets an engine-caveat warning on setPlatform and documents setInsets; plugin-options.md corrects the platform guidance and adds the mocks engine caveat; the feature list on the guide index reflects which helpers work under both engines.

All behavioral claims verified against the code (native/setup.mjs control surface, plugin.ts mocks rejection, helpers.ts setInsets).

…ine reality

- native-rn-matrix.yml: add the RN 0.86 row. The lockfile has shipped RN 0.86
  since #38, so the full gate already ran it on every push, but the matrix —
  which the published fidelity page derives its claim from — still stopped at
  0.85, publishing an understated range. Add a header note documenting that
  coupling.
- fidelity-report.mjs: render which React Native version generated the
  committed probe numbers (report.reactNativeVersion was captured but dropped).
- Update the 0.81–0.85 range to 0.81–0.86 across both READMEs and the website.
- Fix website pages that taught setPlatform() unqualified: under the default
  native engine it throws (platform is fixed at module-graph load). Quick start
  now demonstrates setDimensions/setColorScheme (engine-agnostic), helpers.md
  carries the engine caveat and documents the previously-undocumented
  setInsets(), plugin-options.md documents the per-project alternative and adds
  the missing mock-engine-only caveat on the mocks option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant