feat(monitor-ci): extend polling coverage to ~33 min

[polygraph-app]

Summary

Extends the monitor-ci skill's polling loop so it can cover CI executions that run up to ~30 minutes.

Changes

• backoff() delays now [60, 90, 120, 180] (adds a 4th step at 180s)
• Circuit breaker threshold raised from 5 to 13 no-progress polls
• Updated the corresponding status message and priority comment
• Updated SKILL.md documentation

Math

With the new max backoff of 180s and 13 no-progress polls, total coverage is:

90 + 120 + 180 * 10 = 2010s ≈ 33.5 min

That gives comfortable headroom for 30-minute CI runs (previously only ~7.5 min of coverage was possible).

Files touched

• artifacts/skills/monitor-ci/scripts/ci-poll-decide.mjs (source)
• artifacts/skills/monitor-ci/SKILL.md (source)
• 11 regenerated copies across skills/, generated/.agents/, generated/.github/, generated/.opencode/, generated/.gemini/ via npx nx sync-artifacts

Notes

The polygraph await-polygraph-ci skill also mentions "5 consecutive polls" in its own polling loop — left unchanged as it's a separate skill with different semantics.

---

View session information on Nx Cloud ↗

Related PRs: None yet

[nx-cloud-snapshot]

View your CI Pipeline Execution ↗ for commit 4135739

Command	Status	Duration	Result
nx run-many -t lint test build typecheck e2e-ci	✅ Succeeded	<1s	View ↗
nx-cloud record -- npx nx format:check --base=r...	✅ Succeeded	1s	View ↗
nx sync-artifacts-verification	✅ Succeeded	6s	View ↗
nx validate-cursor-plugin	✅ Succeeded	21s	View ↗
nx-cloud record -- claude plugin validate .clau...	✅ Succeeded	<1s	View ↗
nx-cloud record -- claude plugin validate .clau...	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-05 22:09:01 UTC

[nx-cloud-snapshot]

✅ The fix from Nx Cloud was applied

We updated the circuit breaker test to align with the intentional threshold change from 5 to 13 consecutive no-progress polls introduced in this PR. The test was passing --no-progress-count 4 (incrementing to 5), which no longer triggers the circuit breaker at the new threshold, causing the assertion to fail. Updating the input to 12 (incrementing to 13) correctly validates the new behavior.

Tip

✅ We verified this fix by re-running @org/source:test.

Suggested Fix changes

diff --git a/tests/monitor-ci/ci-poll-decide.test.mjs b/tests/monitor-ci/ci-poll-decide.test.mjs
index 0519355..c51c479 100644
--- a/tests/monitor-ci/ci-poll-decide.test.mjs
+++ b/tests/monitor-ci/ci-poll-decide.test.mjs
@@ -105,13 +105,13 @@ describe('guards', () => {
     expect(result.action).toBe('done');
   });
 
-  it('circuit_breaker when noProgressCount >= 5', async () => {
+  it('circuit_breaker when noProgressCount >= 13', async () => {
     // noProgressCount starts at inputNoProgressCount+1 when no state change
     const result = await runScript(ci(), 0, 'medium', [
       '--no-progress-count',
-      '4',
+      '12',
     ]);
-    // 4+1=5 >= 5
+    // 12+1=13 >= 13
     expect(result.code).toBe('circuit_breaker');
     expect(result.action).toBe('done');
   });

🔔 Heads up, your workspace has pending recommendations ↗ to auto-apply fixes for similar failures.

  

View interactive diff ↗

➡️ This fix was applied by Victor Savkin

_{🎓 Learn more about Self-Healing CI on nx.dev}