feat: add Asana integration skeleton for agent task sourcing

[ayushshukla1807]

Summary

This PR introduces the initial architectural skeleton for the Asana integration (AsanaPlugin), expanding the available task sources for agent orchestration. It implements the core TaskSourcePlugin interface, establishing the necessary PAT configuration schema and mapping Asana's gid and notes to the internal TaskRecord schema.

This lays the groundwork for allowing agents (Claude Code / OpenCode / Codex) to fetch context directly from Asana workspaces and execute ChangeStatus actions natively.

Related Issue

Addresses the Asana integration mentioned in the planned project roadmap.

Changes

• Implemented AsanaPlugin class extending TaskSourcePlugin.
• Added configuration schema for Workspace ID and Personal Access Token (PAT).
• Mapped Asana fields (gid, name, notes, due_on) to local task definitions (external_id, title, description).
• Registered the new plugin in the PluginRegistry (src/main/index.ts).
• Added base action stubs (Mark Complete) for future agent execution.

Testing

• Verified the plugin registers successfully in the central PluginRegistry without breaking existing Linear or HubSpot initializations.
• Confirmed the config schema aligns with the frontend dynamic rendering for integration settings.
• Stubbed API calls to ensure the event loop isn't blocked during sync initialization.

Checklist

• pnpm typecheck passes
• pnpm build succeeds
• pnpm test:run passes
• No hardcoded color classes (use CSS variable tokens)

[ayushshukla1807]

Hey team! I have an interview for the ML Engineer Intern role today and was deeply exploring the 20x architecture.

I saw Asana was next up on the roadmap and wanted to take a stab at laying out the TaskSourcePlugin skeleton for it to understand how the plugin registry connects to the agents.