feat: shared MEMORY.md per workspace

[proofmancer]

Closes #3.

Summary

• New <workspace.cwd>/.argus/MEMORY.md file. Empty save deletes it.
• runAgent() reads memory and prepends it (in a labeled fence) ahead of the agent's own system prompt via --append-system-prompt. Missing or blank file means no flag added, behaves identical to today.
• New GET / POST /api/workspaces/[id]/memory endpoint. Validates the workspace exists, its cwd is absolute, and the directory exists on disk before touching FS.
• SharedMemoryForm client component (textarea, save, status line). Server component pre-loads the file contents so first paint shows what's on disk.
• Wired into the workspace page as a new "Shared memory" section above Agents.

Build fix bundled

The new route added one more parallel worker to next build's page-data-collection phase, which tipped SQLite over with SQLITE_BUSY (multiple processes racing to set WAL mode). Fixed defensively: busy_timeout = 5000 on connection open, plus SQLITE_BUSY swallowed in ensureMigrated() since the schema is idempotent. Necessary to make CI pass; small enough to keep in this PR.

Test plan

• Open a workspace, save some memory, confirm .argus/MEMORY.md appears in the workspace folder on disk.
• Run an agent in that workspace, confirm the memory text appears in the agent's effective system prompt (look at the --append-system-prompt arg or check the run output).
• Save empty memory, confirm .argus/MEMORY.md is deleted.
• Workspace cwd that doesn't exist on disk: API returns 400, UI shows the error.

[coderabbitai]

Warning

Review limit reached

@proofmancer, we couldn't start this review because you've used your available PR reviews for now.

Your plan includes 1 review of capacity. Refill in 3 minutes and 18 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6ec630c5-7687-41d0-a394-5d7f44b7ebf8

📥 Commits

Reviewing files that changed from the base of the PR and between 88cb8a7 and 4270b2b.

📒 Files selected for processing (4)

• src/app/api/workspaces/[id]/memory/route.ts
• src/app/workspace/[id]/page.tsx
• src/components/SharedMemoryForm.tsx
• src/lib/claude.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/shared-memory

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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