What Problem This Solves

Fixes an issue where reliability repairs proven during the v2026.7.1 release train existed only on the release branch, so later releases cut from main could regress Telegram delivery, aborted agent runs, installed CLI launchers, and Parallels update validation.

Why This Change Was Made

Forward-ports the six release fixes that remain applicable to main as exact cherry-picks, while excluding release-only version/changelog commits and fixes already superseded on main.

The changes:

• throttle Telegram reconnect delivery drains so queued updates do not starve normal replies;
• make session-lock acquisition abortable for cancelled agent runs;
• prefer an installed launcher's package root during CLI root discovery;
• allow Linux onboarding enough time to finish in Parallels;
• remove stale single-plugin allowlists from Windows update fixtures;
• preserve the Windows config shape during update validation.

User Impact

Telegram reconnects no longer monopolize delivery, cancelled runs stop while waiting for a session lock, installed launchers resolve their own package correctly, and the Linux/Windows Parallels release lanes validate realistic upgrades without fixture-induced failures.

Evidence

• OPENCLAW_TESTBOX=1 pnpm check:changed equivalent on Blacksmith Testbox tbx_01kww6211wc06mve8h0gwb4k9m: passed all selected typecheck, lint, boundary, import-cycle, database-first, and runtime guards.
• 249 focused tests passed on the same Testbox across Telegram polling, session locking/abort behavior, CLI root discovery, and Parallels Linux/Windows update behavior.
• Branch autoreview against origin/main: no actionable findings.
• git diff --check: clean.

AI-assisted: yes. The maintainer reviewed the selected release commits and the branch was validated against current main.