Keep guest-agent continuity guard aligned with backup deferral

The real-client backup lifecycle passes, but the old source guard still requires its unguarded status-failure fallback. Retain continuity only when no operation lock is present; the connected lifecycle covers both cached fallback and unlock resumption.

Contract-Neutral: Test assertion follows the already documented backup-lock condition; no additional runtime or contract change.
Change-source: pulse-maintainer
This commit is contained in:
pulse-triage[bot]
2026-10-03 14:08:53 +01:00
parent 2df28d5877
commit 577e40edf3
@@ -1913,7 +1913,7 @@ func TestProxmoxGuestAgentContinuityUsesCanonicalEvidenceAndRetryPaths(t *testin
"monitor_pve_guest_builders.go": {
"guestAgentAvailable := shouldQueryGuestAgent(state.detailedStatus, prevVM, now) ||",
"m.hasRecentGuestMetadataEvidence(instanceName, res.Node, res.VMID, now)",
"if guestAgentAvailable && state.detailedStatus == nil {",
`if guestAgentAvailable && res.Lock == "" && state.detailedStatus == nil {`,
},
"monitor_polling_vm.go": {
"prevVMByID := prevGuests.vmsByID",