@superdoc/sdk 2.26.0-next.3 → 2.26.0-next.9

package/README.md

@@ -92,7 +92,7 @@ const document = await client.open(
 
 The credential applies only to that open request. It is not part of the
 collaboration profile or command-line arguments. Per-open token authentication
-is not supported for Liveblocks or the standalone document host.
+is not supported for Liveblocks.
 
 See the [Node.js SDK guide](https://docs.superdoc.dev/agents/automation/node-sdk) for a complete workflow.
 
@@ -183,7 +183,6 @@ const session = await openVersionedDocumentReviewSession({ store, documentId, ac
 const client = createSuperDocClient({
   user: { name: actor },
   requestTimeoutMs: 120_000,
-  env: { SUPERDOC_SDK_DOCUMENT_HOST_BIN: 'embedded' },
 });
 try {
   const { diff, comparisonError, result } = await runTrackedComparisonReview({
@@ -220,7 +219,7 @@ authorization, durable storage, reviewer presentation, and decisions.
 ## Agent execution evidence
 
 The core preset's `agent_apply`, `agent_verify`, and supported named actions
-collect the facts their targets and checks need. Supported document-host sessions
+collect the facts their targets and checks need. CLI-backed sessions
 can read body block identities and text, table shape, exact requested block
 counts, and document revisions without collecting complete snapshots. The named
 paths cover table creation and cell styling, body paragraph formatting and
@@ -229,9 +228,9 @@ rewriting, and paragraph insertion around a selected anchor.
 The shared execution paths on supported hosts guard edits with document revisions.
 An intervening edit can stop a later step; a failed action may therefore include operations that already committed.
 
-This changes default receipts for eligible plans: `preSnapshot.counts` and
-`postSnapshot.counts` are absent, not zero. Callers that previously consumed these
-counts should request `evidence: 'full'`:
+CLI-backed sessions preserve `preSnapshot.counts` and `postSnapshot.counts`
+using compact execution summaries. Request `evidence: 'full'` when a workflow
+needs complete snapshot evidence:
 
 ```js
 import { dispatchSuperDocTool } from '@superdoc/sdk';
@@ -249,14 +248,13 @@ const receipt = await dispatchSuperDocTool(document, 'agent_apply', {
 ```
 
 `evidence: 'required'` is the default. Requested block-count checks remain exact
-without adding unrequested receipt summaries. `evidence: 'full'` is also available
+and CLI receipts retain their count summaries. `evidence: 'full'` is also available
 on `agent_verify` and the named `create_table`, `format_paragraph`, `rewrite_block`,
 and `insert_paragraphs` actions.
 
 Unsupported selectors and checks, inspection dependencies, multiple-operation
-plans, atomic plans, and save verification retain complete evidence. Older hosts
-with compact revision support retain the single-paragraph, revision-only path;
-other unsupported hosts and plain bound API handles use complete snapshots.
+plans, atomic plans, and save verification retain complete evidence. Older CLI hosts
+without typed execution facts and plain bound API handles use complete snapshots.
 
 A failed receipt can disclose a committed mutation when post-edit verification
 fails. Inspect `executedOperations` and the reported error before retrying; do not