@c4a/context 0.7.17 → 0.7.23

package/docs/guides/knowledge-updates.md

@@ -217,7 +217,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
@@ -587,6 +587,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/docs/guides/workspace-prepare.md

@@ -1,5 +1,9 @@
 # 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
@@ -15,6 +19,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/docs/guides/workspace-restore.md

@@ -1,5 +1,8 @@
 # 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.
@@ -19,7 +22,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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context",
-  "version": "0.7.17",
+  "version": "0.7.23",
   "type": "module",
   "description": "Declarative SDK for Context knowledge sources, workflows, review, and package outputs",
   "license": "MIT",