Add Windows MXC lifecycle recovery and exact cleanup

Part of #8178.

This task completes the lifecycle behavior required by the accepted OpenClaw technical-preview candidate. It does not activate MXC or add Hermes support.

## Outcome

NemoClaw can stop, recover, destroy, and reconcile the accepted Windows OpenClaw process-container workload using immutable provider authority and exact cleanup evidence.

## Delivery state

Dormant lifecycle, recovery, and cleanup integration.

## Dependencies

- Blocked by #10585 and acceptance of the restart, orphan, concurrency, and privilege boundaries.
- May proceed in parallel with #10586 and #10587.
- Contributes to the protected E2E and activation gate.

## Deliverables

- Implement the accepted status, stop, destroy, failed-create recovery, restart reconciliation, and orphan behavior through provider-owned surfaces.
- Stop the complete process tree and sandbox-scoped forwarding resources.
- Revalidate exact provider, sandbox, lifecycle generation, and ownership authority before destructive cleanup.
- Report unsupported snapshot, restart, concurrency, or privilege behavior through typed capability results.

## Acceptance evidence

- Allowed: exact owned workload stops and destroys with process, registry, forward, and artifact absence confirmed.
- Denied: missing, stale, shared, reused, or drifted ownership blocks destructive cleanup.
- Ambiguous: controller restart or transport loss reconciles before mutation and never assumes absence.
- Failure or recovery: partial cleanup reports each retained resource and a bounded recovery action.

## Security and authority boundaries

- Destructive operations require exact immutable ownership authority.
- Elevated host operations must be limited to the accepted OpenShell/MXC broker boundary.
- Cleanup must not use broad names, process patterns, directories, or provider fallbacks.

## Test plan

- Focused lifecycle, recovery, cleanup, identity-drift, ambiguity, idempotency, and privilege tests.
- Physical stop, restart, failed-create, destroy, and absence checks against the accepted profile.

## Deferred scope

- Hermes `isolation_session`, snapshot and restore unless accepted, GPU, and activation.

## Stop conditions

- Stop if restart, orphan, concurrency, or privilege ownership remains undefined.
- Stop if cleanup cannot prove exact ownership and final absence.

## Completion evidence

- Link the implementation PR, exact merged commit, accepted lifecycle contract, focused tests, and sanitized physical evidence. One same-repository PR should close this issue.