Skip to content

Complete catalog installation and publication for drive apps #94

Closed

Description

@michielbdejong

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.
  • Show the installed version and follow the update semantics established by Versioning and updating #12.
  • Exercise discovery → installation → connection → first import → reopen in a Pets E2E; use the same mechanism for Notion and Clockify.
  • Link any required atomic-server implementation issue and pin the working host version here.

Keep provider-specific code in this repository. This follows #20 and #52; it does not reopen their completed scaffold/relay work.

Evidence: integrations/pets/e2e/pets.spec.ts (setAppSource) and integrations/pets/README.md (Install).

Reviewed against atomic-plugins main at 110bcaac3252eaeb57fda9afb2c09e0b872c5bf4.

Activity

  1. michielbdejong commented on Sep 24, 2026

    @michielbdejong
    ContributorAuthor

    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.

  2. michielbdejong commented on Sep 24, 2026

    @michielbdejong
    ContributorAuthor

    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.

  3. michielbdejong commented on Sep 24, 2026

    @michielbdejong
    ContributorAuthor

    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.

  4. michielbdejong commented on Sep 25, 2026

    @michielbdejong
    ContributorAuthor

    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.

  5. michielbdejong commented on Oct 1, 2026

    @michielbdejong
    ContributorAuthor

    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.


    Generated by Claude Code

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