[bnsoni]

Stacked on #4 → #3. Uses iblai/iblai-deploy-ops#80 (live.json and seen_elsewhere); without it nothing changes.

Problem

• Too late. A developer learned their build was broken only when the ~1-hour suite finished, though os#617's crash was clear within minutes.
• Shared failures looked like theirs. Failures other PRs were hitting too looked like their own.

Change

Early warning:

• While the run executes, the poll loop fetches the central run's live.json from tests.iblai.app every 2 minutes. That's a CloudFront request, so no GitHub API budget.

• It logs e2e progress: 298 passed, 74 failed so far; most common: App crash x35 TypeError: …``.

• Once a crash or browser error has hit 10 tests, it posts one comment and the run keeps going:

  ⚠️ PR E2E early warning: your build looks broken

  35 tests so far: your build crashes: TypeError: Cannot read properties of undefined (reading 'find')

  The run keeps going (298 passed, 74 failed so far). The full result, with every cause, a screenshot and a trace, is posted when it finishes. You can fix and push now; the push starts a new run.

• Symptoms and server errors never trigger it, and a live.json that isn't published yet is not an error. Nothing in this path can fail the step, which runs under bash -e.

/status adds the same live counts to "Running now".

Shared causes: a cause other PRs' runs hit in the last 48 h shows as "— also failing on os#610, probably not yours". The code quote and the dependency hint follow the PR's own top cause. With nothing of its own, there is no hint.

README: "Reading your PR e2e result" explains the causes, the "also failing" mark and the early warning.

Testing

• tests/test-render.py: 63 cases, 15 of them new:
  • the progress line;
  • the warning's threshold and which kinds trigger it;
  • the --live CLI writing the warning only when due, and tolerating a missing file;
  • shared-cause marking, and the quote and hint following the PR's own cause.
• Mutation: 27 mutants on render.py, all caught.
• The real check_live from action.yml, extracted and run under bash -e with stubbed curl/gh:
  • it asks for …/runs/pr-os-617-41060344848/mentor/live.json;
  • three checks post exactly one comment;
  • below the threshold, none.

🤖 Generated with Claude Code