Prefer a provisioned Lightpanda for qualified LinkedIn profile reads in v0.18.83

[0thernet]

Summary

• createBrowserSession accepts a browser-engine selection: "auto" resolves to Lightpanda only for cookie-yielding realms with an explicitly provisioned 1.0.0 executable, "chrome" keeps the existing lane, "lightpanda" requires both.
• The LinkedIn profile transport defaults to "auto" for its qualified reads — identity, personal stats, connections, organizations. Contact reads stay on Chromium (their overlay harvests live network requests bindings Lightpanda has not been proven to report); article/comment/post/feed/search and all other providers keep the unqualified Chromium default.
• Under durable cleanup admission, a CDP-attached Lightpanda session publishes prepared → launch-intent (never the Chromium control witness) and proves quiescence from daemon-observed inactivity after the owned serve child is reaped. "auto" with a publisher runs a throwaway preflight — spawn, open about:blank, one stdin cookie import, close, reap, production convergence proof — before the durable identity exists, so a protocol incompatibility still resolves to Chromium and a post-publish failure fails closed.
• Fallback is limited to a recognized LightpandaCompatibilityError raised before target navigation inside the original deadline; assertions, denials, identity drift, cleanup failures, and timeouts never fall back.
• Rebased onto current main (which had already shipped 0.18.80–0.18.82): version bump to 0.18.83 with changelog, skill/install docs, version-pinned surfaces, dist rebuild, and re-measured package budget (638 entries, 12,237,548 packed / 24,524,887 unpacked bytes, SHA-256 34a0261f…, byte-identical across two clean packs).

Validation

• Typecheck clean; focused suites green on the rebased tree: browser.test.ts 77, lightpanda-browser.test.ts 100, LinkedIn runtime/profile suites, admission tests — 260 tests in the combined focused run.
• test:npm-release 50 pass; verify:claims 142 pass; verify:oracles 35 pass; standalone package smoke green.
• Broad bun run check local run on the pre-rebase tree: 5231 pass / 62 fail — every failure triaged: concurrency-window flakes caused by a concurrent full check triggered by npm pack's prepack, missing native-derive fixture (provisioned since), and one fixture cold-start; all affected files verified green standalone afterward.
• Three independent review rounds; all majors fixed (cleanup-admission bind, AggregateError-wrapped compat, proxy leak, teardown under-bound, close-ack ordering, batch close exemption, abort-aware converge) and the final round found no blockers (one minor: one-shot rewrite flag consumed by stdin-free invokes — fixed with a regression test).
• Live publisher-enabled round trip verified: prepared → launch-intent → journal-quiescent → root-removal journals → private roots deleted; unprovisioned "auto" resolves to Chromium.
• Residual: one provider-200 LinkedIn read through the integrated path is pending — the saved session is dead across all transports (HTTP 401 identical), so re-authentication is required for that live evidence. Artifact admission does not depend on it.

Test plan

• Focused unit suites for engine selection, preflight, fallback, custody, cleanup journals, stdin secrecy
• Provider engine-forwarding and contact Chrome-pin tests
• Release-workflow and package-budget pins re-measured and green
• Live publisher round trip and unprovisioned fallback probe
• Required CI on this PR head
• Post-relogin provider-200 LinkedIn read through the integrated path (follow-up)

Generated with Devin

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
ghostget	Ready	Preview	Oct 5, 2026 8:31am UTC