nexxo 82916167cf fix(monitoring): MONITORING_ATTEMPTS is now exact (off-by-one); accept int or dict monitor id ... - attempt is 0-based, so compare one-based: ATTEMPTS=2 really means two tries - bridge accepts add_monitor returning {monitorID}|{id}|int (v1.2.1 returns a dict — re-verified: first create on a fresh Kuma is HTTP 200 with the id) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-25 20:08:07 +02:00
..
Actions	fix(auth/admin): atomic user+customer signup; Rule::in for country validation (comma-safe)	2026-07-25 18:33:09 +02:00
Console	feat(engine): orchestrator core (state machine + tick + lock)	2026-07-25 09:54:52 +02:00
Http	fix(admin): remove is_admin self-heal — RBAC is the only console boundary (no revocation bypass)	2026-07-25 18:35:14 +02:00
Livewire	fix(portal): cloud status labels for all instance states; scale storage curve into the quota	2026-07-25 19:16:16 +02:00
Mail	fix(admin): confirm maintenance delivery via MessageSent (retryable until sent); guard resend/cancel on derived state; fix flaky non-unique host wg_ip	2026-07-25 16:14:01 +02:00
Models	fix(portal): scope the per-instance maintenance badge to that instance's host	2026-07-25 19:12:33 +02:00
Notifications	fix(engine-b): default-deny firewall, disk-based capacity, synchronous credential mail	2026-07-25 12:39:15 +02:00
Providers	fix(auth): scope registration throttle to its own route (per-IP), not all Fortify endpoints	2026-07-25 18:41:30 +02:00
Provisioning	fix(monitoring): MONITORING_ATTEMPTS is now exact (off-by-one); accept int or dict monitor id	2026-07-25 20:08:07 +02:00
Services	feat(monitoring): Uptime Kuma support via a REST bridge + resilient monitoring policy	2026-07-25 20:04:58 +02:00