@hraness/ghostget 0.18.2 → 0.18.3

package/CHANGELOG.md

@@ -7,6 +7,38 @@ 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

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.2/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.2 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.2` 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.2
+npx skills add hraness/ghostget#v0.18.3
 # or
-bunx skills add hraness/ghostget#v0.18.2
+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.2/hraness-ghostget-0.18.2.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.2/hraness-ghostget-0.18.2.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,7 +1,7 @@
 // @bun
 import {
   GHOSTGET_VERSION
-} from "./index-hfbygww8.js";
+} from "./index-cnbz0gws.js";
 import {
   canonicalJson,
   sha256

package/dist/beeper-client.js

@@ -4,7 +4,7 @@ import {
 } from "./index-26yq8q16.js";
 import {
   GHOSTGET_VERSION
-} from "./index-hfbygww8.js";
+} from "./index-cnbz0gws.js";
 import {
   canonicalJson,
   sha256

package/dist/{index-hfbygww8.js → index-cnbz0gws.js}

@@ -1,5 +1,5 @@
 // @bun
 // src/version.ts
-var GHOSTGET_VERSION = "0.18.2";
+var GHOSTGET_VERSION = "0.18.3";
 
 export { GHOSTGET_VERSION };

package/docs/control-panel.md

@@ -9,7 +9,7 @@ and capabilities refresh when you return to the app, after changes made in the
 app, or when you choose Refresh. Permission decisions always validate current
 account and integration state.
 
-Build instructions and native qualification live in [desktop/README.md](https://github.com/hraness/ghostget/blob/v0.18.2/desktop/README.md).
+Build instructions and native qualification live in [desktop/README.md](https://github.com/hraness/ghostget/blob/v0.18.3/desktop/README.md).
 The CLI's canonical five-file GitHub Release contract is unchanged. A source
 build is not a signed or notarized public macOS installer.
 
@@ -123,7 +123,7 @@ User and imported interfaces are distinguished from bundled interfaces. Remote
 references, executable import hooks, arbitrary HTTP templates, and unsupported
 input-schema constructs are rejected or remain visibly inert as appropriate.
 An interface without an executor does not become executable by importing it.
-Use the existing [provider plugin protocol](https://github.com/hraness/ghostget/blob/v0.18.2/docs/plugins.md) when a new executor is
+Use the existing [provider plugin protocol](https://github.com/hraness/ghostget/blob/v0.18.3/docs/plugins.md) when a new executor is
 needed. OpenAPI import does not grant it account access.
 
 Middleware and LLM approval are future extensions. Future hooks may propose

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hraness/ghostget",
-  "version": "0.18.2",
+  "version": "0.18.3",
   "description": "Open-source CLI and TypeScript SDK for precise web capabilities for AI agents: page capture, verified media archives, encrypted reads, and typed provider operations.",
   "license": "MIT",
   "type": "module",

package/skills/ghostget/references/control-panel.md

@@ -40,4 +40,4 @@ Unsupported executors remain inert. Follow the existing provider-plugin
 authoring protocol to add an executor; do not synthesize arbitrary authenticated
 HTTP or broaden an existing grant. Interface changes invalidate exact grants.
 
-The product reference is the [Ghostget control panel guide](https://github.com/hraness/ghostget/blob/v0.18.2/docs/control-panel.md).
+The product reference is the [Ghostget control panel guide](https://github.com/hraness/ghostget/blob/v0.18.3/docs/control-panel.md).

package/skills/ghostget/references/install.md

@@ -17,34 +17,34 @@ If Bun is missing, stop and direct the user to the official
 [Bun installation guide](https://bun.sh/docs/installation). Do not switch
 package managers or pipe an unreviewed installer into a shell.
 
-This reference is authored for the exact v0.18.2 release coordinate. Use it
+This reference is authored for the exact v0.18.3 release coordinate. Use it
 only from the matching release-bound Agent Skill after its canonical archive and
 immutable GitHub Release exist. If the coordinate is not public, stop instead
 of substituting `main`, another tag, or a different package version. Install
 that exact release and its reviewed bundled adapter manifests:
 
 ```sh
-bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.2/hraness-ghostget-0.18.2.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 --help
 ghostget doctor --json
 ```
 
-The package is `@hraness/ghostget`; `@hraness/ghostget@0.18.2` is an optional npm
+The package is `@hraness/ghostget`; `@hraness/ghostget@0.18.3` is an optional npm
 mirror only after verified registry publication. Canonical installation does not
 wait for registry publication.
 
 When upgrading from Wrench, use `ghostget` for new commands and
 `GHOSTGET_STATE_HOME` for an explicit state root. Existing state is selected in
 place; do not rename, copy, or delete a state directory as part of the upgrade.
-The [migration guide](https://github.com/hraness/ghostget/blob/v0.18.2/docs/ghostget-migration.md)
+The [migration guide](https://github.com/hraness/ghostget/blob/v0.18.3/docs/ghostget-migration.md)
 explains the retained state aliases and durable protocol names.
 
 Do not clone the repository merely to run the CLI. Importing the SDK is a
 separate project dependency and does not install a global command:
 
 ```sh
-bun add https://github.com/hraness/ghostget/releases/download/v0.18.2/hraness-ghostget-0.18.2.tgz
+bun add https://github.com/hraness/ghostget/releases/download/v0.18.3/hraness-ghostget-0.18.3.tgz
 ```
 
 `ghostget adapter sync-bundled` upgrades exact bundled baselines, including an

package/skills/ghostget/references/linkedin-adapter.md

@@ -256,31 +256,31 @@ fetch. Long SDUI strings used as field labels are skipped instead of aborting
 the profile-stage walk. Otherwise it first inspects the page's exact
 Contact-info NavigateToScreen action. A reviewed action still admits only
 the ProfileContactDetailsOverlay URL (`sduiid` equal to that overlay
-`screenId`). Adapter 1.36.2 then clicks the unique accessible name
+`screenId`). Adapter 1.36.3 then clicks the unique accessible name
 `Contact info` on the already-loaded 1st-degree profile and projects Email
 from that modal DOM, including when that control's `href` matches
 `/overlay/contact-info/` and contained Chrome follows that reviewed vanity
-overlay pathname after click. Malformed or unsupported action fields stop
-the operation. Zero or two-plus matching controls, a path other than the
-bound profile or `/in/:publicIdentifier/overlay/contact-info/`, or a
-missing or ambiguous dialog, fail closed. The contained path does not mint
-a synthetic navigation POST or track headers, and it does not fetch that
-overlay href as a navigation GET. Only when the
-action is absent
-does it use a page-resolved GraphQL `queryId` for
-`voyagerIdentityDashProfileContactInfo`, when the HTML contains exactly one
-decorated revision. Variables are exactly `(profileUrn:{urn})`. When that
-queryId is absent, or when the GraphQL GET returns a reviewed HTTP 403
-`text/html` rejection, the operation GETs the exact vanity
-`/in/:publicIdentifier/overlay/contact-info/` overlay with RSC browser
-binding. ScreenId-only and `profileUrn`-bound
+overlay pathname after click. When the NavigateToScreen extract is
+`absent`, the same click still uses that reviewed overlay `sduiid` plus a
+headed clientArguments payload from the bound vanity, optional
+givenName/familyName parsed from profile HTML when unique,
+`isVanityNameResolved`, nested requestMetadata
+states/screenId/knownTemplates, and `isModal` true. Malformed or
+unsupported action fields stop the operation. Zero or two-plus matching
+controls, a path other than the bound profile or
+`/in/:publicIdentifier/overlay/contact-info/`, or a missing or ambiguous
+dialog, fail closed. The contained path does not mint a synthetic
+navigation POST or track headers, and it does not fetch that overlay href
+as a navigation GET. GraphQL `voyagerIdentityDashProfileContactInfo` and
+the vanity overlay RSC GET stay unused once that click is selected.
+ScreenId-only and `profileUrn`-bound
 `/flagship-web/rsc-action/actions/navigation` overlay GET URLs stay rejected
 because live dormant sessions return HTTP 500 `application/octet-stream`.
 Classic `/voyager/api/identity/profiles/{vanity}/profileContactInfo` now
-returns HTTP 410 and is rejected. The executable contract is those reviewed
-first-party reads, the reviewed Contact info click and modal snapshot, or
-the page-embedded fields. It accepts no caller-selected RSC body, selector,
-or script. This contact read does not message, connect, or InMail.
+returns HTTP 410 and is rejected. The executable contract is the reviewed
+Contact info click and modal snapshot, or the page-embedded fields. It
+accepts no caller-selected RSC body, selector, or script. This contact
+read does not message, connect, or InMail.
 
 The projection returns `email` when LinkedIn shows it, plus any of the vanity
 profile link, connected-since date, phone numbers, websites, and birthday.
@@ -474,9 +474,15 @@ GET. Operator smoke after that click fail-closed because contained
 Chrome left `/in/tessbloch/` for
 `/in/tessbloch/overlay/contact-info/`. Adapter 1.36.2 treats that
 reviewed vanity overlay pathname as still bound after click, then
-snapshots the unique dialog. Authwall and any other path still fail
-closed. It does not mint a navigation POST or track headers. Cloud has
-no signed-in LinkedIn session; do not treat this landing as live green.
+snapshots the unique dialog. Operator smoke after that bind was green
+for Email on tessbloch when the extract was `absent` and the operator
+clicked with the reviewed overlay `sduiid` plus headed clientArguments.
+Official `contacts.read` still used GraphQL or the vanity overlay GET
+on that absent extract. Adapter 1.36.3 uses the same click and modal
+snapshot when extract is `absent`. Authwall and any other path still
+fail closed. It does not mint a navigation POST or track headers.
+Cloud has no signed-in LinkedIn session; do not treat this landing as
+live green.
 
 ```sh
 printf '%s' '{"profile_url":"https://www.linkedin.com/in/tessbloch/"}' \

package/skills/ghostget/references/platform-patterns.md

@@ -20,7 +20,7 @@ Leave the state `capture-required` when current evidence is absent, ambiguous, e
 ## LinkedIn
 
 - Use `linkedin-web` with a browser-session/cookie realm for consumer Home feed, a member's recent-activity posts, inbox folders, conversations, and native article-editor surfaces. The separate official `linkedin` OAuth adapter covers approved post, comment, reply, repost, and reaction scopes; it does not supply the consumer Home feed, recent-activity pager, or inbox.
-- Current bundle 1.36.2 observes `linkedin-web profiles.read@1`, `organizations.read@1`, `contacts.read@1`, `feeds.read@2` for `feed=profile-activity`, `articles.draft.save@7`, and image-only `posts.publish@3`. The two profile-stat reads use a path-backed contained Chrome realm, bind the current member before projecting one exact self profile or requested organization Page, and keep the optional private connection read sequential with the self-profile read. `contacts.read@1` uses the same contained Chrome path, requires a 1st-degree relationship on the requested vanity from classic Profile embeds or Como rehydration (JSON object, RSC flight array, non-flight Como string slots through `decodeStringBootstrap`, `vieweeProfileId` plus vanity, and breadcrumb, string-row, or `vieweeMemberUrn` distance, including multi-escaped PROFILE_VIEW rows and when that member id is not the bound `fsd_profile` URN), and projects Contact-info email plus any shown profile link, connected-since date, phones, websites, or birthday from page-embedded fields while skipping non-bounded SDUI field labels, or from the modal opened by clicking the unique reviewed Contact info control on that already-loaded 1st-degree profile after the same page-instance bind, including when that control's href matches `/overlay/contact-info/` and the document pathname stays on the bound profile or that reviewed vanity overlay path. A present NavigateToScreen action still admits only the reviewed ProfileContactDetailsOverlay URL (`sduiid` equal to that overlay `screenId`); the contained path does not mint a synthetic navigation POST or track headers. GraphQL Contact-info stays a 403 `text/html` fallback when a unique queryId is present and no navigation action is bound. The vanity `/overlay/contact-info/` RSC GET remains HTML-shell honesty when the profile omits that action. An HTML-200 profile shell that omits Email fails as omitted Contact-info fields after that 1st-degree bind; overlay, navigation-flight, or modal HTML that still carries Como Email, a unique mailto, or an RSC/SDUI flight still projects. ScreenId-only, `profileUrn`-bound, and GET `/flagship-web/rsc-action/actions/navigation` overlay URLs stay rejected because live dormant sessions return HTTP 500. The profile-activity page uses the same contained Chrome path, binds the signed-in viewer, resolves the live `voyagerFeedDashProfileUpdates` query, and projects one recent-activity page with engagement counts when present; `feed=home` remains capture-required. The fixed browser evaluation performs only bounded, exact-route first-party fetches, except the reviewed unique Contact info click and modal snapshot on `contacts.read`; it does not accept a caller-selected selector. A cookie-only standalone client is not a fallback because current live evidence shows LinkedIn invalidates an exported `li_at` outside its browser/device context. The Article contract binds the numeric member subject to the normalized Article-author profile, creates or replaces one exact private draft, keeps a supplied cover in the Article banner rather than the body, and can preserve the independently read existing banner during an exact replacement without another cover upload. It supports paragraphs/H1/H2/native blockquotes, native HTTPS links, and 1–20 bounded inline JPEG/PNG/WebP images with required alt text and optional captions, and verifies the exact unpublished editor-response readback. Its fixed cover and inline-image single-upload registrations, byte transfers, autosaves, and readbacks run inside contained Chrome without DOM automation. The separate post contract stages a real-size optional PNG through bounded ordered commands, admits one exact image transfer and post create, durably retains the accepted share target, and independently verifies it. `linkedin-web media.publish@1` separately reserves an MP4 route but remains capture-required; the official `linkedin posts.publish` OAuth contract already observes MP4.
+- Current bundle 1.36.3 observes `linkedin-web profiles.read@1`, `organizations.read@1`, `contacts.read@1`, `feeds.read@2` for `feed=profile-activity`, `articles.draft.save@7`, and image-only `posts.publish@3`. The two profile-stat reads use a path-backed contained Chrome realm, bind the current member before projecting one exact self profile or requested organization Page, and keep the optional private connection read sequential with the self-profile read. `contacts.read@1` uses the same contained Chrome path, requires a 1st-degree relationship on the requested vanity from classic Profile embeds or Como rehydration (JSON object, RSC flight array, non-flight Como string slots through `decodeStringBootstrap`, `vieweeProfileId` plus vanity, and breadcrumb, string-row, or `vieweeMemberUrn` distance, including multi-escaped PROFILE_VIEW rows and when that member id is not the bound `fsd_profile` URN), and projects Contact-info email plus any shown profile link, connected-since date, phones, websites, or birthday from page-embedded fields while skipping non-bounded SDUI field labels, or from the modal opened by clicking the unique reviewed Contact info control on that already-loaded 1st-degree profile after the same page-instance bind, including when that control's href matches `/overlay/contact-info/` and the document pathname stays on the bound profile or that reviewed vanity overlay path. A present NavigateToScreen action still admits only the reviewed ProfileContactDetailsOverlay URL (`sduiid` equal to that overlay `screenId`). When that extract is `absent`, the same click still uses that reviewed overlay `sduiid` plus a headed clientArguments payload from the bound vanity, optional givenName/familyName from profile HTML, `isVanityNameResolved`, and nested requestMetadata. The contained path does not mint a synthetic navigation POST or track headers. GraphQL Contact-info and the vanity `/overlay/contact-info/` RSC GET stay unused once that click is selected. An HTML-200 profile shell that omits Email fails as omitted Contact-info fields after that 1st-degree bind; overlay, navigation-flight, or modal HTML that still carries Como Email, a unique mailto, or an RSC/SDUI flight still projects. ScreenId-only, `profileUrn`-bound, and GET `/flagship-web/rsc-action/actions/navigation` overlay URLs stay rejected because live dormant sessions return HTTP 500. The profile-activity page uses the same contained Chrome path, binds the signed-in viewer, resolves the live `voyagerFeedDashProfileUpdates` query, and projects one recent-activity page with engagement counts when present; `feed=home` remains capture-required. The fixed browser evaluation performs only bounded, exact-route first-party fetches, except the reviewed unique Contact info click and modal snapshot on `contacts.read`; it does not accept a caller-selected selector. A cookie-only standalone client is not a fallback because current live evidence shows LinkedIn invalidates an exported `li_at` outside its browser/device context. The Article contract binds the numeric member subject to the normalized Article-author profile, creates or replaces one exact private draft, keeps a supplied cover in the Article banner rather than the body, and can preserve the independently read existing banner during an exact replacement without another cover upload. It supports paragraphs/H1/H2/native blockquotes, native HTTPS links, and 1–20 bounded inline JPEG/PNG/WebP images with required alt text and optional captions, and verifies the exact unpublished editor-response readback. Its fixed cover and inline-image single-upload registrations, byte transfers, autosaves, and readbacks run inside contained Chrome without DOM automation. The separate post contract stages a real-size optional PNG through bounded ordered commands, admits one exact image transfer and post create, durably retains the accepted share target, and independently verifies it. `linkedin-web media.publish@1` separately reserves an MP4 route but remains capture-required; the official `linkedin posts.publish` OAuth contract already observes MP4.
 - Every other LinkedIn web operation remains capture-required. Explicit inert reservations cover inbox folders, one bounded page of recommended connections, one connection invitation, Article reads/publication, and other comment/message/repost surfaces. Their retained candidates do not confer executable internal requests.
 - Exclude presence, messaging badges, delivery acknowledgements, seen/read receipts, and notification badge traffic from every R1 contract.
 - Bind the current viewer's person/member identity to the auth realm. `organizations.read` views a Page and does not confer Page-actor authority. For organization actions, additionally bind the administered organization actor selected by the plan.

package/src/assets/adapters/linkedin/wrench-web-adapter.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 4,
   "id": "linkedin-web",
-  "version": "1.36.2",
+  "version": "1.36.3",
   "displayName": "LinkedIn (Authenticated Web API)",
   "surfaceId": "linkedin",
   "origins": [

package/src/beeper-client-types.ts

@@ -96,7 +96,7 @@ export type BeeperContactInteractionExportReceipt = Readonly<{
   implementation: Readonly<{
     producer: Readonly<{
       package: "@hraness/ghostget";
-      version: "0.18.2";
+      version: "0.18.3";
     }>;
     officialCli: Readonly<{
       implementation: "github.com/beeper/cli";

package/src/providers/linkedin-contact-program.ts

@@ -4,18 +4,17 @@ import { readAttempt, type ReadEffectFailure, withReadResource } from "../read-e
 import type { WebSessionExecution } from "../web-session-execution";
 import { LinkedInContactPlatform } from "./linkedin-contact-platform";
 import {
-  isLinkedInContactGraphqlUnavailable,
   linkedInContactDiagnostic,
   linkedInContactReadFailure,
   type LinkedInContactStage,
 } from "./linkedin-contact-failure";
 import {
+  buildLinkedInAbsentContactNavigationAction,
   extractLinkedInContactNavigationAction,
   linkedInContactNavigationActionError,
   projectLinkedInContactInfo,
   projectLinkedInEmbeddedContactFields,
   projectLinkedInProfileContactBinding,
-  resolveLinkedInProfileContactInfoQueryId,
   type LinkedInContactInfoTarget,
 } from "./linkedin-web-contact";
 
@@ -65,25 +64,22 @@ export function linkedInContactReadProgram(
               sduiid: navigation.action.sduiid,
               clientArguments: navigation.action.clientArguments,
             });
-          } else if (navigation.kind !== "absent") {
+          } else if (navigation.kind === "absent") {
+            const fallback = yield* readAttempt(() => buildLinkedInAbsentContactNavigationAction({
+              profileHtml,
+              publicIdentifier: binding.vanity,
+              profileUrn: binding.profileUrn,
+            }));
+            contactPayload = yield* platform.contactNavigation(browser, {
+              profileUrl: target.url,
+              profileUrn: binding.profileUrn,
+              sduiid: fallback.sduiid,
+              clientArguments: fallback.clientArguments,
+            });
+          } else {
             yield* readAttempt(() => {
               throw linkedInContactNavigationActionError(navigation);
             });
-          } else {
-            const queryId = resolveLinkedInProfileContactInfoQueryId(profileHtml);
-            const contactInput = {
-              profileUrl: target.url,
-              profileUrn: binding.profileUrn,
-              ...(queryId === undefined ? {} : { queryId }),
-            };
-            contactPayload = queryId === undefined
-              ? yield* platform.contactOverlay(browser, contactInput)
-              : yield* platform.contactPayload(browser, contactInput).pipe(
-                Effect.catchIf(
-                  (error) => isLinkedInContactGraphqlUnavailable(error),
-                  () => platform.contactOverlay(browser, contactInput),
-                ),
-              );
           }
         }
         stage = "projection";

package/src/providers/linkedin-web-contact.ts

@@ -1571,6 +1571,55 @@ export function linkedInContactNavigationActionError(
   );
 }
 
+export function extractLinkedInProfileContactNames(input: {
+  readonly profileHtml: unknown;
+  readonly publicIdentifier: string;
+}): {
+  readonly givenName?: string;
+  readonly familyName?: string;
+} {
+  const publicIdentifier = linkedInPersonalProfilePublicIdentifier(input.publicIdentifier);
+  const given = new Set<string>();
+  const family = new Set<string>();
+  for (const record of embeddedRecords(input.profileHtml)) {
+    if (vanityFromRecord(record) !== publicIdentifier) continue;
+    const givenName = optionalPersonName(record.givenName ?? record.firstName);
+    const familyName = optionalPersonName(record.familyName ?? record.lastName);
+    if (givenName !== null) given.add(givenName);
+    if (familyName !== null) family.add(familyName);
+  }
+  const uniqueGiven = given.size === 1 ? [...given][0] : undefined;
+  const uniqueFamily = family.size === 1 ? [...family][0] : undefined;
+  return Object.freeze({
+    ...(uniqueGiven === undefined ? {} : { givenName: uniqueGiven }),
+    ...(uniqueFamily === undefined ? {} : { familyName: uniqueFamily }),
+  });
+}
+
+export function buildLinkedInAbsentContactNavigationAction(input: {
+  readonly profileHtml: unknown;
+  readonly publicIdentifier: string;
+  readonly profileUrn: string;
+}): LinkedInContactNavigationAction {
+  const publicIdentifier = linkedInPersonalProfilePublicIdentifier(input.publicIdentifier);
+  profileUrn(input.profileUrn);
+  const names = extractLinkedInProfileContactNames({
+    profileHtml: input.profileHtml,
+    publicIdentifier,
+  });
+  return Object.freeze({
+    sduiid: LINKEDIN_CONTACT_DETAILS_OVERLAY_SCREEN_ID,
+    clientArguments: canonicalContactNavigationClientArguments({
+      payload: {
+        vanityName: publicIdentifier,
+        ...names,
+        isVanityNameResolved: true,
+      },
+    }),
+    isModal: true,
+  });
+}
+
 export function extractLinkedInContactNavigationAction(input: {
   readonly profileHtml: unknown;
   readonly publicIdentifier: string;

package/src/version.ts

@@ -1,2 +1,2 @@
 /** Canonical immutable Ghostget package release identity. */
-export const GHOSTGET_VERSION = "0.18.2" as const;
+export const GHOSTGET_VERSION = "0.18.3" as const;