Repository navigation
docs: derive onboarding source pins from the checker - #2424
Merged
Merged
Conversation
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.
The Settings owner guide’s onboarding entry still claims source pins read only
PermissionsOnboardingView.swift. Replace that hard-coded target claim with the current source-pin checker command before moving code. Keep the rest of the entry unchanged, and add no new target list or count.DOCS-2’s broader stale Most-pinned lists are already proposed in #2381; the App-specific ranking and hotspot maps are corrected in #2422. This PR fixes the remaining onboarding-inventory clause without duplicating those hunks. Broad pending #2336 remains untouched and unmerged.
Verified against the actual checker’s resolved target data. Independent full single-clause diff/source review against
origin/main: GREEN from the coordinator before commit. No runtime, policy or baseline changes.Validation on
4793ed619: all five mapped source/documentation checks passed with clean, stable source; preflight passed. The verifier inferred UI/speed checks from the guide’s path: UI failed at the deliberately blocked app build under reviewed invocation guards, and speed SKIPPED because Transcripted was running. Nothing was quit and no native app/model/account workflow ran. No runtime proof claimed. No merge requested.