@c4a/context-cli 0.6.1-beta.3 → 0.6.1-beta.5

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

@@ -51,6 +51,16 @@ user's language. Never hand-write captured source snapshots: the
 CLI owns normalisation (NFC, BOM strip, line endings) and the `content_hash`
 contract, so any manual edit breaks idempotency.
 
+Lark capture obtains the structured XML representation and produces two
+separate artifacts: XML audit evidence and a deterministic readable Markdown
+projection. Do not treat raw XML as Markdown and do not rewrite it yourself.
+Inspect the returned fidelity status and diagnostics. Warnings describe an
+explicitly skipped empty block; errors mean non-empty evidence or a resource
+locator could not be preserved and the workflow must not proceed to Align,
+Compile, or Review. The CLI, not the plugin, parses the document. The plugin
+only displays the structured counts and diagnostics returned by the current
+source resource.
+
 ### Code capture diagnostics
 
 Do not run hand-written dependency preflight commands before code extraction or

package/providers/context/resources/semantic/align/candidate-resolution.md

@@ -45,8 +45,10 @@ Known anomaly kinds:
 Use stable `node_ref`, `view_ref`, and `section_ref` values from the current
 `context.structure.v1` payload for in-payload references. A NodeRef should be
 safe, lower-case, and path-shaped, such as `entity/rspack` or
-`domain/build-tooling`. `slug` and `path` are derived fields in the current
-flow; do not invent alternate reference aliases.
+`domain/build-tooling`. `slug` is the required stable filename choice for a
+View. `path` is derived from collection, optional containment, and slug; omit
+it or use the exact CLI-derived value. Do not invent alternate reference
+aliases.
 
 When an edge or section points at knowledge:
 

package/providers/context/resources/semantic/align/structure-planning.md

@@ -117,10 +117,13 @@ After source evidence identifies a candidate title or stable ref, run:
 context run align:<type>:<source>:<collection> --view existing-knowledge --query <title-or-stable-ref> --format json
 ```
 
-Use the returned pagination command when present. Exact title, NodeRef, ViewRef,
-or tag hits should usually reuse the existing Node instead of creating a
-duplicate candidate. The lookup is deterministic identity discovery; the Agent
-still decides whether the source evidence describes the same concept.
+Use the returned pagination command when present. Exact title, NodeRef, or
+ViewRef hits should usually reuse the existing Node instead of creating a
+duplicate candidate. The lookup returns only the best title/NodeRef/ViewRef
+identity tier. Shared tag matches are summarized separately and never require
+walking the related subgraph merely to determine whether a root identity
+exists. The lookup is deterministic identity discovery; the Agent still
+decides whether the source evidence describes the same concept.
 
 When a code projection Node already represents the object, reuse its slug for prose evidence and plan only prose-owned Sections for the current source evidence.
 
@@ -324,6 +327,6 @@ editing CLI-managed files.
 - [ ] Node classification used the semantic gates in `structure-planning/references/gates.md`. If not, return to **Step 4**.
 - [ ] URL/reference ownership followed CLI diagnostics, not static prompt rules. If not, return to **Step 5**.
 - [ ] The requested align payload passed `context run align:<type>:<source>:<collection> --validate --input - --format json` before stage. If not, return to **Step 6**.
-- [ ] No `sources/`, `unapproved/`, `knowledge/`, `dist/`, `.tmp`, host tool-results, or CLI-managed files were read or written with generic tools. If violated, restart from **Step 1**.
+- [ ] No `sources/`, `knowledge/`, `dist/`, `.tmp`, host tool-results, or CLI-managed files were read or written with generic tools. If violated, restart from **Step 1**.
 
 </procedures>

package/providers/context/schemas/prose-structure-batch.schema.json

@@ -0,0 +1,35 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "context.prose.structure-batch.v1",
+  "title": "Context prose structure batch",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["schema", "items"],
+  "properties": {
+    "schema": {
+      "const": "context.prose.structure-batch.v1"
+    },
+    "items": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 100,
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["phase_id", "input"],
+        "properties": {
+          "phase_id": {
+            "type": "string",
+            "minLength": 1,
+            "description": "One declared phase.align.prose id from the current pending structure targets."
+          },
+          "input": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Project-relative or absolute YAML/JSON context.structure.v1 payload path for this target."
+          }
+        }
+      }
+    }
+  }
+}