nexxo 0135f114d3 fix(traffic): keep retrying the throttle release after a Proxmox blip ... Tying the release to the creation of the new month's row meant a single failed call was never retried: the row exists from then on, and the current period looks unthrottled, so nothing could detect the stale NIC limit. A customer would have stayed slow for a whole month they had paid for. Checked on every sample now, with a test that makes the first release fail. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-25 23:40:33 +02:00
..
Contracts	fix(engine): address Codex round 2 (poll budget, host error state, wg race)	2026-07-25 10:26:37 +02:00
Events	feat(engine-b): live provisioning progress (admin console + customer dashboard)	2026-07-25 11:57:35 +02:00
Jobs	fix(traffic): keep retrying the throttle release after a Proxmox blip	2026-07-25 23:40:33 +02:00
Steps	fix(vpn): lock every hub mutation; resolve duplicate keys inside the lock	2026-07-25 21:55:57 +02:00
PipelineRegistry.php	feat(engine): orchestrator core (state machine + tick + lock)	2026-07-25 09:54:52 +02:00
RunRunner.php	fix(engine): don't reset started_at on poll so step deadlines accumulate	2026-07-25 12:15:26 +02:00
StepResult.php	fix(engine): address Codex round 2 (poll budget, host error state, wg race)	2026-07-25 10:26:37 +02:00