CozyPanel 4.6.6 beta — account launch deadlock repair

Live verification found Page.addScriptToEvaluateOnNewDocument blocked while Fetch held an Instagram response. Cookie response handling now persists the per-space jar and updates network rules without calling renderer script-registration commands. New documents receive the latest non-HttpOnly jar through page-hello before gated fetch/XHR can send. This removes the blocked registration from the response path. Bootstrap queues are separate per tab/frame, Chrome commands have deadlines, and failure disconnects before opening recovery.

98 automated tests pass, including a blocked renderer-registration simulation, stale-cookie redirect handshake, a second launch during a stalled bootstrap, unanswered renderer notification, and timed-out navigation retaining stored account data. Tests use mocked Chrome APIs and do not establish authenticated platform support. Live Chrome verification: reloaded the existing extension (ID mgjdcnamcjkondophcnacgjfambnajbj); the adsa Instagram space reached its login form and mm reached Meta's verification URL instead of remaining blank. Neither completed authentication was verified. WhatsApp reached its platform URL during the initial bounded-launch check; other platforms were covered by automated routing tests only.

Existing v4.6.4 and v4.6.5 installation folders contain this repair, preserving extension IDs and stored spaces. Reload CozyPanel in chrome://extensions, then reopen its spaces. Do not remove the extension or clear storage.
