Keep realtime progress synchronized while BookWave is foregrounded #5
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/recreate-pr-171"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recreated from GitHub PR #171 during the Forgejo migration. This PR is the Forgejo counterpart of that GitHub PR.
Original GitHub PR: https://github.com/AlexanderWilhelmsenBerg/Audiobookshelf-Manager-Claude/pull/171
Original implementation branch:
feat/133-foreground-realtime-sync-cleanForgejo issue: #40 — Keep realtime progress synchronized while BookWave is foregrounded (migrated from GitHub issue #133)
Scope
Moves realtime progress ownership to the application foreground lifecycle so websocket-driven progress stays synchronized while BookWave is foregrounded, without coupling synchronization to the Home UI.
The implementation preserves the existing reconciliation and conflict boundaries:
SyncAccountUseCasereconciliation;LibraryRepository.writeProgressas the conflict/persistence boundary;Validation / handoff
This Forgejo PR points at the same implementation head as the migrated GitHub work:
d5e6e5c2be02f54029682ddd40537a3c16190ce8.The original implementation work included focused JVM coverage and documented manual device checks. At the last GitHub handoff, wrapper validation, secret scan, Room schema checks, dependency/licence reporting and ktlint were green while the full
verifyDebug/ classpath gate was still completing.No merge requested. Review and merge manually after Forgejo CI has validated the recreated PR.
d5e6e5c2be8da001c05a