Repository navigation
Preserve capture recovery and complete individual recurring occurrences - #1
Open
legitimate-apps wants to merge 27 commits into
Open
legitimate-apps wants to merge 27 commits into
legitimate-apps wants to merge 27 commits into
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.
Command could lose unsent editor/calendar text after termination, and stale asynchronous operations could cross sign-in boundaries or overwrite newer voice reviews. Persist typed capture recovery by account/server, retain uncertain-create keys across relaunch, bind transport to the original session, and fence stale voice operations. Same-account multiwindow activation preserves the existing editor store.
MCP and in-app assignment tools now accept an optional original occurrence date, matching calendar behavior. Shared core validates occurrence keys, preserves whole-series compatibility, and carries hidden assignment visibility into new completion facts.
The voice follow-on adds opt-in production primitives for protected stopped audio, atomic review/request checkpoints, current-manifest restoration, ownership fencing, original-create/note-ID/PATCH reconciliation, and terminal cleanup. A real subprocess is killed after the local server commits a note but before the flow receives its ID; relaunch replays the original request and PATCHes later edits onto the same SQLite note.
Voice app integration remains incomplete: RecordingSheet still uses its nonpersistent default. Shared microphone/account lifecycle wiring, retained sheet disappearance, actual unfinished M4A recovery, acknowledged assistant handoff, and app recovery UI are still required. Passing primitive tests does not establish end-to-end voice recovery.
Observed validation:
No merge, deployment or release. Physical microphone/AVAudioSession and rendered Mac/iPad multiwindow behavior are not claimed verified. Existing historical activity visibility is unchanged.
Run state and exact next step · Verification and screenshots · Voice ownership/retention design · Reproduction commands
Operator requested an immediate credit-limit stop. All sound work is committed and pushed;
helpers are stopped, the DerivedData lease is released, and no owned verification process is
running. The final state file records exact unfinished scope and the next implementation step.