Skip to content

Give Devonian's GitHub issues sync a persisted background sync mechanism #10

Closed

Description

@michielbdejong

Background

Follow-up from #3 (removal of the Rust-sandbox-hosted integrations/github-issues pilot in favor of the browser-only Devonian integration). Per that issue's "flip now, fix gaps after" decision, this gap was explicitly scoped out as follow-up work rather than a blocker.

Problem

The removed Rust pilot's one real advantage was server-side polling every minute even with the browser closed (a persisted polling grant executed inside AtomicServer's QuickJS/WASM sandbox). Devonian's browser-only replacement only syncs while its browser tab is open — closing the tab stops sync entirely.

Scope

Design a background sync mechanism for Devonian's GitHub issues integration that doesn't require the browser tab to stay open, without reintroducing a Rust-sandbox-hosted execution path (per #3's "remove outright, no fallback" decision). Options to evaluate include a Service Worker-based background sync, a separate lightweight polling host, or another browser-native mechanism.

Related files: integrations/github-issues/devonian/bridge.mjs, ports.mjs, proxy.mjs.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions