Complete two-way sync for Todoist, Jira, and Asana

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code

[KrisBraun]

Brings the Todoist, Jira, and Asana connectors to Linear-level two-way sync. Linear was the reference throughout. (Notion is out of scope — its source only exists on an unmerged branch.)

What each connector gets

Create items from Plot, write status/assignee/title back, post + edit comments, expanded per-provider statuses (project sections for Todoist/Asana, real workflow statuses for Jira), file attachments, and inbound webhook fixes.

Connector	Highlights
Todoist	Raw fetch client; sections→statuses; onCreateLink; title/assignee/section write-back; description edit; webhook note:updated + comment-history backfill; comment file attachments
Jira	Wired the previously deadupdateIssue as onLinkUpdated (status via transition id, assignee email→accountId); per-project workflow statuses; symmetric ADF transform (jira-adf.ts) so note baselines don't clobber; inbound webhook verified via a registration secret; issue attachments
Asana	See below — needed a deeper fix

Asana: dropped the SDK for a raw-fetch client

Asana had pre-existing runtime blockers (not introduced here): asana@2.0.6 exports ApiClient, not the Client.create() API the code called (so it threw at runtime), and that SDK depends on superagent (Node http), which isn't reliable on Cloudflare Workers. The webhook X-Hook-Secret handshake also needs a response header the runtime can't set.

Fix: removed the asana (and @types/asana) dependency entirely in favour of a thin raw-fetch REST client (asana-api.ts, same pattern as Todoist), replaced webhooks with Events-API polling (sync-token cursor + modified_since delta on 412), and modelled the Asana "like" as a per-user reaction via onNoteReactionChanged (updateStory/updateTask {liked}) with inbound likes[].

Reactions

Per-user via onNoteReactionChanged (like Slack), notonNoteUpdated. Only Asana supports it (the like). Jira has no public reactions API; Todoist's are read-only/undocumented — both intentionally get none.

Verification

• All three: tsc + tsc --noEmit + plot lint + vitest green (5 / 11 / 18 tests). Pure transforms (status mapping, ADF round-trip, like reactions, sync-token parsing) are unit-tested.
• No live E2E — the round-trips need real Todoist/Atlassian/Asana OAuth accounts. Correctness rests on the compiler, two-stage code review, and the Linear pattern. Baseline-hash contracts and source immutability were specifically verified.
• No changeset — these consume the SDK but don't modify twister/.

Not user-facing yet

All three remain available: false in the site and are not in the public deploy.json (they deploy to the "review" env), so there's deliberately no docs/updates.md note. Flipping them on is a separate go-live step.

🤖 Generated with Claude Code