Deploy Check

Verify that a merged PR is actually deployed and working on production.

Steps (execute ALL of them, in order)

1. Identify what shipped

•If a PR number was given, run gh pr view <number> --json mergedAt,files,title
•If no PR number, check git log origin/main -3 --oneline and ask which change to verify
•Note the specific files changed and what the change does

2. Confirm merge landed

bash

git fetch origin main
git log origin/main -1 --oneline

•Verify the merge commit matches the PR

3. Wait for Render deploy

•Check deploy status: use Render MCP list_deploys for the relevant service, or poll the production URL
•If deploy is in progress, wait and re-check (max 3 minutes)
•Do not assume deploy is done — confirm it

4. Verify on production

For website changes (era2/website/):

bash

curl -s https://era-website.onrender.com/<changed-file> | head -20

•Check for the specific content that changed (new text, new elements, removed content)
•If visual change: take a Playwright screenshot and look at it

For API/service changes (era2/ backend):

bash

curl -s https://era2.onrender.com/<relevant-endpoint>

For script/automation changes (scripts/):

•Run the script with --dry-run if available
•Check relevant logs (tail scripts/gh_listener.log, etc.)
•Verify launchd jobs if applicable: launchctl list | grep <name>

5. Check board state

bash

python3 scripts/board_view.py

•Confirm the issue moved to the correct column (Testing or Deployed)
•Flag anything that looks wrong

6. Report with evidence

State exactly what you checked and what you saw. Include actual output. Example:

"Curled the production URL. The page contains 4 <p> tags in the abstract section. The text 'externalizes the costs and undervalues' appears 3 times. Board shows #620 in Testing."

NEVER say "should be deployed" or "it should work." Show proof or say you couldn't verify.