@hraness/ghostget 0.18.0 → 0.18.3

package/CHANGELOG.md

@@ -7,6 +7,321 @@ Historical entries retain their original delivery coordinates.
 
 ## Unreleased
 
+## 0.18.3
+
+- Apply the shared Lantern material to the homepage: luminous grid glass behind
+  the hero, a blurred header, warm open questions, and opaque reading surfaces.
+  Preserve clean marks, ordinary documentation, and the inert native preview.
+
+- Click the unique reviewed Contact info control when the page-bound
+  NavigateToScreen extract is `absent` after adapter 1.36.2. Operator
+  smoke on 2026-09-12 was green for Email on tessbloch through DIRECT
+  transport that clicked after an absent extract, using the reviewed
+  ProfileContactDetailsOverlay `sduiid` and headed clientArguments
+  (bound vanity, optional givenName/familyName from profile HTML,
+  `isVanityNameResolved`, nested requestMetadata
+  states/screenId/knownTemplates, `isModal` true). Official
+  `contacts.read` still fell through that absent extract to GraphQL
+  or the vanity overlay GET (broken 500/HTML-shell path). The
+  contained path now uses the same click and modal snapshot as a
+  present action. It still does not mint a navigation POST or track
+  headers. Zero or two-plus controls and a missing or ambiguous
+  modal still fail closed. GraphQL 403 and vanity HTML-shell
+  honesty stay unused once that click is selected. Soft-labels
+  stay. Self, non-first-degree, and contradictory distances still
+  fail closed, and no email is invented. Adapter bundle 1.36.3.
+  This is the seventeenth live Contact-info drift after the 1.36.2
+  overlay pathname bind. Cloud has no signed-in LinkedIn session;
+  do not treat this landing as live green. Operator smoke:
+
+  ```sh
+  printf '%s' '{"profile_url":"https://www.linkedin.com/in/tessbloch/"}' \
+    | ghostget invoke linkedin-web contacts.read --input - --auth linkedin-main --json
+  ```
+
+- Keep the unique reviewed Contact info click bound after adapter
+  1.36.1 when contained Chrome follows the live vanity overlay path.
+  Operator smoke on 2026-09-12 clicked that unique control, then
+  fail-closed because pathname left `/in/tessbloch/` for
+  `/in/tessbloch/overlay/contact-info/`. Headed proof the same day
+  still showed Email in the modal. After click, the contained path now
+  treats the exact bound profile pathname or that reviewed vanity
+  overlay pathname as still bound, then snapshots the unique dialog.
+  Authwall, other origins, and any other path still fail closed. Zero
+  or two-plus controls and a missing or ambiguous modal still fail
+  closed. It still does not mint a navigation POST or track headers.
+  GraphQL 403, minted navigation GETs, vanity HTML-shell honesty, and
+  embedded-field projection stay. Soft-labels stay. Self,
+  non-first-degree, and contradictory distances still fail closed, and
+  no email is invented. Adapter bundle 1.36.2.
+  This is the sixteenth live Contact-info drift after the 1.36.1
+  overlay-href click. Cloud has no signed-in LinkedIn session; do
+  not treat this landing as live green. Operator smoke:
+
+  ```sh
+  printf '%s' '{"profile_url":"https://www.linkedin.com/in/tessbloch/"}' \
+    | ghostget invoke linkedin-web contacts.read --input - --auth linkedin-dormant-20260911 --json
+  ```
+
+## 0.18.2 - 2026-09-12
+
+- Apply the shared editorial typography, textured background and blurred header
+  to the homepage. Keep logos sharp, phone navigation on one row, and documentation
+  and inert native examples in their existing layouts.
+- Correct canonical archive-size limits for bundled messaging helpers.
+
+- Allow the unique reviewed Contact info control to open the live
+  LinkedIn SPA modal after adapter 1.36.0. Operator smoke on
+  2026-09-12 found that unique control on tessbloch, then fail-closed
+  before click because its href matched `/overlay/contact-info/`.
+  Headed proof the same day showed Email in that modal after click.
+  The contained path now clicks that unique accessible name even when
+  the href is the vanity overlay GET. Zero or two-plus controls and a
+  missing or ambiguous modal still fail closed. It still does not mint
+  a navigation POST or track headers. GraphQL 403, minted navigation
+  GETs, vanity HTML-shell honesty, and embedded-field projection stay.
+  Soft-labels stay. Self, non-first-degree, and contradictory
+  distances still fail closed, and no email is invented. Adapter bundle 1.36.1.
+  This is the fifteenth live Contact-info drift after the 1.36.0
+  Contact info click. Cloud has no signed-in LinkedIn session; do
+  not treat this landing as live green. Operator smoke:
+
+  ```sh
+  printf '%s' '{"profile_url":"https://www.linkedin.com/in/tessbloch/"}' \
+    | ghostget invoke linkedin-web contacts.read --input - --auth linkedin-dormant-20260911 --json
+  ```
+
+- Click the unique reviewed Contact info control on an already-loaded
+  1st-degree LinkedIn profile and project Email from that modal after
+  adapter 1.35.0. Operator headed proof on 2026-09-12 showed Email in
+  the modal DOM. Contained synthetic navigation POST still returned
+  HTTP 500 `text/html` after the exact headed body and observed X-Li
+  set. The contained path now opens that profile, binds a unique
+  page-instance, clicks only the exact accessible name `Contact info`,
+  snapshots the unique dialog, and projects Email from that HTML. Zero
+  or two-plus controls, an overlay GET href, or a missing modal fail
+  closed. It does not mint a navigation POST or track headers.
+  GraphQL 403, navigation GETs, vanity HTML-shell honesty, and
+  embedded-field projection stay. Soft-labels stay. Self,
+  non-first-degree, and contradictory distances still fail closed, and
+  no email is invented. Adapter bundle 1.36.0.
+  This is the fourteenth live Contact-info drift after the 1.35.0
+  observed-header bind. Cloud has no signed-in LinkedIn session; do
+  not treat this landing as live green. Operator smoke:
+
+  ```sh
+  printf '%s' '{"profile_url":"https://www.linkedin.com/in/tessbloch/"}' \
+    | ghostget invoke linkedin-web contacts.read --input - --auth linkedin-dormant-20260911 --json
+  ```
+
+- Copy already-observed LinkedIn `contacts.read@1` rsc-action
+  `x-li-page-instance-tracking-id`, `x-li-pageforestid`,
+  `x-li-traceparent`, `x-li-tracestate`, and optional
+  `x-li-layout-tree` onto the Contact-info overlay POST after adapter
+  1.34.0. Live peel after that bind kept the headed nested body and
+  forwarded page-instance, track (`mpName=web`), application
+  version/instance, anchor page key, and `rscStream=true`, but contained
+  Chrome still returned HTTP 500 `text/html`. The same profile-wait
+  `/flagship-web/rsc-action/` observations already carried those
+  tracking and trace names; 1.34.0 left them off as headed-only. The
+  contained path now copies the original strings from the same selected
+  same-origin rsc-action observation under a reviewed allowlist, prefers
+  that rsc-action bind, and omits a name when that observation lacks it.
+  It does not mint tracking IDs, traces, pageforest, or layout-tree.
+  Missing or malformed observed values fail closed before POST. Headed
+  successful body Content-Length was 400; compact emit at 398 stays.
+  GraphQL 403, navigation GETs, vanity HTML-shell honesty,
+  `sduiid=screenId`, the headed nested body, and prior page-derived
+  copies stay. Soft-labels stay. Self, non-first-degree, and
+  contradictory distances still fail closed, and no email is invented.
+  Adapter bundle 1.35.0.
+  This is the thirteenth live Contact-info drift after the 1.34.0
+  page-derived header bind. Cloud has no signed-in LinkedIn session; do
+  not treat this landing as live green. Operator smoke:
+
+  ```sh
+  printf '%s' '{"profile_url":"https://www.linkedin.com/in/tessbloch/"}' \
+    | ghostget invoke linkedin-web contacts.read --input - --auth linkedin-dormant-20260911 --json
+  ```
+
+- Bind LinkedIn `contacts.read@1` Contact-info navigation POST to the
+  already-loaded profile document after adapter 1.33.0. Live peel of the
+  headed nested `payload.requestMetadata` body matched byte-for-byte,
+  but contained Chrome still returned HTTP 500 `text/html` because that
+  POST ran from the signed-in origin fetch context with only `Accept`,
+  `Content-Type`, and session `csrf-token`. Headed success also sent
+  page-instance and the other X-Li names from the profile SPA. The
+  contained path now opens the exact reviewed profile URL, waits for
+  that document, and copies a unique `d_flagship3_profile*`
+  `x-li-page-instance` plus optional `x-li-track` (`mpName` `web` or
+  `voyager-web`), `x-li-application-version`,
+  `x-li-application-instance`, `x-li-anchor-page-key`, and
+  `x-li-rsc-stream=true` from observed same-origin rsc-action or
+  voyager requests, or page-instance from the loaded document. It does
+  not mint `traceparent`, `tracestate`, `pageforest`,
+  page-instance-tracking-id, or layout-tree; those headed-only values
+  stay blockers if LinkedIn still 500s after the reviewed copies. Live
+  query key stays `sduiid=` (headed 200 plus public SDUI routes);
+  `sduid=` notes are transcription typos. Missing or ambiguous
+  page-instance fails closed before POST. GraphQL 403, navigation GETs,
+  vanity HTML-shell honesty, `sduiid=screenId`, and the headed nested
+  body stay. Soft-labels stay. Self,
+  non-first-degree, and contradictory distances still fail closed, and
+  no email is invented. Adapter bundle 1.34.0.
+  This is the twelfth live Contact-info drift after the 1.33.0 nested
+  body. Cloud has no signed-in LinkedIn session; do not treat this
+  landing as live green.
+
+## 0.18.1 - 2026-09-12
+
+- Add the owner messaging automation protocol for iMessage and WhatsApp:
+  exact conversation enrollment, revocable action grants, durable event cursors,
+  bounded history, admitted attachment bytes, and ordered send receipts. Importing
+  the eighth public SDK entrypoint performs no account or network work.
+- Bundle reviewed private iMessage and wacli helpers with pinned bytes, source
+  patches, resources, and licenses. Installation starts no provider and changes
+  no macOS security settings. WhatsApp synchronization requires an explicit owner
+  action and keeps each outgoing action to one dispatch attempt.
+- Expose text, files, reactions, stickers, links, and polls when the selected
+  provider and its managed permissions support them. Automated iMessage link
+  cards skip helper metadata/image fetching. Native rich iMessage actions require
+  an already-working private bridge; its upstream setup requires disabled SIP.
+  App Clips and arbitrary mini-app experiences remain unavailable. Offline checks
+  do not establish real account pairing or message delivery.
+- Nest LinkedIn `contacts.read@1` Contact-info `requestMetadata` under
+  `payload` after adapter 1.32.0. Live peel of sibling `proto.sdui`
+  types succeeded, but the POST still returned HTTP 500 `text/html`
+  because the body sent empty sibling `RequestMetadata{$type}` and
+  omitted headed children `states`, `screenId`, and `knownTemplates`.
+  Headed 200 Email capture
+  `POST-navigation-body-shape-20260912.md` keeps
+  `clientArguments.$type`, `requestedStateKeys: []`, and nested
+  `payload.requestMetadata` with `$type`, `states: []`, overlay
+  `screenId`, and `knownTemplates: []`. The builder now emits that
+  exact headed shape, including when dormant HTML omits metadata, and
+  copies reviewed string lists when the page already has them. Empty
+  arrays and the two reviewed `proto.sdui` `$type` values come from
+  that capture, not invented opaque state. Extra keys, object-valued
+  states, and unrelated proto prefixes still fail closed. GraphQL 403,
+  navigation GETs, vanity HTML-shell honesty, and `sduiid=screenId`
+  stay. Contained Chrome already sends `Accept: */*`,
+  `Content-Type: application/json`, and session `csrf-token` for this
+  POST; it does not mint `X-Li-*` track values. Soft-labels stay.
+  Self, non-first-degree, and contradictory distances still fail
+  closed, and no email is invented. Adapter bundle 1.33.0.
+  This is the eleventh live Contact-info drift after the 1.32.0 sibling
+  peel. Cloud has no signed-in LinkedIn session; do not treat this
+  landing as live green.
+- Fix LinkedIn `contacts.read@1` Contact-info navigation POST body after
+  adapter 1.31.0. Live 1st-degree bind still succeeded, but building
+  `clientArguments` from NavigateToScreen failed closed on
+  `unreviewed-client-arguments` keys=`["requestMetadata"]` because live
+  HTML keeps `requestMetadata` a sibling of `payload` under
+  `requestedArguments`, and `$type` uses `proto.sdui.*`
+  (`RequestedArguments`, `RequestMetadata`). A payload-only POST then
+  returned HTTP 500. The operation now copies that reviewed sibling
+  shape, lifts headed nested `payload.requestMetadata` to the sibling
+  placement, and admits `proto.sdui.*` types only on this overlay POST
+  body. Extra keys and unrelated proto prefixes still fail closed.
+  GraphQL 403, navigation GETs, vanity HTML-shell honesty, and
+  sduiid=screenId stay. Soft-labels stay. Self, non-first-degree, and
+  contradictory distances still fail closed, and no email is invented.
+  Adapter bundle 1.32.0. This is the tenth live Contact-info drift after
+  the 1.31.0 navigation POST. Cloud has no signed-in LinkedIn session;
+  do not treat this landing as live green.
+- Read LinkedIn `contacts.read@1` Contact-info Email from the headed
+  ProfileContactDetailsOverlay navigation POST after 1st-degree bind.
+  Operator Chrome showed Email in the Contact-info modal; the first
+  response that contained the Email label was POST
+  `/flagship-web/rsc-action/actions/navigation?screenId=…ProfileContactDetailsOverlay&sduiid=…ProfileContactDetailsOverlay`
+  with JSON `{ clientArguments, isModal }` and an RSC
+  `application/octet-stream` flight. Headed capture bound `sduiid` to
+  the same overlay `screenId` constant, not a per-session mint.
+  Dormant profile HTML NavigateToScreen exposes `pageKey`
+  `profile_view_base_contact_details` and
+  `requestedArguments.payload` (`vanityName`, `givenName`,
+  `familyName`, `isVanityNameResolved`) but omits `sduiid`; the
+  operation still POSTs that exact allowlisted URL after 1st-degree
+  bind and peels reviewed payload keys without inventing `$type`,
+  `requestMetadata`, or a stolen id. A different `sduiid` fails
+  closed. GraphQL Contact-info stays 403 `text/html`, navigation
+  overlay GETs stay 500-rejected, and the vanity overlay GET remains
+  HTML-shell honesty when no Contact-info NavigateToScreen is present.
+  Soft-labels stay. Self, non-first-degree, and contradictory
+  distances still fail closed, and no email is invented.
+  Adapter bundle 1.31.0. This is the ninth live Contact-info drift after
+  the 1.30.0 overlay-shell honesty path. Cloud has no signed-in LinkedIn
+  session; do not treat this landing as live green.
+- Keep LinkedIn `contacts.read@1` honest when GraphQL Contact-info stays HTTP
+  403 `text/html` and the vanity `/in/:publicIdentifier/overlay/contact-info/`
+  GET returns an HTML-200 profile shell with no Email. Dormant contained
+  Chrome cannot mint the client-filled Contact-info modal from GET-only
+  RSC or HTML. An HTML shell now fails as omitted Contact-info fields
+  after 1st-degree binding, not as a JSON-object parse. Overlay HTML that
+  still carries Como Email, a unique mailto, or an RSC/SDUI flight still
+  projects. `/flagship-web/rsc-action/actions/navigation` overlay GETs stay
+  rejected. Self, non-first-degree, and contradictory distances still fail
+  closed, and no email is invented. Adapter bundle 1.30.0. This is the eighth live
+  Contact-info drift after the 1.29.0 vanity overlay.
+- Read LinkedIn `contacts.read@1` Contact-info email from the exact vanity
+  `/in/:publicIdentifier/overlay/contact-info/` RSC GET when GraphQL
+  `voyagerIdentityDashProfileContactInfo` is unavailable. Live dormant
+  sessions still bind 1st-degree distance, but the 1.28.0
+  `/flagship-web/rsc-action/actions/navigation` overlay GET returns HTTP
+  500 `application/octet-stream`, GraphQL still returns HTTP 403
+  `text/html`, and long SDUI strings in profile HTML aborted the
+  best-effort embedded walk at profile stage. The operation now skips
+  non-bounded field labels during that walk and GETs the live HTML-200
+  vanity overlay path with RSC browser binding. ScreenId-only and
+  `profileUrn`-bound navigation overlay URLs, other RSC screens, and
+  writes stay rejected. Self, non-first-degree, and contradictory
+  distances still fail closed, and no email is invented. Adapter bundle 1.29.0. This is the seventh live
+  Contact-info drift after the 1.28.0 navigation overlay.
+- Read LinkedIn `contacts.read@1` Contact-info email from the target-bound
+  ProfileContactDetailsOverlay RSC navigation when GraphQL
+  `voyagerIdentityDashProfileContactInfo` is unavailable. Live dormant
+  Chrome and Arc sessions still bind 1st-degree distance from profile HTML,
+  but Contact-info GraphQL returns HTTP 403 `text/html` and the page embeds
+  no queryId. The operation now GETs the overlay with exact `screenId` plus
+  `profileUrn` when queryId is absent, or after that reviewed GraphQL
+  rejection, and projects Email plus Connected since from the RSC or SDUI
+  payload. ScreenId-only overlay URLs, other RSC screens, and writes stay
+  rejected. Self, non-first-degree, and contradictory distances still fail
+  closed, and no email is invented. Adapter bundle 1.28.0. This is the sixth
+  live Contact-info drift after the 1.23.0 flight-array parse, the 1.24.0
+  deep-walk / `vieweeProfileId` join, the 1.25.0 `vieweeMemberUrn` distance
+  join, the 1.26.0 multi-escaped peel, and the 1.27.0 non-flight string-slot
+  bootstrap.
+- Read LinkedIn `contacts.read@1` first-degree distance from non-flight Como
+  rehydration string slots. Live pages after adapter 1.26.0 still bound
+  identity through `vieweeProfileId` plus vanity, but `networkDistance` and
+  paired `vieweeMemberUrn` sat in a Como array string that was not an RSC
+  flight. `decodeComoRehydrationValue` dropped that slot before the 1.26.0
+  peel could run. Non-flight string slots now go through
+  `decodeStringBootstrap`. True RSC flights still use
+  `decodeRscFlightRecords`. Self, non-first-degree, and contradictory
+  distances still fail closed, and no email is invented. Adapter bundle 1.27.0.
+  This is the fifth live Contact-info drift after the 1.23.0
+  flight-array parse, the 1.24.0 deep-walk / `vieweeProfileId` join, the
+  1.25.0 `vieweeMemberUrn` distance join, and the 1.26.0 multi-escaped peel.
+- Read LinkedIn `contacts.read@1` first-degree distance from multi-escaped Como
+  PROFILE_VIEW breadcrumb rows. Live pages after adapter 1.25.0 still bound
+  identity through `vieweeProfileId` plus vanity, but `networkDistance` and
+  paired `vieweeMemberUrn` sat in string rows such as `networkDistance\":1`.
+  The binder now peels JSON string escapes and accepts those escaped key/value
+  forms. Object, flight-array, and lightly escaped breadcrumbs still bind.
+  Self, non-first-degree, and contradictory distances still fail closed, and
+  no email is invented. Adapter bundle 1.26.0. This is the fourth live
+  Contact-info drift after the 1.23.0 flight-array parse, the 1.24.0 deep-walk
+  / `vieweeProfileId` join, and the 1.25.0 `vieweeMemberUrn` distance join.
+- Join LinkedIn `contacts.read@1` first-degree distance when identity comes from
+  `vieweeProfileId` plus vanity and `networkDistance` sits on a PROFILE_VIEW
+  breadcrumb or `vieweeMemberUrn` record, including a member id or a different
+  `fsd_profile` encoding than the bound URN. Self, non-first-degree, and
+  contradictory distances still fail closed, and no email is invented.
+  Adapter bundle 1.25.0. This is the third live Contact-info drift after the
+  1.23.0 flight-array parse and the 1.24.0 deep-walk / `vieweeProfileId` join.
+
 ## 0.18.0 - 2026-09-11
 
 - Add a macOS-first Tauri control panel for accounts, semantic capabilities,

package/README.md

@@ -21,7 +21,7 @@ Bring the model, planner, and tool loop you prefer. Ghostget supplies precise we
 capabilities with local custody and explicit evidence. Its native macOS control
 panel manages accounts, operation permissions, human approvals, editable OpenAPI
 interfaces, and a searchable local web request log. See the
-[control panel guide](docs/control-panel.md) and [native source build](https://github.com/hraness/ghostget/blob/v0.18.0/desktop/README.md).
+[control panel guide](docs/control-panel.md) and [native source build](https://github.com/hraness/ghostget/blob/v0.18.3/desktop/README.md).
 
 The separate public web gateway admits exact HTTPS retrieval URLs under human
 domain and path rules. Use `ghostget web request <url>` with the app open, and
@@ -51,7 +51,7 @@ ghostget plugin list
 
 ## Built-in provider catalog
 
-This v0.18.0 source tree supports executable actions for 20 services: Beeper,
+This v0.18.3 source tree supports executable actions for 20 services: Beeper,
 Bluesky, ClasificadosOnline, Facebook, Facebook Groups, Facebook Marketplace,
 GitHub, Gmail, Hacker News, Instagram, iMessage, LinkedIn, Reddit, Substack,
 Threads, TikTok, Twitch, WhatsApp, X, and YouTube.
@@ -116,7 +116,7 @@ owns the narrow capability boundary that can sit beneath them.
 Wrench is now Ghostget. The package name is `@hraness/ghostget`, and the CLI
 command is `ghostget`. Read the [migration guide](docs/ghostget-migration.md)
 before updating an existing installation. After its optional npm mirror is
-verified public, `@hraness/ghostget@0.18.0` is also available from the registry.
+verified public, `@hraness/ghostget@0.18.3` is also available from the registry.
 
 This README describes the package version in this source tree. Its versioned
 GitHub archive and Agent Skill become a supported public release after the
@@ -127,9 +127,9 @@ The optional npm mirror can follow later without delaying canonical delivery.
 Install the single Ghostget Agent Skill with either runner:
 
 ```sh
-npx skills add hraness/ghostget#v0.18.0
+npx skills add hraness/ghostget#v0.18.3
 # or
-bunx skills add hraness/ghostget#v0.18.0
+bunx skills add hraness/ghostget#v0.18.3
 ```
 
 The skill teaches Codex, Claude Code, Cursor, and other compatible coding
@@ -139,7 +139,7 @@ install the CLI if it is missing. Start a new agent session after installation.
 After the matching immutable Release exists, install this exact canonical archive:
 
 ```sh
-bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.0/hraness-ghostget-0.18.0.tgz
+bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.3/hraness-ghostget-0.18.3.tgz
 ghostget adapter sync-bundled --json
 ghostget doctor
 ```
@@ -167,7 +167,7 @@ For that same released coordinate, install Ghostget in an agent or application
 that owns its own model, planning, tool loop, approvals, and interface:
 
 ```sh
-bun add https://github.com/hraness/ghostget/releases/download/v0.18.0/hraness-ghostget-0.18.0.tgz
+bun add https://github.com/hraness/ghostget/releases/download/v0.18.3/hraness-ghostget-0.18.3.tgz
 ```
 
 ```ts

package/dist/apple-photos-client.js

@@ -1,11 +1,12 @@
 // @bun
 import {
   GHOSTGET_VERSION
-} from "./index-9wca02er.js";
+} from "./index-cnbz0gws.js";
 import {
   canonicalJson,
   sha256
 } from "./index-gwk7rbyj.js";
+import"./index-z1w83f81.js";
 
 // src/apple-photos-client.ts
 import { spawnSync } from "child_process";

package/dist/beeper-client.js

@@ -4,11 +4,12 @@ import {
 } from "./index-26yq8q16.js";
 import {
   GHOSTGET_VERSION
-} from "./index-9wca02er.js";
+} from "./index-cnbz0gws.js";
 import {
   canonicalJson,
   sha256
 } from "./index-gwk7rbyj.js";
+import"./index-z1w83f81.js";
 
 // src/beeper-client.ts
 import { spawnSync } from "child_process";

package/dist/client.js

@@ -9,6 +9,7 @@ import {
   canonicalJson,
   sha256
 } from "./index-gwk7rbyj.js";
+import"./index-z1w83f81.js";
 
 // src/client.ts
 import { spawn, spawnSync } from "child_process";