Remote cleanup failures are accepted as successful shutdown and generation settlement

[Calmingstorm]

Severity: P2

Verified at v4.10.0, 55c15761845b00931ab2ea4aa184a7797dfd0614.

Locations

src/tools/process_manager.py:2351-2377,2508-2519,2544-2550,2584-2585; embedded controller:250-251

Failure scenario and affected installations

Remote job cleanup failure or already-exited response with unverified group. Shutdown increments killed despite failure string and skips process=None finalproof; generation accepts alreadyexited while failed followup poll ignored.

Verification

Independently traced discarded result/status and final skip. Reviewer mocked shutdown returned1 with jobrunning; alreadyexited+unknownpoll yielded terminate_generationtrue/statusrunning.

Correction and regression coverage

Consume structured proven cleanup verdicts for all remote paths, propagate unknown and do not count refusal/failure as killed. Not changing settled shutdown order.

Duplicate screening

Checked open/closed inventory and GitHub title/body search; no matching root. Harmless mocked operations/temporary data and complete source traces; no live processes killed, remote calls or service actions.

[Calmingstorm]

Validated as fixed on campaign/v4.10.0-review (PR #629) at 3047c46c: the fix was reviewed against the final code, and its regression tests pass on the branch and in CI. Round-1 correction 2b06c963: remote cleanup failures stay explicitly unknown and keep their execution authority, while verified-empty groups settle cleanly; transport failures remain unknown. It is not merged to master yet. Closing per the maintainer's instruction; reopen if a later change regresses it.