Repository navigation
docs: explain retained meeting references and explicit associations - #247
Merged
Merged
Conversation
leemour
force-pushed
the
docs/projector-followups
branch
from
October 15, 2026 15:44
5ac6b22 to
bdbeb11
Compare
leemour
changed the title
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
1 participant
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.
Explains how retained meeting-cue references connect a passage to its meeting/revision, and how explicit participant/person and confirmed project associations differ from name matches and speaker attribution. Adds a cue-reference example in EN/RU/ES.
Clarifies the existing person-timeline boundary: confirming a found mention enables mentions: search but does not itself create a timeline entry (same source evidence as #245). Preserves the completed Drive 0.11.1 review from #246.
Reviewed all three shared-guide locales against reviewed Zoom 0.18 usage/skill and Core mention behavior. Existing URLs and headings remain; no term decision or CLI runtime change. Earlier validation passed strict docs/localization/contracts, 302 tests, seven browser smoke checks, and 12 mobile/desktop page checks; scoped checks run again after narrowing/rebase.