window.fastdocShell · smoke

Smoke-run routes — internal checks of the SumDoc build itself. Not used in embedding. Methods on this page: 3.

Internal API

window.fastdocShell is only available inside the desktop SumDoc window. For external integration, use the Rust Session Protocol or the browser surface interface.

How to read the line under the signature

Under each method is a line of four values — for example web_to_host_request_response · invoke · fastdoc-shell:get-state · capability=document.

Value	What it means
web_to_host_request_response	The editor window asks the application shell and waits for a response
web_to_host_event	The editor window notifies the shell and doesn’t wait for a response
host_to_web_event	The shell notifies the editor window; you subscribe to these methods
invoke, send, on	Exchange method: request with a response, send without a response, subscription
fastdoc-shell:…	The name of the channel the message travels on
capability=…	The capability group the method belongs to

All three sets of values are declared in the shell contract: directions in BridgeDirection, domains in ShellContractDomain, capabilities in ShellCapability. The last set doesn’t match the domains: smoke runs and the release center have no capability of their own, so their methods are assigned to internal or document.

The first word of the name tells you what the method does

Start of the name	What happens
apply…	Performs an action and changes the document. The response says what happened
compute…CommandState	Changes nothing: answers whether the action can be performed now (canApply) and why not (disabledReason). The shell uses this response to decide whether to enable the button
run…	Runs an entire scenario — a compatibility check or a release-readiness check
get…, list…	Read state and change nothing
set…, update…	Change a setting, not the document’s content
create…, delete…	Create and delete — a version, a comment, a checkpoint
open…	Opens — the document, one of its versions, a link in an external program
resolve…	Two different meanings, visible from the rest of the name: for comments, it marks one resolved; for recovery and external changes, it resolves a conflict by choosing whose edit to keep
notify…	Notifies the shell of an event and doesn’t wait for a response
on…	Subscription: the shell calls you when the event happens

The apply… and compute…CommandState pairs go together: first you ask for the state, then you apply. A method ending in Copy is a special case, covered below.

Methods on this page — 3

• notifyCurrentDocumentTruthViewerReady
• notifyRendererReady
• notifySmokeCheckpoint

notifyCurrentDocumentTruthViewerReady

notifyCurrentDocumentTruthViewerReady(payload: { availability: string;
  fixtureId: string | null;
  blockedStatesVisible: boolean;
  forbiddenClaimsVisible: boolean;
  unavailableStateVisible: boolean;
  genericFixtureListVisible: boolean;
}): void

web_to_host_event · send · fastdoc-shell:current-document-truth-viewer-ready · capability=internal

notifyRendererReady

notifyRendererReady(): void

web_to_host_event · send · fastdoc-shell:renderer-ready · capability=internal

notifySmokeCheckpoint

notifySmokeCheckpoint(checkpoint: string, payload?: { screenshotDataUrl?: string | null;
    screenshots?: Array<{ name?: string | null;
  dataUrl?: string | null }>;
  telemetry?: unknown;
  reserveCyclesCompleted?: number;
  reserveElapsedMs?: number;
  reserveRichPayloadBytes?: number;
}): void

web_to_host_event · send · fastdoc-shell:smoke-checkpoint · capability=internal