Owned ref boundary and browser errors

Reject a broken ref lifetime

A real Realtime attempt assigned callback refs inside an effect and invoked them from an intrinsic handler. Its build passed, but the browser could not connect because those refs were read-only. Kudzu now reports the authored source line and points to a state-driven effect with effect-local callbacks. The previously accepted WebSocket source retains eleven byte-identical deploy files and a JavaScript-free static sibling.

See caught browser failures

The optional repository browser smoke now reports caught Error objects logged to the console instead of marking that failed page as healthy. Plain string logs remain nonfatal. Chrome connection setup also waits for a complete DevTools port record; the exact cause of the older publication startup failure remains unproven.

Keep cost evidence honest

A Realtime diagnostic-only AI trial initially showed lower tokens at equal success, but its independent confirmation has four unknown timeout tails and a browser failure. No reliable model-token reduction or 1.0 acceptance is claimed. Generator 0.1.158 is unchanged.