docs: update agent coolify instructions

Author: ohld

agents/qa-engineer/AGENTS.md

@@ -26,7 +26,9 @@ You are running without a human operator. NEVER call `AskUserQuestion`. When ski
 ## Log Sources
 
 1. **Sentry** — prefer the new CLI: `sentry issue list --query "is:unresolved" --limit 20 --json --fields shortId,title,level,firstSeen`. If only `sentry-cli` exists, use `sentry-cli issues list --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --status unresolved --max-rows 20`. Use `sentry issue view <id>` or Sentry REST API for details.
-2. **Coolify app logs** — `curl -s "$COOLIFY_BASE_URL/api/v1/applications/v0kkssccwoswgwwscws4kscc/logs?lines=200" -H "Authorization: Bearer $COOLIFY_ACCESS_TOKEN"`.
+2. **Coolify app logs** — use `mcp__coolify__application_logs` for app
+   `v0kkssccwoswgwwscws4kscc`. Use `mcp__coolify__get_application` for app
+   lookup/status.
 3. **DB health** — `psql $ANALYST_DATABASE_URL` (read-only). Query `user_meme_reaction`, `user_stats.updated_at`, `meme_stats.updated_at`, and new `meme` rows in the last hour.
 
 ## Paperclip Runtime

agents/release-engineer/AGENTS.md

@@ -46,11 +46,10 @@ You do **NOT** merge PRs. Staff Engineer owns the review → approve → squash-
 
 ## What you do
 
-1. **Verify the deploy** — check that Coolify finished the deploy and the new commit is live:
-   ```bash
-   curl -s "$COOLIFY_BASE_URL/api/v1/applications/v0kkssccwoswgwwscws4kscc" \
-     -H "Authorization: Bearer $COOLIFY_ACCESS_TOKEN" | jq .status
-   ```
+1. **Verify the deploy** — check that Coolify finished the deploy and the new
+   commit is live. Use `mcp__coolify__get_application` for app status, and
+   `mcp__coolify__deployment` if deployment details are needed for app
+   `v0kkssccwoswgwwscws4kscc`.
 2. **Smoke-test production** — use `/canary` for post-deploy health monitoring (Sentry new errors, container status, health endpoint).
 3. **Update release docs** — if the change is user-facing or architectural, use `/document-release` to sync CHANGELOG / README / ARCHITECTURE / CLAUDE.md.
 4. **Escalate if broken** — if the deploy failed or canary flags regressions, create a CTO issue with `[deploy:<pr-number>]` slug containing the failing check and a link to Sentry / Coolify logs.