Add arca extension

[gre-dev]

Description

This extension brings Arca, a task management app, into Raycast. It lets you create tasks and review your work without switching context.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Greptile Summary

This PR adds a new Arca extension with three commands — Create Task, My Tasks, and Planned Tasks — integrating with the Arca task management API via an API key preference. The extension is well-structured, follows current Raycast conventions (auto-generated Preferences type, correct ESLint v9 flat config, {PR_MERGE_DATE} placeholder, proper category assignment), and all listed dependencies are actively used.

Confidence Score: 5/5

Safe to merge — one minor UX logic note in Planned Tasks but no blocking issues

No P0 or P1 findings; the single comment is a P2 UX concern about how Overdue is determined when both start and due dates are present. All previous review feedback appears addressed.

extensions/arca/src/planned.tsx — bucket logic for tasks with both start_date and due_date

Important Files Changed

Filename	Overview
extensions/arca/src/shared.tsx	Shared types, constants, and components; includes TurndownService for HTML→Markdown conversion, TaskDetail/TaskItem components, and API helpers — well-structured with no major issues
extensions/arca/src/create-task.tsx	Create Task form command; correctly imports BASE_URL from shared, uses auto-generated Preferences type, handles workspace/list/status loading and form submission
extensions/arca/src/my-tasks.tsx	My Tasks list command; fetches all assigned tasks across workspaces with pagination, groups by priority, and persists showCompleted state via useLocalStorage
extensions/arca/src/planned.tsx	Planned Tasks view; buckets tasks by due/start date — when both dates exist the earlier one is used for bucketing, which can cause tasks to show as Overdue based on a past start_date even when due_date is in the future
extensions/arca/package.json	Extension manifest; has $schema, correct Title Case preference titles, Productivity/Applications categories, @types/turndown properly in devDependencies, and platforms set to macOS+Windows

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
extensions/arca/src/planned.tsx:35-38
**Tasks bucketed as "Overdue" based on past start date, not due date**

When both `due_date` and `start_date` are set, the earlier of the two is used for bucketing. A task with a `start_date` in the past but a `due_date` still in the future will land in the "Overdue" bucket, even though it hasn't missed its deadline. Users typically expect "Overdue" to mean the *due date* has passed.

Consider always preferring `due_date` for the bucket comparison, and falling back to `start_date` only when `due_date` is absent:
```typescript
dateStr = due; // prefer due_date when both are present
```

_{Reviews (2): Last reviewed commit: "Refactor getTaskBucket to improve date h..." | Re-trigger Greptile}

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊