Add backoff and jitter to deployment polling

[yoannchaudet]

Summary

• exponentially back off successful non-terminal deployment status polls by 1.5x, capped at 30 seconds
• add ±20% jitter to desynchronize concurrent deployments
• preserve the configured reporting interval as the initial delay and keep error backoff independent
• document the updated polling behavior and rebuild the distribution

Testing

• npm run format:check
• npm run lint:check
• npm run prepare
• npm test -- --runInBand

[Copilot]

Copilot review overview

🟡 Changes recommended

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review tier: Lite
Findings: 1 · 2

New issues introduced by this change (3)

Severity	Finding
	src/​internal/​deployment.js — reporting_interval is parsed with Number(...) but not validated. If the input is non-numeric…
	README.md — The docs say the polling backoff is capped at 30 seconds, but the implementation caps only the…
	action.yml — This input description implies the overall polling interval is capped, but the code caps only the…

What changed in this PR

This PR updates the deployment status polling loop to reduce load and avoid synchronized polling by adding exponential backoff and jitter to non-terminal, successful status checks, and updates the docs/built distribution to match.

Changes:

• Add ±20% jitter to polling delays and apply 1.5× exponential backoff (capped at 30s) after successful non-terminal status responses.
• Extend test coverage for backoff/jitter behavior and ensure error backoff remains separate from success backoff.
• Update reporting_interval documentation and rebuild dist/.

File	Description
src/​internal/​deployment.js	Adds jitter helper and success-path reporting interval backoff logic.
src/​__tests__/​internal/​deployment.test.js	Adds unit tests covering backoff, cap, jitter, and separation from error backoff.
README.md	Documents the updated polling semantics for reporting_interval.
dist/​index.js	Rebuilt distribution bundle reflecting the polling changes.
action.yml	Updates the reporting_interval input description to reflect backoff/jitter behavior.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.