@c4a/context-cli 0.7.17 → 0.7.23

package/providers/context/manifest.json

@@ -2,19 +2,19 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.7.17"
+    "version": "0.7.23"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
     {
       "id": "indexer",
       "path": "graphs/indexer.yaml",
-      "digest": "sha256:bfa5061e08fb7c8ee94f5d4d1afc91dd68efff1d39788db324708e954266a7b7"
+      "digest": "sha256:4992b548a9d19c6d7fd25a5dc0ae6b78a4a494ce39d37633144d389362f21122"
     },
     {
       "id": "workspace",
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:2904eb61889037ffdcdf878c807187f9acf807a9409111ee4de4c5b703b15d5d"
+      "digest": "sha256:a0db554b3506e9a68464afe11a5d486a0ce0a0340747f810d8ebdf2fec285c43"
     }
   ],
   "actions": [
@@ -278,7 +278,7 @@
     {
       "id": "procedure.approved-revision",
       "path": "resources/procedures/approved-revision.md",
-      "digest": "sha256:278ac0a0c7e3577dcabdf71c813b63ff943add712782969fb9496ff15a1f19b2"
+      "digest": "sha256:4ee897e6c13e0e908e4d28b239d93f74e66756ef7707277997225743ca250552"
     },
     {
       "id": "procedure.close-and-build",
@@ -303,12 +303,12 @@
     {
       "id": "procedure.knowledge-review",
       "path": "resources/procedures/knowledge-review.md",
-      "digest": "sha256:69dc39212547ea8a304c20d6fadc2bd3eb1de83eaf0c62dade8fcf5e8695c5d6"
+      "digest": "sha256:f0532acbc93458c90209dfed3395b69873eeea6b7d431ae52a84d44c4553751e"
     },
     {
       "id": "procedure.knowledge-updates",
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:e3bf78d43ebc4263bc5d4c08984e51af6d4df16bd2d5d708622816442b777949"
+      "digest": "sha256:bd457b533803f214899f58e03846354f50fafa479a97e01665beb5065a5e90fb"
     },
     {
       "id": "procedure.note",
@@ -318,7 +318,7 @@
     {
       "id": "procedure.package-output",
       "path": "resources/procedures/package-output.md",
-      "digest": "sha256:fc214d1c6f7d8ce4a67fa56a90727f6676a7801f572e73e907005a37a8a543f7"
+      "digest": "sha256:74441590a5b78768bad327f8947c2c9d78fbfa3b470e08b6c6e0e61c2aba1081"
     },
     {
       "id": "procedure.parallel-agent-batch",
@@ -328,7 +328,7 @@
     {
       "id": "procedure.production-requirements",
       "path": "resources/procedures/production-requirements.md",
-      "digest": "sha256:a01bcdf788d9c8fd1cc6ba4ba47f19da6df99cd2397ed35eaaa3d3fdc8b6ec25"
+      "digest": "sha256:d881da8d538efdcef18b7a876f595f0b0098bbac5ea1fd3148e476f63a435dfb"
     },
     {
       "id": "procedure.production-stage-files",
@@ -358,12 +358,12 @@
     {
       "id": "procedure.source-boundary",
       "path": "resources/procedures/source-boundary.md",
-      "digest": "sha256:4c8e7b237503d95bdd1d8b5b53e0e5816f56a4627f24d9b17711233a26c5dc4a"
+      "digest": "sha256:61d0183954abce3356fca94d0bef966b3351af272b10473cae1119737a5c9e66"
     },
     {
       "id": "procedure.source-capture-detailed",
       "path": "resources/procedures/source-capture-detailed.md",
-      "digest": "sha256:04588ea5955c3796e867d091a0fba6fcc5d854c94805bfca4ae1fd398f5542c4"
+      "digest": "sha256:75694361543f5c44a1077b5e6c4ed9bca844ec9b46c1773198f66e0f20ba3748"
     },
     {
       "id": "procedure.source-update",
@@ -383,7 +383,7 @@
     {
       "id": "procedure.work-start-report",
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:39bb407bbc799c380dc03100473a757e3fa3bcf823be6e6993534444040f4fc9"
+      "digest": "sha256:1d1bbd3ecc0cb6baf5bd07e51ce3837094741b815ae935129f70363c37257ad8"
     },
     {
       "id": "procedure.workspace-commit",
@@ -393,12 +393,12 @@
     {
       "id": "procedure.workspace-prepare",
       "path": "resources/procedures/workspace-prepare.md",
-      "digest": "sha256:9bffefd9d4ac0ab46b9274a07c1a0a0b809659fe22a0bb28e2c78a6dc403a999"
+      "digest": "sha256:5fc94a9197a52ec894d5a58872faf1812c18c1e4ff06fd92244dc551147c1bb4"
     },
     {
       "id": "procedure.workspace-restore",
       "path": "resources/procedures/workspace-restore.md",
-      "digest": "sha256:81f510f339d2970c00444bf0452ef97430840ffb90afdfefbe17611012c86c95"
+      "digest": "sha256:c9ba5b5ee703ca79b5db6499c1361a1b7e7ee7efe43fb5c204ad08876f6e89c7"
     },
     {
       "id": "template.indexer-agent-worker",
@@ -558,19 +558,19 @@
     },
     {
       "path": "codes.yaml",
-      "digest": "sha256:195754031443edc76a314c5165d2089d98bcfba5e00e45facf720b2d6f825804"
+      "digest": "sha256:3e400dafffcd4f9e9d46f1503b005180b594f64a3cc5b2503564fb21327e9e08"
     },
     {
       "path": "graphs/indexer.yaml",
-      "digest": "sha256:bfa5061e08fb7c8ee94f5d4d1afc91dd68efff1d39788db324708e954266a7b7"
+      "digest": "sha256:4992b548a9d19c6d7fd25a5dc0ae6b78a4a494ce39d37633144d389362f21122"
     },
     {
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:2904eb61889037ffdcdf878c807187f9acf807a9409111ee4de4c5b703b15d5d"
+      "digest": "sha256:a0db554b3506e9a68464afe11a5d486a0ce0a0340747f810d8ebdf2fec285c43"
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:30f94e1127da95b0128d4e50ba4bf096954fef4ca09a9b93b7e6c4fa4579ac47"
+      "digest": "sha256:4fa32f047a37039e93af588f116d01423ee50fca99ad54d4e16f881b3f25e9b9"
     },
     {
       "path": "resources/contracts/indexer-provider-guide.yaml",
@@ -626,7 +626,7 @@
     },
     {
       "path": "resources/manuals/guides/knowledge-updates.md",
-      "digest": "sha256:3fa4b18e1919578e8939fffba40d250e8898ed6e85376fd2758abe3d12b908d8"
+      "digest": "sha256:8d408d8d15c4f322a2ffcaac7798ece234f3a0bf58d2a122ee3ab97472ef75c3"
     },
     {
       "path": "resources/manuals/guides/lark-resources.md",
@@ -658,11 +658,11 @@
     },
     {
       "path": "resources/manuals/guides/workspace-prepare.md",
-      "digest": "sha256:a0f801e442331135274de04cfc4006c4641da50421d5e80a47f23b329dd13766"
+      "digest": "sha256:057ab5a00ed51629bf856551a20b18fb9e81a9a597dcd87dd44e9b1c9dffd3f2"
     },
     {
       "path": "resources/manuals/guides/workspace-restore.md",
-      "digest": "sha256:290c321c120bf7c4ef86cc578b77a4b51086e47d6a225786768f65cc122c6626"
+      "digest": "sha256:01530e0ddf701ceba53988bab4531e0e854cccd8ab827dcc1c5fc3cb4dc6c3cb"
     },
     {
       "path": "resources/manuals/reference/code-extractors.md",
@@ -682,7 +682,7 @@
     },
     {
       "path": "resources/procedures/approved-revision.md",
-      "digest": "sha256:278ac0a0c7e3577dcabdf71c813b63ff943add712782969fb9496ff15a1f19b2"
+      "digest": "sha256:4ee897e6c13e0e908e4d28b239d93f74e66756ef7707277997225743ca250552"
     },
     {
       "path": "resources/procedures/close-and-build.md",
@@ -702,11 +702,11 @@
     },
     {
       "path": "resources/procedures/knowledge-review.md",
-      "digest": "sha256:69dc39212547ea8a304c20d6fadc2bd3eb1de83eaf0c62dade8fcf5e8695c5d6"
+      "digest": "sha256:f0532acbc93458c90209dfed3395b69873eeea6b7d431ae52a84d44c4553751e"
     },
     {
       "path": "resources/procedures/knowledge-updates.md",
-      "digest": "sha256:e3bf78d43ebc4263bc5d4c08984e51af6d4df16bd2d5d708622816442b777949"
+      "digest": "sha256:bd457b533803f214899f58e03846354f50fafa479a97e01665beb5065a5e90fb"
     },
     {
       "path": "resources/procedures/note.md",
@@ -714,7 +714,7 @@
     },
     {
       "path": "resources/procedures/package-output.md",
-      "digest": "sha256:fc214d1c6f7d8ce4a67fa56a90727f6676a7801f572e73e907005a37a8a543f7"
+      "digest": "sha256:74441590a5b78768bad327f8947c2c9d78fbfa3b470e08b6c6e0e61c2aba1081"
     },
     {
       "path": "resources/procedures/parallel-agent-batch.md",
@@ -722,7 +722,7 @@
     },
     {
       "path": "resources/procedures/production-requirements.md",
-      "digest": "sha256:a01bcdf788d9c8fd1cc6ba4ba47f19da6df99cd2397ed35eaaa3d3fdc8b6ec25"
+      "digest": "sha256:d881da8d538efdcef18b7a876f595f0b0098bbac5ea1fd3148e476f63a435dfb"
     },
     {
       "path": "resources/procedures/production-stage-files.md",
@@ -746,11 +746,11 @@
     },
     {
       "path": "resources/procedures/source-boundary.md",
-      "digest": "sha256:4c8e7b237503d95bdd1d8b5b53e0e5816f56a4627f24d9b17711233a26c5dc4a"
+      "digest": "sha256:61d0183954abce3356fca94d0bef966b3351af272b10473cae1119737a5c9e66"
     },
     {
       "path": "resources/procedures/source-capture-detailed.md",
-      "digest": "sha256:04588ea5955c3796e867d091a0fba6fcc5d854c94805bfca4ae1fd398f5542c4"
+      "digest": "sha256:75694361543f5c44a1077b5e6c4ed9bca844ec9b46c1773198f66e0f20ba3748"
     },
     {
       "path": "resources/procedures/source-update.md",
@@ -766,7 +766,7 @@
     },
     {
       "path": "resources/procedures/work-start-report.md",
-      "digest": "sha256:39bb407bbc799c380dc03100473a757e3fa3bcf823be6e6993534444040f4fc9"
+      "digest": "sha256:1d1bbd3ecc0cb6baf5bd07e51ce3837094741b815ae935129f70363c37257ad8"
     },
     {
       "path": "resources/procedures/workspace-commit.md",
@@ -774,11 +774,11 @@
     },
     {
       "path": "resources/procedures/workspace-prepare.md",
-      "digest": "sha256:9bffefd9d4ac0ab46b9274a07c1a0a0b809659fe22a0bb28e2c78a6dc403a999"
+      "digest": "sha256:5fc94a9197a52ec894d5a58872faf1812c18c1e4ff06fd92244dc551147c1bb4"
     },
     {
       "path": "resources/procedures/workspace-restore.md",
-      "digest": "sha256:81f510f339d2970c00444bf0452ef97430840ffb90afdfefbe17611012c86c95"
+      "digest": "sha256:c9ba5b5ee703ca79b5db6499c1361a1b7e7ee7efe43fb5c204ad08876f6e89c7"
     },
     {
       "path": "resources/templates/indexer-agent-worker.md",
@@ -850,7 +850,7 @@
     },
     {
       "path": "skills/resolve-current-indexer-gate/SKILL.md",
-      "digest": "sha256:a4be3b069717f2e16af59ec64415bc1f8a269e9798c591087239629d41c7e94d"
+      "digest": "sha256:e5cd37225e555879b90df46206eb61c398250de1dad0378e0fb85cd61e93fca3"
     },
     {
       "path": "skills/run-indexer-agent-step/SKILL.md",
@@ -858,16 +858,16 @@
     },
     {
       "path": "skills/run-indexer-lifecycle/SKILL.md",
-      "digest": "sha256:2e80cd1d81a215859bcea6f483de17705a54d214f91fd33013777e1f84b6b075"
+      "digest": "sha256:e56bf044855a3a66aa75a12d16ecba730b11a1e695f1ce75f2ea0af81384a011"
     },
     {
       "path": "skills/work-production-stage/SKILL.md",
-      "digest": "sha256:cacf6ce1b106cfe7af7b07009e6a3658c04007c6eb49127069fa16e3b2892f31"
+      "digest": "sha256:b7aa28c032e00f93f67d3c9dc3589cf1513451456f589262e22ad7f73d265de7"
     }
   ],
   "graphDependencies": {
     "indexer": [],
     "workspace": []
   },
-  "digest": "sha256:b1e15a2c60465b30bd30b709b98dc7d5c8df1b21fa1f91852dffbcc2fc0c5a3a"
+  "digest": "sha256:e38e780dea12218d57a1d69c66c3f0d78f06f86cf46df6874838648b12fb1714"
 }

package/providers/context/provider.yaml

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

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

@@ -223,7 +223,7 @@ 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
+human review under `context.gate.top_level_directory` 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
@@ -593,6 +593,10 @@ before delivery; inspect both new content and the old articles' disposition.
 
 Preview approved-page retirement with `context task retire --input <file> --format json`:
 
+This standalone retirement does not enter the article HTML Review. Apply
+`context.gate.deletion_scope` to its target list; an already approved deletion
+needs no second confirmation after the preview.
+
 ```yaml
 reason: These reader tasks are now covered by the approved guide.
 targets:

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

@@ -6,6 +6,10 @@ mediaType: text/markdown
 
 # Prepare a workspace for the next 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.
+
 Use only for an explicit workspace preparation request. The goal is usable
 registered sources and no unfinished task, while retaining approved knowledge
 and configuration. Lead with Host tools and actual observations; do not start
@@ -21,6 +25,11 @@ Wait for an active writer to finish and obtain its receipt before changing state
 If status is broken, inspect its diagnostic and files with Host tools rather
 than treating failure as proof that the workspace is empty.
 
+Registered source inventory is not an active task. Preparation does not repair
+invalid snapshots or change source scope; do not repeat preparation to bypass a
+capture diagnostic. Excluding a source from one task is not authorization to
+delete its registration or retained evidence.
+
 ## End the old task
 
 Run `context task prepare --format json`. It previews the exact Context-owned

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

@@ -6,6 +6,9 @@ mediaType: text/markdown
 
 # Restore a historical workspace version
 
+Agent policy: `context.gate.workspace_reset_restore`. An explicit restore
+request needs no second approval when the target and affected files are clear.
+
 Use the Agent's Git and environment tools. This restores selected workspace
 files and usable sources; it does not reset the entire repository, rewind source
 repositories, or restore ignored runtime progress.
@@ -25,7 +28,8 @@ Compare target files with current tracked, untracked and staged files. Include
 current additions absent at the target in the proposed removal scope. Keep
 unrelated files, existing staged work and ignored source checkouts. Account for
 workspace moves or renames instead of treating a missing old path as an empty
-version. Reuse explicit authorization; ask when the target or loss is unresolved.
+version. Reuse explicit authorization; clarify an unresolved target or loss
+before acting rather than asking for a second approval of the same request.
 
 ## Restore files and environment
 

package/providers/context/resources/procedures/approved-revision.md

@@ -17,6 +17,26 @@ to ask about the affected claim, not to reconstruct the whole knowledge base.
 Record new factual contributions as managed sources before expanding source
 ownership; an editing instruction alone is not a permanent factual source.
 
+If a source diagnostic blocks the action, inspect that exact source before
+calling it uncaptured. An invalid retained capture report is not evidence that
+the source was never collected. Do not use rollback, task preparation, or source
+removal to repair a revision-token or submission-schema error. Refresh the
+current action and use its revision and required `stage: approved-revision`.
+If the fresh action still conflicts, preserve the request and report the tool
+blocker instead of repeatedly clearing or re-registering maintenance.
+
+For new independent evidence added during a revision, keep its own managed source.
+A `requirement_ref` alone does not authorize it: the selected requirement in
+`src/indexers.yaml` must connect the new source to an existing task source through
+its target or evidence scopes. When `revision-source-scope-unconfirmed` is returned,
+use its `missing` and `configuration` fields to correct only the user-authorized
+association. Then retry the same `task adjust` without refresh and, once material
+is available, with `refresh: true`; reread the resulting revision. Do not invent
+module references, replace an older note, delete sources or clear the task to
+satisfy this boundary. Already imported material does not need to be imported again.
+A managed-source `base_digest` protects file replacement from conflicts; it is not
+source-scope authorization and is not interchangeable with a snapshot hash.
+
 Return the full revised Markdown in the supplied output schema, preserving the
 page's stable fragment markers and metadata. Do not silently
 turn paraphrased text into a verbatim quotation. Do not directly write knowledge

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

@@ -6,6 +6,10 @@ mediaType: text/markdown
 
 # Knowledge Review
 
+Agent policy: `context.gate.knowledge_review`. An instance-specific Bot may
+override the managed default and require the ordinary HTML review decision.
+The report-inaccessible exception is `context.gate.force_review_approval`.
+
 Review is the authority boundary between candidates and approved knowledge.
 Open one report for the complete current candidate set and apply only a payload
 that matches its collection scope and candidate-set digest.
@@ -17,8 +21,9 @@ blocks Review. Follow the returned identity-coordination route: the default
 mechanical repair preserves the approved identity and approved path, then
 recompiles only the affected source. It keeps the candidate batch intact while
 replacing affected candidates in place. Changing an approved identity or moving
-an approved path is a migration and must never run without a separate, explicit
-authorization.
+an approved path is a migration within the user's requested scope; do not ask
+again when that scope is already clear. The resulting Candidate still enters
+Review.
 
 Without explicit session-managed authority:
 
@@ -31,7 +36,8 @@ Without explicit session-managed authority:
 The ordinary Route also carries a revision-bound force-approval resolution
 Action as an escape path. Do not advertise it when first presenting Review.
 Use it only after the user cannot use the report and explicitly replies with
-the exact phrase `强制批准` in the current conversation. It approves the complete
+the exact phrase `强制批准` in the current conversation. That reply is the
+decision; do not ask a second confirmation. It approves the complete
 current scope atomically; no candidate-specific decisions are inferred.
 
 With explicit session-managed authority, materialize the required
@@ -54,7 +60,8 @@ Do not persist a duplicate review-report ledger in the workspace.
 For restructuring, compare replacement content with the affected approved pages:
 useful conditions, steps and explanations must have a destination before removal.
 Review omission rejects a candidate; it does not retire an approved article.
-Use the explicit retirement preview after replacement delivery, and repair its
+Pure retirement does not enter this HTML report. 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.
 

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

@@ -223,7 +223,7 @@ 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
+human review under `context.gate.top_level_directory` 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
@@ -593,6 +593,10 @@ before delivery; inspect both new content and the old articles' disposition.
 
 Preview approved-page retirement with `context task retire --input <file> --format json`:
 
+This standalone retirement does not enter the article HTML Review. Apply
+`context.gate.deletion_scope` to its target list; an already approved deletion
+needs no second confirmation after the preview.
+
 ```yaml
 reason: These reader tasks are now covered by the approved guide.
 targets:

package/providers/context/resources/procedures/package-output.md

@@ -6,6 +6,10 @@ mediaType: text/markdown
 
 # Package output
 
+Agent policies: `context.gate.package_output` and
+`context.gate.package_template`. Publication uses the separate
+`context.gate.publication` decision.
+
 Before editing, read `context.sdk.package-outputs`, especially its Agent configuration
 and delivery recipe. It contains the concrete SDK declarations and preview steps.
 

package/providers/context/resources/procedures/production-requirements.md

@@ -8,8 +8,9 @@ mediaType: text/markdown
 
 Use the reader purpose and source boundaries already confirmed by the user.
 Ask for missing decisions before writing; registering a source does not authorize
-unrelated modules. This is not the work-start report: the report follows the
-lightweight investigation and must still wait for user feedback.
+unrelated modules. This is not the work-start report: that report follows the
+lightweight investigation and uses `context.gate.work_start_scope` for its
+confirmation decision.
 
 Write `src/indexers.yaml` with this minimal shape, replacing the example values
 with the user's actual purpose and registered source reference:
@@ -57,7 +58,8 @@ plan fields (`capabilities`, `articles`, optional `indexer_usage`) in a file und
 contains `path`, `question`, `sources` and `batch`, with optional `brief` and
 `after`. Add `--input <that-file>` to the returned `action prepare-current`
 command to prepare those tasks without a separate investigation-plan submission.
-This does not approve the report or permit writing before user feedback.
+This does not approve the report or permit writing before its applicable scope
+decision.
 When targets are unclear, use normal preparation and investigate the skeletons.
 
 ## Configured coverage and the current request

package/providers/context/resources/procedures/source-boundary.md

@@ -6,6 +6,12 @@ mediaType: text/markdown
 
 # Source boundary
 
+Agent policy: `context.gate.source_boundary` for source selection,
+`context.gate.source_read` for reading registered external documents, and
+`context.gate.repository_clone` for a missing repository. These labels do not
+replace the current Route's gate ID or authorization command.
+Source removal uses `context.gate.deletion_scope`.
+
 A source boundary is a user decision about which repositories, modules, or
 documents may become approved knowledge. It affects extraction scope,
 provenance, output paths, and freshness checks.
@@ -66,7 +72,9 @@ mutation instead of running registry writes in parallel.
 To retire a registered source, first run `context source remove <source-id>
 --format json`. This is a read-only preview that lists every project, candidate,
 or approved-knowledge reference. Only after those references are intentionally
-resolved may the route use `--yes`; the CLI never silently deletes referenced
+resolved may the route use `--yes`. A user-approved deletion of this exact source
+needs no second confirmation; clarify only a newly affected source outside that
+scope. Source removal does not enter the article HTML Review. The CLI never silently deletes referenced
 knowledge or another source's materialized files. Execute the exact
 digest-bound command returned by the preview. For a shared document batch, the
 manifest entry is the ownership boundary: removal deletes only that entry and
@@ -75,7 +83,9 @@ so removal is registry-only; the shared date directory is never inferred as
 module-owned.
 
 Repository readiness checks are mechanical and may run after the boundary is
-registered. Clone, fetch, checkout, install, build, test, and other external
-repository operations need separate authority. File and remote-document
-registration records metadata only; reading their bodies requires source-read
-permission for the exact pending modules.
+registered. In ordinary mode ask before cloning a missing repository; in fully
+managed mode use the selected source scope without a repeat question. Other
+repository operations stay within existing authorization and must not modify
+source code or perform destructive recovery without a separate grant. File and
+remote-document registration records metadata only; reading their bodies uses
+source-read permission for the exact pending modules.

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

@@ -190,6 +190,23 @@ Do not discover files with `find` / `ls` when the user already supplied paths.
 If the include set is large, summarize it and ask for confirmation before
 registration; do not read file bodies before capture permission is clear.
 
+### Unavailable document acquisition
+
+A `document.capture.warning` is not a successful capture. Report whether the CLI
+retained a validated registered snapshot or deferred a source with no evidence.
+Use retained material with its recorded version; do not claim that upstream is
+current. A deferred source remains registered and must not be cited as evidence.
+Continue unrelated work using the returned workspace Route. Do not remove sources,
+clear tasks, invent content, or repeatedly retry authentication to unblock it.
+
+The warning includes a retry command. Run it when access is restored or the user
+requests another attempt. Changing the source or capture configuration invalidates
+the old deferral. Warning receipts are local runtime state; another checkout may
+attempt acquisition again. Persisted snapshots remain the portable evidence.
+Snapshot corruption, invalid input, write conflicts and repository restore errors
+are not downgraded. Code work still requires its authorized registered repository
+version. Note/session material already saved in the workspace is read locally.
+
 ### Output Handling
 
 Preserve commands, reason codes, ids, and diagnostics exactly; summarize

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

@@ -6,6 +6,10 @@ mediaType: text/markdown
 
 # Present the production plan before bulk writing
 
+Agent policy: `context.gate.work_start_scope`; top-level navigation changes
+add the independent `context.gate.top_level_directory` decision. More than 30
+distinct images without a prior choice uses `context.gate.image_handling`.
+
 Prepare `.tmp/work-start-report.md` after lightweight investigation has formed an
 actionable article plan and before bulk writing. Use the companion template as
 guidance, not a mandatory form. This scratch report is for the user; its existence
@@ -80,6 +84,9 @@ position; reuse its layout and delivery choices instead of proposing them again.
 
 ## Confirm image handling for large tasks
 
+`context.gate.image_handling` asks once in both ordinary and managed mode; a
+previous explicit choice for this task avoids another question.
+
 Before bulk image interpretation or article writing, count distinct image resources
 across the current authorized task (all its sources, not each document or batch).
 Use source descriptors and capture reports; do not download images just to count
@@ -125,13 +132,18 @@ Obtain explicit feedback before applying that structural change, reusing a
 concrete structure already approved by the user. If it emerges later, update this
 same plan and review only the changed decision; do not restart approved batches.
 
-## Mandatory feedback
+## Scope decision
 
 Write the scratch report using the host file tool, show its clickable path,
-summarize scope, first delivery and decisions, then wait. Managed mode, permission
-to plan autonomously and multi-Agent capability do not waive this gate. Silence,
-elapsed time, questions and objections are not approval. Make requested
-adjustments before continuing with the Graph-selected confirmation action.
+summarize scope, first delivery and decisions. Ask for feedback only when the
+scope is complex and changes more than five articles, or when a separate decision
+such as a top-level directory change remains unresolved. A specific earlier user
+request can already approve a matching bounded report, including 1–3 documents
+or a single MR-triggered note; do not ask again solely because the report was
+presented. Apply the same rule in ordinary and managed mode. Silence, elapsed
+time, questions and objections are never approval. Make requested adjustments
+before the Graph-selected confirmation action. If the current Route still
+requires a fresh human decision, stop rather than fabricating it.
 
 The current action records confirmation of planned scope, not report file
 integrity. If saving the report fails, explain the issue and present the proposal
@@ -141,7 +153,8 @@ Reuse approval for an unchanged applicable plan across batches, retries and
 compatible skill changes. Update and explain material changes; wait again for
 scope expansion or unresolved material decisions, not merely another ready batch.
 There is no extra task-count confirmation: crossing 50 planning tasks adds no
-pause. Actual scale belongs in the report whose pre-writing feedback is mandatory.
+separate pause. Actual scale belongs in the report and its applicable scope
+decision.
 
 ## Progress and storage
 

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

@@ -6,6 +6,10 @@ mediaType: text/markdown
 
 # Prepare a workspace for the next 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.
+
 Use only for an explicit workspace preparation request. The goal is usable
 registered sources and no unfinished task, while retaining approved knowledge
 and configuration. Lead with Host tools and actual observations; do not start
@@ -21,6 +25,11 @@ Wait for an active writer to finish and obtain its receipt before changing state
 If status is broken, inspect its diagnostic and files with Host tools rather
 than treating failure as proof that the workspace is empty.
 
+Registered source inventory is not an active task. Preparation does not repair
+invalid snapshots or change source scope; do not repeat preparation to bypass a
+capture diagnostic. Excluding a source from one task is not authorization to
+delete its registration or retained evidence.
+
 ## End the old task
 
 Run `context task prepare --format json`. It previews the exact Context-owned

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

@@ -6,6 +6,9 @@ mediaType: text/markdown
 
 # Restore a historical workspace version
 
+Agent policy: `context.gate.workspace_reset_restore`. An explicit restore
+request needs no second approval when the target and affected files are clear.
+
 Use the Agent's Git and environment tools. This restores selected workspace
 files and usable sources; it does not reset the entire repository, rewind source
 repositories, or restore ignored runtime progress.
@@ -25,7 +28,8 @@ Compare target files with current tracked, untracked and staged files. Include
 current additions absent at the target in the proposed removal scope. Keep
 unrelated files, existing staged work and ignored source checkouts. Account for
 workspace moves or renames instead of treating a missing old path as an empty
-version. Reuse explicit authorization; ask when the target or loss is unresolved.
+version. Reuse explicit authorization; clarify an unresolved target or loss
+before acting rather than asking for a second approval of the same request.
 
 ## Restore files and environment
 

package/providers/context/skills/resolve-current-indexer-gate/SKILL.md

@@ -9,10 +9,15 @@ metadata:
 
 # Resolve the current structure proposal
 
+This structure proposal uses `context.gate.work_start_scope`; a top-level
+directory change additionally uses `context.gate.top_level_directory`.
+
 Read the exact Gate input and its output schema. Explain the proposed new topics,
 affected existing articles, source scope and unresolved gaps in the user's
-language. Reuse prior scope decisions, but wait for the confirmation required by
-this Gate; managed execution does not waive a non-delegatable decision.
+language. Reuse a matching prior scope decision. Ask when the proposal is complex
+and changes more than five articles, or when a separate structural decision is
+unresolved. Managed execution does not waive a required non-delegatable decision;
+if the current Route still requires fresh feedback, wait for it.
 
 Submit approval or specific adjustment feedback through the returned command.
 Use a temporary JSON/YAML file for long feedback. Do not invent another approval