@c4a/context-cli 0.6.19 → 0.7.0

package/plugins/codex/skills/context/SKILL.md

@@ -1,22 +1,11 @@
 ---
 name: context
-description: >
-  Build or continue structured, traceable Agent knowledge from documents and code. Use the local `context` CLI for workspace writes.
+description: Build or continue structured, traceable Agent knowledge from documents and code. Use the local `context` CLI for workspace writes.
 tools:
   - Bash
 ---
 
-# Context
-
-Public Context entry for agents that expose skills instead of slash commands.
-
-- Public entry: `context`
-- Host command names are installation-specific; use the command or skill surfaced by the current host instead of deriving a filesystem path from an example name.
-- CLI primitive prefix: `context ...`
-
----
-
-## Workflow
+## Your Task
 
 Context is a knowledge management tool built for Agent knowledge workflows. It
 compiles Feishu/Lark documents, local Markdown, repository code, and manually
@@ -157,6 +146,81 @@ the same module problem, stop at the one aggregated human-guidance Gate. If a
 legacy workspace returns `route.extract.codeindex-migration-required`, execute
 only its migration command; do not rename `codegraph` paths manually.
 
+### Discover Indexer Providers before selection
+
+For `indexer-provider-required`, `indexer-provider-unavailable`,
+`indexer-customization-required`, `indexer-customization-invalid`, or
+`indexer-customization-upstream-changed`, read
+`node_modules/@c4a/context/docs/guides/indexer-provider-and-customization.md`
+before proposing a selection or project change. It defines the registry-only
+default, six-level customization ladder, upgrade conflict handling, debugging
+commands, and the exit condition for each level. Do not replace it with a
+remembered or host-specific workflow.
+
+When the current Route starts a new Code or Markdown indexing task, run this
+read-only command once before creating or changing any Provider registry entry:
+
+```bash
+context indexer catalog --format json
+```
+
+Report the returned CLI-bundled entry Skills together with every other Indexer
+Skill already visible through the current host. The conversational report must
+include each Skill name, readable exact version when available, and source type
+(CLI-bundled community, workspace, installed plugin, or authorized marketplace
+result). When the host already exposes an exact Skill root or `SKILL.md` path,
+read only its YAML frontmatter and sibling `context-indexer.yaml` during
+discovery. The manifest version is authoritative;
+`metadata.context-provider-version` is a readable copy that must match it. Do
+not load the Provider body or other guidance until the Route selects it. If the
+host exposes no readable root or exact version, report the version as
+unavailable rather than guessing it.
+
+Group observations with the same Skill name and exact version into one
+conversational item and list all observed source types on that item. An
+installed projection of an identical CLI-bundled identity is not a second
+Provider. Keep different versions separate. The route input still preserves
+each distinct source observation as its own `visible_skills` entry because
+`source_type` is singular; never use source count or discovery order as
+selection precedence. Do not search arbitrary directories, infer host cache
+paths, install a plugin, or query a marketplace unless the user separately
+authorizes it. Keep this discovery report only in the conversation: do not
+write it to `src/`, `package.json`, lifecycle state, receipts, audit output, or
+`dist/`. Do not repeat it during an unchanged task resume; repeat it only for a
+new indexing task, a changed host-visible Skill set, or an explicit diagnostic
+request.
+
+After the requirements are applied, author one
+`context.indexer.provider-route-input/v1` payload whose `registry` preserves
+the applied `requirements` block exactly and whose `visible_skills` contains
+only the just-reported path-free identities. Route it before any Host resolves
+or reads an external Provider:
+
+```bash
+context indexer route-indexer-provider-selection --input <payload.yaml-or-json> --format json
+```
+
+On `community-fallback-required`, retry with the applicable CLI-bundled profile
+and set `community_fallback_attempted: true`. Read-scope overlap is allowed, but
+an exact primary owner-cell conflict must be resolved explicitly; do not use
+array or discovery order as precedence. If fallback leaves a required owner
+cell uncovered, preserve the returned `capability_gap_proof`. Only the Route's
+following `propose-indexer-customization` Agent Action may turn that exact proof
+into a dependency-free minimal `extend` draft; do not weaken the requirement,
+write source, add dependencies, or claim the draft is applied.
+
+Only `selection-validation-required` returns a
+`selection_proposal_input`. Pass that exact object to:
+
+```bash
+context indexer validate-indexer-selection-proposal --input <payload.yaml-or-json> --format json
+```
+
+Use only the returned `next_provider_requests` for resolution. A successful
+static report does not authorize materialization, installation, execution, or
+writing the proposal into `src/indexers.yaml`; continue through the Route's
+resolver, staging, final validation, confirmation, and apply Actions.
+
 ### Follow the current Route
 
 Treat `workflow.current` as the current-step authority:

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -1,28 +1,15 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.6.19",
+  "version": "0.7.0",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
-  "author": {
-    "name": "Context4AI",
-    "email": "support@context4ai.dev"
-  },
+  "author": { "name": "Context4AI", "email": "support@context4ai.dev" },
   "homepage": "https://github.com/context4ai/c4a",
   "repository": "https://github.com/context4ai/c4a",
   "license": "MIT",
   "logo": "assets/logo.svg",
-  "keywords": [
-    "context",
-    "knowledge",
-    "citations",
-    "agent-skills"
-  ],
+  "keywords": ["context", "knowledge", "citations", "agent-skills"],
   "category": "developer-tools",
-  "tags": [
-    "knowledge",
-    "documentation",
-    "agent-skills",
-    "citations"
-  ],
+  "tags": ["knowledge", "documentation", "agent-skills", "citations"],
   "commands": "./commands/"
 }

package/plugins/cursor/AGENTS.md

@@ -2,4 +2,4 @@
 
 This directory is generated by `bun run build:plugin`.
 Do not edit files here directly.
-Edit `packages/context-cli/plugin/` and rerun the build instead.
+Edit `plugins/context/` and rerun the build instead.

package/plugins/cursor/README.md

@@ -2,12 +2,13 @@
 
 This directory is generated by `bun run build:plugin`.
 Do not edit files here directly.
-Edit `packages/context-cli/plugin/` and rerun the build instead.
+Edit `plugins/context/` and rerun the build instead.
 
 Install shape:
 
 - Marketplace/GitHub plugin shape: this directory is a plugin root with `.cursor-plugin/plugin.json` and `commands/`.
-- User entries are under `commands/`; Cursor command files are prefixed as `c4a-*` to avoid global slash-command collisions.
+- The public entry is under `commands/`; Cursor command files are prefixed as `c4a-*` to avoid global slash-command collisions.
+- Lifecycle Provider skills are installed separately into the shared user skill directory by `context plugin install`.
 - Local plugin fallback: symlink or copy this directory to `~/.cursor/plugins/local/c4a/` only when Marketplace import is unavailable.
 
 Cursor Marketplace installs this plugin root directly.

package/plugins/cursor/commands/c4a-context.md

@@ -1,7 +1,5 @@
 ---
-description: "Build or continue structured, traceable Agent knowledge from documents and code."
-argument-hint: "[project-dir or user intent]"
-allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
+description: "Build or continue structured, traceable Agent knowledge from documents and code. Use the local `context` CLI for workspace writes."
 ---
 
 Start or continue a C4A Context knowledge workspace.
@@ -149,6 +147,81 @@ the same module problem, stop at the one aggregated human-guidance Gate. If a
 legacy workspace returns `route.extract.codeindex-migration-required`, execute
 only its migration command; do not rename `codegraph` paths manually.
 
+### Discover Indexer Providers before selection
+
+For `indexer-provider-required`, `indexer-provider-unavailable`,
+`indexer-customization-required`, `indexer-customization-invalid`, or
+`indexer-customization-upstream-changed`, read
+`node_modules/@c4a/context/docs/guides/indexer-provider-and-customization.md`
+before proposing a selection or project change. It defines the registry-only
+default, six-level customization ladder, upgrade conflict handling, debugging
+commands, and the exit condition for each level. Do not replace it with a
+remembered or host-specific workflow.
+
+When the current Route starts a new Code or Markdown indexing task, run this
+read-only command once before creating or changing any Provider registry entry:
+
+```bash
+context indexer catalog --format json
+```
+
+Report the returned CLI-bundled entry Skills together with every other Indexer
+Skill already visible through the current host. The conversational report must
+include each Skill name, readable exact version when available, and source type
+(CLI-bundled community, workspace, installed plugin, or authorized marketplace
+result). When the host already exposes an exact Skill root or `SKILL.md` path,
+read only its YAML frontmatter and sibling `context-indexer.yaml` during
+discovery. The manifest version is authoritative;
+`metadata.context-provider-version` is a readable copy that must match it. Do
+not load the Provider body or other guidance until the Route selects it. If the
+host exposes no readable root or exact version, report the version as
+unavailable rather than guessing it.
+
+Group observations with the same Skill name and exact version into one
+conversational item and list all observed source types on that item. An
+installed projection of an identical CLI-bundled identity is not a second
+Provider. Keep different versions separate. The route input still preserves
+each distinct source observation as its own `visible_skills` entry because
+`source_type` is singular; never use source count or discovery order as
+selection precedence. Do not search arbitrary directories, infer host cache
+paths, install a plugin, or query a marketplace unless the user separately
+authorizes it. Keep this discovery report only in the conversation: do not
+write it to `src/`, `package.json`, lifecycle state, receipts, audit output, or
+`dist/`. Do not repeat it during an unchanged task resume; repeat it only for a
+new indexing task, a changed host-visible Skill set, or an explicit diagnostic
+request.
+
+After the requirements are applied, author one
+`context.indexer.provider-route-input/v1` payload whose `registry` preserves
+the applied `requirements` block exactly and whose `visible_skills` contains
+only the just-reported path-free identities. Route it before any Host resolves
+or reads an external Provider:
+
+```bash
+context indexer route-indexer-provider-selection --input <payload.yaml-or-json> --format json
+```
+
+On `community-fallback-required`, retry with the applicable CLI-bundled profile
+and set `community_fallback_attempted: true`. Read-scope overlap is allowed, but
+an exact primary owner-cell conflict must be resolved explicitly; do not use
+array or discovery order as precedence. If fallback leaves a required owner
+cell uncovered, preserve the returned `capability_gap_proof`. Only the Route's
+following `propose-indexer-customization` Agent Action may turn that exact proof
+into a dependency-free minimal `extend` draft; do not weaken the requirement,
+write source, add dependencies, or claim the draft is applied.
+
+Only `selection-validation-required` returns a
+`selection_proposal_input`. Pass that exact object to:
+
+```bash
+context indexer validate-indexer-selection-proposal --input <payload.yaml-or-json> --format json
+```
+
+Use only the returned `next_provider_requests` for resolution. A successful
+static report does not authorize materialization, installation, execution, or
+writing the proposal into `src/indexers.yaml`; continue through the Route's
+resolver, staging, final validation, confirmation, and apply Actions.
+
 ### Follow the current Route
 
 Treat `workflow.current` as the current-step authority:

package/plugins/skills/{c4a-context → context}/SKILL.md

@@ -1,22 +1,11 @@
 ---
-name: c4a-context
-description: >
-  Build or continue structured, traceable Agent knowledge from documents and code. Use the local `context` CLI for workspace writes.
+name: context
+description: Build or continue structured, traceable Agent knowledge from documents and code. Use the local `context` CLI for workspace writes.
 tools:
   - Bash
 ---
 
-# Context
-
-Public Context entry for agents that expose skills instead of slash commands.
-
-- Public entry: `c4a-context`
-- Host command names are installation-specific; use the command or skill surfaced by the current host instead of deriving a filesystem path from an example name.
-- CLI primitive prefix: `context ...`
-
----
-
-## Workflow
+## Your Task
 
 Context is a knowledge management tool built for Agent knowledge workflows. It
 compiles Feishu/Lark documents, local Markdown, repository code, and manually
@@ -157,6 +146,81 @@ the same module problem, stop at the one aggregated human-guidance Gate. If a
 legacy workspace returns `route.extract.codeindex-migration-required`, execute
 only its migration command; do not rename `codegraph` paths manually.
 
+### Discover Indexer Providers before selection
+
+For `indexer-provider-required`, `indexer-provider-unavailable`,
+`indexer-customization-required`, `indexer-customization-invalid`, or
+`indexer-customization-upstream-changed`, read
+`node_modules/@c4a/context/docs/guides/indexer-provider-and-customization.md`
+before proposing a selection or project change. It defines the registry-only
+default, six-level customization ladder, upgrade conflict handling, debugging
+commands, and the exit condition for each level. Do not replace it with a
+remembered or host-specific workflow.
+
+When the current Route starts a new Code or Markdown indexing task, run this
+read-only command once before creating or changing any Provider registry entry:
+
+```bash
+context indexer catalog --format json
+```
+
+Report the returned CLI-bundled entry Skills together with every other Indexer
+Skill already visible through the current host. The conversational report must
+include each Skill name, readable exact version when available, and source type
+(CLI-bundled community, workspace, installed plugin, or authorized marketplace
+result). When the host already exposes an exact Skill root or `SKILL.md` path,
+read only its YAML frontmatter and sibling `context-indexer.yaml` during
+discovery. The manifest version is authoritative;
+`metadata.context-provider-version` is a readable copy that must match it. Do
+not load the Provider body or other guidance until the Route selects it. If the
+host exposes no readable root or exact version, report the version as
+unavailable rather than guessing it.
+
+Group observations with the same Skill name and exact version into one
+conversational item and list all observed source types on that item. An
+installed projection of an identical CLI-bundled identity is not a second
+Provider. Keep different versions separate. The route input still preserves
+each distinct source observation as its own `visible_skills` entry because
+`source_type` is singular; never use source count or discovery order as
+selection precedence. Do not search arbitrary directories, infer host cache
+paths, install a plugin, or query a marketplace unless the user separately
+authorizes it. Keep this discovery report only in the conversation: do not
+write it to `src/`, `package.json`, lifecycle state, receipts, audit output, or
+`dist/`. Do not repeat it during an unchanged task resume; repeat it only for a
+new indexing task, a changed host-visible Skill set, or an explicit diagnostic
+request.
+
+After the requirements are applied, author one
+`context.indexer.provider-route-input/v1` payload whose `registry` preserves
+the applied `requirements` block exactly and whose `visible_skills` contains
+only the just-reported path-free identities. Route it before any Host resolves
+or reads an external Provider:
+
+```bash
+context indexer route-indexer-provider-selection --input <payload.yaml-or-json> --format json
+```
+
+On `community-fallback-required`, retry with the applicable CLI-bundled profile
+and set `community_fallback_attempted: true`. Read-scope overlap is allowed, but
+an exact primary owner-cell conflict must be resolved explicitly; do not use
+array or discovery order as precedence. If fallback leaves a required owner
+cell uncovered, preserve the returned `capability_gap_proof`. Only the Route's
+following `propose-indexer-customization` Agent Action may turn that exact proof
+into a dependency-free minimal `extend` draft; do not weaken the requirement,
+write source, add dependencies, or claim the draft is applied.
+
+Only `selection-validation-required` returns a
+`selection_proposal_input`. Pass that exact object to:
+
+```bash
+context indexer validate-indexer-selection-proposal --input <payload.yaml-or-json> --format json
+```
+
+Use only the returned `next_provider_requests` for resolution. A successful
+static report does not authorize materialization, installation, execution, or
+writing the proposal into `src/indexers.yaml`; continue through the Route's
+resolver, staging, final validation, confirmation, and apply Actions.
+
 ### Follow the current Route
 
 Treat `workflow.current` as the current-step authority:

package/plugins/skills/context-code-indexer/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: context-code-indexer
+description: Context-managed Provider for evidence-bound code knowledge. Use only when the Context Indexer lifecycle selects this Provider, not as a standalone workflow.
+metadata:
+  context-role: "indexer-provider"
+  context-public-entry: "false"
+  context-provider-version: "1.0.0"
+---
+
+# Context Code Indexer
+
+Provider authors must satisfy
+`node_modules/@c4a/context/docs/guides/code-indexer-skill-authoring.md` and the
+shared Provider/customization guide before publishing or extending this Skill.
+Those documents are authoring contracts; the current workset and Route remain
+execution authority.
+
+Use this Provider only through the Context Indexer lifecycle. The workspace registry selects an exact profile, version, integrity, scope, and operation. Do not scan outside the supplied workset or write project files directly.
+
+The machine-readable authority is `context-indexer.yaml`. Detailed authoring guidance is materialized by Context from the registered Bundle after its file ledger and integrity have been verified.

package/plugins/skills/context-code-indexer/context-indexer.yaml

@@ -0,0 +1,230 @@
+protocol: context.indexer.provider/v1
+id: context-code-indexer
+version: 1.0.0
+domains: [code]
+
+activation:
+  target_kinds: [repository, package, library, service, application]
+  required_signals:
+    - id: supported-source
+      description: The registered target scope contains source or contract files supported by Context.
+  supporting_signals:
+    - id: stable-entry
+      description: The target exposes a stable entry, protocol, command, route, export, or runtime boundary.
+    - id: usage-material
+      description: The readable scope contains examples, tests, documentation, or operational material.
+  negative_signals:
+    - id: generated-only
+      description: The scope contains only generated artifacts with no authoritative source boundary.
+  agent_questions:
+    - Which stable reader capability groups the complete eligible inventory?
+
+provides:
+  profiles:
+    - monorepo-container
+    - web-application
+    - component-library
+    - sdk-library
+    - cli-tool
+    - plugin-extension
+    - api-service
+    - gateway-facade
+    - domain-service
+    - background-runtime
+    - event-consumer
+    - data-sync-reconciliation
+    - storage-repository
+    - adapter-integration
+    - contract-source
+    - derived-generated-source
+  partition_strategies:
+    - id: public-target-family
+      profiles: [component-library, sdk-library, plugin-extension, contract-source]
+      priority: 100
+    - id: canonical-semantic-subject
+      profiles:
+        - monorepo-container
+        - web-application
+        - component-library
+        - sdk-library
+        - cli-tool
+        - plugin-extension
+        - api-service
+        - gateway-facade
+        - domain-service
+        - background-runtime
+        - event-consumer
+        - data-sync-reconciliation
+        - storage-repository
+        - adapter-integration
+        - contract-source
+        - derived-generated-source
+      priority: 200
+  operations:
+    - id: main-index
+      consumes: context.indexer.main-workset/v1
+      produces: context.indexer.main-result/v1
+      accepts_layer_fragments: [fact-enrichment, template-variables]
+    - id: material-answer
+      consumes: context.indexer.material-question-workset/v1
+      produces: context.indexer.material-answer-result/v1
+      supported_evidence_kinds: [code, contract, configuration, documentation, runbook, test-result, runtime-observation]
+      accepts_layer_fragments: [fact-enrichment]
+  layer_fragments:
+    - kind: derived-artifact-proposal
+      phase: post-author
+      produces: context.indexer.layer-fragment/v1
+  composers:
+    - id: public-contract
+      supported_profiles: [component-library, sdk-library, cli-tool, plugin-extension, api-service, gateway-facade, domain-service, adapter-integration, contract-source, derived-generated-source]
+      contract:
+        instruction: references/composers/public-contract.md
+        primary_requirements: { fact_kinds: [public-surface], artifact_kinds: [content] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [contract]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: protocol-boundary
+      supported_profiles: [web-application, sdk-library, cli-tool, plugin-extension, api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, storage-repository, adapter-integration, contract-source, derived-generated-source]
+      contract:
+        instruction: references/composers/protocol-boundary.md
+        primary_requirements: { fact_kinds: [protocol-operation], artifact_kinds: [contract] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [contract]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: cross-module-chain
+      supported_profiles: [monorepo-container, web-application, component-library, sdk-library, cli-tool, plugin-extension, api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, storage-repository, adapter-integration]
+      contract:
+        instruction: references/composers/cross-module-chain.md
+        primary_requirements: { fact_kinds: [module-dependency], artifact_kinds: [content] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [content]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: contracts-and-chains
+      supported_profiles: [monorepo-container, web-application, component-library, sdk-library, cli-tool, plugin-extension, api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, storage-repository, adapter-integration, contract-source, derived-generated-source]
+      contract:
+        instruction: references/composers/contracts-and-chains.md
+        primary_requirements: { fact_kinds: [contract-binding, module-dependency], artifact_kinds: [contract] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [contract]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: event-flow
+      supported_profiles: [web-application, plugin-extension, api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, adapter-integration, contract-source]
+      contract:
+        instruction: references/composers/event-flow.md
+        primary_requirements: { fact_kinds: [event-binding], artifact_kinds: [content] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [content]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: persistence-boundary
+      supported_profiles: [api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, storage-repository, adapter-integration]
+      contract:
+        instruction: references/composers/persistence-boundary.md
+        primary_requirements: { fact_kinds: [persistence-binding], artifact_kinds: [content] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [content]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: examples-and-documentation
+      supported_profiles: [monorepo-container, web-application, component-library, sdk-library, cli-tool, plugin-extension, api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, storage-repository, adapter-integration, contract-source, derived-generated-source]
+      contract:
+        instruction: references/composers/examples-and-documentation.md
+        primary_requirements: { fact_kinds: [example-candidate], artifact_kinds: [content] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [examples]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+    - id: development-and-delivery
+      supported_profiles: [monorepo-container, web-application, component-library, sdk-library, cli-tool, plugin-extension, api-service, gateway-facade, domain-service, background-runtime, event-consumer, data-sync-reconciliation, storage-repository, adapter-integration, contract-source, derived-generated-source]
+      contract:
+        instruction: references/composers/development-and-delivery.md
+        primary_requirements: { fact_kinds: [development-entry], artifact_kinds: [content] }
+        derived_artifact_policy:
+          fragment_protocol: context.indexer.layer-fragment/v1
+          fragment_kind: derived-artifact-proposal
+          artifact_policy_variant: standard
+          artifact_kinds: [content]
+        empty_result: { result_protocol: context.indexer.layer-fragment-result/v1, behavior: empty-fragment-set }
+  source_roles: [authoritative-source, public-contract-source, example-source, operational-source]
+  logical_units:
+    - id: semantic-subject
+      identity: canonical-subject-key
+      artifacts:
+        recommended: [content, contract, examples]
+        supported_policy_variants: [compact, standard, expanded]
+
+provider:
+  instructions:
+    - path: references/indexer.md
+      profiles:
+        - monorepo-container
+        - web-application
+        - component-library
+        - sdk-library
+        - cli-tool
+        - plugin-extension
+        - api-service
+        - gateway-facade
+        - domain-service
+        - background-runtime
+        - event-consumer
+        - data-sync-reconciliation
+        - storage-repository
+        - adapter-integration
+        - contract-source
+        - derived-generated-source
+  templates:
+    - { id: monorepo-container, profile: monorepo-container, path: templates/monorepo-container.md }
+    - { id: web-application, profile: web-application, path: templates/web-application.md }
+    - { id: component-library, profile: component-library, path: templates/component-library.md }
+    - { id: sdk-library, profile: sdk-library, path: templates/sdk-library.md }
+    - { id: cli-tool, profile: cli-tool, path: templates/cli-tool.md }
+    - { id: plugin-extension, profile: plugin-extension, path: templates/plugin-extension.md }
+    - { id: api-service, profile: api-service, path: templates/api-service.md }
+    - { id: gateway-facade, profile: gateway-facade, path: templates/gateway-facade.md }
+    - { id: domain-service, profile: domain-service, path: templates/domain-service.md }
+    - { id: background-runtime, profile: background-runtime, path: templates/background-runtime.md }
+    - { id: event-consumer, profile: event-consumer, path: templates/event-consumer.md }
+    - { id: data-sync-reconciliation, profile: data-sync-reconciliation, path: templates/data-sync-reconciliation.md }
+    - { id: storage-repository, profile: storage-repository, path: templates/storage-repository.md }
+    - { id: adapter-integration, profile: adapter-integration, path: templates/adapter-integration.md }
+    - { id: contract-source, profile: contract-source, path: templates/contract-source.md }
+    - { id: derived-generated-source, profile: derived-generated-source, path: templates/derived-generated-source.md }
+  forbidden_fallbacks: [one-page-per-symbol, ordinal-batch-pages, inferred-runtime-chain]
+  completion_checks: [inventory-disposition-closure, subject-owner-closure, evidence-binding]
+
+customization:
+  supports: [config, instructions-append, template-override, program-extend]
+
+quality_guidance:
+  metric_ids:
+    - inventory-disposition-coverage
+    - duplicated-fact-target-ratio
+    - narrative-enumeration-ratio
+    - normalized-template-repetition-ratio
+    - implementation-body-ratio
+    - reference-only-reader-targets
+    - unresolved-ordinal-partitions
+    - discretionary-artifacts-per-logical-unit
+    - example-candidate-decision-coverage
+    - example-representative-coverage
+    - example-public-target-linkage
+  repair: references/metrics.md

package/plugins/skills/context-code-indexer/references/composers/contracts-and-chains.md

@@ -0,0 +1,23 @@
+---
+id: context.code-indexer.composer.contracts-and-chains
+kind: procedure
+media-type: text/markdown
+---
+
+# Contracts and chains composer
+
+Use only when `contracts-and-chains` is present in the effective composer set.
+Consume the exact primary view and return post-author proposals, never another
+complete Indexer Result.
+
+Require both `contract-binding` and `module-dependency` facts plus a primary
+`contract` Artifact. A derived `contract` Artifact may summarize how a stable
+contract identity is produced, transported, implemented, consumed, and traced
+across registered modules. Preserve the authoritative schema and distinguish
+generated bindings from source contracts.
+
+Use the existing target, the `standard` policy, and evidence already bound to
+the view. Do not merge unrelated protocols merely because they share a
+transport. If either fact, the primary Artifact, or an evidenced end-to-end
+binding is absent, return `context.indexer.layer-fragment-result/v1` with an
+empty `fragments` array.

package/plugins/skills/context-code-indexer/references/composers/cross-module-chain.md

@@ -0,0 +1,22 @@
+---
+id: context.code-indexer.composer.cross-module-chain
+kind: procedure
+media-type: text/markdown
+---
+
+# Cross-module chain composer
+
+Run only for the selected composer and the supplied `PrimaryResultView`.
+Derived output supplements an existing target Node; it cannot create scope,
+change ownership, or replace the primary Result.
+
+Require an evidenced `module-dependency` fact and primary `content` Artifact.
+Propose derived `content` only when a stable reader question crosses at least
+two registered module boundaries and every hop has an unambiguous identity and
+evidence. Describe trigger, ordered boundaries, transformations, outcome,
+failure propagation, and recovery without copying each module page.
+
+Use the `standard` policy and view evidence only. Import adjacency, directory
+proximity, or a guessed runtime call is insufficient. Missing requirements,
+an incomplete chain, or an already answered question yields the structured
+empty result: the accepted layer-fragment result with `fragments: []`.