Skip to content

Preserve capture recovery and complete individual recurring occurrences - #1

Open
legitimate-apps wants to merge 27 commits into
mainfrom
astra/capture-reliability-1002
Open

legitimate-apps wants to merge 27 commits into
mainfrom
astra/capture-reliability-1002

Conversation

@legitimate-apps

@legitimate-apps legitimate-apps commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

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:

  • Typed/MCP/race-protection integration: 316 iOS simulator tests, zero failures; Catalyst build succeeded. Real simulator termination/relaunch restores quick draft and offline editor text; retry produces POST 201 + PATCH 200 and exactly one complete SQLite note. Screenshots are linked below.
  • Latest voice primitives: 50 native XCTest cases passed on 62885ec; 8 SIGKILL/relaunch cases passed on a5265d7 before the final account-retirement change. Regression controls demonstrated failures before the fixes.
  • Real voice REST/SQLite acceptance: 1 passed; POST 201, idempotent POST 201, PATCH 200; one note with original key/locale and later review text; audio removed after acknowledgment. Disposable server and clients stopped.
  • Integrated iOS and Catalyst builds passed at a5265d7, including terminal cleanup and retained suspension. The subsequent account-retirement change has native coverage; a broader recheck remains.
  • Full server suite: 778 passed; Ruff and mypy clean. Actual MCP/REST/SQLite occurrence exercise leaves other dates and the series pending, records one completion on repeat, and rejects invalid keys without writes.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant