feat(mcp): agents_presets add/edit/remove

.agents/commands/canaryrelease.md

@@ -0,0 +1,16 @@
+---
+description: Trigger a canary build of the desktop app (rolling internal-testing release, not a versioned stable release)
+allowed-tools: Bash
+---
+
+Trigger the desktop canary release workflow. This is distinct from `bun run release desktop` (which cuts a real versioned stable release) — canary is a rolling, prerelease-tagged internal-testing build (`desktop-canary`) that gets force-rebuilt and replaces the previous one each time.
+
+## Steps
+
+1. Run `bash scripts/release-canary.sh $ARGUMENTS` from the repo root.
+   - With no argument, it triggers `release-desktop-canary.yml` (via `gh workflow run`) against the current default branch.
+   - With a commit SHA/ref argument, it pushes that commit to a temp `canary-release-<sha>` branch first, then triggers the workflow against that branch.
+2. The script prints the GitHub Actions run URL — share it with the user.
+3. Optionally poll `gh run view <run-id>` or check the run URL to confirm the build succeeded and the `desktop-canary` release/tag was updated.
+
+No confirmation is needed before running this — canary is a low-stakes rolling internal build, not a user-facing release.

.agents/commands/ci-check.md

@@ -0,0 +1,34 @@
+---
+description: Run lint:fix, typecheck, test, and sherif to validate the project before pushing
+allowed-tools: Bash
+---
+
+Run all CI checks locally to validate the project.
+
+## Checks
+
+Run these four commands **in parallel** and report all results:
+
+1. `bun run lint:fix` — Biome formatting + linting (auto-fixes)
+2. `bun run typecheck` — TypeScript type checking across all packages
+3. `bun test` — Run all tests
+4. `bunx sherif --fix` — Monorepo dependency linting (auto-fixes)
+
+## Output
+
+After all commands complete, print a summary table:
+
+| Check | Status |
+|-------|--------|
+| lint:fix | pass/fail |
+| typecheck | pass/fail |
+| test | pass/fail |
+| sherif | pass/fail |
+
+If any check fails, show the relevant error output.
+
+## Fix Warnings
+
+After the initial run, if any check produced **warnings** (not just errors), fix them manually since warnings still fail CI. Re-run the failing check(s) to confirm they pass cleanly with zero warnings.
+
+$ARGUMENTS

.agents/commands/clean-neon-branches.md

@@ -0,0 +1,21 @@
+---
+description: Delete Neon database branches created before today (preserves production)
+allowed-tools: Bash, Read
+---
+
+Clean up old Neon database branches from the project's Neon account. This command deletes all non-production branches created before today's date.
+
+## Steps
+
+1. Read the root `.env` file to get `NEON_PROJECT_ID` and `NEON_ORG_ID`.
+2. Run `neonctl branches list --project-id $NEON_PROJECT_ID --org-id $NEON_ORG_ID --output json` to get all branches.
+3. Filter branches to find ones where:
+   - `primary` is `false` (skip the production branch)
+   - `created_at` is before today (UTC)
+4. Show the user a table of branches that will be deleted (name, created date, branch ID).
+5. If there are no branches to delete, inform the user and stop.
+6. Ask the user for confirmation before deleting.
+7. On confirmation, delete each branch in parallel using `neonctl branches delete <branch-id> --project-id $NEON_PROJECT_ID --org-id $NEON_ORG_ID`.
+8. Report results.
+
+$ARGUMENTS