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

package/{plugins/claude/skills/skill-prose-align/references/internal-procedures/structure-planning/references → providers/context/resources/semantic/align}/density-profile.md

@@ -1,4 +1,15 @@
+---
+id: context.semantic.align.density-profile
+kind: procedure
+media-type: text/markdown
+applies-to:
+  - coverage
+  - reading_density
+  - structure
+---
+
 # Evidence Density Selection
+<!-- Context workflow semantic resource. -->
 
 Use density as a private reading and section-planning strategy. It is not a
 separate payload, not a quality score, and not a workflow stage. Persist only

package/{plugins/codex/skills/init/references/internal-procedures/skill-prose-align/references/internal-procedures/structure-planning/references → providers/context/resources/semantic/align}/gates.md

@@ -1,4 +1,17 @@
+---
+id: context.semantic.align.align-gates
+kind: procedure
+media-type: text/markdown
+applies-to:
+  - node_type
+  - domain
+  - action
+  - edges
+  - tags
+---
+
 # Node Classification Gates
+<!-- Context workflow semantic resource. -->
 
 Use these gates before every structure draft and before authoring the align
 payload described by the current schema view.

package/{plugins/cursor/skills/skill-prose-align/references/internal-procedures → providers/context/resources/semantic/align}/structure-planning.md

@@ -1,4 +1,15 @@
 ---
+context_resource: semantic/align/structure-planning
+id: context.semantic.align.structure-planning
+kind: procedure
+media-type: text/markdown
+applies-to:
+  - node_type
+  - title
+  - tags
+  - ownership
+  - edges
+  - structure
 name: structure-planning
 description: "Internal procedure for the current align gate. Reads CLI-guided align evidence, applies semantic Node classification gates, and emits context.structure.v1 payloads for CLI validation/stage."
 ---
@@ -7,7 +18,7 @@ description: "Internal procedure for the current align gate. Reads CLI-guided al
 
 ## TL;DR
 
-Run `context run align:<type>:<source>:<collection> --view read-plan --format json`, follow the top-level `next_action.command` to read the CLI-selected evidence path, produce a `context.structure.v1` structure payload, and continue following top-level `next_action`. The CLI owns route, validation, repair commands, and stage guards; this skill owns only semantic classification and source-bound structure judgment.
+Run `context run align:<type>:<source>:<collection> --view read-plan --format json`, follow the top-level `next_action.command` to read the CLI-selected evidence path, produce a `context.structure.v1` structure payload, and continue following top-level `next_action`. The CLI owns route, validation, repair commands, and stage guards; the Agent owns only semantic classification and source-bound structure judgment.
 
 <reference>
 
@@ -23,9 +34,9 @@ Run `context run align:<type>:<source>:<collection> --view read-plan --format js
 - Schema names and enum values come from
   `context run align:<type>:<source>:<collection> --view schema --format json`. Use
   that schema as the authoring contract for `context.structure.v1`.
-- Existing approved knowledge and `knowledge/structure.yaml` are the lookup
-  registry exposed through current CLI/status/query views. Do not read
-  `knowledge/**` or create a separate registry file.
+- Existing approved knowledge is the lookup registry exposed by the current
+  align `existing-knowledge` View. Do not read `knowledge/**`, guess a top-level
+  query command, or create a separate registry file.
 - Code projection Nodes are reusable knowledge handles. When document evidence belongs on a code symbol, reuse the code slug instead of creating a parallel document Node.
 - Validation diagnostics are the mechanical structure ownership source of
   truth. Non-content spans such as navigation references, placeholders, front
@@ -44,7 +55,10 @@ Run `context run align:<type>:<source>:<collection> --view read-plan --format js
   placeholder/relation source is skipped entirely, leave its relation clues in
   `unresolved[]` only when they still matter; otherwise omit them.
 - `views[]` and diagnostics distinguish citable evidence from supporting context. Do not promote supporting/context-only material into cited Sections unless a later ownership correction makes it citation-eligible.
-- Keep cache-friendly prompt order: fixed protocol/schema first, existing knowledge lookup second, source evidence views third, current semantic payload last. Preserve CLI JSON order and do not add timestamps, random ids, scratch paths, or host paths to generated payloads.
+- Keep cache-friendly prompt order: fixed protocol/schema first, source evidence
+  views second, targeted existing-knowledge results third, and the current
+  semantic payload last. Preserve CLI JSON order and do not add timestamps,
+  random ids, scratch paths, or host paths to generated payloads.
 - Structure digests and snapshot hashes are stale guards. Follow returned
   `next_action.command` and do not invent digest values.
 - Node type, tag, fake-Entity, `domain`, and `action` gates are in `structure-planning/references/gates.md`.
@@ -80,8 +94,9 @@ or `next_command`.
 
 `read-plan` is the navigation surface. It chooses whether the next evidence read
 is `source-index`, `span-detail`, `span-text`, or another current evidence view.
-Read those views and then author the requested
-`context.structure.v1` payload yourself. Never pipe evidence text into validate.
+Read those views and then author the requested `context.structure.v1` payload
+yourself after completing the targeted lookup in Step 3. Never pipe evidence
+text into validate.
 
 If an evidence view is truncated, `page.has_more: true`, or the CLI returns a
 `next_command`, run that command before authoring.
@@ -96,7 +111,16 @@ is explicitly needed, otherwise return to the CLI-designated navigation view.
 
 ### Step 3 — Reuse Existing Knowledge
 
-Query existing knowledge for reusable names before proposing new term/service/system/action Nodes. Exact title/slug/alias hits should usually become references to the existing Node, not duplicate candidates.
+After source evidence identifies a candidate title or stable ref, run:
+
+```bash
+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.
 
 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.
 
@@ -196,6 +220,11 @@ snapshot hash. Section identities are part of the structure gate: choose stable
 section ids such as `overview`, `behavior`, `constraints`, or a source-backed
 domain-specific name when the evidence supports it.
 
+For an independent collection entry, omit `containment`; the CLI derives
+`<collection>/<slug>.md`. Set `containment` only when the confirmed structure
+intentionally places the View under a parent path. Do not add a source/module
+wrapper merely to make every page use the same directory depth.
+
 Use only CLI-provided `source_refs[]` for section and edge evidence. Continuity
 is a per-Section constraint, not a per-View constraint: one View may contain
 many independently retrievable Sections, each with its own continuous mirror.
@@ -218,7 +247,8 @@ otherwise repair source refs from CLI evidence views or move unsupported
 material to `unresolved[]`.
 
 For pure suggested-split repairs, prefer the CLI repair view before hand-editing:
-`context run align:<type>:<source>:<collection> --repair suggested-splits --input <structure.yaml> --format json`.
+Deterministic source-boundary repairs are applied internally by validate/stage
+and are not a separate Agent command.
 It splits non-contiguous Section mirrors and can expand a broad cross-heading
 Section into Markdown structural groups within the same View. Apply the
 non-blocking repair hint when the groups should be independently retrievable;
@@ -252,14 +282,31 @@ mention without a dependency predicate. `edges[].source_refs[]` must include the
 source ref that states the dependency; if the relationship matters but evidence
 is missing, leave the edge unresolved instead of guessing.
 
-Prefer the strongest source-backed `section_kind` using the current schema's `section_kind_priority` and `section_kind_triggers`; avoid planning an entire dense source as `description` when the evidence clearly contains fenced examples, comparison tables, Q&A, decisions, specs, warnings, or principles. Use `example` for fenced command/config/code or literal sample blocks, not ordinary scenario prose. Use `incident` only for dated or timestamped failure evidence with impact scope plus root cause, mitigation, or handling record. Use `decision` only when the source surfaces two or more alternatives or options plus the chosen path and rationale. Treat kind precision as a drafting quality preference, not a reason to block an otherwise source-backed write. Keep only raw-backed semantic decisions in the payload; leave mechanical repair and patch routing to CLI diagnostics.
+Prefer the strongest source-backed `section_kind` using the current schema's
+`section_kind_priority` and the semantic rules below; avoid planning an entire
+dense source as `description` when the evidence clearly contains fenced
+examples, comparison tables, Q&A, decisions, specs, warnings, or principles.
+Use `example` for fenced command/config/code or literal sample blocks, not
+ordinary scenario prose. Use `comparison` for two or more subjects compared
+across two or more dimensions. Use `faq` for a question-and-answer pair. Use
+`incident` only for dated or timestamped failure evidence with impact scope
+plus root cause, mitigation, or handling record. Use `changelog` for a
+versioned or dated change record. Use `decision` only when the source surfaces
+two or more alternatives or options plus the chosen path and rationale. Use
+`spec` for a verifiable rule, threshold, requirement, constraint, or checkable
+target; `warning` for an explicit caveat, risk, hazard, or limitation;
+`principle` for a stable invariant, design rule, or core mechanism without a
+check method; and `description` only as the narrative fallback. Treat kind
+precision as a drafting quality preference, not a reason to block an otherwise
+source-backed write. Keep only raw-backed semantic decisions in the payload;
+leave mechanical repair and patch routing to CLI diagnostics.
 
 There is no parallel candidate-body authoring path. Emit only the
 `context.structure.v1` payload accepted by the current schema view.
 
 ### Step 6 — Validate And Submit
 
-Before staging, run `context run align:<type>:<source>:<collection> --validate --input - --format json` with the `context.structure.v1` payload. If validate returns `repair_confirmation_blockers`, follow its repair route and rerun validate without asking for preliminary approval. `--repair suggested-splits` handles non-contiguous source mirror Sections. For oversized Views, apply the returned child-View and contains-edge suggestions while classifying child Nodes from evidence. Resolve other blockers from evidence; ask the user only when evidence supports multiple incompatible semantic choices, and state that this is not final review. Stage only after `confirmation_ready=true`. The stage result opens the final HTML report and is the human review gate: show the structure to the user through `structure_report.file_url`, `structure_report.absolute_path`, and the compact summary before asking for confirmation. Only write `lifecycle.state: confirmed` only after explicit confirmation; then run `context run align:<type>:<source>:<collection> --confirm --format json` or pass an explicit file with `--confirm --input <structure.yaml> --format json`.
+Before staging, run `context run align:<type>:<source>:<collection> --validate --input - --format json` with the `context.structure.v1` payload. The CLI applies deterministic boundary repairs internally and returns only remaining blockers. For oversized Views, apply the returned child-View and contains-edge suggestions while classifying child Nodes from evidence. Resolve other blockers from evidence; ask the user only when evidence supports multiple incompatible semantic choices. Stage only after validation state is `ready`. The stage result opens the final HTML report for the Route-selected structure-confirmation gate. Execute the revision-bound confirmation command returned by `workflow.current`; managed session authority may resolve that gate without another question.
 
 After stage succeeds, do not rerun the same write command to confirm success.
 Use `context status --format json` or the returned result for read-only

package/providers/context/resources/semantic/compile/index.md

@@ -0,0 +1,31 @@
+---
+context_resource: semantic/compile/index
+id: context.semantic.compile.index
+kind: procedure
+media-type: text/markdown
+applies-to:
+  - diagnostic-routing
+  - evidence-repair
+name: compile-reference-index
+description: "Optional index for non-mechanical structure and evidence diagnostics; normal compile does not require it."
+---
+
+# Compile semantic reference index
+
+Normal source-bound compile is deterministic and does not require these
+references. Read this index only when a structure or evidence diagnostic asks
+for a non-mechanical decision, then open only the matching procedure:
+
+- [Compile action contract](compile-actions.md)
+- [Action and domain gates](action-domain-gates.md)
+- [Notes and caveats](notes.md)
+- [Refresh and update](refresh-and-update.md)
+- [Structural challenges](structural-challenges.md)
+- [Compile judgment](compile-judgment.md)
+- [Semantic judgment](semantic-judgment.md)
+- [Disposition semantics](disposition-semantics.md)
+- [Temporal evidence](temporal-and-evidence.md)
+- [Leakage and ownership](leakage-and-ownership.md)
+- [Scope review and omission](scope-review-and-omit.md)
+- [User confirmation](user-confirmation.md)
+- [Close gate](close-gate.md)

package/providers/context/resources/views/package-current.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.resource.v1
+id: context.package-current
+kind: context-view
+mediaType: text/markdown
+description: Current package declarations, freshness, and output counts.
+materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/review-current.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.resource.v1
+id: context.review-current
+kind: context-view
+mediaType: text/markdown
+description: Current complete review scope and candidate-set identity.
+materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/source-current.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.resource.v1
+id: context.source-current
+kind: context-view
+mediaType: text/markdown
+description: Current repository and document source readiness and pending capture or extraction targets.
+materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/structure-current.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.resource.v1
+id: context.structure-current
+kind: context-view
+mediaType: text/markdown
+description: Current multi-document structure slots, declarations, and compile batch.
+materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/verification-current.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.resource.v1
+id: context.verification-current
+kind: context-view
+mediaType: text/markdown
+description: Current verification, evidence, and deterministic close diagnostics.
+materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/workspace-current.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.resource.v1
+id: context.workspace-current
+kind: context-view
+mediaType: text/markdown
+description: Current workspace counts, route, diagnostics, and declared lifecycle coverage.
+materializer: actions/materialize-context-view.yaml

package/providers/context/schemas/evidence-maintenance-input.schema.json

@@ -0,0 +1,30 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "context.evidence-maintenance.v1",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["schema", "decisions"],
+  "properties": {
+    "schema": {
+      "const": "context.evidence-maintenance.v1"
+    },
+    "decisions": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["view_ref", "action"],
+        "properties": {
+          "view_ref": {
+            "type": "string",
+            "minLength": 1
+          },
+          "action": {
+            "enum": ["re-pin", "deprecate", "keep-orphaned"]
+          }
+        }
+      }
+    }
+  }
+}

package/providers/context/schemas/source-batch-input.schema.json

@@ -0,0 +1,189 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://context4ai.dev/schemas/context-source-batch-input.v1.json",
+  "title": "Context source batch input",
+  "description": "One confirmed batch of repository, local document, and Lark document source boundaries.",
+  "oneOf": [
+    {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "sources"
+      ],
+      "properties": {
+        "sources": {
+          "$ref": "#/$defs/sources"
+        }
+      }
+    },
+    {
+      "$ref": "#/$defs/sources"
+    }
+  ],
+  "$defs": {
+    "module": {
+      "type": "string",
+      "pattern": "^[a-z0-9][a-z0-9._-]*$"
+    },
+    "nonEmptyString": {
+      "type": "string",
+      "minLength": 1
+    },
+    "repo": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "type",
+        "module"
+      ],
+      "properties": {
+        "type": {
+          "const": "repo"
+        },
+        "module": {
+          "$ref": "#/$defs/module"
+        },
+        "local": {
+          "$ref": "#/$defs/nonEmptyString"
+        },
+        "remote": {
+          "$ref": "#/$defs/nonEmptyString"
+        },
+        "ref": {
+          "$ref": "#/$defs/nonEmptyString"
+        }
+      }
+    },
+    "file": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "type",
+        "local"
+      ],
+      "properties": {
+        "type": {
+          "const": "file"
+        },
+        "module": {
+          "$ref": "#/$defs/module"
+        },
+        "local": {
+          "$ref": "#/$defs/nonEmptyString"
+        },
+        "include": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/nonEmptyString"
+          }
+        }
+      }
+    },
+    "lark": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "type"
+      ],
+      "properties": {
+        "type": {
+          "const": "lark"
+        },
+        "module": {
+          "$ref": "#/$defs/module"
+        },
+        "url": {
+          "$ref": "#/$defs/nonEmptyString"
+        },
+        "docToken": {
+          "$ref": "#/$defs/nonEmptyString"
+        },
+        "wikiToken": {
+          "$ref": "#/$defs/nonEmptyString"
+        },
+        "title": {
+          "$ref": "#/$defs/nonEmptyString"
+        }
+      },
+      "oneOf": [
+        {
+          "required": [
+            "url"
+          ],
+          "not": {
+            "anyOf": [
+              {
+                "required": [
+                  "docToken"
+                ]
+              },
+              {
+                "required": [
+                  "wikiToken"
+                ]
+              }
+            ]
+          }
+        },
+        {
+          "required": [
+            "docToken"
+          ],
+          "not": {
+            "anyOf": [
+              {
+                "required": [
+                  "url"
+                ]
+              },
+              {
+                "required": [
+                  "wikiToken"
+                ]
+              }
+            ]
+          }
+        },
+        {
+          "required": [
+            "wikiToken"
+          ],
+          "not": {
+            "anyOf": [
+              {
+                "required": [
+                  "url"
+                ]
+              },
+              {
+                "required": [
+                  "docToken"
+                ]
+              }
+            ]
+          }
+        }
+      ]
+    },
+    "source": {
+      "oneOf": [
+        {
+          "$ref": "#/$defs/repo"
+        },
+        {
+          "$ref": "#/$defs/file"
+        },
+        {
+          "$ref": "#/$defs/lark"
+        }
+      ]
+    },
+    "sources": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "$ref": "#/$defs/source"
+      }
+    }
+  }
+}

package/providers/context/scripts/render-context-view.mjs

@@ -0,0 +1,21 @@
+const rawInput = process.env.AGENT_GRAPH_INPUT;
+const revision = process.env.AGENT_GRAPH_REVISION;
+
+if (typeof rawInput !== "string" || rawInput.length === 0) {
+  throw new Error("Context view input is missing");
+}
+
+const input = JSON.parse(rawInput);
+if (
+  input === null ||
+  typeof input !== "object" ||
+  input.schema !== "context.workflow.resource-input.v1" ||
+  typeof input.content !== "string"
+) {
+  throw new Error("Context view input is invalid");
+}
+if (input.revision !== revision) {
+  throw new Error("Context view revision does not match the selected route");
+}
+
+process.stdout.write(input.content.endsWith("\n") ? input.content : `${input.content}\n`);