PR #241 merged: feat: diagnose_app cross-checks latest deployment status (#239)

Summary

• diagnoseApplication now cross-checks the running app state against its latest deployment. If the app is running but the most recent deployment failed or was cancelled, it adds an explicit finding: the running container predates the last (failed/cancelled) deployment and is serving stale code — including the deployment's uuid and a next-action hint to fetch its logs via the deployment tool (action: get, lines).
• Reuses the deployments already fetched for the diagnostic (no extra API call). If that call fails or returns no deployments, the check is skipped silently — consistent with how the rest of diagnoseApplication degrades on partial failures.
• If the latest deployment succeeded or is in progress, no note is added — matches the existing convention of staying silent on healthy state rather than adding "all good" noise.

Closes #239

Test plan

• Added should flag stale code when app is running but the latest deployment failed
• Added should not flag stale code when the latest deployment succeeded
• Added should skip the deployment-freshness check without breaking diagnosis when deployments are unavailable
• npm test — 366 passed
• npm run lint — 0 errors (pre-existing warnings only, none in changed lines)
• npx prettier --check . — clean
• npm run build — passes

🤖 Generated with Claude Code