Prevent idle owner eviction from stranding bot work and publication

[d3cker]

A bot can finish implementation in its worktree after OpenCode has evicted the idle primary checkout. The dispatcher then disappears, owner reactivation can fail with a held lock, and worker hooks fail with unavailable automation RPC instead of allowing publication or subsequent messages.

Refresh each scheduler/dispatcher owner every 30 seconds through the public plugin-list API, only after verifying that the discovered service PID matches the current process. Heartbeat requests have a deadline, do not overlap, stop on cleanup, and retry transient failures. Standalone instances skip a different or missing background service.

Make scheduler/dispatcher cleanup settle work and attempt every disposal step, including bridge removal and lock release, even when an evicted SDK registration rejects disposal. No active locks are forcibly removed and no failed session is automatically treated as successful. Update operational and runtime documentation.

Validation:

• npm run check: lint, typecheck, 120 tests, and build passed.
• npm run package:check: packaged installation passed.
• Six new lifecycle regression tests cover cleanup failures with real lock reacquisition, service PID isolation, overlapping requests, cancellation, and transient retries.
• Deployed the compiled hotfix on the affected OpenCode background service. The owner stayed active for over seven minutes without the prior idle eviction; explicit owner eviction followed by reactivation also succeeded without a lock error.
• The original failed worktree session accepted a recovery acknowledgement and finished successfully after repair. Its source changes were separately backed up, verified, pushed, and recovered into a draft PR without rerunning implementation.

Release: package.json and package-lock.json are bumped to 0.6.2. Tag v0.6.2 points to the version commit and triggers the existing release workflow. The 0.6.2 package installation check also passed locally.