0.9.2 — Lightpanda opt-in fixes

Lightpanda opt-in fixes

Chrome remains the default; install Lightpanda separately and explicitly select --engine lightpanda on a fresh launch.

• Engine changes now use the existing managed fresh-session recovery instead of replacing an active managed browser's page in place.
• Positively identified Lightpanda images remain verified attachments, labelled rendering: "text" with unknown geometry—not graphical layout or CSS/mouse-coordinate evidence.
• CLI/environment/native-config Lightpanda selection omits wrapper-supplied Chrome profile/executable bootstrap defaults. Caller-selected commands, paths, sessions, config, launch arguments and environment retain native semantics.

No browser bundle, new driver, engine cache, authorization gate or automatic Chrome fallback. The command guide documents single-target, graphical, authentication, native-command, CORS, platform and telemetry limits.

Requires Node 24.21.0+, Pi 1.0.0+ and separately installed agent-browser (stable floor 0.35.0; recommended 0.38.1).

Qualification

PR #256 records the 2026-10-04 final-source evidence: three reviewer approvals; independent locked/latest official and maintained-fork host checks; configured-source tmux reload/exact-ID relaunch; canonical 12/12 Native lifecycle Linux; real-upstream contracts and native geometry; local macOS alternate and Ubuntu platform/consumer suites; actual regular/fullscreen checkout live-site and selected-image model proof; and the retained runtime-only SDK/CLI-smoke-tested npm artifact. All five automatic PR checks passed, including the hosted review with no new findings.

The published artifact is the exact retained smoke-tested tarball, not a repack. SHA-256: 3ed2079ed1f1465001c9325d05430d1f2ef495d2f7845e893bc56358b1962fdd. Validated source commit 6314fcb361d6361a5bff081fd2a62064066138b2 and release merge commit 074af0510204b562f1efd1ff533ed4976bf699d7 have identical source tree 476f915b0532df8bc05ac115a1f574f38c27d15d.

Windows is explicitly owner-waived, not passed. Local macOS evidence is not Crabbox SSH. Individual required checks and the waiver are recorded; the Windows-inclusive composed release gate is not claimed green. Runtime activation is separate from publication—restart participating Pi processes when adopting the update.

Post-publication verification — 2026-10-04

The public registry tarball was downloaded and verified byte-for-byte against the retained artifact above. Isolated global exact-version installs and real unpinned 0.9.1 → 0.9.2 updates passed independently on latest official Pi 1.0.2 and the maintained fork 1.0.2; all installed compiled files matched the published artifact, and native SDK/actual CLI loading passed.

Both hosts also passed published-package-only interactive browser/model smokes (official regular mode, fork fullscreen): Chrome React and Lightpanda Example open/snapshot/code-selected image, plus both session closes. Each host returned eight successful native results. Actual Pi image-block bytes matched the saved PNGs, and an image-capable model and parent inspection confirmed the visual content. Chrome geometry stayed measured; Lightpanda stayed text-rendered with unknown geometry and no coordinate mapping.

Owned test processes, private copied credentials, PNGs, sockets, isolated toolchains/installations and the temporary tarball were removed after proof; manifests, hashes and Pi/subagent evidence were retained. The operator's working runtime and installed extension were not updated or activated. Windows remains owner-waived, not passed.