You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agents/qa-engineer/AGENTS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ You are running without a human operator. NEVER call `AskUserQuestion`. When ski
25
25
26
26
## Log Sources
27
27
28
-
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 --status unresolved --max-rows 20`. Use `sentry issue view <id>`/ `sentry-cli issues info <id>` for details.
28
+
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.
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.
31
31
@@ -113,7 +113,7 @@ even when the run is partial or errored.
113
113
114
114
When reviewing after a deploy, whether from scheduled heartbeat, Sentry trigger, or handoff:
2.**Sentry scan** — run `sentry issue list --query "is:unresolved" --limit 20 --json --fields shortId,title,level,firstSeen`; if only legacy `sentry-cli` exists, run `sentry-cli issues list --status unresolved --max-rows 20`. Cross-reference against the deploy timestamp.
116
+
2.**Sentry scan** — run `sentry issue list --query "is:unresolved" --limit 20 --json --fields shortId,title,level,firstSeen`; if only legacy `sentry-cli` exists, run `sentry-cli issues list --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --status unresolved --max-rows 20`. Cross-reference against the deploy timestamp.
117
117
3. Run E2E smoke tests if credentials are configured (see below).
118
118
4. Report results to **CTO** — GREEN (all clear) or RED (issues found).
`sentry` and legacy `sentry-cli` use different issue-list syntax. Prefer `sentry issue list --query "is:unresolved" --limit 20`; use `sentry-cli issues list --status unresolved --max-rows 20` only as a legacy fallback.
347
+
`sentry` and legacy `sentry-cli` use different issue-list syntax. Prefer `sentry issue list --query "is:unresolved" --limit 20`; use `sentry-cli issues list --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --status unresolved --max-rows 20` only as a legacy fallback. QA and CTO receive `SENTRY_ORG=ffmemes` and `SENTRY_PROJECT=ff-backend` from the manifest.
348
348
349
349
Post-deployment command (runs after each Coolify deploy) is configured to reinstall these,
350
350
but runs as non-root `node` user — see Coolify Quirks below.
0 commit comments