@c4a/context 0.6.1-beta.2 → 0.6.1-beta.3

package/docs/getting-started.md

@@ -17,6 +17,12 @@ Use `--dev` when testing a local link or prepared pack before the matching SDK
 version is published. It writes a `file:` dependency to the SDK resolved beside
 the active CLI. Published users can omit it and install the versioned SDK from
 the registry.
+
+Without `project-dir`, init uses the dedicated `context/` directory. Initializing
+inside a non-empty directory that is not already a Context workspace is blocked
+before any files are written; use the returned `--allow-nonempty` command only
+after confirming that the existing files should share the workspace root.
+
 When operating through an Agent plugin, use the installed Context continuation
 entry from the project root after initialization. It consumes
 `workflow.current`, loads only the selected resources, and calls lower-level

package/docs/guides/agent-guide.md

@@ -30,6 +30,14 @@ without another question. Review uses the CLI's atomic `context review
 approve-all ... --managed` route; valid structure staging records
 `confirmed_by: managed-session`.
 
+After the first managed status evaluation, use
+`context run --managed --until blocked-or-complete --format json` when the
+current work can advance through consecutive mechanical routes. The CLI
+executes only a unique immediate non-read command, re-evaluates after each
+receipt, and stops before Agent interpretation, configuration, missing
+authority, diagnostics, or multiple commands. Continue from the returned
+`workflow.current`.
+
 This is execution authority, not project configuration. Do not add it to
 `defineProject`, environment files, or committed workspace state, and do not
 carry it into a new conversation. It never grants a new source boundary or
@@ -372,6 +380,7 @@ context run align:<type>:<source>:<collection> --view read-plan --format json
 context run align:<type>:<source>:<collection> --view source-index --compact --format json
 context run align:<type>:<source>:<collection> --view span-detail --span <source-ref> --format json
 context run align:<type>:<source>:<collection> --view span-text --span <source-ref> --format json
+context run align:<type>:<source>:<collection> --view existing-knowledge --query <title-or-stable-ref> --format json
 context run align:<type>:<source>:<collection> --view schema --format json
 context run align:<type>:<source>:<collection> --validate --input <structure.yaml> --format json
 context run align:<type>:<source>:<collection> --view structure-summary --input <structure.yaml> --format json
@@ -380,9 +389,12 @@ context run align:<type>:<source>:<collection> --stage --input <structure.yaml>
 
 Read source material only through these evidence views. `source-index` gives a
 compact refs-first map when run with `--compact`; use `span-detail` /
-`span-text` only for exact evidence. The CLI applies deterministic boundary
-repairs internally and returns only blockers that need Agent judgment. For
-oversized Views, use the returned structural diagnostics while classifying
+`span-text` only for exact evidence. Before introducing a new Node identity,
+use the targeted `existing-knowledge` View returned by the read plan to inspect
+approved stable refs; do not inspect `knowledge/**` directly. The CLI applies
+deterministic boundary repairs internally and returns only blockers that need
+Agent judgment. For oversized Views, use the returned structural diagnostics
+while classifying
 child Nodes from evidence. Stage only after validation state is `ready`; stage
 opens the final `structure-summary` report for the current Route's confirmation
 gate. Ask a separate structure-design question only when evidence supports

package/docs/reference/project-api.md

@@ -250,6 +250,17 @@ returned by `workflow.current`. Source boundaries and unread source bodies,
 external operations, payload validation, deterministic close, and verification
 errors are never bypassed.
 
+For consecutive mechanical routes, the Agent may run:
+
+```bash
+context run --managed --until blocked-or-complete --format json
+```
+
+This is a bounded host loop over the same revisioned routes. It stops before
+read-only interpretation, project configuration, unresolved authority,
+diagnostics, or a non-unique command plan; it does not add another workflow
+entry or make semantic decisions.
+
 ### `captureFile`
 
 Capture a registered file source into a committed normalized document snapshot.
@@ -354,6 +365,7 @@ context run align:file:<source-name>:architecture --view read-plan --format json
 context run align:file:<source-name>:architecture --view source-index --compact --format json
 context run align:file:<source-name>:architecture --view span-detail --span <source-ref> --format json
 context run align:file:<source-name>:architecture --view span-text --span <source-ref> --format json
+context run align:file:<source-name>:architecture --view existing-knowledge --query <title-or-stable-ref> --format json
 context run align:file:<source-name>:architecture --view schema --format json
 context run align:file:<source-name>:architecture --view semantic-rules --format json
 context run align:file:<source-name>:architecture --validate --input <structure.yaml> --format json
@@ -371,6 +383,14 @@ schema and full reports stay behind explicit Views, while `--verbose` restores
 the full phase result and repeated contracts. Long diagnostics return a compact
 first page plus an exact diagnostics continuation command.
 
+`existing-knowledge` is the authoring-time lookup for approved identities. It
+returns stable NodeRefs, ViewRefs, titles, tags, collections, and section counts
+without exposing workspace storage paths. `--query` performs deterministic
+case-insensitive exact/prefix/substring matching; `--collection`,
+`--node-type`, `--page-size`, and the returned continuation command narrow or
+page the same View. Use it after reading source evidence and before introducing
+a new Node identity. Structure validation remains the final duplicate gate.
+
 Align and compile evidence results include `semantic_rules`. Its `required`
 array is the rule subset selected for the current judgment, with a selection
 reason and content digest for each rule. `handle`, `digest`, and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context",
-  "version": "0.6.1-beta.2",
+  "version": "0.6.1-beta.3",
   "type": "module",
   "description": "Context SDK — project-local configuration and workspace primitives",
   "license": "MIT",