@c4a/context-cli 0.7.10-alpha.1 → 0.7.10

package/providers/context/manifest.json

@@ -2,7 +2,7 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.7.10-alpha.1"
+    "version": "0.7.10"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
@@ -208,7 +208,7 @@
     {
       "id": "context.sdk.project-api",
       "path": "resources/manuals/reference/project-api.md",
-      "digest": "sha256:c885675aa4c31b6c4b765498dd31517d4851b663636c50cfe538217af20c3148"
+      "digest": "sha256:2a6f4d9856827c5699226216579153b163e184f8c5dec6c9660c859966a3de8d"
     },
     {
       "id": "context.sdk.template-variables",
@@ -293,7 +293,7 @@
     {
       "id": "procedure.close-and-build",
       "path": "resources/procedures/close-and-build.md",
-      "digest": "sha256:397e4e426cc86777e6f34cd22391e8f32785be765714762a908669eeadbb06e9"
+      "digest": "sha256:c2f39abc2867e73a529ded2e475276738f62a4b61811b7792a49d6e358865a74"
     },
     {
       "id": "procedure.document-capture",
@@ -318,7 +318,7 @@
     {
       "id": "procedure.knowledge-updates",
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:cccbd04d452b4c4b5e6661d8d26f449ab4a1476201763a94bc1b1085fe9fc8cb"
+      "digest": "sha256:509c083ee40e96465396ea7ee8281cf18837a669f0882def19d55abc05ce86a7"
     },
     {
       "id": "procedure.note",
@@ -343,7 +343,7 @@
     {
       "id": "procedure.production-stage-files",
       "path": "resources/procedures/production-stage-files.md",
-      "digest": "sha256:cfc137270976b78591b189d274f1dd7fc9576b9325914836e5254ebd7cde7ba6"
+      "digest": "sha256:7ac5ee8e370dd887fb1e24419adfcbe66aec174aa8ce651a1f7f763864972e73"
     },
     {
       "id": "procedure.project-configuration",
@@ -373,7 +373,7 @@
     {
       "id": "procedure.source-capture-detailed",
       "path": "resources/procedures/source-capture-detailed.md",
-      "digest": "sha256:6d9a86e30e2c17df41850463f01e8bb02bcf2744cb10acf1bcaacb48ade9808a"
+      "digest": "sha256:04588ea5955c3796e867d091a0fba6fcc5d854c94805bfca4ae1fd398f5542c4"
     },
     {
       "id": "procedure.source-update",
@@ -393,7 +393,7 @@
     {
       "id": "procedure.work-start-report",
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:6cf90b883205b82579a1c737350c8507513cdde48e78d8e67c35ceb0c743dac1"
+      "digest": "sha256:14574e9874c393f16601604eb1d460012dc7ee5da85c8228562d772407c48761"
     },
     {
       "id": "procedure.workspace-commit",
@@ -403,7 +403,7 @@
     {
       "id": "procedure.workspace-prepare",
       "path": "resources/procedures/workspace-prepare.md",
-      "digest": "sha256:2070ad93fecb856b22e6b7183dce2262ba7ed14d117c9a3fb11ddd7433959dee"
+      "digest": "sha256:fdbfdeb1486c998785b41569cf6ed57c744e6265d11610d320a60ede0ebbc2c8"
     },
     {
       "id": "procedure.workspace-restore",
@@ -593,7 +593,7 @@
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:2f1fafedc777f5040ac75f91bb4a74129987d881063229d9cc72be0ec5b698fa"
+      "digest": "sha256:7aa52ec56fd418284a036924f462e2ff85b4dd0d09c9ebf9598700a6fcf5ee78"
     },
     {
       "path": "resources/contracts/indexer-provider-guide.yaml",
@@ -649,11 +649,11 @@
     },
     {
       "path": "resources/manuals/guides/indexer-provider-and-customization.md",
-      "digest": "sha256:ca719f378668df609f3e8e98847a1c14d5e49cff2acd27d11d99e69726d0d825"
+      "digest": "sha256:57775f65ef70e622162f526522412cd2d54fbfbdf13a303300549705d34d3ccd"
     },
     {
       "path": "resources/manuals/guides/knowledge-updates.md",
-      "digest": "sha256:2ebadaa4a43742f8138ae50a0a06d76cabd73ccc1109c186c622a34abff0dc5b"
+      "digest": "sha256:117f1385d381be6420107ccd0ba399b45ad5c027d9dcdd825740bbebacd28365"
     },
     {
       "path": "resources/manuals/guides/lark-resources.md",
@@ -681,7 +681,7 @@
     },
     {
       "path": "resources/manuals/guides/workspace-prepare.md",
-      "digest": "sha256:914b8889c4430ce5358977354088b10ab806e17ca1ad72587c3778fad7cbc09e"
+      "digest": "sha256:0ee9b75fc2fa3237eef2119a90f217e913297cb036a4653a12369f2b00147ad9"
     },
     {
       "path": "resources/manuals/guides/workspace-restore.md",
@@ -697,7 +697,7 @@
     },
     {
       "path": "resources/manuals/reference/project-api.md",
-      "digest": "sha256:c885675aa4c31b6c4b765498dd31517d4851b663636c50cfe538217af20c3148"
+      "digest": "sha256:2a6f4d9856827c5699226216579153b163e184f8c5dec6c9660c859966a3de8d"
     },
     {
       "path": "resources/manuals/reference/template-variables.md",
@@ -709,7 +709,7 @@
     },
     {
       "path": "resources/procedures/close-and-build.md",
-      "digest": "sha256:397e4e426cc86777e6f34cd22391e8f32785be765714762a908669eeadbb06e9"
+      "digest": "sha256:c2f39abc2867e73a529ded2e475276738f62a4b61811b7792a49d6e358865a74"
     },
     {
       "path": "resources/procedures/document-capture.md",
@@ -729,7 +729,7 @@
     },
     {
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:cccbd04d452b4c4b5e6661d8d26f449ab4a1476201763a94bc1b1085fe9fc8cb"
+      "digest": "sha256:509c083ee40e96465396ea7ee8281cf18837a669f0882def19d55abc05ce86a7"
     },
     {
       "path": "resources/procedures/note.md",
@@ -749,7 +749,7 @@
     },
     {
       "path": "resources/procedures/production-stage-files.md",
-      "digest": "sha256:cfc137270976b78591b189d274f1dd7fc9576b9325914836e5254ebd7cde7ba6"
+      "digest": "sha256:7ac5ee8e370dd887fb1e24419adfcbe66aec174aa8ce651a1f7f763864972e73"
     },
     {
       "path": "resources/procedures/project-configuration.md",
@@ -773,7 +773,7 @@
     },
     {
       "path": "resources/procedures/source-capture-detailed.md",
-      "digest": "sha256:6d9a86e30e2c17df41850463f01e8bb02bcf2744cb10acf1bcaacb48ade9808a"
+      "digest": "sha256:04588ea5955c3796e867d091a0fba6fcc5d854c94805bfca4ae1fd398f5542c4"
     },
     {
       "path": "resources/procedures/source-update.md",
@@ -789,7 +789,7 @@
     },
     {
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:6cf90b883205b82579a1c737350c8507513cdde48e78d8e67c35ceb0c743dac1"
+      "digest": "sha256:14574e9874c393f16601604eb1d460012dc7ee5da85c8228562d772407c48761"
     },
     {
       "path": "resources/procedures/workspace-commit.md",
@@ -797,7 +797,7 @@
     },
     {
       "path": "resources/procedures/workspace-prepare.md",
-      "digest": "sha256:2070ad93fecb856b22e6b7183dce2262ba7ed14d117c9a3fb11ddd7433959dee"
+      "digest": "sha256:fdbfdeb1486c998785b41569cf6ed57c744e6265d11610d320a60ede0ebbc2c8"
     },
     {
       "path": "resources/procedures/workspace-restore.md",
@@ -896,5 +896,5 @@
     "indexer": [],
     "workspace": []
   },
-  "digest": "sha256:ac0730b3cd1060b6def03b9702d36fba6b6d55d72d45d43a3667aaf9999877b6"
+  "digest": "sha256:a0ca654f19065b2ce03eaabdd76631c477eaa951eb7957f6bff027110600f74f"
 }

package/providers/context/provider.yaml

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

package/providers/context/resources/manuals/guides/indexer-provider-and-customization.md

@@ -34,7 +34,6 @@ production assignments. For example, replace the source and goals with the
 user's actual scope:
 
 ```yaml
-protocol: context.indexer.registry/v1
 requirements:
   - id: integration-guide
     purpose: Help application developers understand and integrate the system.
@@ -47,7 +46,6 @@ requirements:
     evidence_source_scope:
       targets:
         - source_ref: repo:sample
-indexers: []
 ```
 
 Use registered source identities, not guessed paths or URLs. Keep any confirmed

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

@@ -22,6 +22,22 @@ and continues through Review and delivery. Expression-only changes need no
 source capture or Parser. Preserve prior confirmed contributions; distinguish
 actual behavior, a confirmed decision, and a proposal that is not implemented.
 
+## Keep planning local to the change
+
+For one or two documents or a clearly bounded module, retain the useful planning
+decision: add or revise which articles, and place them where readers expect them.
+Do not expand this into a whole-workspace taxonomy, full navigation redesign or
+multi-wave plan. Read related existing topics first and expand only as needed.
+One module can contain several topics; scope and ambiguity, not source count,
+determine how much investigation is useful.
+
+Reuse an approved stage's plan for in-scope additions through its existing amendment
+route. Keep completed work and unrelated pending investigation intact. If article
+targets are already decided before approval, the preparation route supports a
+known-task input to combine preparation and task creation. It still prepares
+navigation and retains report confirmation; it is not a bypass for new source
+authorization. Planning depth is an Agent judgment, not an additional CLI gate.
+
 ## First-task intake budget
 
 Before registration and capture, the Agent uses the user's task instructions and
@@ -62,7 +78,14 @@ progress under `.tmp/` never causes a version increase.
 Version recording runs at completed-scope delivery after Review, Close and package
 configuration/template approval, before the final build. The record response
 returns the next workspace Route, so no extra status call is needed. Build retries
-reuse the recorded version when formal content is unchanged. Intermediate batches
+reuse the recorded version when formal content is unchanged. If build preparation
+or rendering fails and formal corrections are needed, `version inspect` returns
+`reusable_version` for the current entry only while it has no successful build or
+publication receipt. Submit that same version with the complete iteration's title,
+changes and triggers, including the repair; this replaces the pending changelog
+entry rather than appending another version. Do not submit only the repair and
+lose the original delivery description. Once built or published, the version is
+sealed and further formal changes require an increase. Intermediate batches
 do not each receive a version.
 
 The workspace AGENTS.md and version-writing instructions require each entry's
@@ -91,7 +114,10 @@ actor:
 ```
 
 `actor` is optional; omit it to use local Git `user.name` when configured. Use a
-Lark display name only when explicitly known from the conversation. Trigger kinds
+Lark display name only when explicitly known from the conversation. Amending an
+unbuilt entry preserves its actor unless a replacement is explicitly supplied.
+If neither the conversation nor Git identifies the user, omit the actor and
+mention the missing identity in the delivery summary; never guess it. Trigger kinds
 are `initial`, `note`, `sessions`, `mr`, `module`, `document`, `navigation`,
 `repair`, `dist`, and `other`. Agent-written fields describe the actual diff and
 conversation; they must not expose credentials, raw transcripts or private IDs.

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

@@ -42,6 +42,23 @@ reports, unique material, unknown files and modified checkouts unless their
 specific loss is authorized. Do not delete locks, transaction records or active
 tool directories. Empty task directories can remain.
 
+Prefer cleanup after successful delivery, not immediately after close: version
+recording, build and retries may still need the current task. Completed production
+drafts and Review state are removed by delivery cleanup. Do not invoke
+`task resume` merely to make a completed workspace advance; it starts a new task
+and requires an actual new user request.
+
+Keep repository checkouts referenced by registered sources, including fixed
+commits: removing them can force a costly clone before the next update. Keep
+pending telemetry and source-region baselines; losing the latter reduces the
+ability to distinguish relocated text from changed text. Debug and historical
+views may be archived or removed after diagnosis when no operation is active,
+but unknown Agent files are not automatically disposable.
+
+After all scratch state is lost, an existing build receipt defaults the workspace
+to waiting for an explicit new task. This does not restore lost drafts or prove
+sources and outputs are current. Use the recovery checks below before resuming.
+
 ## Restore usable sources
 
 For repositories, run `context source recovery-plan --format json` and read

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

@@ -10,8 +10,8 @@ The project has two durable declarations with separate responsibilities:
 
 - `src/index.ts`: source references, document capture, custom non-knowledge
   orchestration, and package outputs.
-- `src/indexers.yaml`: knowledge requirements, Provider selection, target/read
-  scopes, profiles, and Provider customization.
+- `src/indexers.yaml`: long-term reader requirements, authorized target/supporting
+  sources and confirmed exclusions. Skill choices belong to the temporary plan.
 
 Do not describe the same knowledge transformation in both files.
 
@@ -59,6 +59,19 @@ and [knowledge updates](../guides/knowledge-updates.md).
 
 ## Capture phases
 
+For ordinary acquisition, add `--configure` to `context source add repo`, `file`,
+`lark` or `batch`. The command registers the selected inputs and generates explicit
+source references and default document capture phases in `src/index.ts`. It does
+not fetch content, select other registrations or change package outputs.
+
+Generation supports a literal `defineProject` with literal source/phase arrays
+and recognizable SDK calls. Existing capture settings are preserved, repeated
+registration is idempotent, and custom/dynamic entries remain untouched with a
+`configuration.status: manual` hint. Registration is still saved; edit only the
+needed declarations through the normal configuration path. For special processors
+or resource options, configure them before following the capture Route. Omitting
+`--configure` keeps registration-only behavior.
+
 ```ts
 captureFile({ source: docs });
 captureFile({ source: docs, processor: mdxJsonDocs() });
@@ -73,24 +86,27 @@ creating a second capture or knowledge pipeline.
 
 ### Batch capture from the source registry
 
-When all registered Lark documents are intended for this project and share capture
-settings, read the registry once instead of copying its module names into
-`src/index.ts`. For the standard `src/index.ts` entry:
+For documents with shared capture settings, prefer registry-driven configuration
+over repeating source declarations and capture calls, even for two documents.
+Select the task's intended registrations first. The example below assumes all
+registered Lark documents are in scope, with the standard `src/index.ts` entry:
 
 ```ts
 import { fileURLToPath } from "node:url";
 import {
-  allSources, captureLark, defineProject, loadSourcesRegistry, source,
+  captureLark, defineProject, loadSourcesRegistry, source,
 } from "@c4a/context";
 
 const workspaceRoot = fileURLToPath(new URL("../", import.meta.url));
 const registry = await loadSourcesRegistry({ rootDir: workspaceRoot });
+// For a subset, filter registry.larks by the authorized namespace/names here.
 const documents = registry.larks.map(entry =>
   source(entry.name, { type: "lark" }),
 );
 
 export default defineProject({
-  sources: [...allSources("repo"), ...documents],
+  sources: documents,
+  // Shared settings, independent source identities and capture phases.
   phases: documents.map(document => captureLark({ source: document })),
   packages: [],
 });
@@ -115,6 +131,10 @@ Registry loading only reads local registrations; it does not fetch documents.
 - The map declares one phase per document. It does not fetch URLs, change capture
   permissions, or request parallel execution. Run the declared phases through the
   existing CLI flow so each document retains independent refresh and retry behavior.
+  This reduces configuration repetition, not the number of capture operations.
+- Capture boundaries do not dictate article boundaries. During planning and
+  writing, combine related captured documents around reader tasks when useful;
+  do not create one article or a complete production cycle per source by default.
 
 ## `customPhase`
 
@@ -154,18 +174,18 @@ from the package name, if present. Omit it for KB-only output. It accepts `title
 `src/knowledge-map.yaml` independently of KB directories; see
 [Package Outputs](../guides/package-outputs.md#optional-static-documentation-website).
 
-## Indexer registry
+## Knowledge requirements and Indexer Skills
 
-When this file is absent, the configuration Route supplies the initial schema:
-write confirmed `requirements` with `indexers: []`, then re-evaluate. The Provider
-selection Action supplies its own completion schema; that payload is not the
-configuration file. Subsequent changes use typed proposals and applicable gates. Each selected Indexer binds requirements and scopes to one
-primary Provider, with optional declared layers or composers. Provider code
-must return the current Indexer result protocol; it must not write Candidate,
-knowledge, or Review files directly.
+When `src/indexers.yaml` is absent, the configuration Route supplies its schema.
+Write `requirements` only; do not add `protocol`, `indexers`, Provider selections
+or profiles. Re-evaluate after changing confirmed requirements.
 
-Detailed Provider protocol and customization guidance is selected by the
-current workflow Route when it is needed.
+Installed Indexer Skills guide investigation and writing. Relevant Skill choices
+and optional configuration use `indexer_usage` in the temporary production plan,
+not this durable file. There is no separate Provider selection or resolution gate.
+The Agent writes task drafts and reference files under the returned temporary
+directory; the CLI accepts them and owns Candidate, Review and formal output.
+See [Indexer guidance](../guides/indexer-provider-and-customization.md).
 
 ## Persistent versus runtime state
 

package/providers/context/resources/procedures/close-and-build.md

@@ -9,10 +9,31 @@ mediaType: text/markdown
 At completed-scope delivery, follow the version-recording Route. The coordinator
 writes the semantic changelog from formal diffs and the conversation, including
 the triggering source and an explicitly known user (Git name is the default).
+Pass `actor` explicitly when the conversation identifies the triggering user,
+including a known Lark display name. If Git has no name and the conversation
+does not identify the user, leave it absent and mention that in the delivery
+summary; do not infer identity from paths, logins or source authors. Amending
+an unbuilt entry preserves its actor unless an explicit replacement is supplied.
 Record after Close and package/template approval, before the final build, so the
 selected outputs are built with the new version once. Build records hashes without
 increasing versions. Never count temporary progress or a build retry as a change.
 
+For formal repairs before a successful build, use `version inspect`'s
+`reusable_version` when present. Submit the same version and a complete updated
+changelog covering the original work plus repairs, not a repair-only replacement.
+The CLI updates the pending entry in place. A successful build or publication
+seals that version; subsequent changes require an increase. Do not delete build
+or publication receipts to reopen history.
+
+Successful delivery clears completed task drafts. Do not empty `.tmp` or call
+`task resume` as a finalization step. Retain registered repository checkouts,
+source-region baselines and queued logs for reuse; optional historical-cache
+cleanup follows the workspace preparation guide after delivery, not after close.
+
+Website rendering must preserve literal code and template examples. Do not revise
+valid source-grounded JSX or template syntax merely to avoid Vue interpolation;
+report a rendering defect if the website compiler cannot display it literally.
+
 Before an authorized external publication, run `context version publish-check
 --format json`. If `needs_version` is true, inspect with `context version inspect
 --publish --format json`, record a patch changelog using a `dist` trigger, and

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

@@ -22,6 +22,22 @@ and continues through Review and delivery. Expression-only changes need no
 source capture or Parser. Preserve prior confirmed contributions; distinguish
 actual behavior, a confirmed decision, and a proposal that is not implemented.
 
+## Keep planning local to the change
+
+For one or two documents or a clearly bounded module, retain the useful planning
+decision: add or revise which articles, and place them where readers expect them.
+Do not expand this into a whole-workspace taxonomy, full navigation redesign or
+multi-wave plan. Read related existing topics first and expand only as needed.
+One module can contain several topics; scope and ambiguity, not source count,
+determine how much investigation is useful.
+
+Reuse an approved stage's plan for in-scope additions through its existing amendment
+route. Keep completed work and unrelated pending investigation intact. If article
+targets are already decided before approval, the preparation route supports a
+known-task input to combine preparation and task creation. It still prepares
+navigation and retains report confirmation; it is not a bypass for new source
+authorization. Planning depth is an Agent judgment, not an additional CLI gate.
+
 ## First-task intake budget
 
 Before registration and capture, the Agent uses the user's task instructions and
@@ -62,7 +78,14 @@ progress under `.tmp/` never causes a version increase.
 Version recording runs at completed-scope delivery after Review, Close and package
 configuration/template approval, before the final build. The record response
 returns the next workspace Route, so no extra status call is needed. Build retries
-reuse the recorded version when formal content is unchanged. Intermediate batches
+reuse the recorded version when formal content is unchanged. If build preparation
+or rendering fails and formal corrections are needed, `version inspect` returns
+`reusable_version` for the current entry only while it has no successful build or
+publication receipt. Submit that same version with the complete iteration's title,
+changes and triggers, including the repair; this replaces the pending changelog
+entry rather than appending another version. Do not submit only the repair and
+lose the original delivery description. Once built or published, the version is
+sealed and further formal changes require an increase. Intermediate batches
 do not each receive a version.
 
 The workspace AGENTS.md and version-writing instructions require each entry's
@@ -91,7 +114,10 @@ actor:
 ```
 
 `actor` is optional; omit it to use local Git `user.name` when configured. Use a
-Lark display name only when explicitly known from the conversation. Trigger kinds
+Lark display name only when explicitly known from the conversation. Amending an
+unbuilt entry preserves its actor unless a replacement is explicitly supplied.
+If neither the conversation nor Git identifies the user, omit the actor and
+mention the missing identity in the delivery summary; never guess it. Trigger kinds
 are `initial`, `note`, `sessions`, `mr`, `module`, `document`, `navigation`,
 `repair`, `dist`, and `other`. Agent-written fields describe the actual diff and
 conversation; they must not expose credentials, raw transcripts or private IDs.

package/providers/context/resources/procedures/production-stage-files.md

@@ -15,6 +15,20 @@ name useful reading scope; module labels do not imply directory permissions.
 No module mapping file, version receipt or article-level scope fields are needed.
 Read related code as needed within the user's authorized sources.
 
+Keep planning proportional to this request. For a short document task or one
+bounded module, decide whether to add or revise related articles and their reading
+position; do not redesign unrelated modules or the whole site. Start with relevant
+existing topics, not every navigation page. Expand investigation when the material
+requires it, not to fill a planning template. One batch is sufficient unless real
+dependencies or useful parallel work call for more. Source count is not a page
+count or a CLI threshold.
+
+During an approved stage, use the existing plan-amendment path for in-scope
+additions and preserve completed work. Do not restart planning solely because
+another article is ready to write. Keep remaining investigation explicit; a small
+current task does not mean other authorized work is finished. New source or purpose
+authorization still follows the current Route.
+
 Write results under the returned Agent directory. All submission paths are
 relative to that stage directory, even when the manifest is in `submissions/`.
 Copy the CLI's submission template, keep completed tasks only, and keep each

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

@@ -121,6 +121,14 @@ manager or version.
 
 ### Route by source boundary
 
+For explicitly selected sources needing ordinary capture settings, use
+`source add ... --configure` (also supported by `source add batch`) to register
+and generate explicit `src/index.ts` declarations in one call. This does not
+capture, select unrelated registrations, or change output settings. Inspect the
+returned configuration result: custom/dynamic entries return `manual` and remain
+unchanged; preserve them and make a focused edit. If special processors/resources
+are needed, configure those before capture. Do not retry generation in a loop.
+
 Before choosing a local Markdown capture route, honor the surrounding task context. Driver documents such as run instructions, handbooks, READMEs, plans, feedback issues, corpus/index/manifests, and batch lists are not Context sources unless the user explicitly asks to ingest them. Capture only ingest targets that are already explicit in the user request; if they are missing, ask one clarification instead of capturing the driver document.
 
 - One or more local `.md` / `.mdx` files or a local documentation folder to ingest →
@@ -147,15 +155,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark [YYYYMMDD] --module <module> --url <url>` or the
   matching token flag. Register every requested document under the same date;
-  do not ask for `YYYYMMDD-2`. Declare
+  do not ask for `YYYYMMDD-2`. For multiple documents, use the shared configuration
+  pattern below rather than repeating declarations. For a single document, declare
   `captureLark({ source: source("<date>", "<module>", { type: "lark" }) })`,
-  then run `context run capture:lark:<date>/<module> --format json`.
+  then follow the current Route to execute capture.
 - For a registered document batch with shared capture settings, use
   [Batch capture from the source registry](../manuals/reference/project-api.md#batch-capture-from-the-source-registry)
   to load the registry and generate typed references and phases. Do not transcribe
   the full YAML module list into `src/index.ts`. Select only the intended entries;
   use the entire registry only when all its documents are in scope. Preserve
   existing phases/packages and keep processor or resource exceptions per document.
+  Prefer this pattern even for two documents with the same settings. It reduces
+  configuration repetition, not capture operations or permission boundaries.
+  Independent source identities do not require independent articles: plan and
+  write across related captured documents by reader task, not one production
+  cycle per input document.
 - Mixed local document and Lark document batches are separate sources unless
   the current CLI explicitly offers a combined source contract. Mapping registered
   entries into declarative SDK phases is supported; writing an Agent-side loop

package/providers/context/resources/procedures/work-start-report.md

@@ -38,9 +38,13 @@ confirmed/provisional topics, unchecked ranges and delivery implications. If
 document acquisition is blocked, ask whether a limited first scope is acceptable;
 do not silently omit supplied documents or claim full coverage from partial scans.
 
-Small, clearly scoped revisions, notes and conversation summaries can use a short
-handling proposal. Do not invent an independent planning phase to fill a report;
-do not use this exception to bypass feedback on a bulk build.
+Small, clearly scoped document tasks, single-module work, revisions, notes and
+conversation summaries can use a short handling proposal: which related articles
+to add or revise, their reading position and the intended result. A module with
+several reader topics may need more planning within that module, not a redesign
+of the whole knowledge base. Do not invent an independent investigation, batch
+hierarchy or dependency analysis to fill a report. This changes report depth, not
+the current Route's approval boundary.
 
 ## Explain the proposed work
 
@@ -60,12 +64,14 @@ per-module ownership tables. One module may use several Indexers and one article
 may combine their materials. Optional specialist absence does not exclude sources.
 
 Reuse selected KB, website and LLMS delivery channels. For website delivery,
-include a compact proposed menu and layout: top-level groups, a representative
+for a new site or requested navigation redesign, include a compact proposed menu and layout: top-level groups, a representative
 left menu, article chapters and on-page outline. Explain mobile behavior briefly
 when relevant. This is a sketch, not a built site; do not create empty articles,
 temporary websites or promise deployment. Link the existing requirement or
 workspace configuration rather than creating a permanent report identity.
 Estimate timing or savings only when supported by measurements and conditions.
+For a small addition to an existing site, describe only the affected reading
+position; reuse its layout and delivery choices instead of proposing them again.
 
 ## Mandatory feedback
 

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

@@ -42,6 +42,23 @@ reports, unique material, unknown files and modified checkouts unless their
 specific loss is authorized. Do not delete locks, transaction records or active
 tool directories. Empty task directories can remain.
 
+Prefer cleanup after successful delivery, not immediately after close: version
+recording, build and retries may still need the current task. Completed production
+drafts and Review state are removed by delivery cleanup. Do not invoke
+`task resume` merely to make a completed workspace advance; it starts a new task
+and requires an actual new user request.
+
+Keep repository checkouts referenced by registered sources, including fixed
+commits: removing them can force a costly clone before the next update. Keep
+pending telemetry and source-region baselines; losing the latter reduces the
+ability to distinguish relocated text from changed text. Debug and historical
+views may be archived or removed after diagnosis when no operation is active,
+but unknown Agent files are not automatically disposable.
+
+After all scratch state is lost, an existing build receipt defaults the workspace
+to waiting for an explicit new task. This does not restore lost drafts or prove
+sources and outputs are current. Use the recovery checks below before resuming.
+
 ## Restore usable sources
 
 For repositories, run `context source recovery-plan --format json` and read