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
→ Expected: shows step name + env block with new SUPABASE_SERVICE_ROLE_KEY line 2. python3 -c "import yaml; yaml.safe_load(open('.github/workflows/ci.yml'))"
Steps: 1. git add .github/workflows/ci.yml 2. git status -s → Expect: M .github/workflows/ci.yml (only) 3. git commit -m "fix(ci): forward SUPABASE_SERVICE_ROLE_KEY to e2e job" -m "PR #134 moved seeding from a separate CI step into Playwright's globalSetup, but the Run E2E tests step's env block did not include SUPABASE_SERVICE_ROLE_KEY (it was previously set by the now-redundant Seed E2E test users step, in a separate shell with no env persistence).
298
305
299
-
```
300
-
Scenario: Commit + push succeeds
301
-
Tool: Bash
302
-
Preconditions: Task 1 complete
303
-
Steps:
304
-
1. git add .github/workflows/ci.yml
305
-
2. git status -s → Expect: M .github/workflows/ci.yml (only)
306
-
3. git commit -m "fix(ci): forward SUPABASE_SERVICE_ROLE_KEY to e2e job" -m "PR #134 moved seeding from a separate CI step into Playwright's globalSetup, but the Run E2E tests step's env block did not include SUPABASE_SERVICE_ROLE_KEY (it was previously set by the now-redundant Seed E2E test users step, in a separate shell with no env persistence).
307
-
```
306
+
```
308
307
309
308
Adds 1 line forwarding SUPABASE_SERVICE_ROLE_KEY from \$GITHUB_ENV to the Run E2E tests step's env block, so globalSetup's required-env check passes." 4. git push origin fix/payment-status-e2e-auto-seed
310
309
→ Expect: success, no force needed 5. git log origin/main..HEAD --oneline
@@ -320,7 +319,7 @@ Steps: 1. sleep 60 # give CI time to start 2. gh pr checks 134
320
319
→ Expect: CLEAN (or BLOCKED if any other check still pending)
> 4 review agents run in PARALLEL. ALL must APPROVE. Present consolidated results to user and get explicit "okay" before completing.
332
331
333
332
-[ ] F1. **Plan Compliance Audit** — `oracle`
334
-
Read the plan end-to-end. Verify each "Must Have" present in the diff. Verify each "Must NOT Have" absent. Check evidence files exist. Compare deliverables against plan.
335
-
Output: `Must Have [N/N] | Must NOT Have [N/N] | Tasks [N/N] | VERDICT: APPROVE/REJECT`
333
+
Read the plan end-to-end. Verify each "Must Have" present in the diff. Verify each "Must NOT Have" absent. Check evidence files exist. Compare deliverables against plan.
334
+
Output: `Must Have [N/N] | Must NOT Have [N/N] | Tasks [N/N] | VERDICT: APPROVE/REJECT`
336
335
337
336
-[ ] F2. **Diff Audit** — `unspecified-high`
338
-
Verify only `.github/workflows/ci.yml` changed. Verify exactly 1 line added (or 1-7 lines if cleanup). Verify YAML valid. Verify the new env var line syntax matches existing lines in the same block.
Verify only `.github/workflows/ci.yml` changed. Verify exactly 1 line added (or 1-7 lines if cleanup). Verify YAML valid. Verify the new env var line syntax matches existing lines in the same block.
This step is now REDUNDANT because `globalSetup` runs the same seed. Removing it:
393
393
@@ -397,3 +397,4 @@ This step is now REDUNDANT because `globalSetup` runs the same seed. Removing it
397
397
The seed is idempotent (uses `upsert`), so running it twice (once in the separate step, once in globalSetup) is harmless. The plan does NOT require removing it. If the user wants this cleanup, it's a separate small follow-up plan.
398
398
399
399
The MINIMAL fix to make CI green is just adding the env var. The plan focuses on that.
0 commit comments