Repository navigation
issue-tracker: GitHub issues drive app as the host for the Devonian bridge - #113
Merged
Merged
Conversation
…relay errors Bridge: a port may throw ReviewRequired before any request; the pass records the write in bridge.held and carries on. A held write never sent anything, so the next pass plans it again from both sides. reviewGate() wraps the GitHub port and lets through only the exact (entity, id, value) a person approved. resolveConflict(subject, keep) moves only the conflicting fields' baseline to the other side. Conflict errors carry subject, entity and fields. proxyTransport's dispatch path keeps the host's error text, and drops the journal entry only when the dispatcher marks the error notSent. Refs #100 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An iframe drive app (app/, the pets/notion shape) that runs the Devonian GitHub issues Bridge for one repository per install: connect through the host's consent bar, type owner/name, import issues and comments into the app's own table, and sync on open and on "Sync now". - Transport: proxyTransport's dispatch over store.proxy.request; the frame never holds a connection code, the write journal still guards uncertain writes, and host refusals before sending are not uncertain. - Atomic side: AtomicPort unchanged, over frameStore.ts, which gives the frame's PluginStore the predicates target.mjs reads, corrects reads for the app's own saves (the host page's cache did not show them within 5 s in the e2e) and remembers subjects the OPFS-first query can miss. - State: Bridge snapshot and journal as JSON text on a sync resource in the app's subtree (no IndexedDB in a null-origin frame). - Review: every GitHub create/update is held until "Send N changes to GitHub" approves that exact content. Conflicts pause with "Keep GitHub's version" / "Keep this table's version". 401 and lost connections offer "Reconnect GitHub". - npm devonian@0.7.0 in app/package.json (not the plugin root, which certify.mjs would treat as a sandbox package); ci.yml installs integrations/*/app/pnpm-lock.yaml too. - The mock proxy's github-issues fixture seeds atomic-fixture/tracker. - e2e (new lane tier): connect, import, reload + unchanged refresh, a reviewed close of #1, and a title conflict settled for GitHub's side. No catalog entry: there is no catalog install flow for drive apps (#94). Refs #100 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #100 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
michielbdejong
force-pushed
the
claude/issue-100-github-bridge-host
branch
from
September 24, 2026 11:43
ccc6c14 to
6323c33
Compare
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.
Refs #100
Summary
The Devonian GitHub issues bridge gets a host again: an iframe drive app in
integrations/issue-tracker/app/, the same shape aspets/app/andnotion/app/. One app install syncs one repository.store.proxy.connectwith platformgithub-issues. You then type the repository asowner/name. The app creates its own columns and imports issues and comments into its table. Sync runs when the view opens and when you click "Sync now".proxyTransport's existingdispatchhook callsstore.proxy.request, so the frame never holds a connection code.AtomicPortruns over a new adapter,app/frameStore.ts.devonian/github-issues/review.mjs.Bridge.resolveConflict, which moves only the conflicting fields' baseline.atomic-fixture/trackerwith two issues and one comment. The e2e needs this because the mock proxy runs in a separate process, so the test can't seed it directly.Host findings (atomic-server
bae5cdbe3)saveornewResourcefrom the frame is an acknowledged/app-writecommit (hostStore.tswriteAsApp).frameStore.tscorrects its own reads for the app's own saves rather than waiting for the cache. This may be worth an atomic-server issue.querychecks the page's local (OPFS) index first and can miss a resource the app has just created.frameStore.tsremembers every subject it has seen or created in the sync state and adds those back to query results.Verified
node integrations/tooling/run-lane.mjs issue-tracker: the unit tier passes (79 tests), and the new e2e tier passed twice locally against the sharedbae5cdbe3build.app/sync.test.tsuses an in-memory host and the same fixture. It covers:app/build.test.tschecks that the bundle (about 86 KB) is one ES module with no storage orfetchcalls of its own and no Automerge, and it typechecksapp/.localthoughtlane (typecheck and unit, it also uses the GitHub fixture),node --test integrations/tooling/,tsc -p integrations/tsconfig.e2e.json, andoxfmt --check integrationsall pass.Not verified / not done
background.mjsis not used, because the frame has no Web Locks or IndexedDB. The supported cadence is: on open and on "Sync now".GET /user/reposin the proxy's GitHub document is not verified.Decisions for the maintainer
/app-writehas no compare-and-swap, so two tabs or devices syncing the same app at once are not protected against each other. The design (issue-tracker: frontend design, mockups and implementation issue drafts (#89) #103) proposed a per-browser storage op in the host instead, which would need atomic-server work.devonian@0.7.0is pinned inapp/package.json, not in the plugin folder, becausecertify.mjswould treat a plugin-levelpackage.jsonas a sandbox package. This required a one-line change to both install loops inci.yml.syncables@0.18.0is not used. The bridge's GitHub port already handles pagination.Changes outside
integrations/issue-tracker/integrations/lanes.json: the issue-tracker lane gains thee2etier and the spec..github/workflows/ci.yml: both "Install plugin npm dependencies" loops now also installintegrations/*/app/pnpm-lock.yaml.Overlaps
AGENTS.mdandREADINESS.md. That should become "drive app" after this PR.🤖 Generated with Claude Code
🤖 Generated with Claude Code