senke 72ff070876 fix(ci): correct e2e health check jq path — .data.status == "ok" ... Run 459 (e2e on 86faeb16) failed at the health-check gate even though backend was healthy and Playwright's expected next step would have gone green: --- /api/v1/health response --- {"success":true,"data":{"status":"ok"}} ::error::backend health is not ok The standard veza response envelope wraps payloads in `data:`. The health endpoint returns `{"success": true, "data": {"status": "ok"}}`, not `{"status": "ok"}`. The workflow's jq -e '.status == "ok"' reads the root, misses the nested key, and aborts the job. Wasted a CI cycle on a misread. Fix: `jq -e '.data.status == "ok"'`. Comment in the workflow records the symptom so the next person debugging gets the pointer immediately. Followup to 86faeb16 (Day 4 token build fix): ci + security-scan went green on that commit (runs 458, 460). With this jq fix, e2e should also clear, completing the pre-tag green slate. SKIP_TESTS=1 — workflow YAML only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-27 13:05:12 +02:00
..
ISSUE_TEMPLATE	chore(cleanup): remove veza-chat-server directory and all operational references	2026-02-22 21:13:00 +01:00
workflows	fix(ci): correct e2e health check jq path — .data.status == "ok"	2026-04-27 13:05:12 +02:00
dependabot.yml	chore(cleanup): remove veza-chat-server directory and all operational references	2026-02-22 21:13:00 +01:00
pull_request_template.md	chore(cleanup): remove veza-chat-server directory and all operational references	2026-02-22 21:13:00 +01:00