@c4a/context 0.6.0-beta.6 → 0.6.0-beta.7

package/docs/guides/agent-guide.md

@@ -152,6 +152,14 @@ current step:
 - `command_plan[].availability` says whether each command runs immediately or
   only after user confirmation.
 
+Status also returns `declarationGraph` and `configurationGaps`. These expose
+capture, align, compile, and Review coverage for each canonical document source
+and declared align collection. Missing declarations are early warnings while
+structure is still being planned; after confirmation, every collection planned
+by the structure must have an exact compile route for the same source. Do not
+run a compile command from another collection as a fallback. A
+`reviewValidity({ scope: "all" })` declaration covers every collection.
+
 Do not infer permission from the presence of a command. Do not infer a command
 from prose when `commands_available=false`; complete the returned configuration
 action and rerun status instead.

package/docs/reference/project-api.md

@@ -200,6 +200,20 @@ extraction phases, review gates, close/build, and packages explicitly. The CLI
 then routes work through `context status`, `context run <phase-id>`, `context
 review html/apply`, `context close`, `context verify`, and `context build`.
 
+### Status declaration coverage
+
+`context status --format json` includes a `declarationGraph` and
+`configurationGaps` for document workflows. Each row reports capture, align,
+compile, and Review coverage for a canonical source plus collection. Gaps are
+non-blocking before structure confirmation. Once a structure is confirmed,
+compile routing is exact: phase selection uses canonical source plus collection,
+and candidate progress remains bound to the current `structure_digest`. A
+compile phase from another collection is never used as fallback.
+
+Use `context status --format json --view summary` when only the current state,
+target, counts, diagnostics, and recommended command are needed. The full view
+retains source, phase, package, and lifecycle inventories.
+
 ### `captureFile`
 
 Capture a registered file source into a committed normalized document snapshot.
@@ -304,6 +318,30 @@ context run align:file:<source-name>:architecture --view structure-summary --inp
 context run align:file:<source-name>:architecture --stage --input <structure.yaml> --format json
 ```
 
+`--validate`, `--stage`, `--confirm`, and `--repair` are mutually exclusive
+operations. An `--input` without an operation is rejected unless the selected
+view explicitly consumes that input. Successful validation returns a stage
+command with the same file path. JSON run output keeps `next_action` first and
+omits repeated contracts outside `read-plan`/`schema`; add `--verbose` for the
+full phase reads/writes, source metadata, and contracts.
+
+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
+`rules_version` are stable cache checks: reuse a loaded ruleset only while its
+content remains in the active context and both handle and digest still match.
+After context compaction, reload the returned required subset; a handle alone
+does not imply that the rule text is still available.
+
+Document evidence boundaries are deterministic rather than semantic.
+`source-index` and `chunks` mark Markdown AST blocks with
+`boundary_role: "markdown-ast-block"` and `section_candidate: true`.
+`span-text`/`span-detail` mark each returned page as
+`range_role: "transport-page"` and `section_candidate: false`; pagination line
+ranges are never structure boundaries. Structure validation blocks repeated
+fixed-width line grids that cut through AST blocks and reports sections that
+cross multiple heading paths, without classifying document topics.
+
 Evidence views include `read-plan`, `source-index`, `span-detail`,
 `span-text`, `schema`, and `structure-summary`. Additional diagnostic views may
 be present, but the default path is compact index first, then exact source spans.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context",
-  "version": "0.6.0-beta.6",
+  "version": "0.6.0-beta.7",
   "type": "module",
   "dependencies": {
     "yaml": "^2.5.1",