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
Todoist: define completion and disappearance behavior for active-task imports #99
The catalog advertises an Issues view with open/closed tasks, while the read-only connector imports active tasks. When a previously imported task disappears from the active feed, retaining its last open state can mislead users. Absence alone is not proof of completion: it can also mean deletion or lost access.
Acceptance criteria:
Choose an explicit supported behavior for tasks that stop appearing: verified completion data where available, or a clearly explained last-seen/stale state.
Do not infer completion/deletion from a failed or partial fetch.
Cover active → completed/absent, deleted/inaccessible, partial pagination and reappearance using fixture tests.
Explain that local edits/closing do not write to Todoist, and align the catalog's closed-task claim with actual coverage.
Exercise this behavior in the eventual host journey.
Related: #46 owns the recorded Todoist fixture; extend/reuse that work rather than creating a competing fixture project. This issue owns the semantic decision and regression cases.
Evidence: integrations/catalog.json (devonian-todoist) and integrations/issue-tracker/todoist.ts.
Reviewed against atomic-plugins main at 110bcaac3252eaeb57fda9afb2c09e0b872c5bf4.
Picked up by the atomic-plugins oversight session (e6ce43) with a worker agent. One issue-tracker agent handles #100 first, then #99. Each agent plans first. I'll comment again when there's a PR or when work stops on a blocker.
PR #114. A task that goes missing from a complete read is looked up once by id and marked completed, deleted, unavailable (404) or unconfirmed (the lookup failed). Only completed closes it. Partial reads change nothing, and rows are never removed. There are 9 synthetic regression tests. Still open:
whether this lookup-by-id behaviour is right is a user decision;
#273 gives this behaviour a host. The Todoist drive app imports active tasks into issue-v1 rows and runs todoist.ts's lookup-by-id on disappearance. A host e2e (e2e/todoist.spec.ts) checks a completed task closing and an unreachable one staying open as unavailable. Still open: Michiel's confirmation of the semantics (on #227), and live verification (#46).
Activity
michielbdejong commentedon Sep 24, 2026
Picked up by the atomic-plugins oversight session (
e6ce43) with a worker agent. One issue-tracker agent handles #100 first, then #99. 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
PR #114. A task that goes missing from a complete read is looked up once by id and marked
completed,deleted,unavailable(404) orunconfirmed(the lookup failed). Onlycompletedcloses it. Partial reads change nothing, and rows are never removed. There are 9 synthetic regression tests. Still open:todoist.ts.michielbdejong commentedon Oct 2, 2026
#273 gives this behaviour a host. The Todoist drive app imports active tasks into
issue-v1rows and runstodoist.ts's lookup-by-id on disappearance. A host e2e (e2e/todoist.spec.ts) checks a completed task closing and an unreachable one staying open asunavailable. Still open: Michiel's confirmation of the semantics (on #227), and live verification (#46).Generated by Claude Code
Merge pull request #617 from ontola/claude/todoist-active-tasks