You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Complete catalog installation and publication for drive apps #94
Pets and Notion have iframe E2Es, but the tests create a generic App and replace its source through a test helper. That proves execution after installation, not that a user can discover and install the published plugin. The remaining installation work from closed #20 needs its own deliverable.
Acceptance criteria:
Define catalog metadata for a versioned executable app module, distinct from the source/repository link.
Build and publish the module and any required installation metadata.
Through generic host UI, install the selected app, its entry point, table and ontology without injecting source from a test helper.
Picked up by the atomic-plugins oversight session (e6ce43) with a worker agent. It runs in its own agent. Each agent plans first. I'll comment again when there's a PR or when work stops on a blocker.
Draft PR open. It depends on the pin in #110 and on ontola/atomic-server#1689 (the host's Drive apps install and update). It's paused on two user decisions: the npm package name atomic-app-<id> and the Apache-2.0 licence. After those, the first atomic-app-pets publish has to be done by hand before trusted publishing can be set up. Notion and Clockify reuse the same mechanism as follow-ups.
ah interesting, could we create a functional light-weight plugin-iframe runtime for atomic plugins that just implements the plugin contract and the things the plugin can can do without pulling in all of atomic-server? we can still do the full e2e with a real server build as an added check, also for when plugins run in Tauri etc, but for just building these plugins it might be a lot faster to test them on a light-weight runner?
re license, atomic-server has MIT so let's do that here too.
Status: catalog install and Pages publishing (#111) now cover pets, timesheets, issue-tracker, calendar and notion. Each lane's e2e installs from the host's Drive apps section. Money (#148) follows once its PR lands. Leaving this open until money is published too.
Catalog install and Pages publication are in place for pets, calendar, issue-tracker, timesheets and notion, plus money 0.3.0 (#197).
The catalog entries carry app-module and app-module-integrity.
Each lane's e2e installs from Drive apps.
The Pets e2e covers discovery → install → connect → import → reopen → update from an older version.
Money's catalog Install still doesn't give a working app. The app gets its own empty table, and the importer's table doesn't offer the app under Add view. That is a row-class mismatch, not a gap in the install mechanism, so it moves to #177 (money binding to bank-transaction-v1, item 8), which is being picked up now. Moneybird publication moves to #102. Every app entry except Pets stays enabled: false until launch.
Activity
michielbdejong commentedon Sep 24, 2026
Picked up by the atomic-plugins oversight session (
e6ce43) with a worker agent. It runs in its own agent. Each agent plans first. I'll comment again when there's a PR or when work stops on a blocker.michielbdejong commentedon Sep 24, 2026
Draft PR open. It depends on the pin in #110 and on ontola/atomic-server#1689 (the host's Drive apps install and update). It's paused on two user decisions: the npm package name
atomic-app-<id>and the Apache-2.0 licence. After those, the firstatomic-app-petspublish has to be done by hand before trusted publishing can be set up. Notion and Clockify reuse the same mechanism as follow-ups.Pin atomic-server to claude/atomic-plugins-pin 94610046e (atomic-serv…
Pin atomic-server to claude/atomic-plugins-pin cbeff2962 (atomic-serv…
michielbdejong commentedon Sep 24, 2026
ah interesting, could we create a functional light-weight plugin-iframe runtime for atomic plugins that just implements the plugin contract and the things the plugin can can do without pulling in all of atomic-server? we can still do the full e2e with a real server build as an added check, also for when plugins run in Tauri etc, but for just building these plugins it might be a lot faster to test them on a light-weight runner?
re license, atomic-server has MIT so let's do that here too.
re npm, I was thinking we would publish the plugins in this repo via gh-pages on https://ontola.github.io/atomic-plugins/integrations/... just like https://ontola.github.io/atomic-plugins/integrations/catalog.json? we need a design doc and a design issue about that. open one and i'll comment there if there are trade-offs to take into account.
issue-tracker: GitHub issues drive app, the host for the Devonian bridge
Install drive apps from the catalog: versioned modules on GitHub Page…
Install drive apps from the catalog: versioned modules on GitHub Page…
Merge pull request #111 from ontola/claude/issue-94-catalog-install
michielbdejong commentedon Sep 25, 2026
Status: catalog install and Pages publishing (#111) now cover pets, timesheets, issue-tracker, calendar and notion. Each lane's e2e installs from the host's Drive apps section. Money (#148) follows once its PR lands. Leaving this open until money is published too.
docs: READINESS rows, lane notes and READMEs for the published drive …
docs: READINESS rows, lane notes and READMEs for the published drive …
docs: READINESS rows, lane notes and READMEs for the published drive …
michielbdejong commentedon Oct 1, 2026
Catalog install and Pages publication are in place for pets, calendar, issue-tracker, timesheets and notion, plus money 0.3.0 (#197).
app-moduleandapp-module-integrity.Money's catalog Install still doesn't give a working app. The app gets its own empty table, and the importer's table doesn't offer the app under Add view. That is a row-class mismatch, not a gap in the install mechanism, so it moves to #177 (money binding to
bank-transaction-v1, item 8), which is being picked up now. Moneybird publication moves to #102. Every app entry except Pets staysenabled: falseuntil launch.Generated by Claude Code