Repository navigation
docs: place speaker saves in termination sequence (SUPPORT-14) - #2445
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 termination-sequence header places Speakers saving next to Writing admission, and the Support guide omits it. Document the actual sequence: meeting preparation, pending Speakers saves, then app-state shutdown. The implementation and app delegate bindings already use that order; no executable behavior or quit policy changes.
This extracts only SUPPORT-14's factual comments from broad pending #2336, which remains unchanged. Independent full two-file diff, complete sequence, and actual app-binding source review: GREEN before commit.
Validation at be91836: canonical
bash check.shcompleted 16 checks PASS (including concurrency typecheck); app build and unfiltered fast tests were explicitly BLOCKED with exit 3 by reviewed invocation guards, leaving deterministic proof FAIL. Stable, clean exact-head receipt archived before verification. Standalone preflight passed. The verifier inferred speed from the source path and SKIPPED it because Transcripted is already running; nothing was quit. No app, shutdown, audio, preferences, or native runtime behavior was exercised. The source-only change does not establish runtime proof.