Repository navigation
Description
Decision
Deprecate integrations/github-issues's server-side pilot (runs inside AtomicServer's QuickJS/WASM sandbox, Rust-hosted) in favor of integrations/github-issues/devonian (runs entirely in-browser, no Rust involvement). The Rust pilot is being removed outright, not just marked deprecated — no fallback kept.
This was scoped in conversation with @michiel; three sequencing calls were made explicitly:
- Flip now, fix gaps after. We are not blocking the flip on closing Devonian's current gaps (see below) — those become tracked follow-up work instead of prerequisites.
- Remove the Rust pilot outright, including its Rust sandbox tests, rather than leaving it in place as a fallback.
- Actions/approval plumbing gets a separate design pass, not a same-issue reimplementation. Don't build a replacement for the assistant/MCP action-approval host as part of this removal.
Note on repo boundaries
This repo's own README says it's a "Temporary repo for quick iteration" and that ontola/atomic-server's develop branch /integrations is normally the source of truth. Per instruction, the work for this issue happens here regardless. Concretely, that means:
- Everything listed below under "TS-specific — remove" and "shared — keep" lives in this repo (
integrations/github-issues/) and is in scope here. - The Rust sandbox test functions referenced by
package.json'satomicCertification.sandboxTests(plugins::sync_session_tests::*,plugins::actions::tests::*,plugins::triggers::tests::*,plugins::scheduler::tests::*) and theAppSetup/registry.tsbrowser wiring that adaptsgithub-issuesto the legacyinstall()do not exist in this checkout — they live inontola/atomic-server's Rust source andbrowser/tree. This issue tracks the removal of this repo's references to them (thepackage.jsoncertification block, the CLI/install-path files) but the actual Rust deletion and registry update happen separately inatomic-server— flagged as a dependency below, not done as part of this issue unless that changes.
What "the Rust pilot" actually is, and what must survive
Already mapped in integrations/github-issues/:
Shared — Devonian imports these directly, must be kept:
adapter.ts/adapter.test.ts— GitHub API projection and request builder (project,manifest,endpoint,request,preview,get). Devonian'sports.mjs/bridge.mjsreuse this.tracker-actions.ts— scoped issue/comment request construction, reused by Devonian's browser transport.
Rust-pilot-specific — remove from this repo:
atomic.ts(install(), schema/kanban/connection setup against the real drive, importsrequireInstallationServerfrombrowser/lib/src/plugin-installation.js)plugin.ts/plugin.js(the QuickJS/WASM sandbox entry point —manifest,run()— the code that actually executes inside the Rust host)cli.ts(install/preview/apply/resume CLI against the Rust-hosted sandbox)setup.ts(setupDeclaration, typed setup migration, adapted byatomic-server'sAppSetup/registry.ts)manifest.fixture.jsonatomic.live.test.ts,github.live.test.ts(opt-in live tests against the Rust-hosted flow)package.json'satomicCertification.sandboxTestslist (all 13 entries point at Rust test functions that live inatomic-server, not here)tsconfig.json'sincludelist currently has["adapter.ts", "atomic.ts", "cli.ts", "plugin.ts"]— drop the three pilot-only entriesREADME.mdsections describing CLI install, server-side setup, the typed-setup migration section, and the live-test instructions
Not touched — unrelated to GitHub despite living in this folder:
automation.test.ts— tests generic event-automation wiring (imports frombrowser/data-browser/src/chunks/PluginRuns/integrationAutomation, a file that lives inatomic-server), not GitHub-specific. Leave in place.
Dependency on ontola/atomic-server
Two things this issue cannot fully close without a corresponding change there, since they don't exist in this checkout:
- The Rust sandbox tests (
plugins::sync_session_tests::*,plugins::actions::tests::*,plugins::triggers::tests::*,plugins::scheduler::tests::*) — need to be read first to confirm which are GitHub-pilot-specific vs. shared harness also used by mt940/notion/clockify/moneybird (perintegrations/README.md, several other providers also run "exact named Rust tests through QuickJS/WASM" via the same certification command). Deleting shared harness code by mistake would break other providers' certification. AppSetup/registry.ts's dynamic destination lookup that currently adaptsgithub-issuestoinstall().
Explicitly out of scope for this issue (tracked separately)
Per the "flip now, fix gaps after" decision, these are follow-ups, not blockers:
- Pointing Devonian's sync at the user's real Atomic drive instead of the isolated local-only browser drive (OPFS/IndexedDB) it currently uses.
- Giving Devonian a persisted background sync mechanism (today it only syncs while the browser tab is open — the Rust pilot's one advantage was server-side polling every minute with the browser closed).
- Designing a replacement host for actions/approval (review-before-write, the uncertain-write journal, MCP action exposure via
integrations/ACTIONS.md) now that the Rust sandbox runtime is gone for GitHub.
Suggested sequence
- Remove the TS files listed above from
integrations/github-issues/in this repo, keepingadapter.ts,adapter.test.ts,tracker-actions.ts,devonian/, andautomation.test.ts. - Update
package.json(drop pilot capabilities/sandboxTests, rewrite the certification block for what Devonian actually provides),tsconfig.json,README.md. - Update
integrations/catalog.jsonif needed — currently there's no catalog entry for the Rust pilot itself (onlydevonian-github-issues), so likely no change needed there; confirm. - Update
integrations/evidence.json(regenerate or remove the stalegithub-issuesentry) and re-runnode integrations/tooling/certify.mjs. - Update
integrations/ACTIONS.md's stale example line ("GitHub providesget_issueandcreate_issue"). - Flag the
atomic-server-side dependency (Rust test classification +AppSetup/registry.ts) so it doesn't get lost, since it can't be done from this repo. - File the three follow-up issues (real-drive sync, background sync, actions/approval design pass) referencing this one.
Activity
[-]Make Devonian (browser TS) the canonical GitHub issues integration; remove the server-side Rust pilot[/-][+]Issue Tracker[/+]