@c4a/context-cli 0.7.14-beta.1 → 0.7.15

package/indexers/release-manifest.json

@@ -1,7 +1,7 @@
 {
   "protocol": "context.indexer.cli-release-manifest/v1",
   "package": "@c4a/context-cli",
-  "version": "0.7.14-beta.1",
+  "version": "0.7.15",
   "issuer": "context4ai/context",
   "bundles": [
     {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.7.14-beta.1",
+  "version": "0.7.15",
   "type": "module",
   "description": "Local runtime and Agent integration for traceable knowledge production",
   "license": "MIT",
@@ -24,17 +24,17 @@
   },
   "dependencies": {
     "@c4a/agent-graph": "0.3.0",
-    "@c4a/context": "0.7.14-beta.1",
-    "@c4a/extract": "0.7.14-beta.1",
-    "@c4a/extract-contract": "0.7.14-beta.1",
-    "@c4a/extract-go": "0.7.14-beta.1",
-    "@c4a/extract-mdx": "0.7.14-beta.1",
-    "@c4a/extract-proto": "0.7.14-beta.1",
-    "@c4a/extract-rush": "0.7.14-beta.1",
-    "@c4a/extract-sql": "0.7.14-beta.1",
-    "@c4a/extract-style": "0.7.14-beta.1",
-    "@c4a/extract-thrift": "0.7.14-beta.1",
-    "@c4a/extract-ts": "0.7.14-beta.1",
+    "@c4a/context": "0.7.15",
+    "@c4a/extract": "0.7.15",
+    "@c4a/extract-contract": "0.7.15",
+    "@c4a/extract-go": "0.7.15",
+    "@c4a/extract-mdx": "0.7.15",
+    "@c4a/extract-proto": "0.7.15",
+    "@c4a/extract-rush": "0.7.15",
+    "@c4a/extract-sql": "0.7.15",
+    "@c4a/extract-style": "0.7.15",
+    "@c4a/extract-thrift": "0.7.15",
+    "@c4a/extract-ts": "0.7.15",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",
     "handlebars": "^4.7.8",

package/parserEntryWorker.js

@@ -19955,6 +19955,12 @@ var getSourceType = (sourceDefinition) => {
 }), captureLark = (definition) => {
   const sourceDefinition = bindSourceType(definition.source, "lark", "captureLark source");
   const sourceId = getSourceName(sourceDefinition);
+  for (const key of ["images", "gifs"]) {
+    const value = definition.resources?.[key];
+    if (value !== undefined && value !== "bundle" && value !== "reference-only") {
+      throw new TypeError(`captureLark resources.${key} must be bundle or reference-only`);
+    }
+  }
   const maxBytesPerResource = definition.resources?.maxBytesPerResource ?? 20 * 1024 * 1024;
   const maxTotalBytes = definition.resources?.maxTotalBytes ?? 200 * 1024 * 1024;
   if (!Number.isSafeInteger(maxBytesPerResource) || maxBytesPerResource < 1) {
@@ -19973,6 +19979,8 @@ var getSourceType = (sourceDefinition) => {
     writes: [sourceSnapshotResource(sourceDefinition, "lark")],
     source: sourceDefinition,
     resources: {
+      ...definition.resources?.images === undefined ? {} : { images: definition.resources.images },
+      ...definition.resources?.gifs === undefined ? {} : { gifs: definition.resources.gifs },
       videos: definition.resources?.videos ?? "reference-only",
       maxBytesPerResource,
       maxTotalBytes

package/plugins/VERSION

@@ -1 +1 @@
-0.7.14-beta.1
+0.7.15

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
-  "version": "0.7.14-beta.1",
+  "version": "0.7.15",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/commands/context.md

@@ -49,6 +49,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

package/plugins/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.7.14-beta.1",
+  "version": "0.7.15",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": { "name": "c4a" },
   "homepage": "https://github.com/context4ai/c4a",
@@ -10,7 +10,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.14-beta.1",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.15",
     "longDescription": "Create a Context workspace and use agent-guided next steps to register sources, run extraction, review candidates, build package outputs, and verify health without silently mutating source repositories.",
     "developerName": "c4a",
     "category": "Productivity",

package/plugins/codex/skills/context/SKILL.md

@@ -47,6 +47,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.7.14-beta.1",
+  "version": "0.7.15",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": {
     "name": "Context4AI",

package/plugins/cursor/commands/c4a-context.md

@@ -44,6 +44,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

package/plugins/skills/context/SKILL.md

@@ -47,6 +47,17 @@ Within an active Context workflow, requests include, but are not limited to:
 | Commit workspace results | Save selected workspace files in local Git, without pushing or including unrelated changes. |
 | Restore a historical workspace version | Select a saved commit, restore only the agreed workspace scope and make its sources usable again. |
 
+## Preserve existing reading organization
+
+For additions as well as navigation edits, first read the workspace AGENTS.md,
+current map and relevant overview/category articles. Reuse their category intent;
+a new source or product does not by itself justify a top-level menu. Follow the
+knowledge-updates guidance returned by `context entry` or the current Route,
+especially "Preserve established navigation intent". Include proposed top-level
+changes in the work-start report or current plan for explicit human review before
+applying them; reuse a concrete structure the user has already approved. Ordinary
+placements within the approved organization do not require another review gate.
+
 ## Read the task before registering sources
 
 For a knowledge-map-only request, use the existing workspace directly. Read

package/providers/context/manifest.json

@@ -2,7 +2,7 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.7.14-beta.1"
+    "version": "0.7.15"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
@@ -183,7 +183,7 @@
     {
       "id": "context.sdk.lark-resources",
       "path": "resources/manuals/guides/lark-resources.md",
-      "digest": "sha256:3a80574fd70c160b362cee23ab01cbdc3ec366b503daa11aaaf242b7cf5dbe50"
+      "digest": "sha256:b1ffb74a145962ff89a5db29cffd1318e4ec038b97884dcd43804170cb0f6f64"
     },
     {
       "id": "context.sdk.package-outputs",
@@ -258,7 +258,7 @@
     {
       "id": "dialogue.knowledge-review",
       "path": "resources/dialogue/knowledge-review.md",
-      "digest": "sha256:2938843d7c07f03ea70144cd4f1800dedf2fca35610b815800c78c0ad6c2d723"
+      "digest": "sha256:d61cd56bc74ea0653ac6d02588115575ca7d7c21b4ac071d3868c4a2524242b6"
     },
     {
       "id": "dialogue.package-output",
@@ -288,7 +288,7 @@
     {
       "id": "procedure.document-capture",
       "path": "resources/procedures/document-capture.md",
-      "digest": "sha256:f09100425c2b89a126c35c4490b0644519a4eee214114f2f0f52b6ea20467a04"
+      "digest": "sha256:9d0d1b9187bbe540a4afffb366cd549385dbf61bfaffa96ae51de848b2dd5460"
     },
     {
       "id": "procedure.homogeneous-source-review",
@@ -303,12 +303,12 @@
     {
       "id": "procedure.knowledge-review",
       "path": "resources/procedures/knowledge-review.md",
-      "digest": "sha256:56185e8ea580015e89429a18faf3c7598f8200dc3ee458dbee04d6cbffadcb58"
+      "digest": "sha256:69dc39212547ea8a304c20d6fadc2bd3eb1de83eaf0c62dade8fcf5e8695c5d6"
     },
     {
       "id": "procedure.knowledge-updates",
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:f43943fdf9265e5181c2e8cf3753d981fc9f59a44ee11b5beac404ec481344ea"
+      "digest": "sha256:e3bf78d43ebc4263bc5d4c08984e51af6d4df16bd2d5d708622816442b777949"
     },
     {
       "id": "procedure.note",
@@ -328,7 +328,7 @@
     {
       "id": "procedure.production-requirements",
       "path": "resources/procedures/production-requirements.md",
-      "digest": "sha256:be0eda60679808dfe4f8fbe30639ad6f24590d8e7f2b588c233a4f611c045c92"
+      "digest": "sha256:a01bcdf788d9c8fd1cc6ba4ba47f19da6df99cd2397ed35eaaa3d3fdc8b6ec25"
     },
     {
       "id": "procedure.production-stage-files",
@@ -348,7 +348,7 @@
     {
       "id": "procedure.runtime-event-delivery",
       "path": "resources/procedures/runtime-event-delivery.md",
-      "digest": "sha256:bb7e695270d9d8780fa7b7cdd4cde883cc05a5f63e97fb18088838623f4ce381"
+      "digest": "sha256:06cf0f47ce2d88915645dcf17012159141ce0a02d427cb7784130345928c0700"
     },
     {
       "id": "procedure.sessions",
@@ -383,7 +383,7 @@
     {
       "id": "procedure.work-start-report",
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:d41a91d89eb917bcc15a601ef85d4ac5187bec18365098442e45647eb19b1e90"
+      "digest": "sha256:dd9de0f63a5de562f84ac1e860e8802934d5a6302e92a666028cd72e0cf18e48"
     },
     {
       "id": "procedure.workspace-commit",
@@ -413,7 +413,7 @@
     {
       "id": "template.work-start-report",
       "path": "resources/templates/work-start-report.md",
-      "digest": "sha256:fb7c5bba6d1c6b9f71e28539c5edda63c162e6a3ccc6623d81e6d649638c8802"
+      "digest": "sha256:f9acb9a959dee3d93e1877cd9737dfff7702733ae2121b454a9cc90adbaf89b2"
     }
   ],
   "schemas": [
@@ -570,7 +570,7 @@
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:820cc81bd72613211c7f1a48406bc881f6f4baf09ef415e635aa8da01aa08f0a"
+      "digest": "sha256:a2518b2b208567cf4ef63ab83d7c087de2f9ace2043e0e2b07f2218337d353f3"
     },
     {
       "path": "resources/contracts/indexer-provider-guide.yaml",
@@ -602,7 +602,7 @@
     },
     {
       "path": "resources/dialogue/knowledge-review.md",
-      "digest": "sha256:2938843d7c07f03ea70144cd4f1800dedf2fca35610b815800c78c0ad6c2d723"
+      "digest": "sha256:d61cd56bc74ea0653ac6d02588115575ca7d7c21b4ac071d3868c4a2524242b6"
     },
     {
       "path": "resources/dialogue/package-output.md",
@@ -626,11 +626,11 @@
     },
     {
       "path": "resources/manuals/guides/knowledge-updates.md",
-      "digest": "sha256:fe8c9e4dbe7413bce3c2007bf230f1312fca31de69d434d0c41171a27e1a68f5"
+      "digest": "sha256:3fa4b18e1919578e8939fffba40d250e8898ed6e85376fd2758abe3d12b908d8"
     },
     {
       "path": "resources/manuals/guides/lark-resources.md",
-      "digest": "sha256:3a80574fd70c160b362cee23ab01cbdc3ec366b503daa11aaaf242b7cf5dbe50"
+      "digest": "sha256:b1ffb74a145962ff89a5db29cffd1318e4ec038b97884dcd43804170cb0f6f64"
     },
     {
       "path": "resources/manuals/guides/markdown-indexer-skill-authoring.md",
@@ -690,7 +690,7 @@
     },
     {
       "path": "resources/procedures/document-capture.md",
-      "digest": "sha256:f09100425c2b89a126c35c4490b0644519a4eee214114f2f0f52b6ea20467a04"
+      "digest": "sha256:9d0d1b9187bbe540a4afffb366cd549385dbf61bfaffa96ae51de848b2dd5460"
     },
     {
       "path": "resources/procedures/homogeneous-source-review.md",
@@ -702,11 +702,11 @@
     },
     {
       "path": "resources/procedures/knowledge-review.md",
-      "digest": "sha256:56185e8ea580015e89429a18faf3c7598f8200dc3ee458dbee04d6cbffadcb58"
+      "digest": "sha256:69dc39212547ea8a304c20d6fadc2bd3eb1de83eaf0c62dade8fcf5e8695c5d6"
     },
     {
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:f43943fdf9265e5181c2e8cf3753d981fc9f59a44ee11b5beac404ec481344ea"
+      "digest": "sha256:e3bf78d43ebc4263bc5d4c08984e51af6d4df16bd2d5d708622816442b777949"
     },
     {
       "path": "resources/procedures/note.md",
@@ -722,7 +722,7 @@
     },
     {
       "path": "resources/procedures/production-requirements.md",
-      "digest": "sha256:be0eda60679808dfe4f8fbe30639ad6f24590d8e7f2b588c233a4f611c045c92"
+      "digest": "sha256:a01bcdf788d9c8fd1cc6ba4ba47f19da6df99cd2397ed35eaaa3d3fdc8b6ec25"
     },
     {
       "path": "resources/procedures/production-stage-files.md",
@@ -738,7 +738,7 @@
     },
     {
       "path": "resources/procedures/runtime-event-delivery.md",
-      "digest": "sha256:bb7e695270d9d8780fa7b7cdd4cde883cc05a5f63e97fb18088838623f4ce381"
+      "digest": "sha256:06cf0f47ce2d88915645dcf17012159141ce0a02d427cb7784130345928c0700"
     },
     {
       "path": "resources/procedures/sessions.md",
@@ -766,7 +766,7 @@
     },
     {
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:d41a91d89eb917bcc15a601ef85d4ac5187bec18365098442e45647eb19b1e90"
+      "digest": "sha256:dd9de0f63a5de562f84ac1e860e8802934d5a6302e92a666028cd72e0cf18e48"
     },
     {
       "path": "resources/procedures/workspace-commit.md",
@@ -790,7 +790,7 @@
     },
     {
       "path": "resources/templates/work-start-report.md",
-      "digest": "sha256:fb7c5bba6d1c6b9f71e28539c5edda63c162e6a3ccc6623d81e6d649638c8802"
+      "digest": "sha256:f9acb9a959dee3d93e1877cd9737dfff7702733ae2121b454a9cc90adbaf89b2"
     },
     {
       "path": "resources/views/package-current.yaml",
@@ -862,12 +862,12 @@
     },
     {
       "path": "skills/work-production-stage/SKILL.md",
-      "digest": "sha256:5bb250f42d5d28243daca30427b5fd9db52127460862748fc36935f0e0d0f754"
+      "digest": "sha256:cacf6ce1b106cfe7af7b07009e6a3658c04007c6eb49127069fa16e3b2892f31"
     }
   ],
   "graphDependencies": {
     "indexer": [],
     "workspace": []
   },
-  "digest": "sha256:0ce9bbc43630874ad90cf5663348b2c6f96dcdf7dd911f5e6b33c71154a3ea9e"
+  "digest": "sha256:40dfe816123dd5ab631d088d2c2337290dbc91516bb968b7be5f31be45282f6b"
 }

package/providers/context/provider.yaml

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

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

@@ -10,17 +10,18 @@ Explain that Review is the boundary between draft candidates and approved
 Markdown. In ordinary mode:
 
 1. open the complete current Review report;
-2. let the user approve or reject candidates;
+2. let the user approve, reject, or request revisions to candidates;
 3. ask them to copy the review code back into the conversation; and
 4. apply only that exact review code through the returned command.
 
 The user does not need to create a payload file; the Agent may write the pasted
 review code to ignored scratch storage for the CLI command. Preserve it exactly;
-do not decode, regenerate, summarize, or edit it. Each segment is at most 980
-characters. If there are multiple segments, collect all of them and write one
-segment per line in the same input file before applying once. Never apply a
-partial set. If CLI reports missing, mixed, damaged, or stale segments, follow
-its diagnostic; ask for missing segments or a fresh review code as appropriate.
+do not decode, regenerate, summarize, or edit it. The code carries decisions and
+revision instructions together. If it exceeds 1,000 characters, use a direct
+reply (mention the Bot when relevant) instead of a length-limited form. Older
+segmented codes still require every segment in the same input file. If the CLI
+reports damaged or stale feedback, follow its diagnostic and request a fresh
+report/code; never repair a code by hand.
 Never derive a payload
 from HTML, candidate ids, snapshots, or a default decision.
 
@@ -50,3 +51,10 @@ the index's current scope template. Approve only pages actually reviewed; leave
 undecided and repair pages pending. Do not open HTML or persist a parallel review
 ledger. A partial review code in ordinary mode likewise leaves pending pages
 unchanged; all segments of that code are still required.
+
+After applying feedback, follow each returned repair command with the user's
+exact instruction. Repairs remain pending; neither copying nor applying the
+code approves them. Pending instructions are retained by the CLI and exposed in
+the current review resource after a session restart. Re-read and review the
+resulting candidate before approval. Do not silently replace a revision request
+with rejection or bulk approval.

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

@@ -200,6 +200,48 @@ coverage by mechanically placing every new page under an unrelated catch-all.
 Build reports missing bindings for the Agent to resolve; it does not classify
 content. Moving a menu entry does not change the article URL.
 
+### Preserve established navigation intent
+
+Before placing new knowledge, read the workspace's AGENTS.md, current
+`src/knowledge-map.yaml`, existing overview pages and relevant category/article
+bodies. Reuse any settled directory intent in the current plan. Establish what
+each affected category helps readers do and why adjacent categories are separate;
+do not infer this from labels alone. Read only affected branches and enough
+neighboring content to distinguish them, not the entire library on every update.
+If intent remains ambiguous, state the proposed interpretation in the plan.
+
+Prefer, in order: revise an existing article; add a page to a matching category;
+add a coherent child category; propose a top-level change only when existing
+categories cannot serve a distinct, lasting reader need. Do not create a top-level
+category merely because a source, repository, product, team or batch is new.
+For example, a new assistant's usage guide, frontend integration and runtime
+architecture can belong in existing usage, frontend and backend categories, with
+cross-links for the shared product. Keep them together only when the site's
+established organizing principle supports that choice.
+
+In the work-start report or current plan, briefly state the affected articles'
+intended placements and reused category intent. For proposed top-level additions,
+renames, removals or changes of purpose, show the before/after tree, why reuse is
+insufficient, affected existing pages and reading order. Present that change for
+human review before applying it. This uses the existing report feedback where
+available; do not add a new CLI state, schema field or routine per-article gate.
+Explicit user approval of that concrete structure is sufficient; do not ask again.
+General permission to write knowledge or organize batches is not approval to
+change the site's top-level organization. If the need emerges after report
+approval, update the same plan and ask about that structural change only; continue
+independent work within the approved organization.
+
+Before delivery, compare the resulting map with the approved plan: article
+placement matches its main reader task, titles match the bodies, sibling ordering
+is deliberate, and directories are neither empty nor accidental duplicates.
+Honor the workspace's chosen directory depth and homogeneous sibling convention;
+where it requires directory-only or article-only siblings, do not mix them.
+Use an "Other" group last only for genuinely useful residual content, not to
+avoid classification. Apply supported map adjustments through the current CLI
+flow, retaining article identities and URLs. Record lasting category intent
+briefly in the workspace AGENTS.md or existing organization guide; do not create
+a separate taxonomy ledger or put planning instructions in reader articles.
+
 ### Reader tasks, names and reading order
 
 Read the affected articles' bodies before changing their categories or titles.
@@ -257,8 +299,8 @@ change does not require a prose rewrite or file migration; changing its label do
 not silently rename the approved article. Needed title or content revisions use
 the existing revision and Review flow. Splits and merges use ordinary article
 tasks, link repair and any explicit retirement after replacement content is
-delivered. These are Agent editorial decisions, not new CLI checks or approval
-gates.
+delivered. These are Agent editorial decisions, not new CLI checks or routine per-article
+approval gates. Top-level changes follow the focused review described above.
 
 ## Edit one section or review part of a batch
 
@@ -283,6 +325,12 @@ input without that flag to continue. A preview is not approval and does not make
 a stale revision valid.
 
 Review can approve checked pages while leaving repair pages pending. The HTML
+report shows the current site navigation, candidate changes and expected file
+paths. Unchanged approved pages retain their titles with omitted bodies. Enter
+revision instructions directly in the report; the copied code and following
+instruction lines must be returned together without edits. The CLI binds them to
+the reviewed content and baseline and returns repair commands while leaving
+those pages pending. Changed candidates require a fresh review. The HTML
 review code includes pending positions; managed Review provides the same current
 scope as a JSON template. Send decisions only for pages actually reviewed. Omit
 means a durable exclusion, not repair. Partial approval alone does not build.

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

@@ -130,3 +130,41 @@ fixed. Accepted failures remain visible as warnings and unavailable-resource
 notices; they are never represented as downloaded evidence. Review shows
 available previews, references, and warnings so the human or managed policy can
 assess the page with its non-text evidence.
+
+## Image choices for a production task
+
+The work-start report asks once when a task contains more than 30 distinct images
+and has no explicit image policy. The choices are intelligent conversion and
+inclusion (recommended), include all as images with compression, or include none
+with placeholders. Count the whole task, not each capture or writing batch.
+Review reports show the resulting image handling and any fallbacks.
+
+To skip image acquisition while preserving visible source placeholders:
+
+```ts
+captureLark({ source: handbook, resources: { images: "reference-only" } });
+```
+
+To retain static images but exclude GIF files:
+
+```ts
+captureLark({ source: handbook, resources: { gifs: "reference-only" } });
+```
+
+Both fields also accept `bundle`; omitted fields retain normal capture behavior.
+Known GIF metadata avoids downloading; when a source only supplies an opaque
+media token, identification may require downloading the file. Such a GIF is then
+excluded from the snapshot assets and knowledge, rather than decoded or retained.
+Existing evidence is not deleted by changing a policy. Already approved image
+references must be revised through the normal Review flow to change their content.
+
+Inclusion does not mean lossless original-byte delivery. The package optimizer
+preserves animations without decoding every frame or silently flattening them.
+Codec failures and images that cannot fit delivery budgets become visible output
+placeholders with a build warning; approved source bytes remain unchanged.
+Do not rewrite approved prose to repair a codec error or disable pixel safety
+limits. The reading meaning of an image is handled in writing and Review.
+
+Source document links can be retained for viewing under the reader's permissions.
+Temporary signed media links are not durable image hosting. Do not embed access
+tokens in generated pages or claim that excluded images have been interpreted.

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

@@ -62,3 +62,10 @@ are available while another capture remains pending. Keep unresolved sources in
 `pending_scopes`; do not cite their unavailable snapshots. The Route returns to
 pending capture after the active production/review work, before delivery completes.
 This does not mark failed captures as complete or waive source-read authorization.
+
+For image-heavy tasks, reuse the image choice in the work-start report. When
+source descriptors already show more than 30 distinct images across the task,
+resolve that question before bulk media acquisition. If counts emerge only from
+capture, stop further image processing to confirm the choice during planning.
+Use explicit image/GIF reference-only policies for exclusions; never substitute
+temporary signed media URLs as permanent public image links.

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

@@ -23,7 +23,7 @@ authorization.
 Without explicit session-managed authority:
 
 - open the report returned by the route;
-- let the user publish or durably omit candidates;
+- let the user approve, reject, or request revisions to candidates;
 - apply the exact copied review code through the returned review apply command; and
 - retain the exact report reference and reviewed scope in this conversation for
   the final completion summary.
@@ -58,10 +58,24 @@ Use the explicit retirement 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.
 
-The Review UI names the internal `rejected` decision **Omit** because it is a
-durable content decision, not a request to rewrite the page. When a page needs
-changes, leave that page pending and use `context revise` so the owning
-Author or Composer produces a new Candidate through the same lifecycle.
+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
+summary in place of candidate content or rewrite the HTML. New workspaces show
+all candidate pages as New. Existing unchanged pages show titles only; changed
+blocks and previous text remain available for comparison. Navigation without a
+Git baseline is labelled as current context, not an invented historical diff.
+
+Approve accepts a candidate. Reject durably omits it; it does not request a
+rewrite or retire an approved article. Entering revision instructions requests
+repair and locks the other choices for that page until cancelled. Bulk approval
+requires confirmation and affects only undecided pages. When the report contains
+new top-level categories, the dialog lists them and requires explicit
+acknowledgment plus an eight-second wait before confirmation is enabled.
+New descendant pages under an existing category do not trigger this extra step. The copied code binds
+the candidate scope, exact content, displayed baseline and revision instructions;
+the CLI validates these together before writing any decision. Follow returned
+repair commands, then obtain review of the repaired candidates.
 
 Use the affected page's `Repair` command in the review material, replacing only
 the correction instruction. Current candidates are repaired within this batch;
@@ -132,3 +146,10 @@ only its own titles. When revising or merging, preserve useful existing detail
 instead of replacing it with generic lookup advice. Repair affected pages or
 use the current planning route for missing topics. These are Agent judgments,
 not minimum article counts, a new coverage ledger or an extra CLI approval gate.
+
+For image-heavy work, show the selected task image policy and actual retained,
+converted and placeholder counts from the candidates and capture reports. Explain
+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.