**Back off optional Proxmox permission-denied reads**
Keep typed HTTP 403 denials on the existing 30-minute APT and
five-minute guest-memory negative intervals, without promoting stale or
absent observations. Preserve successful clocks, independent target
scopes, ordinary transient retries and guest lifecycle/uncertainty
fences. Cover direct and cluster transports, expiry, recovery, zero
evidence and shared runtime separation.
Report and patch reference: Pulse #3546 by @tyvsmith; this candidate
implements the scoped repair from current source.
Reported-by: tyvsmith
**Keep Proxmox update recovery zeros explicit on the wire**
Consuming browser proof for #3546 exposed a connected recovery failure:
the canonical merge retained seven stale updates and its access reason
when a successful empty response omitted zero and empty fields. Emit the
complete existing count/status/reason/origin tuple for an explicit node
verdict, preserving guest and legacy payloads.
Register JSON merge, API/realtime and legacy controls with precise
ownership. This fixes the changed producer through the existing
consuming surface without a frontend, permission or cadence change.
**Keep SSO provider labels on complete UTF-8 boundaries**
Preserve the existing 128-byte cap without slicing a valid code point
into invented replacement characters. Keep trim/control order and
intentional replacement characters, and cover byte-boundary cases,
registered Community HTTP writes and persisted/list/detail/login
discovery, redaction, stable IDs and presentation-only runtime reuse.
Register the focused SSO management proof route.
Contract-Neutral: Restore valid UTF-8 within the existing 128-byte label
cap; API shapes, byte limit, trim/control rules, IDs, credentials,
authorisation and runtime-reuse contracts are unchanged.
**Keep SSO verification paths in canonical order**
The first composed source proof passed all 131 SSO/API race roots, vet
and the native consuming exporter, but the registry's sorted-path
invariant failed on the new SSO policy. Sort the same exact six proof
paths; preserve their scope and every runtime byte.
Contract-Neutral: Verification-path ordering only; runtime, API, proof
selection, contract and frontend content are unchanged.
---
Fleet candidate `20261030T064533Z-core-runtime` from the `core-runtime`
lane. Reviewed tip `3279b66588c06775ef6d5aab0a868d4e055a8602` on `main`.
[How Pulse handles
triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)
pulse-triage[bot]
be25170ee1