Repository navigation
Batch 2026-10-02: issue-tracker issue-v1, timesheets time-entry-v1, moneybird publish, domain bundles proposal (#254, #257, #242, #241) - #265
Merged
Conversation
…ers and lenses Records Michiel's decisions (catalog lists bundles, bundles per domain, built-in views on the same contract as plugin views, inline only for host-compiled bundles) and proposes the catalog shape, repo layout, atomic-server requirements and order of work. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L5aQY5QYngBKqaPkmCFZWM
…102) apps.mjs gets an APP_FOLDERS map for drive apps that do not live at integrations/<id>/app/: Moneybird builds from integrations/money/moneybird/ and records its version in a private package.json there, never in the Bank statements importer's integrations/money/package.json. Tests cover the mapping, the version file and write for a mapped app. apps/moneybird/0.1.0/ui.js is written by `apps.mjs write moneybird` (9,866 bytes minified, within build.test.ts's dated 11,000 limit). The catalog entry gets version, app-module, integrity and Contact/Contacts row names, and stays enabled: false. It drops requires-api-plugins (the host hides such entries from Drive apps) and platform, both fields of the removed LocalThought flow. moneybird.spec.ts now installs from the catalog card instead of replacing a New app's source. Catalog copy: the Moneybird and Todoist `events` no longer say "Connect through LocalThought"; that flow was removed from atomic-server. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # integrations/catalog.json
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The GitHub issues drive app now syncs into the shared class issue-v1, at
its published GitHub Pages subject:
- Rows are issue-v1: title in name, task/v1 body and status (the task/v1
tags todo, doing, blocked, done). Shared fields are read by subject
through ontology-kit's resolver only. On first open the app adds
issue-v1 to its App's renders, declares its row extras (issue number,
GitHub source, sync baseline) as row-extras, and sets its own table's
classtype to issue-v1. Shown on an Issue table it did not make, it only
shows a notice ("Sync this table" is item 14, not built).
- Blocked is the GitHub label atomic:blocked, like atomic:doing (#177 Q8):
lens, GitHubPort, the tracker actions and the sandbox plugin (plugin.js
rebuilt, manifest fixture updated). Board and list get a Blocked column;
keys 1-4.
- A status that is not exactly one of the four tags no longer fails the
pass: the row is shown with its status as it is and keeps the status it
last agreed with GitHub for the sync.
- Local-only rows (#177 Q6, this plugin's choice): a row with no GitHub
issue is left alone until "Publish to GitHub" in its panel; the create is
then held for review as before. Cards made with the app's own New issue
form are published at once (still reviewed).
- Baselines live on the rows as github-sync-baseline (#177 decision 7), not
in github-sync-state: written with every row the Bridge writes, written
at a checkpoint when they changed otherwise, read back into the Bridge's
records when a row is read. The snapshot's identity graph stays in the
sync state.
- An update over a 0.1.x install rewrites its rows in place once (own
Status tags to task/v1 tags, description to task/v1 body, isA to
issue-v1) and keeps the sync state, so unsent edits are still offered.
e2e: installs 0.2.0 from the catalog, checks the table and rows are
issue-v1 and the App renders it, publishes a row added outside the app,
and moves it to Blocked, all against the mock proxy; beforeAll checks Pages
serves issue-v1 (ontology-kit/served.mjs, copied byte-identical from the
money branch, #252). App 0.2.0 (usertest-6); catalog entry stays
enabled: false; size limit 167 KiB (measured 154,931 bytes).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Rows are time-entry-v1: name, work-start, work-end, work-billable, and work-project and work-person as links (#177 Q11), from ontology-kit/terms.mjs and read and written through ontology-kit's strict resolver only (app/fields.ts). - The app makes and owns two more tables under its App, "Projects" (work-project-v1) and "People" (work-person-v1), found again by class. A sync makes a row per active Clockify project and per user an entry names, with Clockify's names (app/links.ts). The Clockify ids stay provider extras of the app's own ontology: clockify-entry-id on time entry rows, clockify-project-id and clockify-user-id on project and person rows. - A link to a project row without a Clockify id is resolved by name when listed to send, as a typed project name was up to 0.4.0. - First open (app/adopt.ts): moves a 0.4.0 table's rows onto time-entry-v1 in place (old fields to shared fields and links, isA rewritten, old values removed), so unsent edits survive (#177 Q10); then the table's classtype, renders and row-extras. - On another time-entry-v1 table (via Add view) the app shows its rows read only and syncs nothing. - e2e checks the three classes are served on Pages first (ontology-kit/served.mjs), uses the real subjects, checks the rows and their links, and adds the app to a hand-made time-entry-v1 table. - Release: apps/timesheets/0.5.0, catalog stays enabled: false, usertest-5, size limit 177,000 bytes (measured 160,904). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iew Add view adds Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # integrations/READINESS.md
…nnection' into m-iv1 # Conflicts: # integrations/READINESS.md # usertest/catalog.mjs
…he catalog (#102) # Conflicts: # integrations/READINESS.md
This was referenced Oct 2, 2026
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.
Requested by Joep
Before: Michiel's four finished PRs from 1 October each waited for their own CI. Three of them conflicted with main in
integrations/READINESS.md, and three showed a failing e2e lane that is not their own (#257 timesheets fails the money lane, #242 moneybird fails the timesheets lane).After: they sit together on one branch off main, decided by one CI run. Merge this with a merge commit; that marks all four as merged.
Included:
Left out: #252 (money 0.4.0, still a draft).
Resolved:
integrations/READINESS.mdis one wide Markdown table. Rows are merged per plugin: main's newer remoteStorage row is kept, each PR's own changed row wins, and the columns are re-aligned.Note for review: #254 and #257 rewrite existing rows in place when an installation upgrades (0.1.x → 0.2.0, 0.4.0 → 0.5.0). Both PRs say this was only unit-tested against the fake host, not a real host.