feat(sync): add Composio asana memory-sync pipeline

[CodeGhost21]

Summary

Adds AsanaSyncPipeline — a Composio memory-sync pipeline for the asana toolkit — implementing both SyncPipeline and IncrementalSource, registered alongside the existing six (gmail, github, notion, linear, clickup, slack). Before this, connecting Asana reported ACTIVE but sync failed with tinycortex sync does not support toolkit 'asana' and ingested nothing.

Pipeline shape

Asana is task-shaped, so the pipeline follows GitHub (server-side incremental depth) combined with ClickUp (multi-scope discovery):

• Scopes = projects. scopes() enumerates every accessible workspace via ASANA_GET_MULTIPLE_WORKSPACES, then lists each workspace's projects via ASANA_GET_MULTIPLE_PROJECTS.
• Fetch = ASANA_GET_MULTIPLE_TASKS per project, paging on Asana's next_page.offset cursor, requesting opt_fields so modified_at (the incremental cursor) is present.
• Incremental depth is server-side via Asana's modified_since filter (server_side_depth() -> true), mirroring GitHub's updated:>cursor. Every fetched task is strictly newer than the persisted cursor, so the engine's boundary check never truncates an unordered page. tolerate_scope_errors() -> true keeps one unreachable project from aborting the whole run.

Stable dedupe (openhuman#4953 lesson)

• document_id = asana:<gid> — the stable Asana task gid, never a per-run id, so re-syncs upsert in place.
• metadata.taint = "external_sync", metadata.path_scope = "asana/project/<project_gid>" (stable collection scope), plus project_id / workspace_id.
• dedup_key = <gid>@<modified_at> so an edited task re-ingests a new version while keeping the same document id.

Reference followed

src/memory/sync/composio/providers/github.rs (server-side depth) and clickup.rs (workspace→scope enumeration); shared helpers from providers/common.rs; engine contract in orchestrator.rs.

Tests run

• src/memory/sync/composio/providers/asana_tests.rs — unit coverage: toolkit()/action(), extract_page() on a sample Composio JSON payload (+ no-next_page stop), dedup_key/sort_cursor, arguments() carrying project/modified_since/offset, and a stable asana:<gid> document_id with path_scope from document().
• tests/composio_sync_mock.rs::asana_enumerates_projects_and_stores_stable_task_documents — end-to-end workspaces→projects→tasks mock asserting stable document id, taint/path_scope/workspace_id metadata, cursor advance, and idempotent re-sync (0 duplicates).
• cargo fmt --all clean; cargo test --features sync sync::composio green (23 tests).
• No PII/secrets logged — debug logging emits scope counts only, no task titles or bodies.

Scope

Part of #83 (tinycortex pipeline body; openhuman wiring is the follow-up step). The openhuman-side work — bumping the vendor/tinycortex submodule, adding the sync.rs selector arm, and registering the ComposioProvider so memory_sources.supported_toolkits advertises the slug — is intentionally not included here.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5be3349f-122e-4385-a6ed-e954743278c6

📥 Commits

Reviewing files that changed from the base of the PR and between 9a0603a and aca204d.

📒 Files selected for processing (6)

• src/memory/sync/composio/mod.rs
• src/memory/sync/composio/providers/asana.rs
• src/memory/sync/composio/providers/asana_tests.rs
• src/memory/sync/composio/providers/mod.rs
• src/memory/sync/mod.rs
• tests/composio_sync_mock.rs

---

_{Comment @coderabbitai help to get the list of available commands.}