@c4a/context-cli 0.6.16 → 0.6.18

package/docs/document-optimization.md

@@ -1,19 +1,21 @@
 # Document revisions
 
-Document optimization is an optional build phase for source-backed prose. It
-repairs presentation-level Markdown without changing the approved knowledge
-page.
+New workspaces enable conservative document optimization by default. It is a
+build phase for source-backed prose that repairs presentation-level Markdown,
+links, and obvious local errors without changing the approved knowledge page or
+broadly rewriting its meaning.
 
-Enable it during initialization:
+To opt out during initialization:
 
 ```bash
-context init context --optimize-docs
+context init context --no-optimize-docs
 ```
 
-Or enable it in an existing workspace:
+Existing workspaces retain their current setting. Change it explicitly with:
 
 ```bash
 context optimize-docs enable
+context optimize-docs disable
 context status --format json
 ```
 
@@ -52,11 +54,5 @@ broad document optimization was disabled, this entry activates only the target
 page and keeps every other eligible page out of the pending batch. If upstream
 content changes, the revision becomes a conflict and must be reviewed again.
 
-Disable and restore baseline output with:
-
-```bash
-context optimize-docs disable
-```
-
-Revision pages move to Context runtime recovery storage, and the next build
-uses approved knowledge directly.
+Disabling moves active revision pages to Context runtime recovery storage. The
+next build uses approved knowledge directly.

package/docs/document-optimization.zh-CN.md

@@ -1,18 +1,19 @@
 # 文档修订页
 
-文档编译优化是面向来源可追溯正文的可选构建阶段。它只修复 Markdown
-排版和明显的局部问题，不修改正式知识页。
+新工作区默认开启保守的文档编译优化。它是面向来源可追溯正文的构建阶段，只修复
+Markdown 排版、链接和明显的局部错误，不修改正式知识页，也不大段改写原意。
 
-初始化时开启：
+初始化时如需关闭：
 
 ```bash
-context init context --optimize-docs
+context init context --no-optimize-docs
 ```
 
-已有工作区可以运行：
+已有工作区保持当前设置，可显式调整：
 
 ```bash
 context optimize-docs enable
+context optimize-docs disable
 context status --format json
 ```
 
@@ -42,13 +43,8 @@ CLI 只在目标唯一时创建或复用该页修订，并由 Agent Graph 返回
 否则询问用户。Agent 只编辑面向读者的正文，不修改来源信息和
 `context:section` 边界，随后运行 `context optimize-docs validate`。校验成功后，
 请求自动结束；若产物因此过期，下一条 Route 会直接提示重新构建。即使工作区
-此前没有开启整库文档编译优化，这个入口也只激活目标页面，不会让其他页面进入
+此前关闭了整库文档编译优化，这个入口也只激活目标页面，不会让其他页面进入
 待优化队列。上游内容变化后，旧修订页会成为冲突，不会被静默应用。
 
-关闭并恢复基础构建结果：
-
-```bash
-context optimize-docs disable
-```
-
-修订页会被移动到 Context 的运行时恢复目录，下一次构建直接使用正式知识。
+关闭后，修订页会被移动到 Context 的运行时恢复目录，下一次构建直接使用正式
+知识。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.6.16",
+  "version": "0.6.18",
   "type": "module",
   "description": "Local runtime and Agent integration for traceable knowledge production",
   "license": "MIT",
@@ -24,7 +24,7 @@
   },
   "dependencies": {
     "@c4a/agent-graph": "0.2.6",
-    "@c4a/context": "0.6.16",
+    "@c4a/context": "0.6.18",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",
     "handlebars": "^4.7.8",

package/plugins/VERSION

@@ -1 +1 @@
-0.6.16
+0.6.18

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.6.16",
+  "version": "0.6.18",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/commands/context.md

@@ -28,12 +28,12 @@ context entry [project-dir] --language <language> --format json
 
 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`, `--debug`, or `--optimize-docs` only when the
-user explicitly requested that initialization choice. Treat requests to enable
-document compilation optimization, document formatting optimization, or
-equivalent conservative build-time cleanup as `--optimize-docs`. Pass
-`--managed` only after the user
-explicitly authorizes fully managed operation in this conversation.
+`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.
 
 If the `context` process itself cannot start because the command is missing
 (`ENOENT`, or shell exit 127 explicitly identifying `context` as the missing
@@ -90,13 +90,19 @@ before workflow evaluation. Debugging records traces below
 `.tmp/context-runtime/debug/` but does not grant workflow authority or provide
 source evidence.
 
-Enable document optimization only when the user explicitly requests it. If
-initialization is required, pass `--optimize-docs` through `context entry`; for
-an existing workspace, run `context optimize-docs enable` before workflow
-evaluation. The feature 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.
+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.
+
+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.
 
@@ -133,6 +139,11 @@ Treat `workflow.current` as the current-step authority:
    `inspection_action` resource only while inspecting the decision, and read a
    `resolution_action` resource only after the user confirms the Gate. Neither
    replaces ordinary required resources.
+   For ordinary Knowledge Review, follow the Route-selected dialogue: do not
+   advertise force approval in the initial prompt. If the user cannot access
+   the report, only their exact current-conversation reply `强制批准` authorizes
+   the returned force-approval resolution command; generic approval wording
+   does not.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` waits
    for the current Gate decision. Run a command whose `execution.target` is `agent-host`
@@ -140,6 +151,9 @@ Treat `workflow.current` as the current-step authority:
    not inside a restricted child sandbox. Follow the Route-selected procedure
    for its audit and approval contract; never invent a payload, destination, or
    substitute command.
+   A Context command is complete only after its process returns an exit code and
+   receipt. If the host reports that it is still running, keep polling that same
+   invocation; never start a second Context write command in parallel.
    Treat a code-extraction batch preview as one Route action. Read its complete
    index-unit report and keep same-kind capability or scale decisions in the
    single returned Gate; do not ask about modules one by one. A non-delegatable

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

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.6.16",
+  "version": "0.6.18",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": {
     "name": "c4a"
@@ -18,7 +18,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.16",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.18",
     "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

@@ -40,12 +40,12 @@ context entry [project-dir] --language <language> --format json
 
 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`, `--debug`, or `--optimize-docs` only when the
-user explicitly requested that initialization choice. Treat requests to enable
-document compilation optimization, document formatting optimization, or
-equivalent conservative build-time cleanup as `--optimize-docs`. Pass
-`--managed` only after the user
-explicitly authorizes fully managed operation in this conversation.
+`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.
 
 If the `context` process itself cannot start because the command is missing
 (`ENOENT`, or shell exit 127 explicitly identifying `context` as the missing
@@ -102,13 +102,19 @@ before workflow evaluation. Debugging records traces below
 `.tmp/context-runtime/debug/` but does not grant workflow authority or provide
 source evidence.
 
-Enable document optimization only when the user explicitly requests it. If
-initialization is required, pass `--optimize-docs` through `context entry`; for
-an existing workspace, run `context optimize-docs enable` before workflow
-evaluation. The feature 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.
+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.
+
+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.
 
@@ -145,6 +151,11 @@ Treat `workflow.current` as the current-step authority:
    `inspection_action` resource only while inspecting the decision, and read a
    `resolution_action` resource only after the user confirms the Gate. Neither
    replaces ordinary required resources.
+   For ordinary Knowledge Review, follow the Route-selected dialogue: do not
+   advertise force approval in the initial prompt. If the user cannot access
+   the report, only their exact current-conversation reply `强制批准` authorizes
+   the returned force-approval resolution command; generic approval wording
+   does not.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` waits
    for the current Gate decision. Run a command whose `execution.target` is `agent-host`
@@ -152,6 +163,9 @@ Treat `workflow.current` as the current-step authority:
    not inside a restricted child sandbox. Follow the Route-selected procedure
    for its audit and approval contract; never invent a payload, destination, or
    substitute command.
+   A Context command is complete only after its process returns an exit code and
+   receipt. If the host reports that it is still running, keep polling that same
+   invocation; never start a second Context write command in parallel.
    Treat a code-extraction batch preview as one Route action. Read its complete
    index-unit report and keep same-kind capability or scale decisions in the
    single returned Gate; do not ask about modules one by one. A non-delegatable

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

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.6.16",
+  "version": "0.6.18",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": {
     "name": "Context4AI",

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

@@ -32,12 +32,12 @@ context entry [project-dir] --language <language> --format json
 
 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`, `--debug`, or `--optimize-docs` only when the
-user explicitly requested that initialization choice. Treat requests to enable
-document compilation optimization, document formatting optimization, or
-equivalent conservative build-time cleanup as `--optimize-docs`. Pass
-`--managed` only after the user
-explicitly authorizes fully managed operation in this conversation.
+`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.
 
 If the `context` process itself cannot start because the command is missing
 (`ENOENT`, or shell exit 127 explicitly identifying `context` as the missing
@@ -94,13 +94,19 @@ before workflow evaluation. Debugging records traces below
 `.tmp/context-runtime/debug/` but does not grant workflow authority or provide
 source evidence.
 
-Enable document optimization only when the user explicitly requests it. If
-initialization is required, pass `--optimize-docs` through `context entry`; for
-an existing workspace, run `context optimize-docs enable` before workflow
-evaluation. The feature 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.
+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.
+
+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.
 
@@ -137,6 +143,11 @@ Treat `workflow.current` as the current-step authority:
    `inspection_action` resource only while inspecting the decision, and read a
    `resolution_action` resource only after the user confirms the Gate. Neither
    replaces ordinary required resources.
+   For ordinary Knowledge Review, follow the Route-selected dialogue: do not
+   advertise force approval in the initial prompt. If the user cannot access
+   the report, only their exact current-conversation reply `强制批准` authorizes
+   the returned force-approval resolution command; generic approval wording
+   does not.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` waits
    for the current Gate decision. Run a command whose `execution.target` is `agent-host`
@@ -144,6 +155,9 @@ Treat `workflow.current` as the current-step authority:
    not inside a restricted child sandbox. Follow the Route-selected procedure
    for its audit and approval contract; never invent a payload, destination, or
    substitute command.
+   A Context command is complete only after its process returns an exit code and
+   receipt. If the host reports that it is still running, keep polling that same
+   invocation; never start a second Context write command in parallel.
    Treat a code-extraction batch preview as one Route action. Read its complete
    index-unit report and keep same-kind capability or scale decisions in the
    single returned Gate; do not ask about modules one by one. A non-delegatable

package/plugins/skills/c4a-context/SKILL.md

@@ -40,12 +40,12 @@ context entry [project-dir] --language <language> --format json
 
 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`, `--debug`, or `--optimize-docs` only when the
-user explicitly requested that initialization choice. Treat requests to enable
-document compilation optimization, document formatting optimization, or
-equivalent conservative build-time cleanup as `--optimize-docs`. Pass
-`--managed` only after the user
-explicitly authorizes fully managed operation in this conversation.
+`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.
 
 If the `context` process itself cannot start because the command is missing
 (`ENOENT`, or shell exit 127 explicitly identifying `context` as the missing
@@ -102,13 +102,19 @@ before workflow evaluation. Debugging records traces below
 `.tmp/context-runtime/debug/` but does not grant workflow authority or provide
 source evidence.
 
-Enable document optimization only when the user explicitly requests it. If
-initialization is required, pass `--optimize-docs` through `context entry`; for
-an existing workspace, run `context optimize-docs enable` before workflow
-evaluation. The feature 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.
+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.
+
+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.
 
@@ -145,6 +151,11 @@ Treat `workflow.current` as the current-step authority:
    `inspection_action` resource only while inspecting the decision, and read a
    `resolution_action` resource only after the user confirms the Gate. Neither
    replaces ordinary required resources.
+   For ordinary Knowledge Review, follow the Route-selected dialogue: do not
+   advertise force approval in the initial prompt. If the user cannot access
+   the report, only their exact current-conversation reply `强制批准` authorizes
+   the returned force-approval resolution command; generic approval wording
+   does not.
 3. Execute only `commands` returned by the Route, preserving revision and
    authority flags exactly. A command marked `after-human-confirmation` waits
    for the current Gate decision. Run a command whose `execution.target` is `agent-host`
@@ -152,6 +163,9 @@ Treat `workflow.current` as the current-step authority:
    not inside a restricted child sandbox. Follow the Route-selected procedure
    for its audit and approval contract; never invent a payload, destination, or
    substitute command.
+   A Context command is complete only after its process returns an exit code and
+   receipt. If the host reports that it is still running, keep polling that same
+   invocation; never start a second Context write command in parallel.
    Treat a code-extraction batch preview as one Route action. Read its complete
    index-unit report and keep same-kind capability or scale decisions in the
    single returned Gate; do not ask about modules one by one. A non-delegatable

package/providers/context/actions/apply-forced-review.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: apply-forced-review
+runner: host
+effect: write
+handler: context.review.force-approve-current

package/providers/context/actions/revise-code-index-audit.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: revise-code-index-audit
+runner: host
+effect: write
+handler: context.project.revise-code-index

package/providers/context/actions/submit-code-index-audit.yaml

@@ -0,0 +1,6 @@
+schema: agent-graph.action.v1
+id: submit-code-index-audit
+runner: host
+effect: write
+handler: context.code-index-audit.submit
+inputSchema: schemas/code-index-audit-decision.schema.json

package/providers/context/codes.yaml

@@ -29,6 +29,9 @@ codes:
   - { code: route.extract.ownership-required, kind: route-reason, summary: Revise the index plan so every projected page has one output owner., document: resources/procedures/code-extraction.md }
   - { code: route.extract.scale-limit-exceeded, kind: route-reason, summary: At least one index unit exceeds the supported page limit., document: resources/procedures/code-extraction.md }
   - { code: route.extract.pending-target, kind: route-reason, summary: Extract the next pending code target before another workflow family., document: resources/procedures/code-extraction.md }
+  - { code: route.extract.audit-input-required, kind: route-reason, summary: The code-index audit requires specific source or protocol material that is not currently available., document: resources/procedures/code-index-audit.md }
+  - { code: route.extract.audit-revision-required, kind: route-reason, summary: Revise the code-index plan and content for issues confirmed by the Agent audit., document: resources/procedures/code-index-audit.md }
+  - { code: route.extract.audit-required, kind: route-reason, summary: The complete proposed code index requires one Agent semantic audit decision., document: resources/procedures/code-index-audit.md }
   - { code: route.document.classification-required, kind: route-reason, summary: A captured document needs an evidence-backed collection decision., document: resources/procedures/document-classification.md }
   - { code: route.prose.configuration-required, kind: route-reason, summary: A document target is missing a complete prose lifecycle declaration., document: resources/procedures/project-configuration.md }
   - { code: route.structure.pending-target, kind: route-reason, summary: Prepare the next document structure slot from source evidence., document: resources/procedures/prose-align.md }

package/providers/context/graphs/workspace.yaml

@@ -172,6 +172,7 @@ nodes:
     kind: gate
     reasonCode: route.review.decision-required
     inspectionAction: actions/inspect-review.yaml
+    resolutionAction: actions/apply-forced-review.yaml
     delegated:
       inspection: skip
       resolutionAction: actions/apply-managed-review.yaml
@@ -440,6 +441,51 @@ nodes:
         - resources/procedures/code-extraction.md
         - resources/views/source-boundary.yaml
 
+  - id: resolve-code-index-audit-input
+    kind: gate
+    reasonCode: route.extract.audit-input-required
+    resolutionAction: actions/submit-code-index-audit.yaml
+    gate:
+      id: code-index-audit-input
+      prompt: Provide the specific missing source or protocol material required to complete the code-index audit.
+      delegatable: false
+    satisfiedBy:
+      - path: extract.audit_input_required
+        equals: false
+    resources:
+      required:
+        - resources/procedures/code-index-audit.md
+        - resources/dialogue/human-gates.md
+        - resources/views/code-index-audit.yaml
+
+  - id: revise-code-index-audit
+    kind: action
+    reasonCode: route.extract.audit-revision-required
+    action: actions/revise-code-index-audit.yaml
+    satisfiedBy:
+      - path: extract.audit_revision_required
+        equals: false
+    resources:
+      required:
+        - resources/procedures/code-index-audit.md
+        - resources/semantic/code-index/classification.md
+        - resources/views/code-index-audit.yaml
+      recommended:
+        - resources/manuals/reference/code-extractors.md
+
+  - id: audit-code-index
+    kind: action
+    reasonCode: route.extract.audit-required
+    action: actions/submit-code-index-audit.yaml
+    satisfiedBy:
+      - path: extract.audit_resolved
+        equals: true
+    resources:
+      required:
+        - resources/procedures/code-index-audit.md
+        - resources/semantic/code-index/classification.md
+        - resources/views/code-index-audit.yaml
+
   - id: classify-document
     kind: gate
     reasonCode: route.document.classification-required
@@ -501,6 +547,7 @@ nodes:
     kind: gate
     reasonCode: route.review.decision-required
     inspectionAction: actions/inspect-review.yaml
+    resolutionAction: actions/apply-forced-review.yaml
     delegated:
       inspection: skip
       resolutionAction: actions/apply-managed-review.yaml
@@ -689,7 +736,10 @@ edges:
   - { from: preview-extraction-batch, to: repair-extraction-ownership }
   - { from: repair-extraction-ownership, to: revise-extraction-scale }
   - { from: revise-extraction-scale, to: extract-next }
-  - { from: extract-next, to: review-current-batch }
+  - { from: extract-next, to: resolve-code-index-audit-input }
+  - { from: resolve-code-index-audit-input, to: revise-code-index-audit, kind: gatedBy }
+  - { from: revise-code-index-audit, to: audit-code-index }
+  - { from: audit-code-index, to: review-current-batch }
   - { from: review-current-batch, to: apply-managed-review, kind: gatedBy }
   - { from: apply-managed-review, to: classify-document }
   - { from: classify-document, to: configure-prose-lifecycle, kind: gatedBy }