@hraness/ghostget 0.17.2

package/skills/ghostget/references/article-drafts.md

@@ -0,0 +1,235 @@
+# Native article drafts
+
+## Contents
+
+- [Own the editorial translation](#own-the-editorial-translation)
+- [Build the mixed document](#build-the-mixed-document)
+- [Project source-post embeds](#project-source-post-embeds)
+- [Save without publishing](#save-without-publishing)
+- [Read one saved X draft](#read-one-saved-x-draft)
+- [Handle uncertainty](#handle-uncertainty)
+- [Check provider state](#check-provider-state)
+
+Use `articles.draft.save` to create or replace one private native long-form
+draft. Treat it as an R2 mutation with its own preview, confirmation, dispatch
+record, and provider-bound unpublished result. It has no publish-capable
+branch.
+
+Keep `articles.publish` separate. Publication is R3 and requires a different
+installed observed contract, input, preview, and confirmation. A saved draft
+ID is not permission to publish, and a draft preview cannot be reused for
+publication.
+
+## Own the editorial translation
+
+Capture or read source material separately. The caller decides how to
+translate, abridge, retitle, attribute, link, and place images. Ghostget does not
+turn source HTML, Markdown, or a URL into provider copy and does not infer
+attribution or alternative text. Pass only the final reviewed title, canonical
+document, and exact local image files to the mutation.
+
+## Build the mixed document
+
+The current `x-web` and `linkedin-web` capabilities require canonical JSON for
+`ArticleDraftDocument` schemaVersion 2. Text blocks are:
+
+- `paragraph`
+- `heading1`
+- `heading2`
+- `blockquote`
+- `unordered-list-item`
+- `ordered-list-item`
+
+Represent a native link with an ordered, non-overlapping range over the
+block's UTF-16 text and one canonical absolute HTTPS URL. Represent bold,
+italic, or strikethrough with ordered style ranges. Put each paragraph or list
+item in its own block; block text cannot contain a newline.
+
+Place an inline image with an `image` block. Its `imageIndex` is the zero-based
+position of the matching file in outer `input.inline_images`. Image indexes
+must be unique, contiguous from zero, and referenced exactly once. A caption
+is optional. Platform metadata differs:
+
+- `x-web` supports captions but its native alt-text write remains
+  capture-required, so omit `altText`.
+- `linkedin-web` requires a non-empty descriptive `altText`; captions are
+  optional.
+
+Both current web adapters accept 1–20 ordered JPEG, PNG, or WebP files, at most
+5 MiB each. Ghostget sniffs the bytes, copies them into the encrypted preview's
+plan-asset bundle, hashes them, removes source paths and filenames from the
+preview, and reverifies the exact bytes before dispatch. Do not pass a URL,
+provider asset ID, expiring CDN source, cover, video, embed, HTML, Markdown, or
+editor payload as an inline image.
+
+`linkedin-web` requires one outer `input.cover_image` JPEG, PNG, or WebP file
+up to 5 MiB when creating a draft. Supply it on replacement only to replace
+the banner; omit it with an exact `draft_id` to preserve the independently
+read existing banner without another cover registration or transfer. A
+supplied cover is a separate plan-bound attachment and does not
+implicitly create a document `image` block or appear in `input.inline_images`.
+For a cover-only source asset, keep it out of the body; include the same bytes
+as an inline image only when the reviewed article intentionally shows them in
+both places.
+Ghostget registers it as `PUBLISHING_COVER_IMAGE`, transfers the exact bytes,
+binds the returned asset only through LinkedIn's `coverMediaV2Union.coverImage`
+autosave, and independently verifies both saved cover projections. The current
+contract writes an empty cover caption. `x-web` cover saving remains
+capture-required.
+
+Provider text support remains narrower where capture evidence is narrower:
+`linkedin-web` accepts `paragraph`, `heading1`, `heading2`, and `blockquote`, native
+HTTPS links, and no text styles. `x-web` accepts all listed text block types,
+native links, and bold, italic, or strikethrough.
+
+## Project source-post embeds
+
+Treat a source X status as editorial content, not as provider editor payload.
+Do not copy its profile chrome, timestamp, engagement counts, or screenshot of
+the rendered card into an Article by default. Do not assume that pasting a URL
+creates a proprietary embed.
+
+Use the exported `projectXStatusArticleEmbed` helper with the exact status text,
+canonical source URL, and destination adapter. It removes share-tracking query
+parameters and emits the status URL as one native linked paragraph immediately
+after the content:
+
+- `x-web` and `linkedin-web`: emit each non-empty source line as a native
+  `blockquote`.
+
+Preserve media attached to the source status only when the user explicitly
+wants that media as independent Article images. Otherwise keep the quote and
+status link only. The helper does not fetch a status, infer its text, upload
+media, or claim that either provider created a native embed card.
+
+```ts
+import { projectXStatusArticleEmbed } from "@hraness/ghostget";
+
+const blocks = projectXStatusArticleEmbed({
+  text: "Exact source-post text",
+  url: "https://x.com/example/status/123?s=20",
+}, "x-web");
+```
+
+This is canonical X document JSON with one native link and one image:
+
+```json
+{"blocks":[{"links":[{"length":6,"offset":9,"url":"https://example.com/source"}],"text":"Read the source","type":"paragraph"},{"caption":"Puerto Rico","imageIndex":0,"type":"image"}],"schemaVersion":2}
+```
+
+Put that exact inner JSON string and an absolute local image path in a private
+invocation input file:
+
+```json
+{
+  "title": "Reviewed title",
+  "document": "{\"blocks\":[{\"links\":[{\"length\":6,\"offset\":9,\"url\":\"https://example.com/source\"}],\"text\":\"Read the source\",\"type\":\"paragraph\"},{\"caption\":\"Puerto Rico\",\"imageIndex\":0,\"type\":\"image\"}],\"schemaVersion\":2}",
+  "inline_images": ["/absolute/private/puerto-rico.png"]
+}
+```
+
+For LinkedIn, add `"altText":"A descriptive account of the image"` before
+`caption` in the canonical image block. If the final block is an image, do not
+add an empty paragraph after it; LinkedIn owns that editor-only trailing block
+and Ghostget removes exactly that provider-added value during readback.
+Also add a sibling `"cover_image":"/absolute/private/banner.jpg"` to the
+outer invocation object when creating or replacing the banner; keep the banner
+out of the document blocks and out of `inline_images`. For a replacement that
+must retain its existing banner, omit `cover_image` and keep the exact
+`draft_id`.
+
+Add `draft_id` only to replace the exact existing private draft owned by the
+bound account. Treat `ghostget capabilities <adapter> --json` as authoritative
+for all installed bounds and contract versions.
+
+## Save without publishing
+
+Inspect support and use the exact provider and auth realm printed by the
+installed capability:
+
+```sh
+ghostget capabilities x-web --json
+ghostget x-web articles.draft.save \
+  --input @/absolute/private/article-draft-input.json \
+  --auth x-main --preview --json
+ghostget confirm <preview-digest> --json
+```
+
+Use the same sequence with `linkedin-web` and its bound LinkedIn cookie realm;
+never switch adapter or auth realm after preview. LinkedIn executes its fixed
+reviewed current single-upload registration, signed byte-transfer, autosave,
+and editor-response readback contract inside contained headed Chrome. The reviewed editor proceeds
+from the transfer's `201` response directly to autosave; Ghostget does not invent
+a processing poll that the editor does not perform. The window may appear, but
+Ghostget does not type into or read the editor DOM, and callers cannot supply a
+URL, header, script, or selector.
+
+Review the account, title, canonical document, separate cover hash, ordered inline attachment hashes,
+optional draft ID, R2 side effect, contract version, and every planned
+dispatch. X plans one dispatch per image followed by create, or image uploads
+then title and content replacement. LinkedIn create plans the title shell,
+cover, each inline image, then content; replacement plans cover, each inline
+image, then one conservative title/content replacement.
+
+Require a successful result to identify `articles.draft.save`, report
+`published: false` and `mode: "draft"`, return the private draft identity, and
+report the exact cover and inline image counts. X verifies the owner, private Draft lifecycle,
+title, text/link/style structure, captions, image order, and uploaded media
+IDs. LinkedIn verifies the current author, private `DRAFT` lifecycle, title,
+separate cover asset, text/link structure, inline-image order, alt text,
+captions, and stable asset URNs.
+Never continue into publication.
+
+## Read one saved X draft
+
+`x-web articles.read@2` reads one exact current-viewer-owned private Article
+draft by its 1–19 digit provider ID. It is an R1 operation, uses the same bound
+X cookie realm, and never enters the mutation dispatch ledger.
+
+```sh
+ghostget x-web articles.read \
+  --input '{"article_id":"1234567890123456789"}' \
+  --auth x-main --json
+```
+
+The closed result identifies `provider: "x"` and `operation: "articles.read"`.
+Its `article` binds the requested ID, current viewer's owner ID,
+`kind: "private-draft"`, `lifecycle: "Draft"`, `published: false`, one bounded
+single-line title, and bounded rich content. The contract fails closed if the
+Article is missing, published, not in the Draft lifecycle, or owned by another
+account.
+
+This operation does not list drafts or read published X Articles. LinkedIn
+Article reads remain capture-required; do not infer them from
+`linkedin-web articles.draft.save` or switch transports to fill the gap.
+
+## Handle uncertainty
+
+Do not retry a partial or indeterminate image save. An upload may have produced
+a provider asset even when its stable identity never entered the confirmed
+result. Preserve the run, inspect the exact private draft, and do not search by
+title, guess an ID, repeat uploads, switch transports, or publish as recovery.
+
+Current image-capable X and LinkedIn draft contracts deliberately have no
+automated reconciliation path. Only already-durable historical text-only
+contracts retain read-only replacement reconciliation for an exact confirmed
+`draft_id`; that historical route is never selected for a new preview.
+
+## Check provider state
+
+- `x`: the documented OAuth adapter has separate response-bound private-draft
+  and publish operations with its own plain-text/optional-cover schema. It is
+  not a substitute for `x-web` and does not accept this mixed document.
+- `x-web`: `articles.draft.save@2` creates or replaces one private structured
+  Article with native links, styles, ordered inline images, and captions, then
+  verifies the unpublished result. `articles.read@2` separately reads one exact
+  current-viewer-owned private Draft. Alt text, covers, published Article reads,
+  and `articles.publish` remain capture-required.
+- `linkedin-web`: `articles.draft.save@7` creates or replaces one private
+  paragraphs/headings/blockquotes/links Article with one separate new or preserved banner plus
+  ordered inline images, required alt text, and optional captions, then
+  verifies the exact current-author unpublished result. Styles, lists,
+  `articles.read`, and `articles.publish` remain capture-required.
+
+Never switch between an official API and a signed-in web adapter because one
+lacks a field or publishing capability.

package/skills/ghostget/references/code-owned-provider-scaffold.md

@@ -0,0 +1,134 @@
+# Scaffold a provider source plugin
+
+Use the scaffold after a managed derivation has produced
+`internal-api-evidence.json`. It turns one explicitly selected, sanitized
+candidate into a fail-closed source-plugin unit. It never reads a raw HAR,
+copies an endpoint into executable code, replays a request, or generates a
+browser action.
+
+Read [provider-plugins.md](provider-plugins.md) first. Source plugins are trusted
+code in Ghostget's process, not isolated installed extensions.
+
+## Contents
+
+- [Create the scaffold](#create-the-scaffold)
+- [Implement the direct contract](#implement-the-direct-contract)
+- [Prove promotion](#prove-promotion)
+
+## Create the scaffold
+
+Keep the derivation output private and select one candidate only after reviewing
+it with `ghostget derive review`:
+
+```sh
+ghostget plugin scaffold \
+  --site example \
+  --display-name Example \
+  --origin https://www.example.com \
+  --operation feeds.read \
+  --risk R1 \
+  --evidence /absolute/private/capture/internal-api-evidence.json \
+  --candidate 0 \
+  --output src/plugins/example-web
+```
+
+`ghostget adapter scaffold` remains a compatibility alias. New workflows should use
+`ghostget plugin scaffold`.
+
+Use the exact `targetOrigin` and zero-based candidate index from the sanitized
+evidence. The script requires a private, regular evidence file, refuses a
+pre-existing non-empty output, rejects transport-shaped operation names, and
+binds only the sanitized evidence file hash and candidate index into its
+checklist. It also enforces the canonical risk for known verbs: reads and lists
+are R1, reversible `set` and `save` operations are R2, and externally visible
+creation, editing, publishing, sharing, and messaging are R3.
+
+The generated source unit is self-contained:
+
+```text
+src/plugins/<site>-web/
+├── plugin.ts
+├── runtime.ts
+├── plugin.test.ts
+├── runtime.internal.test.ts
+├── wrench-adapter.json
+└── promotion-checklist.json
+```
+
+Check the inert unit before registering it:
+
+```sh
+ghostget plugin check src/plugins/example-web --json
+bun test src/plugins/example-web
+bun run src/scripts/generate-provider-plugin-catalog.ts
+```
+
+Every generated operation is `capture-required`. The runtime throws before
+cookie acquisition, account bootstrap, or network I/O. The manifest contains a
+schema-v4 semantic selector, not a request description. Do not install it until
+the plugin is present in the generated static catalog and its exact input schema
+replaces the empty placeholder. `plugin check` reads and syntax-checks the fixed
+file set without importing it; that check is not a sandbox or code review.
+
+## Implement the direct contract
+
+Replace the fail-closed boundaries one at a time without adding provider
+switches to the kernel:
+
+1. Define one `ProviderPluginV1` in `plugin.ts`. Bind the plugin ID, version,
+   display name, source kind, transport, site, exact origin, accepted auth
+   kinds, subject format and matcher, semantic operation, contract version,
+   current-subject probe, executor, and complete implementation-source list.
+2. Implement a typed request authorizer in `runtime.ts` that fixes origin, method, path
+   structure, query names, body shape, non-secret headers, redirect behavior,
+   timeout, and output bound.
+3. Acquire only the reviewed auth realm. If a dynamic token or registered
+   operation revision is unavoidable, use browser bootstrap only to resolve
+   that one value and route it only to its named sink.
+4. Implement a reviewed current-account request and compare its stable,
+   namespaced provider subject with the bound auth realm before private reads or
+   dispatch.
+5. Parse foreign responses from `unknown`, require exact success status and
+   content type, project bounded semantic fields, and verify target,
+   actor/parent, and desired-state bindings.
+6. Replace the manifest input placeholder with precise IDs, enums, text,
+   attachment, pagination, and count bounds. Never accept arbitrary URLs,
+   headers, request bodies, GraphQL, Rest.li, JavaScript, selectors, or cookies.
+7. Replace the generated tests with deterministic request, response, identity,
+   drift, size, dispatch, and recovery coverage. Keep provider-specific
+   behavior inside the plugin unit or its declared implementation sources.
+8. Regenerate the static catalog. Use `ghostget plugin show <plugin-id> --json` to
+   verify registry ownership, then validate and install the separate data
+   manifest.
+
+Use direct first-party HTTP for the semantic operation. Agent-browser may
+navigate and exercise an authorized fixture during capture, or supply narrowly
+reviewed session material at bootstrap. It must not click, type, upload, send,
+publish, react, or read the DOM on behalf of the installed operation.
+
+## Prove promotion
+
+Treat `promotion-checklist.json` as review state, not proof by itself. The
+scaffold checker requires every proof to remain false because it checks the
+initial network-inert reservation. Set no operation to `observed` until all of
+these are independently true:
+
+- exact request shape and credential sinks;
+- exact response variants and bounded projection;
+- current-account, actor, target, and parent bindings;
+- explicit exclusion or modeling of incidental acknowledgements;
+- deterministic request, response, redirect, drift, mismatch, and size tests;
+- durable dispatch and uncertainty behavior for R2/R3;
+- one authorized low-stakes live fixture through the public CLI;
+- duplicate refusal and independent provider-visible readback for mutations;
+- secret scan of plans, receipts, logs, output, and temporary state.
+
+For R1, prove that the request does not emit seen, presence, delivery, badge, or
+read acknowledgements. For R2/R3, preview and confirm the exact bounded action
+once. If any fact drifts, restore `capture-required` before another request.
+
+After the reviewed source facts have been transferred into
+`src/plugins/<plugin-id>`, delete the sanitized derivation output, managed
+browser profile, any abandoned derivation, and any duplicate private scaffold.
+Never commit raw HARs, profile state, tokens, cookies, captured payloads, or
+authenticated DOM.

package/skills/ghostget/references/cross-posting-video.md

@@ -0,0 +1,139 @@
+# Cross-post video
+
+Use the installed `ghostget` CLI as the only posting transport. Orchestrate
+provider operations; do not implement a second HTTP client, click a composer
+at runtime, or treat a browser login as proof that video publishing is
+supported.
+
+Reuse the preview, confirm, settlement, and ledger rules in
+[cross-post text and images](cross-posting.md). Do not invent a second
+confirmation model.
+
+## Build one exact video package
+
+Record these values before planning:
+
+- one absolute path to the exact video file that will be posted;
+- exact caption text, preserving whitespace and punctuation;
+- selected platforms;
+- explicit provider choices such as audience, visibility, or a YouTube title.
+
+Do not silently recut, restyle, watermark, or replace the video after the
+user has approved the package. Encoding happens before planning.
+
+### Social encode
+
+Prepare one social-friendly cut before any preview:
+
+- 9:16, 1080x1920, H.264 Main, yuv420p, `+faststart`, AAC;
+- if the source is landscape, letterbox or blur-pad into 9:16;
+- do not crop away a required subject unless the user asked for a crop;
+- if replacement background audio is supplied, replace the soundtrack and
+  trim or fade it to the video duration. Do not leave the original audio
+  mixed under it unless asked.
+
+Encoding may use a local encoder such as ffmpeg. Posting may not.
+
+### Caption and tags
+
+- If the user provided a caption, use it exactly. Do not rewrite it to pass
+  a provider limit; ask for a shorter shared caption or an explicit
+  platform-specific variant. Never mark that user-supplied caption as
+  AI-generated; follow [X AI disclosure](x-ai-disclosure.md).
+- If no caption was provided, write one short caption from the video's
+  actual subject: about one sentence, under 120 characters. Do not invent a
+  long marketing paragraph.
+- Add hashtags only on TikTok, Instagram, and YouTube Shorts. Put a few
+  relevant tags after the caption on those platforms only.
+- Do not add hashtags on X, LinkedIn, Substack, Bluesky, Threads, or Reddit.
+
+That tag split is an explicit allowed platform-specific variant. It is not
+a license to rewrite the caption.
+
+Give the package a task-local identity. Preserve the same video bytes
+through planning, settlement, duplicate accounting, and any cleanup
+assessment.
+
+## Preflight every target
+
+1. Run `ghostget --help`; if it is unavailable, follow
+   [installation and diagnostics](install.md).
+2. Read [video platform routing](social-video-platform-routing.md).
+3. Run `ghostget capabilities <adapter> --json` for every candidate adapter.
+   Treat its current operation state and input schema as authoritative over
+   the reference and over remembered platform behavior.
+4. Select one exact transport and auth realm per platform. Never switch
+   between a browser-session and official OAuth adapter after planning.
+5. Choose the operation that actually accepts `video/mp4` on that adapter,
+   usually `media.publish`. A text or image `posts.publish` is not a video
+   operation, even when it is observed.
+6. Require that video operation to be `observed`, the adapter to be valid,
+   and the auth realm to be bound to its current provider subject.
+   `capture-required` is unavailable, not degraded support.
+7. Validate the exact file path, bytes, detected media type, caption, and
+   required scalars against each installed input schema before creating any
+   plan.
+
+If a platform cannot accept this video under an observed contract, exclude
+it from the batch and keep it on the ledger as unavailable. Never silently
+drop it. Never post through the capture browser as the installed fallback.
+
+Prefer a target-filtered cookie locator for a signed-in web adapter. Use a
+profile-backed realm only when the provider contract requires browser
+storage and the user has accepted that exact broader egress boundary. Bind
+a new realm with `ghostget auth bind <id> --site <surface> --json` before any
+preview.
+
+If support is missing and the user asked to develop it, use the packaged
+Ghostget derivation workflow with one expressly authorized low-stakes
+fixture. Keep the operation `capture-required` until its contracts pass.
+
+## Preview the complete batch
+
+Construct each input only from its current installed schema. In CLI input
+JSON, represent a scalar file field as one absolute path string.
+
+Run every target with `--preview --json` before confirming any target.
+Review and summarize adapter, transport, operation, risk, bound account,
+exact scalar input, attachment hash, side effect, contract hash, and
+five-minute expiry.
+
+Cancel superseded or unused plans. If one target cannot be planned, report
+that target separately; do not weaken the other inputs to manufacture
+parity.
+
+## Confirm once per platform
+
+Cross-posting is not atomic. Confirm each reviewed digest once with
+`ghostget confirm <digest> --json`. Do not recreate an expired plan without
+rechecking the video package and authorization.
+
+Classify each result independently:
+
+- `submitted`: record the run and provider-created object evidence, then
+  settle availability through exact readback;
+- pre-dispatch `failed`: diagnose safely and create a fresh preview only if
+  the original action remains authorized;
+- `pending`, `partial`, or `indeterminate`: preserve the run and use only
+  an advertised, separately reviewed exact readback through
+  `ghostget runs reconcile`.
+
+Never retry pending, partial, or indeterminate work. An unsettled target
+does not create authority to delete or repost on other platforms.
+
+## Settle and account for every attempt
+
+Read [settlement and duplicate cleanup](settlement-and-duplicate-cleanup.md)
+after confirmation. Give every attempt its own immutable ledger entry. Use
+exact returned locators and exact provider readback; never infer delivery
+from a cleared composer, a profile search, or matching text.
+
+## Finish with a platform ledger
+
+Return one row per requested platform and attempt with adapter, auth realm
+label, plan or run ID, attachment hash summary, terminal state, exact
+provider locator or public URL when exposed, readback state, and
+availability timing.
+
+Keep caption text, credentials, cookies, private response bodies, and
+original local paths out of receipts and diagnostics.

package/skills/ghostget/references/cross-posting.md

@@ -0,0 +1,82 @@
+# Cross-post text and images
+
+Use the installed `ghostget` CLI as the only posting transport. Orchestrate provider operations; do not implement a second HTTP client, click a composer at runtime, or treat a browser login as proof that publishing is supported.
+
+## Build one exact post package
+
+Record these values before planning:
+
+- exact text, preserving whitespace and punctuation;
+- an ordered optional image package, with one absolute path and optional alt description per image;
+- selected platforms;
+- explicit provider choices such as LinkedIn visibility or a platform-specific text variant.
+
+Do not truncate text, omit or reorder images, make a collage, split a thread, or rewrite copy to pass a provider limit. Ask for a material content choice when exact parity is impossible. A social Substack target means a public Note; an article or newsletter is a different operation.
+
+If alt text is absent, draft a short factual description from visible image content and include it in the preview summary. Never infer identity, health, ethnicity, relationships, or other sensitive traits from an image.
+
+Give the package a task-local identity. Preserve image order through planning, settlement, duplicate accounting, and any cleanup assessment.
+
+## Keep user-supplied copy unlabeled
+
+When the user supplied the cross-post copy, never mark that package as AI-generated. This rule applies to X and every other platform in this workflow. On X, follow [X AI disclosure](x-ai-disclosure.md).
+
+- Do not add "Made with AI", "Made with Grok", or similar disclosure text to the body.
+- Do not set a provider metadata flag that labels the post or its media as AI-generated. Official `x` `posts.publish` exposes `made_with_ai`; leave it unset or `false` for this workflow. `x-web` `posts.publish` has no such input field; do not invent one. Inspect each installed schema for a comparable field and leave it unset or `false`.
+- Prefer the installed Ghostget transport. Do not click the X composer because a contract is missing or `capture-required`.
+- If the user explicitly asked for a composer fallback, open Content disclosure and require Made with AI OFF before Post. A locked or greyed toggle is an auto-label; stop. After publishing, open the live permalink. A sparkle Made with AI or Made with Grok label means the publish failed; do not report success, and do not delete or repost unless the user asks.
+
+## Preflight every target
+
+1. Run `ghostget --help`; if it is unavailable, follow [installation and diagnostics](install.md).
+2. Read [social platform routing](social-platform-routing.md).
+3. Run `ghostget capabilities <adapter> --json` for every candidate adapter. Treat its current operation state and input schema as authoritative over the reference and over remembered platform behavior.
+4. Select one exact transport and auth realm per platform. Never switch between a browser-session and official OAuth adapter after planning.
+5. Require `posts.publish` to be `observed`, the adapter to be valid, and the auth realm to be bound to its current provider subject. `capture-required` is unavailable, not degraded support.
+6. Validate the exact text, ordered image count, bytes, detected media types, alt-field shape, and required scalar fields against each installed input schema before creating any plan.
+
+Map the package only as the installed schema permits: a scalar file gets one path, a file array gets an ordered path array, and aligned accessibility fields retain the same image order. If a provider accepts fewer images, requires an image, or lacks an alt field, report that exact constraint. Obtain an explicit per-provider package choice when parity is impossible; never silently drop, duplicate, merge, convert, or reorder images.
+
+Prefer a target-filtered cookie locator for a signed-in web adapter. Use a profile-backed realm only when the provider contract requires browser storage and the user has accepted that exact broader egress boundary. Bind a new realm with `ghostget auth bind <id> --site <surface> --json` before any preview.
+
+If support is missing and the user asked to develop it, use the packaged Ghostget derivation workflow with one expressly authorized low-stakes fixture. Bind authorized capture images or MP4 video at derivation start with repeated `--fixture` options and upload only their returned `fixture:<n>` references. Keep the operation `capture-required` until its code-owned request, response, current-account, actor, attachment, returned-object, independent-readback, duplicate, and uncertainty contracts pass. Never post through the capture browser as the installed fallback.
+
+## Preview the complete batch
+
+Construct each input only from its current installed schema. In CLI input JSON, represent a scalar file field as one absolute path string and a file-array field as an ordered array of absolute path strings. Ghostget replaces those paths with plan-bound opaque file references and binds immutable attachment bytes, sizes, media types, and hashes into the plan.
+
+Run every target with `--preview --json` before confirming any target. Capability availability is evaluated at preview time and the resulting contract identity is bound into the digest; a later adapter change must not be used to reinterpret that plan or an existing run. Review and summarize:
+
+- adapter, transport, operation, and risk;
+- bound account realm and provider subject;
+- exact scalar input, without hiding platform-specific variants;
+- attachment order, sizes, detected types, and SHA-256 hashes;
+- side effect, contract hash, dispatch count, and five-minute expiry.
+
+Cancel superseded or unused plans. If one target cannot be planned, report that target separately; do not weaken the other inputs to manufacture parity.
+
+## Confirm once per platform
+
+Cross-posting is not atomic. Confirm each reviewed digest once with `ghostget confirm <digest> --json`. Do not recreate an expired plan without rechecking the post package and authorization.
+
+Classify each result independently:
+
+- `submitted`: record the run and provider-created object evidence, then settle availability through exact readback;
+- pre-dispatch `failed`: diagnose safely and create a fresh preview only if the original action remains authorized;
+- `pending`, `partial`, or `indeterminate`: preserve the run and use only an advertised, separately reviewed exact readback through `ghostget runs reconcile`.
+
+An unsettled target does not create authority to delete or repost on other platforms. Continue with another already-reviewed platform only when its dispatch is independent and still matches the user's requested batch.
+
+## Settle and account for every attempt
+
+Read [settlement and duplicate cleanup](settlement-and-duplicate-cleanup.md) after confirmation. Give every attempt its own immutable ledger entry. Use exact returned locators and exact provider readback; never infer delivery from a cleared composer, a profile search, or matching text.
+
+A duplicate-tolerant action is a materially new intent, not a retry. Permit it only after explicit fresh authorization of the exact platform/package and duplicate risk. In the current v1 workflow, create the new preview with one exact eligible source run via `--duplicate-risk-of <run-id>`; Ghostget binds that run to one deterministic successor intent. Keep every other prior uncertain attempt linked separately in the task ledger. Never clear, overwrite, or weaken an old Ghostget ledger, receipt, recovery capsule, or attachment bundle.
+
+Assess cleanup only through the installed canonical `content.delete` capability. If it is absent, `capture-required`, or blocked as R4, report cleanup as unavailable. Never use a semantic alias, raw HTTP, composer automation, or a capture session to perform deletion.
+
+## Finish with a platform ledger
+
+Return one row per requested platform and attempt with adapter, auth realm label, plan or run ID, attachment hash summary, terminal state, exact provider locator or public URL when exposed, readback state, and availability timing. Label provider creation time and first independent observation time separately; observation means the post was available no later than that check, not that it became available at that instant. If exact readback never observes it, report availability as unverified even when the provider accepted the mutation.
+
+Keep post text, credentials, cookies, private response bodies, and original local paths out of receipts and diagnostics. Remove task-owned derivations and temporary profile snapshots after verified cleanup; retain evidence needed for unsettled runs.