docs+ci: sync trust surfaces with the actually-gated RN range and engine reality#69
Open
danfry1 wants to merge 1 commit into
Open
docs+ci: sync trust surfaces with the actually-gated RN range and engine reality#69danfry1 wants to merge 1 commit into
danfry1 wants to merge 1 commit into
Conversation
…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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Three drift classes on the project's trust surfaces:
native-rn-matrix.yml(whichfidelity-report.mjsderives 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.reactNativeVersion; the page template dropped it.setPlatform('android'), which throws underengine: '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 themocksoption page lacked its mock-engine-only caveat (the plugin throws a configuration error when it's set under native).Change
0.86row to the matrix, with a header note documenting the matrix→fidelity-page coupling so the newest row stays in sync with the lockfile.fidelity:checkpasses).setDimensions/setColorScheme(engine-agnostic) and explains the config/projects route for platform testing;helpers.mdgets an engine-caveat warning onsetPlatformand documentssetInsets;plugin-options.mdcorrects theplatformguidance and adds themocksengine caveat; the feature list on the guide index reflects which helpers work under both engines.All behavioral claims verified against the code (
native/setup.mjscontrol surface,plugin.tsmocks rejection,helpers.tssetInsets).