@c4a/context-cli 0.7.1 → 0.7.5

package/indexers/release-manifest.json

@@ -1,26 +1,26 @@
 {
   "protocol": "context.indexer.cli-release-manifest/v1",
   "package": "@c4a/context-cli",
-  "version": "0.7.1",
+  "version": "0.7.5",
   "issuer": "context4ai/context",
   "bundles": [
     {
       "skill": "context-code-indexer",
-      "version": "1.0.0",
+      "version": "1.1.2",
       "distribution": {
         "kind": "cli-bundled",
         "locator": "cli-bundled://context/context-code-indexer"
       },
-      "integrity": "sha256:3719500f30c5920037dc2421b1ade80befdcfba0ea0eb0e38cccf13ed1ad04b5",
-      "manifest_digest": "sha256:eee1260214de0cca784c9984158a69c1d687ba6912edff006b896a1aa536e2d4",
+      "integrity": "sha256:1ed6831f383cee2399b3c49b01378010ed40c65dce554cf50fc0a5d8ecac6a04",
+      "manifest_digest": "sha256:17f70fd4018068892a8067a3008855d2914f16728a90134328b5da4754429c11",
       "files": [
         {
           "path": "SKILL.md",
-          "digest": "sha256:b0404c969051ad490e4ccfa49b44d99780bf4d052a5a31b2b252ec0463d49b78"
+          "digest": "sha256:d08738034dc6ed4fab857184ea92927a207a4c712be7626ae58ce3a0be1499fd"
         },
         {
           "path": "context-indexer.yaml",
-          "digest": "sha256:eee1260214de0cca784c9984158a69c1d687ba6912edff006b896a1aa536e2d4"
+          "digest": "sha256:17f70fd4018068892a8067a3008855d2914f16728a90134328b5da4754429c11"
         },
         {
           "path": "references/composers/contracts-and-chains.md",
@@ -56,15 +56,15 @@
         },
         {
           "path": "references/indexer.md",
-          "digest": "sha256:583997d7cc096ebccc3981f733608ccb553a3c6964747f95fd4d356ff08d758b"
+          "digest": "sha256:e5b13a60a58b49461ed49cf8abac0f24aa4d19a2df42181d7b045a9984d5aab0"
         },
         {
           "path": "references/metrics.md",
-          "digest": "sha256:38de0a9ef59b70e252d446b55c87796a360047571ac725baed1a7afa2379cd07"
+          "digest": "sha256:4f32874ad81695b412f830f76c4f8bc7663a37e4d0c652fe24efebcffe7698bb"
         },
         {
           "path": "templates/adapter-integration.md",
-          "digest": "sha256:f6eb18e62cea2edaf08d5babf10dd9c8c4cbbcde9d5002ad35b89a4a24b2fc93"
+          "digest": "sha256:be6aa650aad7f70f4bf924c64f4bc73fa28314d512245d61d159ffde6c29a91d"
         },
         {
           "path": "templates/api-service.md",
@@ -80,7 +80,7 @@
         },
         {
           "path": "templates/component-library.md",
-          "digest": "sha256:aa21a8a0395c95e402ff58ae036c64a1cc9e6d223b676cfde50ac0556a4fb2de"
+          "digest": "sha256:53d53824b22c339ee2405d66fb406ed908930f5ced095e6bad69c97650a3afd5"
         },
         {
           "path": "templates/contract-source.md",
@@ -104,7 +104,7 @@
         },
         {
           "path": "templates/gateway-facade.md",
-          "digest": "sha256:0fbfb5195dbb84f1833aee21947c0605a0a8d85b93d2fcde577dbf85cb5b92b1"
+          "digest": "sha256:6b5e7ea03ff3acf4d88879f835ff7c2c470fe6a0f2cb3641d46406b5fb4da544"
         },
         {
           "path": "templates/monorepo-container.md",
@@ -146,21 +146,21 @@
     },
     {
       "skill": "context-markdown-indexer",
-      "version": "1.0.0",
+      "version": "1.1.1",
       "distribution": {
         "kind": "cli-bundled",
         "locator": "cli-bundled://context/context-markdown-indexer"
       },
-      "integrity": "sha256:308c84e7ca62c87614eb8318939f7fee8ccd859907d63effd10b33247708bb48",
-      "manifest_digest": "sha256:ef7b4649f39d1ac8d38413770012c73c9a54d63d120c9d2a5bbf7c68ff8c01bc",
+      "integrity": "sha256:082664b409f05861cf69c77f45de0cf9c3269522c949b1c1f5fb25d2e78d59b9",
+      "manifest_digest": "sha256:6ed1f921e340d1ba8876dec57da9a41308cb72bd12c7aacf24acd93c7dd59439",
       "files": [
         {
           "path": "SKILL.md",
-          "digest": "sha256:1c6c261541fed808ff791b48324cb490f58dd1234deb09c7a43661564d6045b3"
+          "digest": "sha256:ed1684c9b2659ec5f42a3785803f6bf3fec3061cc5bc6f4ea69cc3b0a5a42b6e"
         },
         {
           "path": "context-indexer.yaml",
-          "digest": "sha256:ef7b4649f39d1ac8d38413770012c73c9a54d63d120c9d2a5bbf7c68ff8c01bc"
+          "digest": "sha256:6ed1f921e340d1ba8876dec57da9a41308cb72bd12c7aacf24acd93c7dd59439"
         },
         {
           "path": "references/classification.md",
@@ -172,19 +172,19 @@
         },
         {
           "path": "references/indexer.md",
-          "digest": "sha256:ed506c14b13a2855c47a7503df78dd5a9abbd55d3663584369b85f4cbba14c95"
+          "digest": "sha256:385700d8c016759527ef9b2a140b17c81fa136031e24f1ce56ff1f3c7fd73b5d"
         },
         {
           "path": "references/semantic-planning.md",
-          "digest": "sha256:fd0b7cfe28c44a7cc2bfcf4fe575c8df595a9931fae06ece1d3a48f21c9ea2b2"
+          "digest": "sha256:0789c470aeb59797714ecc1349092cfd8aaf818fcf72b72208318ab15f73eee2"
         },
         {
           "path": "references/structure-and-artifacts.md",
-          "digest": "sha256:c8a31e5ed4cad1369f3647e4eff796509db5a3609183ad7d63c215f0da9ab4c6"
+          "digest": "sha256:275078306c2dc03d2fafea2d61e1df9c7cb1107bdff9e7d223044fe4e551e72b"
         },
         {
           "path": "tests/fixtures/anonymous.json",
-          "digest": "sha256:38c4cfe7c39f3d5358b265b39b2799219019ef1c94cc9961ef6a7b09250cbebe"
+          "digest": "sha256:4c1c43e41c9e24178ced63fede6fa5d0b04897e24cfc7cb7b54aaa314762bb3d"
         },
         {
           "path": "tests/fixtures/editorial.json",
@@ -196,11 +196,11 @@
         },
         {
           "path": "tests/fixtures/profiles.json",
-          "digest": "sha256:c43fc25f7f00a662a1fd144623041be16a149778eb88064b497aef1690f33850"
+          "digest": "sha256:55fe69e5518d158c4a36fcf344eb98de85304c0e1452c95049819addedc6429f"
         },
         {
           "path": "tests/fixtures/routing.json",
-          "digest": "sha256:85675d965ac67289672145e80f6cb54922eeddb5cc4b6d80b9e5ce0e5dcd8947"
+          "digest": "sha256:c879d226a2f20f8e68c83fe60fa81cb3ff88465b6c666b02bd835b68280981a0"
         }
       ]
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.7.1",
+  "version": "0.7.5",
   "type": "module",
   "description": "Local runtime and Agent integration for traceable knowledge production",
   "license": "MIT",
@@ -24,7 +24,17 @@
   },
   "dependencies": {
     "@c4a/agent-graph": "0.3.0",
-    "@c4a/context": "0.7.1",
+    "@c4a/context": "0.7.5",
+    "@c4a/extract": "0.7.5",
+    "@c4a/extract-contract": "0.7.5",
+    "@c4a/extract-go": "0.7.5",
+    "@c4a/extract-mdx": "0.7.5",
+    "@c4a/extract-proto": "0.7.5",
+    "@c4a/extract-rush": "0.7.5",
+    "@c4a/extract-sql": "0.7.5",
+    "@c4a/extract-style": "0.7.5",
+    "@c4a/extract-thrift": "0.7.5",
+    "@c4a/extract-ts": "0.7.5",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",
     "handlebars": "^4.7.8",

package/plugins/VERSION

@@ -1 +1 @@
-0.7.1
+0.7.5

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

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

package/plugins/claude/commands/context.md

@@ -41,11 +41,8 @@ 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
-requested that initialization choice. New workspaces enable conservative
-document compilation optimization by default. Pass `--no-optimize-docs` only
-when the user explicitly asks to disable it during initialization. Pass
-`--managed` only after the user explicitly authorizes fully managed operation
-in this conversation.
+requested that initialization choice. Pass `--managed` only after the user
+explicitly authorizes fully managed operation in this conversation.
 
 If the `context` process itself cannot start because the command is missing
 (`ENOENT`, or shell exit 127 explicitly identifying `context` as the missing
@@ -74,23 +71,18 @@ Execute only `next_action.command` returned by `context entry`:
   init`, enter the project root, read the generated `AGENTS.md`, and run this
   entry again.
 
-If the user explicitly asks to correct or revise an existing approved or built
-knowledge page, first let `context entry` relocate into the existing workspace
-and evaluate its current Route once. Resolve a blocking workspace diagnostic,
-evidence-maintenance action, or already-pending Review batch first; these may
-change the approved baseline. Before continuing unrelated capture, extraction,
-package configuration, or build work, start the correction with:
+If the user asks to correct a current Candidate before approval, first let
+`context entry` relocate into the workspace and evaluate its current Route.
+Start the correction with:
 
 ```bash
-context revise "<the user's page title, approved path, ViewRef, or wording>" --format json
+context revise "<candidate title, path, or id>" --instruction "<requested correction>" --format json
 ```
 
-When the target is unique, run the returned status command and follow
-`route.document-revision.requested`. When candidates are returned, select one
-only if the conversation identifies it uniquely; otherwise ask which page the
-user means. Never edit the approved base page or `dist/` for this operation.
-After the Route validates the revision, continue normally: Context will offer
-the package build when the correction makes its output stale.
+When the target is unique, Context invalidates only its derived outputs and
+reopens the owning Author workset. Run the returned status command and follow
+the current Route. If the target is ambiguous, ask which Candidate the user
+means. Never edit `knowledge/`, `dist/`, or create a side-channel revision page.
 
 ### Conversation modes
 
@@ -102,24 +94,6 @@ before workflow evaluation. Debugging records traces below
 `.tmp/context-runtime/debug/` but does not grant workflow authority or provide
 source evidence.
 
-Document optimization is enabled by default for newly initialized workspaces.
-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
-user explicitly changes that preference. If initialization is required and the
-user opts out, pass `--no-optimize-docs` through `context entry`; otherwise let
-the default initialization command enable it.
-Follow the resulting Route instead of editing approved knowledge or package
-output by hand.
-
 For explicitly authorized fully managed operation, use:
 
 ```bash
@@ -139,13 +113,13 @@ 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.
+and page shape without producing a total score. Blocking mechanical failures
+reopen the owning Author or Composer workset; advisory metrics remain warnings
+and do not create a retry ledger or override 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
+### Select Indexer Providers
 
 For `indexer-provider-required`, `indexer-provider-unavailable`,
 `indexer-customization-required`, `indexer-customization-invalid`, or
@@ -156,69 +130,40 @@ 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.
+When the current Route starts a new Code or Markdown indexing task, its
+`configure-indexer-providers` Action input already contains the exact applied
+requirements and CLI-bundled Provider catalog. Select applicable Providers from
+the Skills already visible to the Host and that supplied catalog. Do not add a
+catalog command, installation preflight, discovery report, or discovery-only
+confirmation to the normal workflow. The main entry being visible is not proof
+that every Provider is available; the CLI checks the selected distribution
+when it is used and returns any missing/version-conflict recovery.
+
+Use the supplied CLI-bundled identity for a selected shipped Provider, including
+when the same Skill/version is also visible as an installed projection. Do not
+resolve that copy through the Host or re-read its installed metadata. For a
+relevant external Skill, read only the exact Host-exposed frontmatter and
+sibling `context-indexer.yaml` needed for selection; do not guess a version or
+scan caches. Different versions remain distinct. Read Provider guidance only
+when selected. Discovery is not a durable workspace artifact.
+
+Return only `stage: provider-selection`, the non-CLI
+`host_visible_skills`, and the selected semantic `indexers` through the exact
+`context action complete-current` command returned by the Route. The CLI owns
+construction of the full registry payload, fallback/conflict checks, static
+validation, Provider resolution and staging, final validation, and atomic
+application of `src/indexers.yaml`. Do not call their low-level commands as a
+second production workflow.
+
+If a selected external Provider needs Host resolution, the next current Route
+contains one `context.resolve-indexer-provider/v1` Host Action and its exact
+request. Invoke that Host Action once, then submit
+`stage: provider-resolution` with the returned Host result through the Route's
+`complete-current` command. If the Bundle carries a non-allowlisted program,
+the following current Route presents the existing program-execution Gate; wait
+for its user/session-authority decision and submit that decision through
+`complete-current`. A recovered `provider-finalization` Route consumes
+only its fixed Action input; it must not resolve or install the Provider again.
 
 ### Follow the current Route
 
@@ -226,8 +171,12 @@ Treat `workflow.current` as the current-step authority:
 
 1. Read every `resources.required` item whose `read_state` is `read-required`.
    Read a returned `path` completely, or execute a returned resource `command`
-   and read its complete output file. Materializing a resource is not reading
-   it. Keep the merged receipts only in this conversation and submit them with
+   and read its complete output file. For a current Indexer Partition, Author,
+   Composer or structure-review Route, read the materialized files and then use
+   the Route's immediate completion command; do not create or submit a read
+   receipt. Other workflow resources may still require the returned receipt
+   command. Materializing a resource is not reading it. Keep those receipts only
+   in this conversation and submit them with
    the exact returned `context status --resource-receipts @<file>` command. Use
    `after_read_receipts` only after the full resource has been read. The exact
    `resources.after_read.command` already returns the re-evaluated

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

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.7.1",
+  "version": "0.7.5",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": { "name": "c4a" },
   "homepage": "https://github.com/context4ai/c4a",
@@ -10,7 +10,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.1",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.5",
     "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",

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

@@ -42,11 +42,8 @@ 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
-requested that initialization choice. New workspaces enable conservative
-document compilation optimization by default. Pass `--no-optimize-docs` only
-when the user explicitly asks to disable it during initialization. Pass
-`--managed` only after the user explicitly authorizes fully managed operation
-in this conversation.
+requested that initialization choice. Pass `--managed` only after the user
+explicitly authorizes fully managed operation in this conversation.
 
 If the `context` process itself cannot start because the command is missing
 (`ENOENT`, or shell exit 127 explicitly identifying `context` as the missing
@@ -75,23 +72,18 @@ Execute only `next_action.command` returned by `context entry`:
   init`, enter the project root, read the generated `AGENTS.md`, and run this
   entry again.
 
-If the user explicitly asks to correct or revise an existing approved or built
-knowledge page, first let `context entry` relocate into the existing workspace
-and evaluate its current Route once. Resolve a blocking workspace diagnostic,
-evidence-maintenance action, or already-pending Review batch first; these may
-change the approved baseline. Before continuing unrelated capture, extraction,
-package configuration, or build work, start the correction with:
+If the user asks to correct a current Candidate before approval, first let
+`context entry` relocate into the workspace and evaluate its current Route.
+Start the correction with:
 
 ```bash
-context revise "<the user's page title, approved path, ViewRef, or wording>" --format json
+context revise "<candidate title, path, or id>" --instruction "<requested correction>" --format json
 ```
 
-When the target is unique, run the returned status command and follow
-`route.document-revision.requested`. When candidates are returned, select one
-only if the conversation identifies it uniquely; otherwise ask which page the
-user means. Never edit the approved base page or `dist/` for this operation.
-After the Route validates the revision, continue normally: Context will offer
-the package build when the correction makes its output stale.
+When the target is unique, Context invalidates only its derived outputs and
+reopens the owning Author workset. Run the returned status command and follow
+the current Route. If the target is ambiguous, ask which Candidate the user
+means. Never edit `knowledge/`, `dist/`, or create a side-channel revision page.
 
 ### Conversation modes
 
@@ -103,24 +95,6 @@ before workflow evaluation. Debugging records traces below
 `.tmp/context-runtime/debug/` but does not grant workflow authority or provide
 source evidence.
 
-Document optimization is enabled by default for newly initialized workspaces.
-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
-user explicitly changes that preference. If initialization is required and the
-user opts out, pass `--no-optimize-docs` through `context entry`; otherwise let
-the default initialization command enable it.
-Follow the resulting Route instead of editing approved knowledge or package
-output by hand.
-
 For explicitly authorized fully managed operation, use:
 
 ```bash
@@ -140,13 +114,13 @@ 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.
+and page shape without producing a total score. Blocking mechanical failures
+reopen the owning Author or Composer workset; advisory metrics remain warnings
+and do not create a retry ledger or override 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
+### Select Indexer Providers
 
 For `indexer-provider-required`, `indexer-provider-unavailable`,
 `indexer-customization-required`, `indexer-customization-invalid`, or
@@ -157,69 +131,40 @@ 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.
+When the current Route starts a new Code or Markdown indexing task, its
+`configure-indexer-providers` Action input already contains the exact applied
+requirements and CLI-bundled Provider catalog. Select applicable Providers from
+the Skills already visible to the Host and that supplied catalog. Do not add a
+catalog command, installation preflight, discovery report, or discovery-only
+confirmation to the normal workflow. The main entry being visible is not proof
+that every Provider is available; the CLI checks the selected distribution
+when it is used and returns any missing/version-conflict recovery.
+
+Use the supplied CLI-bundled identity for a selected shipped Provider, including
+when the same Skill/version is also visible as an installed projection. Do not
+resolve that copy through the Host or re-read its installed metadata. For a
+relevant external Skill, read only the exact Host-exposed frontmatter and
+sibling `context-indexer.yaml` needed for selection; do not guess a version or
+scan caches. Different versions remain distinct. Read Provider guidance only
+when selected. Discovery is not a durable workspace artifact.
+
+Return only `stage: provider-selection`, the non-CLI
+`host_visible_skills`, and the selected semantic `indexers` through the exact
+`context action complete-current` command returned by the Route. The CLI owns
+construction of the full registry payload, fallback/conflict checks, static
+validation, Provider resolution and staging, final validation, and atomic
+application of `src/indexers.yaml`. Do not call their low-level commands as a
+second production workflow.
+
+If a selected external Provider needs Host resolution, the next current Route
+contains one `context.resolve-indexer-provider/v1` Host Action and its exact
+request. Invoke that Host Action once, then submit
+`stage: provider-resolution` with the returned Host result through the Route's
+`complete-current` command. If the Bundle carries a non-allowlisted program,
+the following current Route presents the existing program-execution Gate; wait
+for its user/session-authority decision and submit that decision through
+`complete-current`. A recovered `provider-finalization` Route consumes
+only its fixed Action input; it must not resolve or install the Provider again.
 
 ### Follow the current Route
 
@@ -227,8 +172,12 @@ Treat `workflow.current` as the current-step authority:
 
 1. Read every `resources.required` item whose `read_state` is `read-required`.
    Read a returned `path` completely, or execute a returned resource `command`
-   and read its complete output file. Materializing a resource is not reading
-   it. Keep the merged receipts only in this conversation and submit them with
+   and read its complete output file. For a current Indexer Partition, Author,
+   Composer or structure-review Route, read the materialized files and then use
+   the Route's immediate completion command; do not create or submit a read
+   receipt. Other workflow resources may still require the returned receipt
+   command. Materializing a resource is not reading it. Keep those receipts only
+   in this conversation and submit them with
    the exact returned `context status --resource-receipts @<file>` command. Use
    `after_read_receipts` only after the full resource has been read. The exact
    `resources.after_read.command` already returns the re-evaluated