@hraness/ghostget 0.17.2

package/skills/ghostget/references/install.md

@@ -0,0 +1,66 @@
+# Install and diagnose Ghostget
+
+Use this reference only when `ghostget` is unavailable or `ghostget doctor`
+reports a dependency needed by the requested workflow.
+
+## Install the CLI
+
+Ghostget requires Bun 1.3.14 or newer and supports macOS and Linux. Check both
+commands before changing the machine:
+
+```sh
+command -v bun
+command -v ghostget
+```
+
+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.17.2 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.17.2/hraness-ghostget-0.17.2.tgz
+ghostget adapter sync-bundled --json
+ghostget --help
+ghostget doctor --json
+```
+
+The package is `@hraness/ghostget`; `@hraness/ghostget@0.17.2` 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.17.2/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.17.2/hraness-ghostget-0.17.2.tgz
+```
+
+`ghostget adapter sync-bundled` upgrades exact bundled baselines, including an
+older generation whose bytes later drifted, and preserves independently
+modified current or newer manifests that this CLI can execute. If an installed
+source-owned bundled manifest was generated by an incompatible Ghostget release,
+sync atomically repairs it with this release's contract and emits a warning.
+Install the intended Ghostget release again to restore that release's newer
+contracts. This prevents one incompatible manifest from disabling an entire
+adapter while still preserving compatible current or newer custom installs.
+
+## Add only required optional tools
+
+Treat `ghostget doctor --json` as the capability report. Install a browser,
+`yt-dlp`, FFmpeg, a local transcription runtime, a provider-specific helper,
+or another operating-system dependency only when the requested route needs
+it and the user has authorized that machine change. Re-run doctor after the
+install. Do not weaken a provider or archive boundary when an optional tool is
+absent.

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

@@ -0,0 +1,442 @@
+# LinkedIn authenticated web API adapter
+
+The current `linkedin-web` schema-v4 adapter has six observed operations:
+`profiles.read@1`, `organizations.read@1`, `contacts.read@1`, `feeds.read@2`,
+`articles.draft.save@7`, and `posts.publish@3`. The two profile-stat operations
+bind the current member, then read one exact self profile or requested
+organization Page without DOM automation. `contacts.read@1` reads Contact info
+for one exact 1st-degree connection profile through the same contained Chrome
+session. `feeds.read@2` pages one member's
+recent-activity posts through the same contained Chrome session: it binds the
+signed-in viewer, resolves the live `voyagerFeedDashProfileUpdates` query on
+`/in/{vanity}/recent-activity/all/`, and projects authored text, engagement
+counts when present, original-versus-reshare kind, and an opaque next cursor.
+`feed=home` remains capture-required and is refused before any browser starts.
+The draft operation creates or replaces one private native Article
+draft for the bound current member, supports paragraphs, H1/H2 headings, native blockquotes,
+native HTTPS links, one distinct banner cover, and ordered inline images with
+required alt text and optional captions, and independently verifies the exact unpublished result
+from the authenticated editor-page server payload. The post operation publishes
+one confirmed text post with an optional single plan-bound PNG, stages real-size
+image bytes in bounded ordered contained-browser commands, binds the exact
+member and returned share, durably retains that accepted share target, and
+verifies an independent exact-share readback.
+Every other consumer-web capability remains `capture-required` and inert.
+
+A browser may record a managed HAR, bootstrap the private session, or resolve
+current session material. Runtime draft saving executes only Ghostget's fixed
+reviewed first-party API/write and editor-response readback contract inside a contained headed Chrome session;
+LinkedIn rejects the same editor exchange from a standalone HTTP client after
+its initial authenticated probe. It never types into or reads the Article
+editor DOM. Callers cannot choose a URL, header, script, or selector. Ghostget
+never lists an inbox, opens a conversation, sends a message, or performs
+another semantic action through LinkedIn's DOM.
+
+First-party traffic is not the same as a documented public API. Use this local client only with the user's account authority, comply with applicable provider rules, and keep bulk outreach and engagement outside ghostget.
+
+## Contents
+
+- [Install and inspect](#install-and-inspect)
+- [Configure the signed-in realm](#configure-the-signed-in-realm)
+- [Recapture inbox listing](#recapture-inbox-listing)
+- [1st-degree Contact info](#1st-degree-contact-info)
+- [Native Article draft saving](#native-article-draft-saving)
+- [Resolve current LinkedIn material](#resolve-current-linkedin-material)
+- [Preserve capture-required operations](#preserve-capture-required-operations)
+- [Risk and confirmation](#risk-and-confirmation)
+- [Recapture on drift](#recapture-on-drift)
+
+## Install and inspect
+
+Validate the reviewed manifest before installation:
+
+```sh
+ghostget adapter validate src/assets/adapters/linkedin/wrench-web-adapter.json
+ghostget adapter install src/assets/adapters/linkedin/wrench-web-adapter.json
+ghostget capabilities linkedin-web --json
+```
+
+Treat capability state as authoritative. `observed` means the exact contract version is eligible to execute after its account and current-session preflight passes. `capture-required` means the operation is reserved but unavailable; it performs no request and has no browser fallback.
+
+The separate `linkedin` adapter uses LinkedIn's documented OAuth API for approved post, comment, reply, repost, and reaction scopes. It does not supply the consumer Home feed or consumer inbox. Keep its OAuth token and preview separate from the `linkedin-web` cookie realm, and never switch transports silently.
+
+## Configure the signed-in realm
+
+LinkedIn currently rejects exported session cookies outside their browser
+context. Configure profile statistics with a path-backed, dormant Chrome
+profile and the exact Chrome executable. A filtered cookie source may overlay
+fresh origin-scoped cookies when the source browser is running:
+
+```sh
+ghostget auth add linkedin-main \
+  --browser-profile /absolute/private/chrome-snapshot/Default \
+  --browser-executable "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \
+  --trust-profile-egress \
+  --cookie-source chrome \
+  --cookie-profile "Profile 2"
+ghostget auth bind linkedin-main --site linkedin
+ghostget auth list --json
+```
+
+The profile path grants its contained page scripts unfiltered public-host
+egress and may contain every signed-in session in that browser profile. Keep it
+private, outside the repository, and use it only with the user's informed
+authority. Ghostget refuses to clone an active Chromium user-data root. For a
+scheduled realm, first load LinkedIn normally in the selected source profile
+and confirm that its first-party session is current. Fully quit Chrome, take
+one private snapshot, then point the auth locator at that dormant snapshot and
+use the filtered cookie overlay for current session values. The overlay can
+refresh valid cookies, but it cannot revive a source session that LinkedIn
+already rejects with 401. Never attach the runtime operation to a live inbox
+tab or copy LinkedIn session material into an OAuth token document.
+
+Bind `linkedin-main` to one stable current member/person identity before private
+reads or mutations. The observed organization Page read remains a
+member-authenticated view and does not select an organization actor. A future
+organization mutation must bind that actor separately and prove that the
+current member can act for it. Reject account ambiguity, login changes,
+request-actor mismatch, and response-actor mismatch before dispatch.
+
+The retained candidate parser derives a mailbox only when the current-account
+response directly names one bounded `miniProfile` reference and exactly one
+included entity binds that reference to the same numeric member subject. It
+does not scan other included profile entities as a fallback. Missing,
+unbound, conflicting, or ambiguous direct bindings fail.
+
+The standalone client can strictly review a short-lived `__cf_bm` edge-cookie
+rotation: it accepts only that name, validates origin, attributes, expiry, and
+deletion semantics, and binds the encrypted cache to the auth-locator hash.
+Removing the auth locator removes that cache. Profile-backed statistics do not
+export their session into that standalone client. Only the six observed
+operations may cross the execution boundary; every capture-required operation
+still refuses before its provider client is created.
+
+Verification on July 23, 2026 produced a durable projection-drift failure and
+every available LinkedIn realm returned `401` at current-account preflight.
+That remains negative evidence for the independently capture-required inbox
+contracts, not a demotion of the separately observed profile and Page reads.
+Reauthentication alone does not promote an inbox contract; a fresh low-stakes
+capture must also prove its current identity, mailbox, query, response
+projection, and completeness semantics.
+
+## Recapture inbox listing
+
+`messaging.list` is a capture-required reservation. Version 1.1.0 remains
+archived as historical evidence of the formerly observed bundle; version
+1.2.0 first demoted it, and version 1.7.0 preserves that unavailable contract
+history. The current bundle remains capture-required and cannot execute. The
+intended folder input still reserves:
+
+- `focused` for the main inbox;
+- `other` for the additional inbox;
+- `requests` for pending message requests;
+- `archive`;
+- `spam`;
+- `all` for conversations in the returned inbox page.
+
+The prior candidate projected bounded conversation identity, participants,
+latest-message preview, read metadata, and an opaque sync token. Those shapes
+are retained for comparison, not claimed as current. A new capture must prove
+folder classification, whether continuation is executable, when a page is
+complete, and the exclusion of presence, delivery acknowledgements,
+seen/read receipts, and notification-badge requests. An inbox preview must not
+be described as full conversation history.
+
+Inspect the reservations without executing them:
+
+```sh
+ghostget capabilities linkedin-web --json
+```
+
+Captured evidence identifies article, feed, mailbox-count, secondary-inbox,
+conversation-list, and message endpoint families. Every family remains
+capture-required until its current variables, bounded target-bound projection,
+completeness, and incidental effects are proved. Reading a conversation must
+use only a reviewed message query and must not mark it read.
+
+## Profile activity posts
+
+`feeds.read@2` is an observed R1 read for one page of a member's
+`/in/{vanity}/recent-activity/all/` posts. It does not require official OAuth
+`posts.read` or `w_member_social`. Use a path-backed Chrome profile or a
+cookie-source overlay that is already signed into LinkedIn. The operation
+always uses contained headed Chrome; a standalone exported-cookie HTTP client
+is not a fallback.
+
+Pass `feed=profile-activity` plus one `profile_url` or `vanity`. The URL may
+be the public profile or the recent-activity path. An opaque `cursor` from the
+previous page continues the same vanity. `limit` is 1–100 and defaults to 20.
+`feed=home` stays reserved and refuses before the browser starts.
+
+The page binds the signed-in viewer to the auth subject, then observes exactly
+one live `voyagerFeedDashProfileUpdates.<32-hex>` query and one target profile
+URN. Zero or several hashes fail closed. Each item projects the activity URN,
+canonical feed URL, author vanity or URN when present, full commentary text,
+created or relative time when present, reaction/comment/repost counts when
+LinkedIn supplies them, media presence, and original-versus-reshare kind.
+Missing counts stay `null`; the runtime never invents zero. A next cursor is
+returned only when paging includes a strictly advancing `rel=next` link, or
+when `paging.total` is a positive count still above `start + count`. LinkedIn's
+current profile-activity page sends `{count, start, total: 0}` with no next
+link; that page is complete and does not invent an offset from a full page.
+When LinkedIn omits paging, `complete` stays false and `nextCursor` is `null`.
+Contradictory paging or a provider page larger than `limit` fails closed.
+
+```sh
+printf '%s' '{"feed":"profile-activity","profile_url":"https://www.linkedin.com/in/j-hawkins/","limit":20}' \
+  | ghostget invoke linkedin-web feeds.read --input - --auth linkedin-main --json
+printf '%s' '{"feed":"profile-activity","vanity":"varunr96","cursor":"<opaque>","limit":20}' \
+  | ghostget invoke linkedin-web feeds.read --input - --auth linkedin-main --json
+```
+
+Do not treat this page as a complete profile history, a home feed, or
+permission to like, comment, or message.
+
+## Profiles, organization Pages, and connections
+
+`profiles.read@1` is an observed R1 read for one exact signed-in self profile
+URL. It binds the current member to the requested public slug and projects the
+exact follower count. When `include_connections` is true, it also reads the
+exact private My Network connection total in the same ordered browser
+transport. `organizations.read@1` is an observed R1 read for one exact company
+Page URL. It binds the requested company record and its matching following
+state before projecting the exact follower count. Viewing a Page does not
+confer Page-actor authority.
+
+For a path-backed auth realm, Ghostget starts a task-private contained clone and
+uses the browser path before any standalone cookie preflight. One code-owned
+evaluation derives the reviewed CSRF header from the unique `JSESSIONID` and
+performs exact `GET /voyager/api/me`. After binding that response to the auth
+subject and requested self slug, it reads the exact profile response and, when
+requested, the private connections response in order. The organization branch
+instead reads only the exact requested Page after the same member binding.
+Every response is bounded, same-origin, exact-route, status- and media-type
+checked before projection. Login, checkpoint, redirect, network, cookie,
+identity, target, or response drift fails closed. Ghostget does not click or
+inspect LinkedIn DOM, expose a caller-selected selector or script, follow a
+redirect, or retry after an arbitrary browser failure. It closes the contained
+browser and verifies cleanup after success or failure.
+
+Live evidence on August 23, 2026 showed that LinkedIn returned deletion
+cookies for a valid `li_at` when the same Chrome session was replayed through a
+standalone client, even with Chrome's normal request headers. A cookie-only
+realm is therefore not the scheduled profile-stat transport. The path-backed
+browser branch preserves the browser/device context while still keeping the
+operation fixed and target-bound.
+
+## 1st-degree Contact info
+
+`contacts.read@1` is an observed R1 read for one exact 1st-degree connection
+profile URL. It binds the signed-in viewer, then requires a 1st-degree
+relationship on that vanity from the profile page. Current LinkedIn pages are
+SDUI/RSC and often omit classic `bpr-guid-*` Profile embeds. The binder
+therefore walks both those Voyager code payloads and `window.__como_rehydration__`,
+and treats `memberDistance`, `networkDistance`, or `distance` of `DISTANCE_1`,
+`1`, or `"1"` as first-degree when that value is joined to the requested vanity
+or its profile URN.
+
+When the same page already embeds Contact-info fields, including a labeled
+Email row, the operation projects those fields and does not issue a second
+fetch. Otherwise it GETs `/voyager/api/graphql` for
+`voyagerIdentityDashProfileContactInfo`, using a page-resolved `queryId` when
+the HTML contains exactly one decorated revision and `queryName` otherwise.
+Variables are exactly `(profileUrn:{urn})`. Classic
+`/voyager/api/identity/profiles/{vanity}/profileContactInfo` now returns HTTP
+410 and is rejected. The executable contract is that reviewed first-party GET
+or the page-embedded fields, not a caller-selected RSC body, DOM click, or
+selector. Ghostget 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.
+Completeness is `complete` when at least one of those optional fields is
+present and `partial` when the payload bound but LinkedIn omitted every
+optional field.
+
+A 2026-09-08 signed-in capture of a 1st-degree profile showed the Contact info
+control on the intro card and a modal with the vanity link, Email, and
+Connected since. The same capture had Como rehydration with numeric
+`networkDistance: 1`, a `ProfileContactDetailsOverlay` screen, and no
+`bpr-guid-*` Profile records. Voyager `profileContactInfo`, `networkinfo`, and
+`profileView` returned 410. That drift is why the binder and fetch path
+changed.
+
+Self profiles fail closed with guidance to use `profiles.read`. Second-degree,
+third-degree, and out-of-network profiles fail closed because LinkedIn hid
+Contact info from that viewer. The operation never invents a hidden email.
+
+```sh
+printf '%s' '{"profile_url":"https://www.linkedin.com/in/example/"}' \
+  | ghostget invoke linkedin-web contacts.read --input - --auth linkedin-main --json
+```
+
+`relationships.recommendations.read` and `relationships.connect` remain
+`capture-required`. The former reserves one bounded R1 page from the `all`
+recommended-connections surface. The latter reserves one R3 invitation to an
+exact profile URN, with an optional note of at most 300 characters and a
+24-hour local-at-most-once window. Neither performs a request before a managed
+HAR proves its exact request, viewer scope, target, response, paging,
+completeness, and duplicate-state behavior.
+
+Do not treat `organizations.read` as organization-actor authority. A future
+Page-authored post or comment must separately bind the current member, selected
+organization actor, administered-role entitlement, request actor, and returned
+actor. `comments.create` targets an exact post URN; LinkedIn does not have a
+separate ghostget operation for “commenting on a profile” or “commenting on a
+Page.” A member- or organization-authored post remains the comment target.
+
+## Native Article draft saving
+
+`articles.draft.save` is an observed R2 operation for one private native
+LinkedIn Article draft. Its input uses the canonical provider-neutral
+`ArticleDraftDocument` described in [native article drafts](article-drafts.md),
+with an optional exact existing `draft_id`. The current contract accepts
+paragraph, `heading1`, `heading2`, and `blockquote` blocks, native HTTPS link ranges, and
+one separate plan-bound JPEG, PNG, or WebP cover on create, or preserves the
+independently read existing banner on an exact replacement when `cover_image`
+is omitted, plus 1–20 ordered inline images up to 5 MiB each. Every inline image requires descriptive alt text and
+may have a caption. The cover is outer input rendered only in the banner slot;
+it is never a document body block. Styles, list items, proprietary embeds,
+HTML, Markdown, and editor payloads are rejected. The caller owns editorial
+translation, image placement, captions, and alt text.
+
+When the source Article contains an X status, use
+`projectXStatusArticleEmbed` with the `linkedin-web` target. The reviewed
+LinkedIn contract emits the exact status text as native blockquotes followed
+immediately by one canonical linked X URL.
+Omit source-post chrome, metrics, and card screenshots by default.
+
+On August 18, 2026, an authorized private draft create and editor reload
+independently returned the same text block as provider type `QUOTE`; this
+reviewed shape is the evidence for `blockquote` write and readback support.
+
+Create first binds a private title shell and its exact current-author
+unpublished readback, registers, transfers, binds, and verifies the cover,
+then registers and transfers each inline image before saving and reading back
+the complete document. Replacement reads the exact private draft, performs
+the same distinct cover and inline-image steps, then performs one conservative
+title/document replacement. Neither schedule contains a publication or
+feed-share request.
+
+The contained browser is an authenticated transport, not a browser-operation
+fallback. Chrome supplies the bound device session, cookies, user agent, and
+TLS context; code-owned evaluation sends only the fixed current-member,
+create, distinct cover/inline image registrations, signed byte transfers,
+exact editor-page readback, cover-autosave, title-autosave, and
+content-autosave requests.
+The headed window may be visible during the save. Cleanup is tracked as part
+of the durable operation and an unverified close preserves private artifacts
+for explicit recovery instead of silently deleting evidence.
+
+Authorized August 15–16, 2026 captures proved the current first-party Article
+route family, exact create and partial-update bodies, the returned Rest.li
+draft identity, normalized current-member-to-Article-author binding, private
+`DRAFT` lifecycle, null publication/share fields, exact title/content/link
+projection, and persistence after reopening. The August 16 live recapture also
+proved that exact draft reads now come from one bounded hidden JSON payload in
+the authenticated editor HTML response rather than the retired Rest.li finder.
+The August 16 inline-image capture additionally proved bounded still-image
+registration, a signed transfer returning `201`, stable asset-URN projection,
+ordered image blocks, required accessibility text, optional captions,
+provider-restored CDN sources, and persistence after reopening. The editor
+proceeded directly from transfer to Article autosave and made no processing
+status poll, so Ghostget follows that exact sequence and gates success on the
+later private Article response and independent readback.
+
+An August 18 recapture after registration drift proved the current
+`PUBLISHING_INLINE_IMAGE` response uses LinkedIn's bounded single-upload
+variant. Ghostget accepts that exact known-field family and the prior vector
+variant, but still rejects multipart mechanisms, unknown response fields,
+unreviewed headers, and upload targets outside the fixed LinkedIn origin and
+path. File selection in the editor's preview dialog was not upload completion:
+the reviewed flow selected the staged image, advanced the dialog once, waited
+for the signed transfer, and only then observed the Article autosave.
+
+An August 19 capture proved that the Article banner is not a body image. The
+editor registers it with `PUBLISHING_COVER_IMAGE`, transfers the bytes once,
+and autosaves the returned asset through
+`coverMediaV2Union.coverImage` with the exact reviewed CoverImage type and an
+empty caption. Independent editor-response readback exposes matching legacy
+and V2 cover projections bound to the same stable asset URN. The current draft
+contract therefore requires one outer `cover_image` on create and plans a
+supplied replacement cover as `articles.cover` before body images. When an
+exact replacement omits it, Ghostget preserves and verifies the current banner
+asset without registering or transferring another cover. In either case, the
+banner stays out of the document and `inline_images`.
+
+An August 19 recovery exercise also proved why this distinction matters: a
+cover dispatch can become indeterminate after LinkedIn has retained the banner
+but before Ghostget verifies that dispatch. Never retry that cover upload. After
+separate inspection establishes that an exact replacement draft already has
+the intended banner, a new confirmed replacement may omit `cover_image` and
+preserve that independently read asset while repairing only its body. That is
+a distinct intent, not reconciliation or retry of the uncertain upload.
+
+The active image contract has no automated reconciliation path because an
+uncertain upload may have created a provider asset absent from the confirmed
+input. Preserve partial or indeterminate runs and do not retry or repeat
+uploads. Exact read-only replacement reconciliation remains only for
+already-durable historical text-only contract evidence.
+
+The presence of a LinkedIn editor or saved UI state alone is not a contract.
+Do not type into the editor as a runtime fallback. `articles.publish` remains a
+separate capture-required R3 operation with its own publication evidence.
+
+## Resolve current LinkedIn material
+
+Derive the `csrf-token` header from exactly one bounded `JSESSIONID` cookie. Strip only the reviewed wrapper quotes and require the expected `ajax:` token form. Never log or return the cookie or derived token.
+
+Resolve a registered query such as `voyagerFeedDashMainFeed` or `messengerMessages` from bounded current candidates by exact operation prefix. Require exactly one `<prefix>.<32-hex>` match. Zero matches mean drift; several matches mean ambiguity. Both fail before the API request.
+
+Keep query IDs, CSRF material, cookies, variables, feature sets, and private identifiers out of manifests and receipts.
+
+## Preserve capture-required operations
+
+The current registry keeps these unavailable until their exact first-party exchanges are captured and reviewed:
+
+- `feeds.read` `feed=home`, `relationships.recommendations.read`, `messaging.list`, `messaging.read`, `posts.read`, `comments.read`, and `articles.read` (`R1`);
+- `messaging.send` (`R3`);
+- `posts.repost` and `posts.quote` (`R3`);
+- `comments.create` and `replies.create` (`R3`);
+- `relationships.connect` (`R3`);
+- `reactions.set` (`R2`);
+- `articles.publish` (`R3`);
+
+Do not guess a Voyager/GraphQL mutation from a bundle, replay a captured payload, or use the composer as a fallback. To graduate one operation:
+
+1. capture one exact low-stakes fixture;
+2. bind the current member/organization actor;
+3. bind conversation/profile/organization/post/root/parent target IDs;
+4. bind returned message/comment/post/article identity and successful state;
+5. exclude unrelated background mutations;
+6. test revision drift, account mismatch, response drift, and uncertainty;
+7. bump the contract and adapter versions.
+
+For `messaging.send`, use an already-read, user-approved, low-stakes conversation. Keep recruiting and employment threads out of fixtures. A successful pressure test requires the internal `createMessage` response contract and an independent R1 read of the exact returned message; a visibly cleared textbox is irrelevant. Text-only and each attachment family are separate fixtures: the current manifest accepts one reviewed image, GIF, MP4 video, PDF, presentation, or word-processing document, but that input schema remains inert until upload initialization, byte transfer, asset ownership, message association, and independent readback are all captured and response-bound.
+
+`posts.publish@3` is the separate observed R3 post contract. It accepts exact
+text and at most one plan-bound PNG with descriptive alt text, admits the
+image transfer and post create once, stages the PNG as at most 569 ordered
+48-KiB base64 chunks in batches of at most 32 commands, clears that page state
+before transfer, durably retains the response-bound share URN, and verifies it
+through an independent current-member readback. It does not authorize an
+Article publication, repost, quote, comment, message, or additional media.
+
+For `relationships.connect`, use a user-approved profile that is not already
+connected or invitation-pending. Prove the preflight relationship state, exact
+target profile URN, optional note, returned invitation identity/state, and
+independent relationship readback. A disabled Connect button is not evidence.
+
+## Risk and confirmation
+
+R1 reads run only after they graduate and pass account binding.
+`reactions.set` is R2 only as an exact desired-state create/delete pair. A
+private `articles.draft.save` is R2 because its exact autosave and unpublished
+readback contract has graduated. Messages, comments, replies, posts, reposts,
+quotes, connection requests, and article publication are R3; only the exact
+observed `posts.publish@3` post shape is executable among those R3 families.
+
+Every R2/R3 operation must preview the exact account realm, actor, target, text/media hashes, side effect, contract hash, and dispatch schedule. Confirm once. Require local duplicate refusal. Treat an uncertain response after request start as `indeterminate`; never retry by clicking LinkedIn or by changing message whitespace.
+
+## Recapture on drift
+
+Fail before the semantic request when the registered query, path, allowed query fields, Rest.li shape, feature contract, CSRF source, response status/content type, projection, or target/account binding changes. Restore the affected operation to `capture-required`, record a new managed HAR, update owned code, and rerun deterministic plus authorized live tests. Never update the client directly from arbitrary live traffic.