@c4a/context-cli 0.6.18 → 0.7.0

package/plugins/codex/.codex-plugin/plugin.json

@@ -1,34 +1,23 @@
 {
   "name": "c4a",
-  "version": "0.6.18",
+  "version": "0.7.0",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
-  "author": {
-    "name": "c4a"
-  },
+  "author": { "name": "c4a" },
   "homepage": "https://github.com/context4ai/c4a",
-  "repository": "https://github.com/context4ai/c4a/tree/main/packages/context-cli",
+  "repository": "https://github.com/context4ai/c4a",
   "license": "MIT",
-  "keywords": [
-    "context",
-    "knowledge-base",
-    "codex-plugin",
-    "agent-skills",
-    "c4a"
-  ],
+  "keywords": ["context", "knowledge-base", "codex-plugin", "agent-skills", "c4a"],
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.18",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.0",
     "longDescription": "Create a Context workspace and use agent-guided next steps to register sources, run extraction, review candidates, build package outputs, and verify health without silently mutating source repositories.",
     "developerName": "c4a",
     "category": "Productivity",
     "brandColor": "#ef6f2e",
     "composerIcon": "./assets/icon.svg",
     "logo": "./assets/logo.svg",
-    "capabilities": [
-      "Read",
-      "Write"
-    ],
+    "capabilities": ["Read", "Write"],
     "websiteURL": "https://github.com/context4ai/c4a",
     "defaultPrompt": [
       "Continue my Context workspace with the next useful step.",

package/plugins/codex/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/codex/README.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/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
@@ -38,6 +27,18 @@ Run:
 context entry [project-dir] --language <language> --format json
 ```
 
+If the request does not already choose ordinary review or fully managed
+operation, first use the read-only entry result to state a short execution
+plan, then ask the user to choose once. Explain that ordinary review pauses at
+human Gates and presents HTML reports, while fully managed operation resolves
+delegatable Gates within this conversation but still stops for permissions,
+hard validation, or non-delegatable decisions. Prefer the host's native choice
+UI. When initialization already needs a confirmation or missing option, combine
+the mode choice with that question instead of adding another round. Keep the
+answer only in this conversation and do not ask again after initialization,
+capture, or resume. An explicit request for review, human confirmation, fully
+managed work, or no further review already resolves this choice.
+
 Use the user's explicit language choice when present; otherwise pass `zh-CN`
 for a Chinese conversation and `en` for an English conversation. Pass
 `project-dir`, `--name`, `--dev`, or `--debug` only when the user explicitly
@@ -103,12 +104,14 @@ before workflow evaluation. Debugging records traces below
 source evidence.
 
 Document optimization is enabled by default for newly initialized workspaces.
-It conservatively repairs formatting, Markdown, links, and obvious local errors
-without broadly rewriting source-backed prose. It keeps approved pages
-source-faithful and stores only changed full-page revisions beside them as
-`knowledge/**/*__revision.md`. Default knowledge discovery excludes those
-reserved sidecars; validation and package compilation apply them to the
-matching base page.
+It performs source-constrained editorial revision: the CLI identifies
+readability and knowledge-value signals, and the Agent may keep, repair,
+reshape, or safely omit content only inside its existing source Section. It
+must preserve facts, link targets, images, code, numbers, identifiers, and
+source evidence. Approved pages remain source-faithful; only changed full-page
+revisions are stored beside them as `knowledge/**/*__revision.md`. Default
+knowledge discovery excludes those reserved sidecars, and internal editorial
+audit state is not included in package output.
 
 For an existing workspace, respect its current `package.json` setting. Run
 `context optimize-docs enable` or `context optimize-docs disable` only when the
@@ -135,6 +138,89 @@ The managed loop executes only Route-selected work and returns the current
 host execution, diagnostics, or a non-unique plan needs attention. Resume from
 that returned Route; never reconstruct a command from an earlier step.
 
+Code knowledge is published under `codeindex`. Context mechanically audits each
+module's input analysis, stable boundaries, facts, explanation, evidence scope,
+and page shape without producing a total score. In fully managed operation,
+follow returned repair actions automatically; after three failed revisions of
+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:
@@ -180,6 +266,14 @@ Explain, ask, confirm, and summarize in the user's current conversation
 language. Keep commands, flags, paths, ids, status values, JSONL keys,
 `source_ref` values, and copied CLI tokens unchanged.
 
+Keep a conversation-local list of HTML review reports that the user actually
+used to make a review decision. Preserve each exact report URL or local path
+and its reviewed scope when the Route provides them. In the final completion
+summary, include one compact `Review reports` section containing those exact
+references. Do not scan workspace internals to reconstruct the list, persist a
+second ledger, invent a public URL, or describe an inaccessible report or a
+fully managed/force approval as user-reviewed.
+
 When the user explicitly asks to publish a completed build, treat publication
 as a downstream distribution step outside the Context Route. Use only an
 explicitly installed distribution tool and its documented complete-output

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

@@ -1,28 +1,15 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.6.18",
+  "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.
@@ -30,6 +28,18 @@ Run:
 context entry [project-dir] --language <language> --format json
 ```
 
+If the request does not already choose ordinary review or fully managed
+operation, first use the read-only entry result to state a short execution
+plan, then ask the user to choose once. Explain that ordinary review pauses at
+human Gates and presents HTML reports, while fully managed operation resolves
+delegatable Gates within this conversation but still stops for permissions,
+hard validation, or non-delegatable decisions. Prefer the host's native choice
+UI. When initialization already needs a confirmation or missing option, combine
+the mode choice with that question instead of adding another round. Keep the
+answer only in this conversation and do not ask again after initialization,
+capture, or resume. An explicit request for review, human confirmation, fully
+managed work, or no further review already resolves this choice.
+
 Use the user's explicit language choice when present; otherwise pass `zh-CN`
 for a Chinese conversation and `en` for an English conversation. Pass
 `project-dir`, `--name`, `--dev`, or `--debug` only when the user explicitly
@@ -95,12 +105,14 @@ before workflow evaluation. Debugging records traces below
 source evidence.
 
 Document optimization is enabled by default for newly initialized workspaces.
-It conservatively repairs formatting, Markdown, links, and obvious local errors
-without broadly rewriting source-backed prose. It keeps approved pages
-source-faithful and stores only changed full-page revisions beside them as
-`knowledge/**/*__revision.md`. Default knowledge discovery excludes those
-reserved sidecars; validation and package compilation apply them to the
-matching base page.
+It performs source-constrained editorial revision: the CLI identifies
+readability and knowledge-value signals, and the Agent may keep, repair,
+reshape, or safely omit content only inside its existing source Section. It
+must preserve facts, link targets, images, code, numbers, identifiers, and
+source evidence. Approved pages remain source-faithful; only changed full-page
+revisions are stored beside them as `knowledge/**/*__revision.md`. Default
+knowledge discovery excludes those reserved sidecars, and internal editorial
+audit state is not included in package output.
 
 For an existing workspace, respect its current `package.json` setting. Run
 `context optimize-docs enable` or `context optimize-docs disable` only when the
@@ -127,6 +139,89 @@ The managed loop executes only Route-selected work and returns the current
 host execution, diagnostics, or a non-unique plan needs attention. Resume from
 that returned Route; never reconstruct a command from an earlier step.
 
+Code knowledge is published under `codeindex`. Context mechanically audits each
+module's input analysis, stable boundaries, facts, explanation, evidence scope,
+and page shape without producing a total score. In fully managed operation,
+follow returned repair actions automatically; after three failed revisions of
+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:
@@ -172,6 +267,14 @@ Explain, ask, confirm, and summarize in the user's current conversation
 language. Keep commands, flags, paths, ids, status values, JSONL keys,
 `source_ref` values, and copied CLI tokens unchanged.
 
+Keep a conversation-local list of HTML review reports that the user actually
+used to make a review decision. Preserve each exact report URL or local path
+and its reviewed scope when the Route provides them. In the final completion
+summary, include one compact `Review reports` section containing those exact
+references. Do not scan workspace internals to reconstruct the list, persist a
+second ledger, invent a public URL, or describe an inaccessible report or a
+fully managed/force approval as user-reviewed.
+
 When the user explicitly asks to publish a completed build, treat publication
 as a downstream distribution step outside the Context Route. Use only an
 explicitly installed distribution tool and its documented complete-output

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
@@ -38,6 +27,18 @@ Run:
 context entry [project-dir] --language <language> --format json
 ```
 
+If the request does not already choose ordinary review or fully managed
+operation, first use the read-only entry result to state a short execution
+plan, then ask the user to choose once. Explain that ordinary review pauses at
+human Gates and presents HTML reports, while fully managed operation resolves
+delegatable Gates within this conversation but still stops for permissions,
+hard validation, or non-delegatable decisions. Prefer the host's native choice
+UI. When initialization already needs a confirmation or missing option, combine
+the mode choice with that question instead of adding another round. Keep the
+answer only in this conversation and do not ask again after initialization,
+capture, or resume. An explicit request for review, human confirmation, fully
+managed work, or no further review already resolves this choice.
+
 Use the user's explicit language choice when present; otherwise pass `zh-CN`
 for a Chinese conversation and `en` for an English conversation. Pass
 `project-dir`, `--name`, `--dev`, or `--debug` only when the user explicitly
@@ -103,12 +104,14 @@ before workflow evaluation. Debugging records traces below
 source evidence.
 
 Document optimization is enabled by default for newly initialized workspaces.
-It conservatively repairs formatting, Markdown, links, and obvious local errors
-without broadly rewriting source-backed prose. It keeps approved pages
-source-faithful and stores only changed full-page revisions beside them as
-`knowledge/**/*__revision.md`. Default knowledge discovery excludes those
-reserved sidecars; validation and package compilation apply them to the
-matching base page.
+It performs source-constrained editorial revision: the CLI identifies
+readability and knowledge-value signals, and the Agent may keep, repair,
+reshape, or safely omit content only inside its existing source Section. It
+must preserve facts, link targets, images, code, numbers, identifiers, and
+source evidence. Approved pages remain source-faithful; only changed full-page
+revisions are stored beside them as `knowledge/**/*__revision.md`. Default
+knowledge discovery excludes those reserved sidecars, and internal editorial
+audit state is not included in package output.
 
 For an existing workspace, respect its current `package.json` setting. Run
 `context optimize-docs enable` or `context optimize-docs disable` only when the
@@ -135,6 +138,89 @@ The managed loop executes only Route-selected work and returns the current
 host execution, diagnostics, or a non-unique plan needs attention. Resume from
 that returned Route; never reconstruct a command from an earlier step.
 
+Code knowledge is published under `codeindex`. Context mechanically audits each
+module's input analysis, stable boundaries, facts, explanation, evidence scope,
+and page shape without producing a total score. In fully managed operation,
+follow returned repair actions automatically; after three failed revisions of
+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:
@@ -180,6 +266,14 @@ Explain, ask, confirm, and summarize in the user's current conversation
 language. Keep commands, flags, paths, ids, status values, JSONL keys,
 `source_ref` values, and copied CLI tokens unchanged.
 
+Keep a conversation-local list of HTML review reports that the user actually
+used to make a review decision. Preserve each exact report URL or local path
+and its reviewed scope when the Route provides them. In the final completion
+summary, include one compact `Review reports` section containing those exact
+references. Do not scan workspace internals to reconstruct the list, persist a
+second ledger, invent a public URL, or describe an inaccessible report or a
+fully managed/force approval as user-reviewed.
+
 When the user explicitly asks to publish a completed build, treat publication
 as a downstream distribution step outside the Context Route. Use only an
 explicitly installed distribution tool and its documented complete-output

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.