@c4a/context-cli 0.6.18 → 0.7.0

package/docs/document-optimization.md

@@ -1,9 +1,8 @@
 # Document revisions
 
-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.
+New workspaces enable source-constrained editorial revision by default. It is a
+build phase for source-backed prose that improves publication value and
+readability without changing the approved knowledge page or inventing facts.
 
 To opt out during initialization:
 
@@ -19,9 +18,22 @@ context optimize-docs disable
 context status --format json
 ```
 
-When enabled, the workflow plans only new or changed fragments. The Agent may
-keep a fragment unchanged or apply a conservative replacement. Only changed
-pages receive a full revision beside their approved page:
+When enabled, the workflow plans only new or changed source Sections. For each
+Section the CLI reports mechanical signals and allowed actions. The Agent may
+keep it, repair local presentation, reshape it within the same source boundary,
+or omit it when the CLI confirms a non-knowledge reason. Only changed pages
+receive a full revision beside their approved page:
+
+Signals are review leads rather than a complete readability verdict. The Agent
+must read every Section. Keeping a signaled Section requires a concrete,
+decision-only assessment explaining why each signal is a false positive or why
+editing would reduce source fidelity. The assessment names every reported
+signal code so the CLI can verify complete coverage; it is never published.
+Time, cost, workload, batch size, or delivery pressure are not valid keep or
+defer reasons. Fully managed operation applies all safe repairs, reshapes, and
+eligible omissions autonomously; only genuinely unavailable semantic input is
+batched for the user. A large fragment set must meet the same quality standard
+as a single fragment.
 
 ```text
 knowledge/guides/setup.md
@@ -32,10 +44,21 @@ The `__revision.md` suffix is reserved. Default knowledge discovery, structure,
 search, and package selection exclude revision files. Validation and build
 associate a revision with its sibling base page and apply it under the original
 package path. A revision stores only the base digest that cannot be inferred;
-its path and revised fragments are derived. Unchanged fragments inside a full
+its path and revised Sections are derived. Unchanged Sections inside a full
 revision are inferred. A page with no changes stores only one derived negative
 cache key below `.tmp/context-runtime/document-optimization/`; replacement
-prose and fragment metadata are not duplicated there.
+prose and Section metadata are not duplicated there.
+
+Typical repair candidates are Markdown syntax, spacing, empty table rows, and
+descriptive labels for links whose purpose is already present. Reshape handles
+wide tables, long cells, mixed images and links, or long prose by creating a
+clearer structure inside the same Section. Unanswered question sets, empty
+placeholders, decision-free drafts, duplicates, and obsolete-only Sections may
+be omitted. Questions with answers, limitations with an action, and
+deprecations with a replacement remain knowledge. Link targets, images, code,
+commands, numbers, identifiers, conditions, and source references are protected
+through validation. Ambiguous currency, ownership, or sensitive values appear
+together in the plan's `input_requests` and require one batched user decision.
 
 After capture, review, or build, a user may ask conversationally to correct one
 existing knowledge page. Start the correction by title, approved path, or
@@ -47,8 +70,9 @@ context revise "<title, approved path, or ViewRef>" --format json
 
 Context starts `route.document-revision.requested` only after resolving one
 page. Ambiguous requests return candidates instead of guessing. Edit
-reader-visible prose without changing provenance or `context:section`
-boundaries, then run `context optimize-docs validate`. A valid correction ends
+reader-visible prose within existing `context:section` boundaries without
+changing provenance or protected values, then run `context optimize-docs
+validate`. A valid correction ends
 the request and the next Route offers a package build when output is stale. If
 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

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

@@ -1,7 +1,7 @@
 # 文档修订页
 
-新工作区默认开启保守的文档编译优化。它是面向来源可追溯正文的构建阶段，只修复
-Markdown 排版、链接和明显的局部错误，不修改正式知识页，也不大段改写原意。
+新工作区默认开启来源约束的编辑修订。它是面向来源可追溯正文的构建阶段，在不修改
+正式知识页、不补写事实的前提下，提高发布内容的知识价值和可读性。
 
 初始化时如需关闭：
 
@@ -17,8 +17,9 @@ context optimize-docs disable
 context status --format json
 ```
 
-开启后，工作流只规划新增或发生变化的片段。Agent 可以保持片段不变，或提交
-保守的局部替换。只有实际改写的页面才在原文旁生成完整修订页：
+开启后，工作流只规划新增或发生变化的来源 Section。CLI 为每个 Section 枚举机械
+信号和允许动作；Agent 可以保持不变、局部修复、在同一来源边界内重排，或在 CLI
+确认其属于无知识价值内容时省略。只有实际变化的页面才在原文旁生成完整修订页：
 
 ```text
 knowledge/guides/setup.md
@@ -27,9 +28,28 @@ knowledge/guides/setup__revision.md
 
 `__revision.md` 是保留后缀。默认知识发现、结构、检索和包选择都排除修订页；
 校验和构建根据文件名把它关联回同目录原文，并仍按原文件名输出。修订页只额外
-记录无法推导的原文摘要；原文路径和修订片段由文件名与正文差异推导。完整修订
-页中未变化的片段直接推导为 `keep`；整页都不修改时，运行时只保存一个页级负
-缓存键，不重复保存改写正文或片段元数据。
+记录无法推导的原文摘要；原文路径和修订 Section 由文件名与正文差异推导。完整修订
+页中未变化的 Section 直接推导为 `keep`；整页都不修改时，运行时只保存一个页级负
+缓存键，不重复保存改写正文或 Section 元数据。
+
+局部修复适用于 Markdown、空白、空表格行，以及来源已经说明用途的链接名称。结构
+重排适用于宽表格、长单元格、图片与链接混排或过长段落，但不能跨 Section 搬运事实。
+未回答的问题集合、空占位、没有结论的草稿、重复内容和只有旧稿的 Section 可以省略；
+有答案的问句、有影响和动作的限制、带替代方案的废弃说明仍属于知识。链接目标、图片、
+代码、命令、数字、标识符、条件和来源引用由 CLI 机械保护。事实时效、职责或敏感值不
+明确时，CLI 会把相关 Section 集中列入计划的 `input_requests`，工作流只询问用户一次，
+不会自动省略。
+
+机械信号只是审阅线索，不代表最终结论，也不是完整的可读性检查。Agent 必须阅读每个
+Section；若对带信号的 Section 选择 `keep`，需要在本次决策中逐段说明信号为何误报，
+或修改为何会损害来源忠实度，并在说明中逐一写出对应的信号 code，供 CLI 机械核对覆盖
+是否完整。CLI 会拒绝没有具体说明或漏掉信号的 `keep`，但这段说明只用于当前决策审计，
+不会写入正式知识、修订页或构建产物。部分信号误报也不能成为整批保持不变的理由。
+
+时间、成本、工作量、批次规模或赶进度都不是 `keep`、跳过或延期的有效理由。全托管
+模式下，Agent 应自动完成所有安全的局部修复、结构重排和允许省略，直到当前批次收敛；
+只有确实无法从当前 Section 或来源证据取得的语义信息，才集中向用户询问一次。片段多
+不能降低质量标准，也不能把整批默认判为 `keep`。
 
 工作区采集、审核或构建完成后，用户可以直接通过对话要求修正某篇知识。Agent
 先使用标题、正式知识路径或 ViewRef 启动修订：
@@ -40,8 +60,8 @@ context revise "<标题、正式知识路径或 ViewRef>" --format json
 
 CLI 只在目标唯一时创建或复用该页修订，并由 Agent Graph 返回
 `route.document-revision.requested`。若有多个候选，Agent 必须依据当前对话选定，
-否则询问用户。Agent 只编辑面向读者的正文，不修改来源信息和
-`context:section` 边界，随后运行 `context optimize-docs validate`。校验成功后，
+否则询问用户。Agent 只在已有 `context:section` 内编辑面向读者的正文，不修改来源
+信息、Section 边界和受保护值，随后运行 `context optimize-docs validate`。校验成功后，
 请求自动结束；若产物因此过期，下一条 Route 会直接提示重新构建。即使工作区
 此前关闭了整库文档编译优化，这个入口也只激活目标页面，不会让其他页面进入
 待优化队列。上游内容变化后，旧修订页会成为冲突，不会被静默应用。

package/indexers/bundles/context-code-indexer/SKILL.md

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

package/indexers/bundles/context-code-indexer/context-indexer.yaml

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

package/indexers/bundles/context-code-indexer/references/composers/contracts-and-chains.md

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

package/indexers/bundles/context-code-indexer/references/composers/cross-module-chain.md

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

package/indexers/bundles/context-code-indexer/references/composers/development-and-delivery.md

@@ -0,0 +1,22 @@
+---
+id: context.code-indexer.composer.development-and-delivery
+kind: procedure
+media-type: text/markdown
+---
+
+# Development and delivery composer
+
+Run only for an effective `development-and-delivery` workset. It supplements
+the primary target and cannot own repository scope, release authority, or the
+final Indexer Result.
+
+Require an evidenced `development-entry` fact and primary `content` Artifact.
+Propose derived `content` only for module-owned setup, build, test, packaging,
+deployment, release, rollback, or recovery behavior that answers a stable
+reader question. Distinguish local commands from CI orchestration and record
+configuration inputs without copying secret-like values.
+
+Use the existing Node, `standard` policy, and view evidence. Workspace-wide
+processes belong on a container target, not every module. If the required input
+is absent or the view contains no module-owned development/delivery contract,
+return `fragments: []` in the ordinary structured result.

package/indexers/bundles/context-code-indexer/references/composers/event-flow.md

@@ -0,0 +1,21 @@
+---
+id: context.code-indexer.composer.event-flow
+kind: procedure
+media-type: text/markdown
+---
+
+# Event flow composer
+
+Run only from an effective `event-flow` workset. The supplied primary view is
+the complete authority boundary for this invocation.
+
+Require an evidenced `event-binding` fact and primary `content` Artifact.
+Propose derived `content` only when a stable event identity connects producer,
+transport or dispatch, consumer, state effect, retry/idempotency behavior, and
+failure handling. Timers and scheduled triggers qualify only when their
+registration and downstream behavior are explicit.
+
+Keep the current target Node, use `standard`, and cite view evidence. Do not
+invent a producer from a consumer name or infer delivery guarantees from a
+library default. Missing requirements, an unpaired boundary, or no additional
+reader value must return the normal result envelope with `fragments: []`.

package/indexers/bundles/context-code-indexer/references/composers/examples-and-documentation.md

@@ -0,0 +1,22 @@
+---
+id: context.code-indexer.composer.examples-and-documentation
+kind: procedure
+media-type: text/markdown
+---
+
+# Examples and documentation composer
+
+Run only when selected for the current profile. The workset-scoped primary
+view is the sole input; documentation files outside that view are not implicit
+authority.
+
+Require an evidenced `example-candidate` fact and primary `content` Artifact.
+Propose an `examples` Artifact only for maintained usage that demonstrates a
+supported public target, meaningful setup, expected outcome, and important
+constraints. Merge scenario variants and exclude fixtures, generated samples,
+and demos that do not represent supported use.
+
+Use the existing target Node and `standard` policy. Evidence must come from the
+view. When no representative example closes the reader question, or either
+required input is missing, return the structured empty fragment-set result;
+never invent tutorial steps.

package/indexers/bundles/context-code-indexer/references/composers/persistence-boundary.md

@@ -0,0 +1,21 @@
+---
+id: context.code-indexer.composer.persistence-boundary
+kind: procedure
+media-type: text/markdown
+---
+
+# Persistence boundary composer
+
+Run only for an effective `persistence-boundary` selection. Consume the exact
+`PrimaryResultView` and keep all proposals subordinate to its Node and Result.
+
+Require an evidenced `persistence-binding` fact and primary `content`
+Artifact. Derived `content` may connect the domain operation to repository or
+store, model/schema authority, transaction or consistency boundary, caching,
+migration, failure, and recovery. Separate authoritative schema sources from
+generated models and runtime observations.
+
+Use `standard` and existing evidence. Do not infer storage semantics from a
+driver dependency or method name. If the binding, required Artifact, or a
+source-backed persistence question is absent, return a valid empty fragment
+set rather than reading outside the workset.

package/indexers/bundles/context-code-indexer/references/composers/protocol-boundary.md

@@ -0,0 +1,22 @@
+---
+id: context.code-indexer.composer.protocol-boundary
+kind: procedure
+media-type: text/markdown
+---
+
+# Protocol boundary composer
+
+Run only for an effective `protocol-boundary` composer workset and consume its
+exact `PrimaryResultView`. Never discover new scope or claim final Result
+authority.
+
+Require an evidenced `protocol-operation` fact and a primary `contract`
+Artifact. A derived `contract` proposal may connect a stable operation identity
+to transport, request/response or message shapes, provider and consumer,
+errors, compatibility, and authoritative schema evidence. Keep generated
+clients and bindings pointed at their source contract.
+
+Use the existing target Node and `standard` policy. Do not infer operations
+from names or import adjacency. If the required fact/Artifact is missing, the
+provider/consumer pairing is ambiguous, or the primary contract already
+answers the reader question, return a valid result with `fragments: []`.

package/indexers/bundles/context-code-indexer/references/composers/public-contract.md

@@ -0,0 +1,23 @@
+---
+id: context.code-indexer.composer.public-contract
+kind: procedure
+media-type: text/markdown
+---
+
+# Public contract composer
+
+Run only for an effective `public-contract` composer workset. Consume the
+workset-scoped `PrimaryResultView`; do not inspect a broader repository or
+replace the primary Result.
+
+Require an evidenced `public-surface` fact and its owning primary `content`
+Artifact. Propose a `contract` Artifact only when the view establishes stable
+consumer identities, entrypoints, behavior, constraints, and evidence. Group
+related exports, commands, routes, or extension points by the public concept a
+consumer uses; do not enumerate incidental symbols.
+
+Every proposal must retain the existing target Node, use the `standard`
+Artifact policy variant, and cite evidence already present in the view. Return
+only a post-author `derived-artifact-proposal` fragment. If either required
+input is absent or no independent reader question is supported, return the
+normal layer-fragment result with `fragments: []`.

package/indexers/bundles/context-code-indexer/references/indexer.md

@@ -0,0 +1,49 @@
+# Code Indexer authoring contract
+
+Consume only the current workset, normalized parser facts, verified layer input, and scoped evidence views supplied by Context.
+
+## Classify before selecting templates
+
+Classify each requested module from current manifests, stable entries, public contracts, runtime registration, maintained documentation, and source-backed boundary evidence. Select one primary profile and only the additional profiles supplied by the current workset. A directory name, framework dependency, class suffix, or generated file is not sufficient classification evidence.
+
+Read only the templates materialized for the selected profiles. Combine their questions into one deduplicated plan for the reader-visible capability; a template is guidance, not a source of facts, page counts, output paths, thresholds, or authority. Keep a repository container, public contract, runtime boundary, event flow, persistence boundary, adapter, generated-source provenance, and cross-module handoff separate when they answer different reader questions. Do not copy a template outline when source evidence does not support its sections.
+
+## Partition and identity
+
+For partition work, close every inventory member as owned, excluded, or unsupported and use stable semantic subjects. Each member has exactly one primary owner; extension layers may enrich but cannot claim final authority. Do not create ordinal batches or infer identity from display titles, filenames, headings, or traversal order. If no defensible semantic grouping exists, return the protocol failure that permits the CLI-owned catalog fallback.
+
+Use only the ordered partition strategy materialized by Context for the current workset. The order is project-first and authority-bound; do not skip to a CLI builtin, substitute another strategy id, or recalculate an implementation digest. A strategy may group only the canonical members and profiles supplied with that workset.
+
+Group related identities by a capability, entrypoint, protocol boundary, lifecycle stage, state owner, or handoff. A granular catalog is appropriate only when the selected profile and reader goal require a public API, protocol, command, or registry reference. A cross-module chain requires an explicit trigger, source-backed joins on both sides of every boundary, transformations or state handoffs, and a terminal outcome; imports or similar names do not prove execution order.
+
+Create a reader target only from a CLI-supplied declaration, public export, contract declaration, runtime registration, approved Subject, or Partition Subject identity. Import/re-export aliases, ordinary references, internal helpers, and lightweight evidence may enrich their canonical owner but cannot independently authorize a target. Normalize aliases into the supplied canonical identity. Never promote a name merely because it appears in prose or has many inbound references.
+
+## Author Result and evidence
+
+For author work, produce exactly one Result for the supplied logical unit. Keep deterministic catalogs separate from explanatory prose, bind every declaration and Section to current evidence, and select only an Artifact policy variant listed in the workset. Missing material must become a canonical question disposition; never invent an answer or emit placeholder knowledge.
+
+Treat the CLI inventory as the complete denominator, not a sample. Parser facts may prove files, declarations, entries, contracts, and relationships; they do not by themselves prove business meaning, runtime defaults, failure behavior, or ownership. Every relationship must cite the concrete evidence for its own handoff. Do not repeat one whole-page evidence set across unrelated facts, and do not reduce a multi-source fact to one arbitrary primary file.
+
+Close every CLI-supplied example candidate with exactly one decision: link it to its public target, merge it into a canonical example for the same target and scenario, retain it as a documentation example, exclude it with a reason, or request missing material. A retained representative must decide setup, key calls, parameters, and expected behavior as either extracted facts or evidence-backed not-applicable facets. Merge only by the full example identity supplied by Context; filenames and basenames are not identities. Do not omit an unresolved candidate from the decision set, and do not treat a material request as completed linkage.
+
+Explain stable responsibility, inputs, outputs, state and failure boundaries, the next handoff, and the evidence that supports each claim. Keep implementation bodies, generated payloads, exhaustive internal helper lists, and normalized template repetition out of reader prose. Empty Results are valid only when every target receives a legal disposition.
+
+## Post-author composer result
+
+For a post-author workset, use only the effective composer named by Context and the matching composer instruction materialized beside this contract. Consume the complete workset-scoped `PrimaryResultView`; do not reopen discovery, expand scope, change Subject identity or ownership, or return another complete main Result. A composer may emit only the declared `derived-artifact-proposal` kind and Artifact policy.
+
+If a declared primary fact or Artifact requirement is absent, or the view does not support an independent reader question, return the ordinary `context.indexer.layer-fragment-result/v1` with `fragments: []` and the exact consumed view digest. This is a successful structured empty invocation, not a license to inspect temporary files or infer missing content.
+
+## Mechanical audit and revision
+
+Context independently validates inventory closure, owner closure, parser coverage, Artifact completeness, evidence scope, relationship candidates, semantic density, template repetition, enumeration, and implementation-body limits. These dimensions are independent; one strong dimension cannot offset a hard failure in another. Do not alter wording, Markdown syntax, sentence counts, or partitions solely to influence a counter.
+
+For a failed metric, follow the matching entry in `references/metrics.md`. Each entry explains the denominator-preserving repair, a positive example, and an anti-example. It deliberately contains no numeric threshold: use the current CLI audit for actual, recommended, and hard values.
+
+The reference-only reader-target metric is a zero-count hard gate. Context joins the proposed reader-target projection to its own current identity observations and separately rejects targets with no identity observation at all. Provider prose, display titles, filenames, inbound-reference counts, and self-reported target authority cannot satisfy this gate.
+
+Context recomputes example candidate decision coverage over the complete example inventory. Representative coverage and public-target linkage keep undecided and material-request candidates in their denominator, while only a confirmed exclusion removes a candidate. A scenario variant inherits coverage only when its canonical decision chain terminates at a retained representative; it inherits public-target linkage only when that terminal decision links the exact public target.
+
+When the current audit reports a repairable profile failure, revise the complete affected logical-unit set and return a new Result under the same stable problem lineage. Use the reported uncovered identities, failed metric ids, evidence locators, and legal actions. Request material only when reliable correction requires a source, contract, protocol, or access boundary absent from the registered scope. Three failed revisions produce one complete human report; only the explicit non-delegable profile-risk Gate may accept that runtime profile risk, and no baseline integrity failure is bypassable.
+
+Do not return output paths, collection names, quality thresholds, pass/fail decisions, extra owners, ad hoc question contracts, or facts outside the supplied authority. Context validates structure, evidence, layout, metrics, freshness, reconciliation, and final Review independently.