@c4a/context-cli 0.7.34 → 0.7.35

package/providers/context/manifest.json

@@ -2,7 +2,7 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.7.34"
+    "version": "0.7.35"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
@@ -14,7 +14,7 @@
     {
       "id": "workspace",
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:a0db554b3506e9a68464afe11a5d486a0ce0a0340747f810d8ebdf2fec285c43"
+      "digest": "sha256:d2cab288ca8c31fa361316f014f5a60c36ac433070acf28331198c750cdb8d73"
     }
   ],
   "actions": [
@@ -126,7 +126,7 @@
     {
       "id": "repair-project-entry",
       "path": "actions/repair-project-entry.yaml",
-      "digest": "sha256:8ffa98a8d15d82aabe63786d473fc3154507cb1ab2389e2e6ed7827b47187312"
+      "digest": "sha256:c232c81d0a3e77b54faa7e9383e6ba23ca4ce68411dad9e61eaad53d175bc1cd"
     },
     {
       "id": "repair-verification",
@@ -183,7 +183,7 @@
     {
       "id": "context.sdk.lark-resources",
       "path": "resources/manuals/guides/lark-resources.md",
-      "digest": "sha256:ca488cf7d5c818b82c81ea2d9a058cb5e7b91b7de2656506dbc40f19c79fada8"
+      "digest": "sha256:18e00d57ecb21e990f847a5a104992a7c8cb24769f2b7dcdf7153137dd707663"
     },
     {
       "id": "context.sdk.package-outputs",
@@ -203,7 +203,7 @@
     {
       "id": "context.sdk.project-api",
       "path": "resources/manuals/reference/project-api.md",
-      "digest": "sha256:a65131d5cd351d8353f5028303ab1d75447f5d0c09496fd8ec83bb5d76adfd78"
+      "digest": "sha256:d7af120518aa721f06ae2233a824a674b50eee5096244d1b9eb5efb659f8ea90"
     },
     {
       "id": "context.sdk.template-variables",
@@ -288,7 +288,7 @@
     {
       "id": "procedure.document-capture",
       "path": "resources/procedures/document-capture.md",
-      "digest": "sha256:fea23e68a535ff1a567439fe8b05e027575762c4a8f04da2fd181c17e58076f4"
+      "digest": "sha256:bc5b30df9dabe85f5bfe1cd9b4bdd7c1504e0ecb7fb7870f6f09de4dc1fb44fc"
     },
     {
       "id": "procedure.document-code-investigation",
@@ -308,12 +308,12 @@
     {
       "id": "procedure.knowledge-review",
       "path": "resources/procedures/knowledge-review.md",
-      "digest": "sha256:f0532acbc93458c90209dfed3395b69873eeea6b7d431ae52a84d44c4553751e"
+      "digest": "sha256:fa37908e7766f62227e02f6d38f3f3cc9ec023fd1ab01374bcb56e11338cf6fa"
     },
     {
       "id": "procedure.knowledge-updates",
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:bd457b533803f214899f58e03846354f50fafa479a97e01665beb5065a5e90fb"
+      "digest": "sha256:44cea5c34793c775a0729f589f4436546528ddcde524e36fe16b5bad0f8e32e1"
     },
     {
       "id": "procedure.note",
@@ -368,7 +368,7 @@
     {
       "id": "procedure.source-capture-detailed",
       "path": "resources/procedures/source-capture-detailed.md",
-      "digest": "sha256:39644875f09bac66580332357c3d9701c234da036b61205c8a02029165455f76"
+      "digest": "sha256:f49fd80a51f68c1e27c59c9aeb4875fb21a4e53d10f26e75d251b4e024f49b83"
     },
     {
       "id": "procedure.source-update",
@@ -398,7 +398,7 @@
     {
       "id": "procedure.workspace-prepare",
       "path": "resources/procedures/workspace-prepare.md",
-      "digest": "sha256:5fc94a9197a52ec894d5a58872faf1812c18c1e4ff06fd92244dc551147c1bb4"
+      "digest": "sha256:023b97b68dcfa74f5024f9e1cbebdb417af40f6918624e3154cd62a063f854eb"
     },
     {
       "id": "procedure.workspace-restore",
@@ -535,7 +535,7 @@
     },
     {
       "path": "actions/repair-project-entry.yaml",
-      "digest": "sha256:8ffa98a8d15d82aabe63786d473fc3154507cb1ab2389e2e6ed7827b47187312"
+      "digest": "sha256:c232c81d0a3e77b54faa7e9383e6ba23ca4ce68411dad9e61eaad53d175bc1cd"
     },
     {
       "path": "actions/repair-verification.yaml",
@@ -571,11 +571,11 @@
     },
     {
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:a0db554b3506e9a68464afe11a5d486a0ce0a0340747f810d8ebdf2fec285c43"
+      "digest": "sha256:d2cab288ca8c31fa361316f014f5a60c36ac433070acf28331198c750cdb8d73"
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:ba2618496299deb80171ab9e7472a26b09d9187083347f22bdf65294564acc5d"
+      "digest": "sha256:145fbe98232a53f310b8c26cc6e0cb66b132677b9edd8b98656783430a39e66a"
     },
     {
       "path": "resources/contracts/indexer-provider-guide.yaml",
@@ -631,11 +631,11 @@
     },
     {
       "path": "resources/manuals/guides/knowledge-updates.md",
-      "digest": "sha256:8d408d8d15c4f322a2ffcaac7798ece234f3a0bf58d2a122ee3ab97472ef75c3"
+      "digest": "sha256:c85e58acf930b9ffae128f0bb83d5494024dd81ae1c338df4a2fa6fa0a95695f"
     },
     {
       "path": "resources/manuals/guides/lark-resources.md",
-      "digest": "sha256:ca488cf7d5c818b82c81ea2d9a058cb5e7b91b7de2656506dbc40f19c79fada8"
+      "digest": "sha256:18e00d57ecb21e990f847a5a104992a7c8cb24769f2b7dcdf7153137dd707663"
     },
     {
       "path": "resources/manuals/guides/markdown-indexer-skill-authoring.md",
@@ -657,13 +657,17 @@
       "path": "resources/manuals/guides/sessions.md",
       "digest": "sha256:b1d86d1fb96f1caba5baf7859bf20ac43e4fe890a40db453727cf2627d44fac6"
     },
+    {
+      "path": "resources/manuals/guides/source-batches.md",
+      "digest": "sha256:9e338332986deab67932e62398db0221a7be139ac056f0856a46738164df411e"
+    },
     {
       "path": "resources/manuals/guides/workspace-commit.md",
       "digest": "sha256:586ef0f6fc21b4c2183ef0f6764baac27558690aa4a0b75b9295a942135222d6"
     },
     {
       "path": "resources/manuals/guides/workspace-prepare.md",
-      "digest": "sha256:057ab5a00ed51629bf856551a20b18fb9e81a9a597dcd87dd44e9b1c9dffd3f2"
+      "digest": "sha256:2b6ad6ab07597a6cf36cd91c36991cc8b042468cf0f87c1c72952074b47f29e7"
     },
     {
       "path": "resources/manuals/guides/workspace-restore.md",
@@ -679,7 +683,7 @@
     },
     {
       "path": "resources/manuals/reference/project-api.md",
-      "digest": "sha256:a65131d5cd351d8353f5028303ab1d75447f5d0c09496fd8ec83bb5d76adfd78"
+      "digest": "sha256:d7af120518aa721f06ae2233a824a674b50eee5096244d1b9eb5efb659f8ea90"
     },
     {
       "path": "resources/manuals/reference/template-variables.md",
@@ -695,7 +699,7 @@
     },
     {
       "path": "resources/procedures/document-capture.md",
-      "digest": "sha256:fea23e68a535ff1a567439fe8b05e027575762c4a8f04da2fd181c17e58076f4"
+      "digest": "sha256:bc5b30df9dabe85f5bfe1cd9b4bdd7c1504e0ecb7fb7870f6f09de4dc1fb44fc"
     },
     {
       "path": "resources/procedures/document-code-investigation.md",
@@ -711,11 +715,11 @@
     },
     {
       "path": "resources/procedures/knowledge-review.md",
-      "digest": "sha256:f0532acbc93458c90209dfed3395b69873eeea6b7d431ae52a84d44c4553751e"
+      "digest": "sha256:fa37908e7766f62227e02f6d38f3f3cc9ec023fd1ab01374bcb56e11338cf6fa"
     },
     {
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:bd457b533803f214899f58e03846354f50fafa479a97e01665beb5065a5e90fb"
+      "digest": "sha256:44cea5c34793c775a0729f589f4436546528ddcde524e36fe16b5bad0f8e32e1"
     },
     {
       "path": "resources/procedures/note.md",
@@ -759,7 +763,7 @@
     },
     {
       "path": "resources/procedures/source-capture-detailed.md",
-      "digest": "sha256:39644875f09bac66580332357c3d9701c234da036b61205c8a02029165455f76"
+      "digest": "sha256:f49fd80a51f68c1e27c59c9aeb4875fb21a4e53d10f26e75d251b4e024f49b83"
     },
     {
       "path": "resources/procedures/source-update.md",
@@ -783,7 +787,7 @@
     },
     {
       "path": "resources/procedures/workspace-prepare.md",
-      "digest": "sha256:5fc94a9197a52ec894d5a58872faf1812c18c1e4ff06fd92244dc551147c1bb4"
+      "digest": "sha256:023b97b68dcfa74f5024f9e1cbebdb417af40f6918624e3154cd62a063f854eb"
     },
     {
       "path": "resources/procedures/workspace-restore.md",
@@ -878,5 +882,5 @@
     "indexer": [],
     "workspace": []
   },
-  "digest": "sha256:b68d36eaf96c10f0a19ed342e9b15dc21e8ebec3e5864586e66e5f4af8c198f6"
+  "digest": "sha256:95dc30eefd6778add4f5d3adc118e5e41691a12d2d6df57c139c41e13443782f"
 }

package/providers/context/provider.yaml

@@ -1,6 +1,6 @@
 schema: agent-graph.provider.v1
 id: c4a/context
-version: 0.7.34
+version: 0.7.35
 name: Context workflow
 description: Internal work contract for Context knowledge workspaces.
 graphs:

package/providers/context/resources/manuals/guides/knowledge-updates.md

@@ -500,6 +500,12 @@ the user without blocking an independently supported local correction.
 
 ## Import a document response already read by the host
 
+For complete snapshots produced by `context source fetch lark`, use the optional
+`snapshot_dir` form described in [Lark resource reuse](lark-resources.md#reuse-a-complete-planning-snapshot).
+It reuses saved bodies and all captured resources without remote reads, retaining
+their original capture time and source revision. The response-file form below
+remains supported when the host supplies its own full document responses.
+
 For a registered Lark source, retain the actual full JSON response from
 `lark-cli docs +fetch` and each returned continuation page. Do not reconstruct a
 response from a summary. Use the same source import command:

package/providers/context/resources/manuals/guides/lark-resources.md

@@ -14,6 +14,56 @@ actual full response files and downloaded media for the same normalization and
 resource checks; it does not fetch that supplied body again. See
 [importing an existing response](knowledge-updates.md#import-a-document-response-already-read-by-the-host).
 
+## Reuse a complete planning snapshot
+
+Before creating a workspace or registering sources, an authorized research task
+can save a portable snapshot:
+
+```bash
+context source fetch lark https://example.larkoffice.com/docx/example-token \
+  --output .tmp/research/handbook --as bot --format json
+```
+
+The output directory must not exist. Fetch keeps one fixed identity for the body
+and resources; Bot is the default and never switches to User automatically.
+Explicit User reads use the host's existing authorization behavior. Supported
+resources retain the same permission handling and rate-limit recovery as capture.
+Read the returned fidelity and resource diagnostics before using the material.
+A failed operation can leave an incomplete directory; only an intact completion
+receipt can be imported.
+
+After registering the matching source in the selected workspace, save this input
+using its actual registered name and local snapshot path:
+
+```json
+{
+  "type": "lark",
+  "name": "20260101/handbook",
+  "snapshot_dir": ".tmp/research/handbook"
+}
+```
+
+```bash
+context source import --input .tmp/import-handbook.json --format json
+```
+
+Keep or move the complete directory: `snapshot.json`, document, original response
+pages and resource files. Paths in the input resolve from the selected workspace.
+Import checks the source match, file integrity and capture report, then follows
+the existing capture write and workflow protections. It reuses structured
+resources as well as images without remote reads. It retains the original
+capture time, source revision and coverage gaps; importing does not establish
+upstream freshness. The receipt verifies local integrity, not source authenticity.
+The saved resource policy must match the configured capture phase. If it differs,
+use that phase's normal capture operation or explicitly reconcile its configuration;
+import does not silently reinterpret saved resources under a new policy.
+Do not synthesize platform responses or repair a damaged receipt by editing it;
+use an intact snapshot or fetch again into a new directory.
+
+The existing `response_files` import contract remains supported. It avoids
+fetching the supplied body again, but may fetch other resources; `snapshot_dir`
+is the complete-snapshot alternative.
+
 ## Resource policy
 
 | Resource | Default capture behavior |
@@ -22,7 +72,7 @@ resource checks; it does not fetch that supplied body again. See
 | Attachment | Download the original file and link it from the Markdown projection. |
 | Sheet | Read the complete selected sheet, render a Markdown table, and retain a CSV snapshot. |
 | Base | Read the selected table/view with pagination, render a Markdown table, and retain a canonical JSON snapshot. |
-| Whiteboard and diagram | Retain a readable preview plus the raw structured export. |
+| Whiteboard and diagram | Retain a readable preview plus the raw structured export; if only raw export is denied, retain and explicitly label the available preview. |
 | Synced block | Resolve the exact source block, project its body, and retain a Markdown evidence snapshot. |
 | Poll | Preserve exported options and metadata as non-interactive Markdown; warn when the export omits them. |
 | Bookmark, citation, sub-document, chat, and generic embed | Preserve a stable navigation reference and provenance. |
@@ -45,6 +95,12 @@ resources remain explicit in the capture report. Unknown non-empty XML blocks
 stay auditable in the raw XML and receive a warning; the CLI does not infer
 their meaning.
 
+When raw whiteboard export is denied after its preview succeeds, the preview is
+usable visual material, not complete structured evidence. The report retains a
+preview warning; unavailable raw nodes must not be reconstructed or described as
+successfully acquired. A permission failure before any usable representation is
+obtained leaves only the reference and an unavailable-resource notice.
+
 Document and resource reads share one access identity. The configured default is
 user. Bot mode permits one whole-document user fallback for a body authorization
 failure, restarting all pages. After the body is read, resources remain under
@@ -52,6 +108,21 @@ that identity. A resource failure never requests another identity's credentials.
 Legacy explicit auto mode may select Bot when user credentials are unavailable;
 all resources still use the identity that supplied the complete body.
 
+## Download concurrency and throttling
+
+Independent resources use up to four concurrent requests within one capture.
+Nested synced-block projections follow leaf resources. The CLI keeps one access
+identity, deduplicates resources, and enforces the existing byte limits.
+
+Explicit structured HTTP 429 or rate-limit responses reduce concurrency and
+pause queued requests together. Each request receives at most three retries
+with exponential backoff; exposed Retry-After values are respected. Eight
+successful requests allow concurrency to increase by one, up to four. Exhausted
+retries or a server wait longer than 30 seconds stop further resource requests
+for this capture. Already acquired resources and failure diagnostics are retained.
+This recovery does not ask for user confirmation or another identity's credentials;
+persistent failures remain visible and are not reported as successful acquisition.
+
 ## Storage lifecycle
 
 Resources have three distinct locations:

package/providers/context/resources/manuals/guides/source-batches.md

@@ -0,0 +1,89 @@
+---
+id: context.sdk.source-batches
+kind: procedure
+mediaType: text/markdown
+---
+
+# Resumable source operations
+
+These optional commands improve source discovery and registration. They do not
+select a production scope, capture document bodies, approve articles, or change
+the current workflow. Existing single-source and batch commands remain valid.
+
+## Register a large batch
+
+Use the existing batch payload and add checkpoints when recovery is useful:
+
+```bash
+context source add batch 20260101 --input .tmp/sources.json --checkpoint --progress --format json
+```
+
+The final JSON retains `kind`, `namespace`, `total`, and `registered`. When
+checkpoints are enabled, `checkpoint` also provides `job_id`, `status_command`,
+and `resume_command`. Progress is bounded JSON on stderr; stdout contains the
+final receipt. Without `--progress`, existing output behavior is retained.
+
+```bash
+context source batch-status <job-id> --format json
+context source add batch --resume <job-id> --progress --format json
+```
+
+The saved input remains under `.tmp/context-runtime/source-batches/`. Resume
+validates and replays every input against the current registry; a saved cursor
+is advisory and never authorizes skipping validation. Resume does not require
+the original payload file. It registers sources only; `--configure` remains an
+explicit choice. Do not combine `--resume` with a date or replacement input.
+
+Batch registration retains partial-success semantics. Valid entries before a
+failed item remain registered, and the error identifies completed entries and
+the failed position. Lark entries are validated in memory and committed in
+bounded atomic chunks. Repository and file entries retain their existing
+registration checks. An unchanged chunk does not rewrite its registry.
+
+Checkpoint initialization is checked before registration starts. If later
+progress storage becomes unavailable, successful registration remains successful
+and the receipt includes a warning. A missing progress file does not prevent
+replaying an intact saved input.
+
+Only one workspace writer may run at a time. Poll an active command rather than
+starting another writer or deleting its lock. Normal cancellation finishes the
+current bounded write and releases the lock. Forced termination can leave a
+stale lock; follow `context task recover --format json` before resuming. A saved
+checkpoint survives process restarts in the same workspace, but not deletion of
+its temporary directory or a new workspace without those files.
+
+## Discover a Wiki directory
+
+For an explicitly authorized Wiki subtree:
+
+Run discovery from an existing Context workspace. It saves research metadata
+without changing the source registry or production scope.
+
+```bash
+context source discover lark https://example.larkoffice.com/wiki/example-token --as bot --format json
+context source discover lark https://example.larkoffice.com/wiki/example-token --as bot --resume --format json
+```
+
+Discovery saves directory metadata, object identities, aliases, and page receipts
+under `.tmp/context-runtime/wiki-discovery/`. It reads neither document bodies nor
+their external links, and does not register sources or create capture phases.
+The result gives the manifest path and counts instead of printing the whole tree.
+
+The identity defaults to Bot and is fixed for the job. Bot reads never switch to User credentials.
+Permission failures are recorded without prompting for authorization or stopping
+independent directories. Completed pages are reused; explicit resume retries
+transient failures. The manifest describes the observed scan, not an atomic
+snapshot of a remotely changing Wiki.
+
+Explicit `--as user` uses the host's existing user-authorization behavior, which
+may request consent when credentials or scopes are missing.
+
+`--concurrency` accepts 1 through 4 and defaults to 4. Rate limits reduce active
+concurrency and apply bounded retries with a shared cooldown. Exhausted retries
+leave a resumable partial result. Progress goes to stderr by default; use
+`--no-progress` to disable it. `completed`, `partial`, and `paused` distinguish
+the outcome; partial or paused discovery exits nonzero while preserving results.
+
+Existing jobs require `--resume` and the same identity. A running discovery owns
+its job lease; a second invocation cannot overwrite it. Discovery does not hold
+the workspace source-registration lock.

package/providers/context/resources/manuals/guides/workspace-prepare.md

@@ -6,6 +6,18 @@ mediaType: text/markdown
 
 # Prepare a workspace for the next task
 
+## Capture-only requests in an existing workspace
+
+An explicit request to capture named documents and pause does not start article
+production. Register those sources first using the source-registration contract,
+then reevaluate status for the capture Route. Capture precedes the cleared-task
+resumption gate, so `task resume` is unnecessary for this request. Do not create
+a production stage and then clear it to return to capture. Retain existing tasks,
+drafts, approved content and source registrations. Stop after reporting the
+selected capture results; resumption requires a request to produce knowledge.
+The preparation and cleanup procedure below applies only when cleanup itself
+is requested, not merely because the workspace previously completed a task.
+
 Agent policy: `context.gate.workspace_reset_restore`. A clear request to
 prepare this workspace authorizes the described task-state cleanup; clarify
 only an unresolved target or loss.

package/providers/context/resources/manuals/reference/project-api.md

@@ -30,6 +30,10 @@ state.
 
 ## Sources
 
+For optional directory inventories and recoverable registration, see
+[Resumable source operations](../guides/source-batches.md). These operations do
+not select or expand the current production scope.
+
 ```ts
 const repo = source("20260901", "component-lib");
 const docs = source("20260901/product-docs", { type: "file" });

package/providers/context/resources/procedures/document-capture.md

@@ -9,6 +9,12 @@ mediaType: text/markdown
 Capture creates a reproducible local snapshot of a registered document source.
 It does not classify, summarize, approve, or build knowledge.
 
+For an explicit capture-and-pause request, register the named sources before
+starting article production. Do not call `task resume` or prepare/clear a
+production stage merely to reach capture. Once the selected documents have
+outcomes, report those outcomes and stop. Preserve unrelated pending sources
+and unfinished production work; a Route does not broaden the user's scope.
+
 Before capture:
 
 1. every registered document module must have a matching capture declaration;
@@ -36,10 +42,17 @@ child sandbox. If the CLI reports an external-environment requirement, retry
 the same returned command through the host. Never downgrade credential
 protection as a recovery step.
 
-Capture targets are a batch. Process one current target, evaluate status again,
+Capture targets are a batch. Process one current target, consume its freshly
+returned Route if present, or evaluate status when no fresh Route is returned,
 and continue until the graph reports the batch complete. Never treat one
 successful module as completion of the whole batch.
 
+Use the capture result's source identity, fidelity and resource-materialization
+summary for the final report. Open the full audit file only for truncated output,
+an unexplained outcome, or a requested investigation. Report previews as previews
+and unavailable resources as unavailable; no additional Git inspection or source
+lookup is required solely to repeat an already complete capture receipt.
+
 The CLI owns normalization, snapshot identity, hashes, manifests, and
 idempotency. For Lark sources it also owns embedded-resource download,
 structured export, completeness reporting, and link projection. Required

package/providers/context/resources/procedures/knowledge-review.md

@@ -65,6 +65,13 @@ preview after replacement delivery, and repair its
 reported incoming references. Navigation removal alone does not remove content
 from search or packages. A renamed menu does not require a new article identity.
 
+Before requesting human review, follow the report's navigation diagnostics.
+Bind unplaced drafts to suitable existing categories using the returned adjustment
+action, then regenerate the report. Draft placement does not require content
+approval. Ask about placement only when the existing structure and task do not
+establish a reasonable destination. Keep unplaced pages visible for diagnosis;
+do not describe the report as ready while placement is unresolved.
+
 The report opens on a change overview, with the existing navigation and an
 expected workspace file tree. The CLI collects approved titles, navigation and
 candidate bodies; it renders their changes mechanically. Do not write a second
@@ -160,3 +167,9 @@ any fallback affecting reader understanding. Reuse the planning choice; do not
 turn image handling into another per-article approval. Missing image content must
 not be presented as read or fully covered. Build-only media fallbacks are reported
 in the build receipt and do not rewrite approved evidence.
+
+Within the current revision scope, remove research-baseline prose (repository
+commit IDs or capture revisions repeated in the article). Preserve source
+references and exact citation destinations. Keep versions or comparison baselines
+that explain business behavior, compatibility, migrations or measured performance.
+Do not turn this editorial check into a keyword gate or an unrelated cleanup.

package/providers/context/resources/procedures/knowledge-updates.md

@@ -500,6 +500,12 @@ the user without blocking an independently supported local correction.
 
 ## Import a document response already read by the host
 
+For complete snapshots produced by `context source fetch lark`, use the optional
+`snapshot_dir` form described in [Lark resource reuse](../manuals/guides/lark-resources.md#reuse-a-complete-planning-snapshot).
+It reuses saved bodies and all captured resources without remote reads, retaining
+their original capture time and source revision. The response-file form below
+remains supported when the host supplies its own full document responses.
+
 For a registered Lark source, retain the actual full JSON response from
 `lark-cli docs +fetch` and each returned continuation page. Do not reconstruct a
 response from a summary. Use the same source import command:

package/providers/context/resources/procedures/source-capture-detailed.md

@@ -43,10 +43,21 @@ discussion, or register-only request is not permission, and an explicit refusal
 always wins.
 Register several file/Lark/repo sources with `context source add batch [date]
 --input <yaml|json|->`; do not launch multiple `source add` processes in
-parallel. Repo batch items require `module`; file/Lark items may omit it and use
+parallel. Long authorized batches can add `--checkpoint --progress`; use the
+returned status and resume commands after interruption instead of rebuilding
+the input. The checkpoint is advisory; resume revalidates the original input
+against current sources. Repo batch items require `module`; file/Lark items may omit it and use
 the module returned by the CLI. A write-lock error means another Context mutation is active: wait for
 it to finish and retry rather than editing registry files.
 
+Register a supplied Lark document or Wiki URL directly. `title` and `module` are
+optional: the CLI derives a stable module locally, and capture obtains the title
+with the document body. Do not call Wiki metadata, resolve a document token, or
+fetch a title separately just to prepare registration. Keep an already known
+title when useful; otherwise omit it instead of delaying capture to discover it.
+For several URLs, one batch payload can contain only `type: lark` and `url` for
+each source. Registration itself does not fetch remote content or grant access.
+
 
 ## Repository boundaries before bulk work
 
@@ -89,14 +100,22 @@ separate artifacts: XML audit evidence and a deterministic readable Markdown
 projection. Do not treat raw XML as Markdown and do not rewrite it yourself.
 The CLI also materializes supported embedded resources and returns a closed
 `resource_materialization` report. Required images, attachments, Sheets, Bases,
-whiteboards, diagrams, and synced blocks must be materialized before downstream
-Review. Polls and navigation references remain explicit non-interactive
+whiteboards, diagrams, and synced blocks are processed under the source's
+effective resource policy. Polls and navigation references remain explicit non-interactive
 projections; video is reference-only unless the project SDK opts into bundling.
 If the remote API explicitly confirms that a referenced whiteboard or diagram
 no longer exists, preserve the unresolved placeholder and the structured
 `document.resource.source-missing` warning, then continue through the Route.
-This is an audited source-side deletion, not successful materialization. Access,
-network, parameter, and unknown resource failures still block downstream work.
+This is an audited source-side deletion, not successful materialization.
+For an explicitly recognized permission denial, the CLI tries a supported
+same-identity fallback. A preview is retained as a preview; a resource that
+remains inaccessible stays unavailable with its reference and reason. These
+warnings do not block the preserved body or trigger resource-level identity
+switching, authorization prompts, or requests to change application permissions.
+Do not use unavailable resources as content evidence or claim that previews
+contain the original's complete data. Network, parameter, and unknown failures
+retain the CLI's failure classification; a generic HTTP 400 is not proof of a
+permission error.
 Do not manually download resources or patch links. Approved resources move to
 `knowledge/assets/`, and package build projects selected resources to
 `others/assets/`.
@@ -219,9 +238,10 @@ Preserve commands, reason codes, ids, and diagnostics exactly; summarize
 successful capture results for the user instead of dumping raw JSON. After any
 capture result:
 
-- Run `context status --format json` and treat `workflow.current` as the
-  current-step authority; if the route returns `configuration`, perform only
-  that declared project edit and rerun status.
+- Consume a fresh `workflow.current` returned with the command result as the
+  current-step authority. If no fresh workspace Route was returned, run
+  `context status --format json` once. If the route returns `configuration`,
+  perform only that declared project edit and rerun status.
 - If `workflow.current.commands` contains another capture command for the
   confirmed batch, execute it before asking another naming, collection, or
   read-permission question.
@@ -250,6 +270,18 @@ retrying capture.
 
 Report in the user's conversation language. Translate section headings into the user's language instead of copying the English labels below verbatim. Optimize for human readability: use document titles instead of source ids, package names instead of internal source id strings, and human-readable kind labels ("local markdown", "Feishu doc", "code package") instead of internal tokens. Do not surface content hashes, snapshot digests, internal payload identifiers, or absolute file paths.
 
+Use the capture command's returned `source`, `documents`, `snapshot`, `fidelity`,
+and `resource_materialization` for the completion summary. They already contain
+the title, body line count, change flag, resource counts, and per-resource reasons;
+`access_identity` records the identity actually used. Reuse `source.url` when
+present, or the user's original URL; do not construct a host URL from an opaque
+token. Count `document.resource.preview` items separately from original downloads,
+and distinguish reference-only or unavailable resources from acquired evidence.
+Do not reopen the manifest/report, inspect Git changes, or perform a separate
+link lookup solely to repeat fields already returned. Open detailed evidence only
+for a concrete missing fact, failure investigation, or requested audit. The
+workspace Route, not a successful resource count, determines workflow readiness.
+
 Stable structure:
 
 1. Completion headline. Single line with the action verb plus core counts: how

package/providers/context/resources/procedures/workspace-prepare.md

@@ -6,6 +6,18 @@ mediaType: text/markdown
 
 # Prepare a workspace for the next task
 
+## Capture-only requests in an existing workspace
+
+An explicit request to capture named documents and pause does not start article
+production. Register those sources first using the source-registration contract,
+then reevaluate status for the capture Route. Capture precedes the cleared-task
+resumption gate, so `task resume` is unnecessary for this request. Do not create
+a production stage and then clear it to return to capture. Retain existing tasks,
+drafts, approved content and source registrations. Stop after reporting the
+selected capture results; resumption requires a request to produce knowledge.
+The preparation and cleanup procedure below applies only when cleanup itself
+is requested, not merely because the workspace previously completed a task.
+
 Agent policy: `context.gate.workspace_reset_restore`. A clear request to
 prepare this workspace authorizes the described task-state cleanup; clarify
 only an unresolved target or loss.