@c4a/context-cli 0.6.18 → 0.7.0

package/indexers/release-manifest.json

@@ -0,0 +1,208 @@
+{
+  "protocol": "context.indexer.cli-release-manifest/v1",
+  "package": "@c4a/context-cli",
+  "version": "0.7.0",
+  "issuer": "context4ai/context",
+  "bundles": [
+    {
+      "skill": "context-code-indexer",
+      "version": "1.0.0",
+      "distribution": {
+        "kind": "cli-bundled",
+        "locator": "cli-bundled://context/context-code-indexer"
+      },
+      "integrity": "sha256:3719500f30c5920037dc2421b1ade80befdcfba0ea0eb0e38cccf13ed1ad04b5",
+      "manifest_digest": "sha256:eee1260214de0cca784c9984158a69c1d687ba6912edff006b896a1aa536e2d4",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "digest": "sha256:b0404c969051ad490e4ccfa49b44d99780bf4d052a5a31b2b252ec0463d49b78"
+        },
+        {
+          "path": "context-indexer.yaml",
+          "digest": "sha256:eee1260214de0cca784c9984158a69c1d687ba6912edff006b896a1aa536e2d4"
+        },
+        {
+          "path": "references/composers/contracts-and-chains.md",
+          "digest": "sha256:b462e6b140c99a05c69ab0b60f64d377e40a12ba63019e4ffcef43ea4680fce2"
+        },
+        {
+          "path": "references/composers/cross-module-chain.md",
+          "digest": "sha256:a1ef4ee3a6aa248f721620b02be89b714a9fc1ff73d1ced51a9d22aeebf9e3cf"
+        },
+        {
+          "path": "references/composers/development-and-delivery.md",
+          "digest": "sha256:494a2db4ca16cfb5061e4185feea4ebcbad243811bdfe52e4b8c699a60cff015"
+        },
+        {
+          "path": "references/composers/event-flow.md",
+          "digest": "sha256:597a6ace833b2c1eec5cd753ac6f841b93e655a2a350812cbad93e8188286446"
+        },
+        {
+          "path": "references/composers/examples-and-documentation.md",
+          "digest": "sha256:3d3e89f512d3c163f23abe6b6766b92f3835a6d194c7c4c9292083a05d124e93"
+        },
+        {
+          "path": "references/composers/persistence-boundary.md",
+          "digest": "sha256:50124b8644f9fd68db5b95a5d7885d3d4433fe00b53539c6627173490fdd718b"
+        },
+        {
+          "path": "references/composers/protocol-boundary.md",
+          "digest": "sha256:4658e69dd1fa69920e6dcb383125f096cea8f772ea8103a38ce12d57c40ec7ae"
+        },
+        {
+          "path": "references/composers/public-contract.md",
+          "digest": "sha256:aab601aed34492ec33e662471842a64512aa3fa1433cb8450fb6858e3895a89d"
+        },
+        {
+          "path": "references/indexer.md",
+          "digest": "sha256:583997d7cc096ebccc3981f733608ccb553a3c6964747f95fd4d356ff08d758b"
+        },
+        {
+          "path": "references/metrics.md",
+          "digest": "sha256:38de0a9ef59b70e252d446b55c87796a360047571ac725baed1a7afa2379cd07"
+        },
+        {
+          "path": "templates/adapter-integration.md",
+          "digest": "sha256:f6eb18e62cea2edaf08d5babf10dd9c8c4cbbcde9d5002ad35b89a4a24b2fc93"
+        },
+        {
+          "path": "templates/api-service.md",
+          "digest": "sha256:55b1f42541a001d3a86b815e14b03ac6e5dfab8480e5e133c8425c946e7e96dc"
+        },
+        {
+          "path": "templates/background-runtime.md",
+          "digest": "sha256:ab79645c0e32921a69dc1e82cc98da030958579ce3b525c162077d040fd7a40d"
+        },
+        {
+          "path": "templates/cli-tool.md",
+          "digest": "sha256:4de15964d515a28c8f6e56786f1b287a5132159a29f5f0fae1022aaaa84c0313"
+        },
+        {
+          "path": "templates/component-library.md",
+          "digest": "sha256:aa21a8a0395c95e402ff58ae036c64a1cc9e6d223b676cfde50ac0556a4fb2de"
+        },
+        {
+          "path": "templates/contract-source.md",
+          "digest": "sha256:0380b7393cd60eec1d5430787d3406bf7e43ba97f1d87c438432ef95e4b5114b"
+        },
+        {
+          "path": "templates/data-sync-reconciliation.md",
+          "digest": "sha256:eecacb3869edad0e4f31f24a6d9ed45b31da99cde90adbbd6e39b8428e06b3c6"
+        },
+        {
+          "path": "templates/derived-generated-source.md",
+          "digest": "sha256:da01d6c8306b1f2e9d12d1b63b66b5ed62c062ec22869bf2a9e61527d7ef98b1"
+        },
+        {
+          "path": "templates/domain-service.md",
+          "digest": "sha256:a249498adf6b6a3a88997946964c7ff11448e18a3efaba2f6feccbb7bac314d5"
+        },
+        {
+          "path": "templates/event-consumer.md",
+          "digest": "sha256:9884cda5e5e64bf5a96745b793cfc7eff093827119f775b8aed824a6317a2f3c"
+        },
+        {
+          "path": "templates/gateway-facade.md",
+          "digest": "sha256:0fbfb5195dbb84f1833aee21947c0605a0a8d85b93d2fcde577dbf85cb5b92b1"
+        },
+        {
+          "path": "templates/monorepo-container.md",
+          "digest": "sha256:8bfc79d942a6c7c3ccc5d8cb4ec12e2ce725bd37094d8be39133e93cf0c75d19"
+        },
+        {
+          "path": "templates/plugin-extension.md",
+          "digest": "sha256:bd8cd97644d6aad1900e82bf0993ed32464781203c295af8e84fca5d106e4d37"
+        },
+        {
+          "path": "templates/sdk-library.md",
+          "digest": "sha256:a46a8d057ba422dfb0265b9942a96fda8fa2ffe735952e545bae6480901270d7"
+        },
+        {
+          "path": "templates/storage-repository.md",
+          "digest": "sha256:800bce6f6eac3b2a672ec839c4313d85a78a2819e7aa30681ba38634e786103e"
+        },
+        {
+          "path": "templates/web-application.md",
+          "digest": "sha256:c8d734caec97b1a42f12fcf4cc029a4dc49cc1ba7edfbb5b7fdb9293cf40aa26"
+        },
+        {
+          "path": "tests/fixtures/chapters.json",
+          "digest": "sha256:0af13cfd8bc39dd43caf2f23fc92c84eb7ce5905bf683a5d7f6f6bd1ebc3ccf2"
+        },
+        {
+          "path": "tests/fixtures/composers.json",
+          "digest": "sha256:43dee25ee924eb2f6096fdf166e83d2e5695f25b7dda8ee625aaefdd831b68f3"
+        },
+        {
+          "path": "tests/fixtures/profiles.json",
+          "digest": "sha256:4dca7f2504b95c67d647c5678a1eeb4f629772b2674b5b53b49f1e382d33ba01"
+        },
+        {
+          "path": "tests/fixtures/scenarios.json",
+          "digest": "sha256:7f12c65cce5469f7c84b06c973bdc8179b244ee845521ca5978c5b87d6255ddd"
+        }
+      ]
+    },
+    {
+      "skill": "context-markdown-indexer",
+      "version": "1.0.0",
+      "distribution": {
+        "kind": "cli-bundled",
+        "locator": "cli-bundled://context/context-markdown-indexer"
+      },
+      "integrity": "sha256:308c84e7ca62c87614eb8318939f7fee8ccd859907d63effd10b33247708bb48",
+      "manifest_digest": "sha256:ef7b4649f39d1ac8d38413770012c73c9a54d63d120c9d2a5bbf7c68ff8c01bc",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "digest": "sha256:1c6c261541fed808ff791b48324cb490f58dd1234deb09c7a43661564d6045b3"
+        },
+        {
+          "path": "context-indexer.yaml",
+          "digest": "sha256:ef7b4649f39d1ac8d38413770012c73c9a54d63d120c9d2a5bbf7c68ff8c01bc"
+        },
+        {
+          "path": "references/classification.md",
+          "digest": "sha256:c09cf236f730eea1f3a3959ffd099cf62561e84d5c255ed047c4ee4ccad84f3c"
+        },
+        {
+          "path": "references/editorial-policy.md",
+          "digest": "sha256:c34d1ecc0d18d7cb0226993053523e4a7e5e6553b77e7b47d0b4264c8c78b23b"
+        },
+        {
+          "path": "references/indexer.md",
+          "digest": "sha256:ed506c14b13a2855c47a7503df78dd5a9abbd55d3663584369b85f4cbba14c95"
+        },
+        {
+          "path": "references/semantic-planning.md",
+          "digest": "sha256:fd0b7cfe28c44a7cc2bfcf4fe575c8df595a9931fae06ece1d3a48f21c9ea2b2"
+        },
+        {
+          "path": "references/structure-and-artifacts.md",
+          "digest": "sha256:c8a31e5ed4cad1369f3647e4eff796509db5a3609183ad7d63c215f0da9ab4c6"
+        },
+        {
+          "path": "tests/fixtures/anonymous.json",
+          "digest": "sha256:38c4cfe7c39f3d5358b265b39b2799219019ef1c94cc9961ef6a7b09250cbebe"
+        },
+        {
+          "path": "tests/fixtures/editorial.json",
+          "digest": "sha256:e62699eef46733b0b5ec52db594b88de7c45eb18e2bc22957f9e32d612182d79"
+        },
+        {
+          "path": "tests/fixtures/migration-equivalence.json",
+          "digest": "sha256:51f3834f5a90482d9e4aa92fad874a0661085c121e8cc78efc313a1c8b362740"
+        },
+        {
+          "path": "tests/fixtures/profiles.json",
+          "digest": "sha256:c43fc25f7f00a662a1fd144623041be16a149778eb88064b497aef1690f33850"
+        },
+        {
+          "path": "tests/fixtures/routing.json",
+          "digest": "sha256:85675d965ac67289672145e80f6cb54922eeddb5cc4b6d80b9e5ce0e5dcd8947"
+        }
+      ]
+    }
+  ]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.6.18",
+  "version": "0.7.0",
   "type": "module",
   "description": "Local runtime and Agent integration for traceable knowledge production",
   "license": "MIT",
@@ -23,8 +23,8 @@
     "context": "cli.js"
   },
   "dependencies": {
-    "@c4a/agent-graph": "0.2.6",
-    "@c4a/context": "0.6.18",
+    "@c4a/agent-graph": "0.2.7",
+    "@c4a/context": "0.7.0",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",
     "handlebars": "^4.7.8",
@@ -40,7 +40,8 @@
     "typescript": "^5.5.4",
     "unified": "^11.0.5",
     "web-tree-sitter": "^0.20.8",
-    "yaml": "^2.5.1"
+    "yaml": "^2.5.1",
+    "zod": "^3.23.8"
   },
   "main": "./cli.js",
   "scripts": {

package/plugins/README.md

@@ -2,112 +2,20 @@
 
 [简体中文](./README_CN.md)
 
-<p align="center"><img src="./assets/logo.svg" alt="Context" width="180"/></p>
-
-This plugin is the conversational entry to the Context knowledge production
-workflow. It lets users describe a knowledge goal to an Agent, then connects
-that conversation to the local Context runtime, current workspace facts, and
-Route-selected procedures.
-
-The plugin deliberately exposes one thin public entry instead of separate
-commands for initialization, source capture, review, and build. The detailed
-workflow stays in the runtime's Provider bundle, where it can be selected by
-current facts, validated, tested, and updated without turning the entry into a
-large prompt.
-
-## User experience
-
-After the integration is installed and the Agent host is refreshed, invoke the
-Context entry and describe the desired knowledge:
-
-```text
-/c4a:context Build a searchable Agent knowledge package from our architecture
-documents and this repository. Preserve source evidence and show me the final
-structure before approval.
-```
-
-The same entry can initialize a requested workspace, locate an existing one,
-or continue its current production round. The Agent explains user decisions in
-the conversation and uses the runtime for mechanical state transitions. Users
-do not need to select low-level lifecycle commands themselves.
-
-## Install
-
-The plugin is bundled with the Context runtime:
-
-```bash
-npm install -g @c4a/context-cli@latest
-context plugin install
-```
-
-For a source checkout, build first and install the development projection:
-
-```bash
-bun run --filter @c4a/context-cli build
-context plugin install --dev
-```
-
-Use `context plugin install --dry-run` to inspect the host projections and
-`context plugin status` to diagnose an installation. Refresh the Agent host
-after changing or reinstalling the plugin.
-
-## Entry contract
-
-The maintained source is [`commands/context.md`](./commands/context.md). Its
-bootstrap flow is:
-
-1. run the read-only `context entry --language <language> --format json`;
-2. execute only its returned `next_action.command`;
-3. after workspace setup, treat `workflow.current` as the current-step
-   authority;
-4. read every required Route resource completely;
-5. execute only the selected action or configuration change;
-6. evaluate the workspace again.
-
-The entry does not infer workspace state from surrounding files. Initialization
-is executed only when explicitly requested or confirmed; entering and
-evaluating an existing workspace is read-only. There is no `context continue`
-primitive and no stage-specific public Skill.
-
-## Progressive workflow context
-
-Procedures, dialogue, diagnostics, schemas, source bodies, and generated views
-are addressable workflow resources. Static resources use content digests;
-dynamic views are tied to the workflow revision that selected them. Read
-receipts can keep unchanged resources current within one conversation, but a
-receipt never proves that an external action completed.
-
-At a human Gate, inspection and resolution resources remain phase-local. The
-Agent loads inspection material before a decision and resolution material only
-after confirmation. This keeps the ordinary review path available without
-preloading every possible decision surface.
-
-## Fully managed conversations
-
-Fully managed operation is used only after the user explicitly authorizes it in
-the current conversation. The Agent then starts with:
-
-```bash
-context run --managed --until blocked-or-complete --format json
-```
-
-The loop executes consecutive deterministic actions and Route-delegated Gates,
-re-evaluating after every action. It stops before semantic reading, project
-configuration, unresolved permission, diagnostic repair, or a non-unique plan.
-Managed authority is never persisted or reused in another conversation.
-
-## Boundaries
-
-- The plugin does not call an LLM; it is consumed by the host Agent.
-- All workspace lifecycle writes go through Route-selected Context actions.
-- It does not silently clone, fetch, checkout, install, build, test, or read
-  external content without the required authority.
-- It does not duplicate workflow facts or lifecycle routing in the prompt.
-- It keeps CLI tokens, paths, ids, flags, and `source_ref` values unchanged,
-  while explaining decisions in the user's current conversation language.
-
-## Maintainer note
-
-`plugin/` is the only hand-maintained integration source. The build projects it
-to Claude commands, Codex Skills, Cursor commands, and a Skill-only layout under
-`dist/plugins`. Do not edit generated projections directly.
+This directory is the only human-maintained source for the Context Agent
+integration. It contains the single Context entry Skill, the Code and Markdown
+Indexer Provider Skills, host manifest templates, and shared assets.
+
+Run `bun run --filter @c4a/context-cli build:plugin` to regenerate the npm
+projection and the committed `repo-install/` tree. Do not edit generated files
+under `repo-install/` or `packages/context-cli/dist/plugins/`.
+
+`repo-install/{claude,codex,cursor}/` contains host-specific plugin roots with
+only the public Context entry; `repo-install/skills/` is the portable Skill
+projection. In the same install, `context plugin install` projects Providers
+to the Codex/Cursor shared `~/.agents/skills` directory and Claude's
+`~/.claude/skills`, so Provider names do not inherit a plugin namespace.
+
+The conversational entry delegates workspace state and lifecycle authority to
+the local `context` CLI. Indexer Skills are activated only through the verified
+Context workflow and Indexer Provider lifecycle.

package/plugins/README_CN.md

@@ -2,95 +2,17 @@
 
 [English](./README.md)
 
-<p align="center"><img src="./assets/logo.svg" alt="Context" width="180"/></p>
+本目录是 Context Agent 接入唯一的人工维护真源，包含单一 Context 入口 Skill、
+Code/Markdown Indexer Provider Skills、各宿主 manifest 模板和共享资产。
 
-这个插件是 Context 知识生产工作流的对话入口。用户向 Agent 说明知识目标，插件再
-把对话连接到本地 Context 运行时、当前工作区事实和 Route 选择的操作资源。
+运行 `bun run --filter @c4a/context-cli build:plugin` 可重新生成 npm 投影及提交到
+仓库的 `repo-install/`。不要直接编辑 `repo-install/` 或
+`packages/context-cli/dist/plugins/` 下的生成文件。
 
-插件有意只暴露一个精简入口，不为初始化、来源采集、审核和构建分别提供公开命令。
-详细工作流保存在运行时的 Provider bundle 中，可以依据当前事实按需选择、校验、
-测试和升级，而不会让入口 Prompt 越来越长。
+`repo-install/{claude,codex,cursor}/` 分别是只包含 Context 主入口的宿主插件根；
+`repo-install/skills/` 是可移植 Skill 投影。`context plugin install` 在同一次安装中
+把 Provider 投影到 Codex/Cursor 共用的 `~/.agents/skills` 与 Claude 的
+`~/.claude/skills`，因此 Provider 不获得插件命名空间。
 
-## 用户体验
-
-安装接入并刷新 Agent 宿主后，调用 Context 入口并说明期望知识：
-
-```text
-/c4a:context 请把架构文档和当前仓库整理成可搜索的 Agent 知识包，保留来源证据，
-最终结构批准前先让我确认。
-```
-
-同一个入口可以初始化用户请求的工作区、定位已有工作区，或继续当前知识生产轮次。
-Agent 在对话中解释用户决策，并使用运行时完成机械状态变更；用户不需要自行选择
-底层生命周期命令。
-
-## 安装
-
-插件随 Context 运行时一起发布：
-
-```bash
-npm install -g @c4a/context-cli@latest
-context plugin install
-```
-
-从源码开发时，先构建再安装开发投影：
-
-```bash
-bun run --filter @c4a/context-cli build
-context plugin install --dev
-```
-
-`context plugin install --dry-run` 可以预览宿主投影，`context plugin status`
-用于诊断安装。修改或重装插件后需要刷新 Agent 宿主。
-
-## 入口契约
-
-人工维护的源文件是 [`commands/context.md`](./commands/context.md)，启动流程为：
-
-1. 运行只读的 `context entry --language <language> --format json`；
-2. 只执行它返回的 `next_action.command`；
-3. 工作区就绪后，将 `workflow.current` 视为当前步骤权威；
-4. 完整读取当前 Route 的所有必需资源；
-5. 只执行选中的动作或配置修改；
-6. 再次求值工作区。
-
-入口不会根据周边文件自行推断工作区状态。只有用户明确请求或确认时才执行初始化；
-进入或求值已有工作区是只读行为。不存在 `context continue` primitive，也没有阶段
-专属的公开 Skill。
-
-## 按需加载工作流上下文
-
-操作说明、对话、诊断、Schema、来源正文和生成 View 都是可寻址的工作流资源。
-静态资源使用内容 digest，动态 View 绑定选择它的 workflow revision。读取回执可以
-在同一对话中复用未变化资源，但不能证明外部动作已经完成。
-
-人工 Gate 的检查和决议资源保持阶段隔离：Agent 在决定前加载 inspection 内容，
-用户确认后才加载 resolution 内容。这样既保留普通审核能力，也不会预加载所有可能
-的决策界面。
-
-## 全托管对话
-
-只有用户在当前对话明确授权后，才使用全托管模式。Agent 从以下命令开始：
-
-```bash
-context run --managed --until blocked-or-complete --format json
-```
-
-循环会执行连续的确定性动作和 Route-delegated Gate，并在每个动作后重新求值。遇到
-语义阅读、项目配置、未解决权限、诊断修复或非唯一计划时停止。全托管权限不会被
-持久化，也不能在另一场对话复用。
-
-## 边界
-
-- 插件本身不调用 LLM，而是由宿主 Agent 消费。
-- 所有工作区生命周期写入都通过 Route 选择的 Context Action 完成。
-- 不会在缺少相应授权时静默 clone、fetch、checkout、install、build、test 或
-  读取外部内容。
-- 不在 Prompt 中复制工作流事实或生命周期路由。
-- CLI token、路径、id、flag 和 `source_ref` 保持原样；面向用户的解释使用当前
-  对话语言。
-
-## 维护说明
-
-`plugin/` 是唯一人工维护的接入源。构建会将它投影为 `dist/plugins` 下的 Claude
-commands、Codex Skills、Cursor commands 和纯 Skill 目录。不要直接编辑生成投影。
+对话入口把工作区状态和 workflow 生命周期权威交给本地 `context` CLI；Indexer
+Skills 只能通过完成校验的 Context Indexer Provider 生命周期激活。

package/plugins/VERSION

@@ -1 +1 @@
-0.6.18
+0.7.0

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,16 +1,8 @@
 {
   "name": "c4a",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
-  "version": "0.6.18",
-  "author": {
-    "name": "c4a"
-  },
+  "version": "0.7.0",
+  "author": { "name": "c4a" },
   "license": "MIT",
-  "keywords": [
-    "context",
-    "knowledge-base",
-    "wiki",
-    "claude-plugin",
-    "c4a"
-  ]
+  "keywords": ["context", "knowledge-base", "wiki", "claude-plugin", "c4a"]
 }

package/plugins/claude/CLAUDE.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/claude/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/claude/commands/context.md

@@ -1,5 +1,5 @@
 ---
-description: "Build or continue structured, traceable Agent knowledge from documents and code."
+description: "Build or continue structured, traceable Agent knowledge from documents and code. Use the local `context` CLI for workspace writes."
 argument-hint: "[project-dir or user intent]"
 allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
 ---
@@ -26,6 +26,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
@@ -91,12 +103,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
@@ -123,6 +137,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:
@@ -168,6 +265,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