Skip to content

Mark the Lightpanda capture plan completed with v0.18.83 delivery #561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0thernet merged 1 commit into from
Oct 5, 2026
Merged

Mark the Lightpanda capture plan completed with v0.18.83 delivery #561

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 14 additions & 11 deletions kb/plans/lightpanda-semantic-capture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
type: plan
area: browser-verification
status: in-progress
status: completed
---

# Prefer provisioned Lightpanda for public semantic capture
Expand Down Expand Up @@ -221,16 +221,19 @@ Lightpanda reads is not supported by the evidence.
- Delivered and verified: Lightpanda-first public semantic capture in
Ghostget `v0.18.79` and Direct `v0.7.29`, released, mirrored
byte-exact on npm, and promoted to production.
- LinkedIn authenticated Lightpanda reads: **qualified for identity,
personal stats, connections, and organization reads.** Live adapter
evidence covered identity, profile HTML, and connections HTML on real
auth; unit tests cover engine selection, fallback, custody, and
seeding. The profile transport defaults to `"auto"` — Lightpanda
first for cookie-yielding realms with a provisioned binary, Chromium
otherwise. Contact reads stay on Chromium pending live
network-request-observation evidence. This contradicts the adapter
note's earlier finding for that realm: a bound `cookie-source`
handoff is accepted where whole-profile reuse is impossible.
- LinkedIn authenticated Lightpanda reads shipped in `v0.18.83`
(PR #560, merge `0137e55b`, immutable GitHub Release with the
five-file contract, npm `0.18.83` admitted): **qualified for
identity, personal stats, connections, and organization reads.**
Live adapter evidence covered identity, profile HTML, and
connections HTML on real auth; unit tests cover engine selection,
fallback, custody, and seeding. The profile transport defaults to
`"auto"` — Lightpanda first for cookie-yielding realms with a
provisioned binary, Chromium otherwise. Contact reads stay on
Chromium pending live network-request-observation evidence. This
contradicts the adapter note's earlier finding for that realm: a
bound `cookie-source` handoff is accepted where whole-profile reuse
is impossible.
- Residual live gap: the integrated session path (including durable
cleanup admission) is now mechanically green — a publisher-enabled
Lightpanda session published, journaled, and removed every private
Expand Down
Loading