Repository navigation
Correct source-pin and window-coverage guidance - #2381
Merged
Merged
Conversation
r3dbars
marked this pull request as ready for review
November 10, 2026 04:23
This was referenced Nov 10, 2026
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.
Live agent guides no longer carry stale lists of pinned UI files (SCRIPTS-DEV-10 / TESTS-FAST-7). They point to the source-pin checker and distinguish the source-scanning window-inventory check from the real-window sharing tests. No runtime or UI behavior changes.
The scan wording overlaps DOCS-1 in pending broad audit PR #2336; this PR also fixes the remaining stale pin lists. The old burn-down inventory remains historical under separate PR #2343. App-hotspot wording already owned by DOCS-11/#2336 is left there.
Validation: all five final mapped checks passed, including source pins, UI automation contracts, and documentation paths. Current extraction confirms that several former pin targets are gone. Independent full five-file diff and checker/test source review against origin/main: GREEN, no findings. verify-change.sh selected UI/speed solely from Markdown paths under Sources. The isolated app build passed; both native checks explicitly SKIP because Transcripted is already running. No native UI/speed proof is claimed. The existing app was left running.