[Proxicon]

Fresh telemetry could invalidate acknowledgement of the same active monitoring occurrence, Windows could reject a valid renewal because its cache deadline preceded the signed token expiry, and incident-only pairing still required reverse orchestration resources. This release fixes those owning state/authority boundaries and delivers the monitoring, Flow editor, pairing and operational dashboard changes together.

• Renewal separates cache scheduling from token authority, preserves all expiry/envelope fences and outage recovery, and reports local protocol failures separately from credential attention. The validated streaming readTimeout=0s setting is documented; no live proxy or credentials were changed.
• Monitoring actions lock current durable occurrence state, retain meaningful configuration/operator conflicts, make duplicates idempotent, and persist the authenticated actor and submitted reason. Batched historical/current identities and bounded server-filtered selection remove primary GUID labels and page-dependent lookup gaps.
• Flow retains Velox and the graph adapter, adds reusable Mud drag handles with viewport-coordinate conversion, node-specific cog/trash controls, compact canvas/properties controls and one Save and leave / Discard / Keep editing dialog. Saving remains distinct from publication and execution.
• Incident-only pairing uses an additive negotiated control/verification reverse grant, normal browser sign-in continuation, managed installation readiness, persistent producer adoption and an immediately usable tenant-owned Flow connector. Existing grants and credential owners retain their meanings.
• Dashboard counts distinct firing clients separately from occurrences, including acknowledged alerts, using authorized persisted state and bounded tables. Landing-page notification/watchlist duplication is removed.

Compatible pair: NetRatel 0.1.1-beta.3 and RatelDesk 0.1.1-beta.17. Upgrade RatelDesk then NetRatel before creating incident-only connections; existing links/history survive mixed-version rollout. No release tag, artifact or image has been published.

Selected validation: 166 renewal/resilience checks (12.559s); 22 Flow component/adapter checks (13.987s); seven monitoring page/picker checks; three monitoring rendered cases (17.579s); nine pairing browser cases (32.119s); atomic acknowledgement/history/legacy-wire/continuation regressions. Corrected authority/readiness recovery checks passed, as did optional-task readiness and dashboard aggregates (61.4s). Final native pointer/drop/save/reload/zero-edge deletion passed; the immediate-close unsaved-dialog regression passed in 8.656s. Final exact-head hosted checks are recorded below. Default CI retains fast assertions; full browser/native/deployment acceptance remains opt-in.

The cache/authority source defect is reproduced with separate clocks at subsecond and 30-second offsets. It is not yet a confirmed explanation of the supplied deployed Windows DataLoss logs. Backend log correlation, measured machine clock offset, Windows helper readiness and unexplained process replacement remain explicit owner checks.

Tracks #171; related work #138, #142, #143, #144, #145, #146, #164. Companion tracking: BostonTechnologies/rateldesk#136.

Bounded source/API exercise: both products activated an incident-only link, verified zero reverse business resources, adopted one ready Flow connector and reused it on duplicate completion. Save/validate/dry run and both authenticated Test connection actions left incident count at zero. Real telemetry persisted an occurrence and durable Flow run. Its delivery returned HTTP 500 (receiver-commit-unconfirmed) with no incident/receipt; the fixture lacked its normal notification-template bootstrap (an unconfirmed candidate for the HTTP 500), and the subsequent check was blocked by the genuine expired presence lease. The temporary rules were removed, Flows disabled, link revoked on both peers and owned fixtures stopped. Committed delivery/idempotent retry, reverse initiation and paired acknowledgement remain explicit acceptance checks; focused owning-layer regressions cover their contract/state behavior separately.

Normal deployed local/OIDC/hybrid approval, native execution and Windows machine/log checks remain manual. No credential reset, live proxy modification or release publication occurred.

Final source head: bd06ca19fbe5b0e77bc25f8f81c179cfe405336f. Required hosted validation passed: 3,719 tests, zero failures/skips (3,270 core + 35 API integration + 414 components). .NET 16m24s; whole workflow 17m08s, within the required 20-minute limit and above the 10–15-minute target. All three hosted MTP receipt gates, Release build and static/integrity checks passed.

The final narrow Flow fixture correction makes lookup/event dispatch atomic on the owning renderer; its 13 focused cases passed in 5.860s with unchanged assertions, and Slopwatch reported zero findings. Full browser/native/deployment checks remain opt-in; required integrity tests were retained.