@c4a/context 0.6.18 → 0.6.19

package/README.md

@@ -58,8 +58,8 @@ const sampleLib = source("20260712", "sample-lib");
 export default defineProject({
   sources: [sampleLib],
   phases: [
-    extractTs({ source: sampleLib, collection: "codegraph" }),
-    reviewValidity({ collection: "codegraph" }),
+    extractTs({ source: sampleLib, collection: "codeindex" }),
+    reviewValidity({ collection: "codeindex" }),
   ],
   packages: [
     kbPackage({
@@ -68,7 +68,7 @@ export default defineProject({
         path: "src/package-templates/kb",
         vars: { displayName: "Sample Library KB" },
       },
-      select: { collections: ["codegraph"], okfRoots: ["wikis"] },
+      select: { collections: ["codeindex"], okfRoots: ["wikis"] },
     }),
   ],
 });
@@ -86,7 +86,7 @@ maintain this declaration from the user's requirements.
 |---|---|
 | `defineProject()` | Declares the complete project graph. |
 | `source()` and `allSources()` | References registered repo, file, or Lark source boundaries. |
-| `extractTs()` | Extracts TypeScript/TSX symbols and relationships into `codegraph` candidates. |
+| `extractTs()` | Extracts TypeScript/TSX symbols and relationships into `codeindex` candidates. |
 | `extractCustom()` | Runs a project-owned code extractor while Context owns candidate, evidence, freshness, and Review state. |
 | `alignProse()` and `compileProse()` | Structures document evidence and compiles source-bound knowledge candidates. |
 | `reviewValidity()` | Declares the review gate for one collection or the project. |
@@ -120,7 +120,7 @@ Approved Markdown is organized under `knowledge/<collection>/`:
 
 | Collection | What it contains | Typical sources |
 |---|---|---|
-| `codegraph` | Code symbols, modules, and relationships | Code repositories |
+| `codeindex` | Code symbols, modules, and relationships | Code repositories |
 | `business` | Business concepts, roles, and relationships | Business and Lark documents |
 | `product` | Product capabilities and behavior | Product and requirement documents |
 | `architecture` | System structure and design explanations | Architecture and design documents |

package/README.zh-CN.md

@@ -54,8 +54,8 @@ const sampleLib = source("20260712", "sample-lib");
 export default defineProject({
   sources: [sampleLib],
   phases: [
-    extractTs({ source: sampleLib, collection: "codegraph" }),
-    reviewValidity({ collection: "codegraph" }),
+    extractTs({ source: sampleLib, collection: "codeindex" }),
+    reviewValidity({ collection: "codeindex" }),
   ],
   packages: [
     kbPackage({
@@ -64,7 +64,7 @@ export default defineProject({
         path: "src/package-templates/kb",
         vars: { displayName: "Sample Library KB" },
       },
-      select: { collections: ["codegraph"], okfRoots: ["wikis"] },
+      select: { collections: ["codeindex"], okfRoots: ["wikis"] },
     }),
   ],
 });
@@ -80,7 +80,7 @@ Route 会按需选择维护这份声明所需的操作说明、Schema 和手册
 |---|---|
 | `defineProject()` | 声明完整的项目处理图。 |
 | `source()` 和 `allSources()` | 引用已经登记的代码仓库、本地文件或飞书来源边界。 |
-| `extractTs()` | 从 TypeScript/TSX 中提取符号和关系，生成 `codegraph` 候选。 |
+| `extractTs()` | 从 TypeScript/TSX 中提取符号和关系，生成 `codeindex` 候选。 |
 | `extractCustom()` | 运行项目自有代码提取器，同时由 Context 维护候选、证据、新鲜度和审核状态。 |
 | `alignProse()` 和 `compileProse()` | 整理文档证据，并生成与来源绑定的知识候选。 |
 | `reviewValidity()` | 声明单个知识类型或整个项目的审核门禁。 |
@@ -109,7 +109,7 @@ Context CLI 不会把所有语言和仓库解析器都打入自身。知识项
 
 | 知识类型 | 主要内容 | 常见来源 |
 |---|---|---|
-| `codegraph` | 代码符号、模块和调用关系 | 代码仓库 |
+| `codeindex` | 代码符号、模块和调用关系 | 代码仓库 |
 | `business` | 业务概念、角色和业务关系 | 业务文档、飞书文档 |
 | `product` | 产品能力、功能行为和产品关系 | 产品文档、需求文档 |
 | `architecture` | 系统结构、模块职责和设计说明 | 架构文档、设计文档 |

package/codeIndexPlan.d.ts

@@ -27,6 +27,8 @@ export interface CodeIndexUnitPlan {
     facets?: readonly CodeIndexModuleFacet[];
     /** Source-backed reasons for the selected module type. */
     moduleTypeEvidence?: readonly string[];
+    /** Source-relative Markdown documents read while classifying this index unit. */
+    documents?: readonly string[];
     outputProfile: CodeIndexOutputProfile;
     responsibility: string;
     entries: readonly string[];
@@ -51,9 +53,57 @@ export interface CodeIndexCapabilityGap {
     reason: string;
     requestedMaterial?: string;
 }
+/** Complete source inventory returned by a project adapter for mechanical quality scoring. */
+export interface CodeIndexInspectionInventory {
+    indexUnitId: string;
+    eligibleFiles: number;
+    analyzedFiles: number;
+    /** Complete eligible source identities used as the file denominator. */
+    eligibleFileTargets: readonly string[];
+    /** Complete source identities successfully analyzed by the adapter. */
+    analyzedFileTargets: readonly string[];
+    eligibleLoc: number;
+    analyzedLoc: number;
+    documentsDiscovered: number;
+    documentsRead: number;
+    /** Discovered Markdown identities, relative to the registered source root. */
+    documentTargets?: readonly string[];
+    /** Root README or documentation entry identities that require complete reading. */
+    rootDocumentTargets?: readonly string[];
+    /** Discovered document identities read during module classification. */
+    readDocumentTargets?: readonly string[];
+    /** Documents already referenced by emitted knowledge candidates. */
+    referencedDocumentTargets?: readonly string[];
+    symbolsDiscovered: number;
+    symbolsAnalyzed: number;
+    targetSymbols: number;
+    exportedSymbols: number;
+    /** Stable target identities, normally exported or profile-selected symbol names. */
+    targetSymbolIdentities: readonly string[];
+    /** Public export identities that must remain discoverable. */
+    exportedTargetIdentities: readonly string[];
+    entryTargets: readonly string[];
+    protocolTargets: readonly string[];
+    boundaryTargets?: readonly {
+        kind: "entry" | "export" | "route" | "operation" | "handler" | "downstream" | "command" | "event" | "plugin" | "handoff";
+        identity: string;
+    }[];
+    coveredBoundaryTargets?: readonly {
+        kind: "entry" | "export" | "route" | "operation" | "handler" | "downstream" | "command" | "event" | "plugin" | "handoff";
+        identity: string;
+    }[];
+    excludedFiles: number;
+    /** Complete identities deliberately excluded after discovery. */
+    excludedFileTargets: readonly string[];
+    excludedReasons: readonly string[];
+    parserSkippedFiles: number;
+    /** Complete eligible identities that the parser could not analyze. */
+    parserSkippedFileTargets: readonly string[];
+}
 export interface CodeIndexInspectionResult {
     findings: readonly CodeIndexInspectionFinding[];
     capabilityGaps?: readonly CodeIndexCapabilityGap[];
+    inventories?: readonly CodeIndexInspectionInventory[];
 }
 export interface CodeIndexInspectionContext {
     projectRoot: string;

package/contracts.d.ts

@@ -1,6 +1,7 @@
 export type DocumentMainlineCollection = "business" | "product" | "architecture" | "sop" | "faq" | "standards" | "decision" | "incident" | "test";
 export type CodegraphCollection = "codegraph";
-export type MainlineCollection = CodegraphCollection | DocumentMainlineCollection;
+export type CodeIndexCollection = "codeindex" | CodegraphCollection;
+export type MainlineCollection = CodeIndexCollection | DocumentMainlineCollection;
 export type TopLevelNamespace = MainlineCollection | "feats";
 export type OkfRoot = "guides" | "rules" | "wikis" | "feats";
 export type KnowledgeCollection = TopLevelNamespace;

package/docs/getting-started.md

@@ -186,8 +186,8 @@ For a monorepo or subspace, choose the boundary deliberately:
 The long-term multi-module knowledge shape is stable across capture dates:
 
 ```text
-knowledge/codegraph/module-a/...
-knowledge/codegraph/module-b/...
+knowledge/codeindex/module-a/...
+knowledge/codeindex/module-b/...
 ```
 
 The CLI records each module's git root and subpath, then materializes
@@ -274,8 +274,8 @@ const componentLib = source("20260712", "component-lib");
 export default defineProject({
   sources: [componentLib],
   phases: [
-    extractTs({ source: componentLib, collection: "codegraph" }),
-    reviewValidity({ collection: "codegraph" }),
+    extractTs({ source: componentLib, collection: "codeindex" }),
+    reviewValidity({ collection: "codeindex" }),
   ],
   packages: [],
 });
@@ -285,8 +285,8 @@ Inspect and run:
 
 ```bash
 context run --list
-context run extract:20260712/component-lib:codegraph --dry-run
-context run extract:20260712/component-lib:codegraph
+context run extract:20260712/component-lib:codeindex --dry-run
+context run extract:20260712/component-lib:codeindex
 ```
 
 When operating through an Agent, use `--dry-run --format json` as the CLI
@@ -298,11 +298,11 @@ Treat that preview as a structural scope check before producing draft
 candidates; the CLI does not decide which symbols are important to a business
 or audience.
 
-The codegraph path keeps the stable module identity. The date stays in the repo
+The codeindex path keeps the stable module identity. The date stays in the repo
 source ref and phase id, not in the knowledge path:
 
 ```text
-knowledge/codegraph/<module>/symbol/<slug>.md
+knowledge/codeindex/<module>/symbol/<slug>.md
 ```
 
 Show the tree/path preview to the user before first extraction and describe it
@@ -423,8 +423,8 @@ const componentLib = source("20260712", "component-lib");
 export default defineProject({
   sources: [componentLib],
   phases: [
-    extractTs({ source: componentLib, collection: "codegraph" }),
-    reviewValidity({ collection: "codegraph" }),
+    extractTs({ source: componentLib, collection: "codeindex" }),
+    reviewValidity({ collection: "codeindex" }),
   ],
   packages: [
     kbPackage({
@@ -433,7 +433,7 @@ export default defineProject({
         path: "src/package-templates/kb",
         vars: { displayName: "Component Library KB" },
       },
-      select: { include: ["codegraph/component-lib/**"] },
+      select: { include: ["codeindex/component-lib/**"] },
     }),
   ],
 });
@@ -446,7 +446,7 @@ of the agent knowledge-base package:
 llmsPackage({
   name: "component-lib-llms",
   template: "src/package-templates/llms",
-  select: { include: ["codegraph/component-lib/**"] },
+  select: { include: ["codeindex/component-lib/**"] },
 });
 ```
 

package/docs/guides/agent-guide.md

@@ -146,7 +146,7 @@ action as adding a knowledge source, not as filling CLI placeholders. Treat this
 as a source boundary decision. Document sources use today's local date as their
 name. Repo sources use the date as a batch and require the confirmed module
 identity. Do not invent semantic date suffixes. The concrete repo selector
-appears in source refs, phase ids, and codegraph paths:
+appears in source refs, phase ids, and codeindex paths:
 
 ```text
 knowledge/<collection>/<slug>.md
@@ -178,6 +178,15 @@ If the user supplies several repo/file/Lark sources in one request, create one
 register them under a single project write lock. Never parallelize mutating
 `source add` commands; on a lock-held error, wait and retry.
 
+Do not select sources from repository layout or Git metadata. After the user
+has named an exact local module or path, however, resolving one unique matching
+directory and reading its Git root, `origin`, and current commit are mechanical
+identity checks. Pass the resolved local path relative to the Context project
+root; when the workspace was initialized in a child `context/` directory,
+recompute sibling paths from that new root. In ordinary and fully managed modes,
+do not request a remote URL again when that confirmed local checkout provides
+it.
+
 Current execution supports repo sources, local Markdown/MDX file sources, and Lark /
 Feishu document sources. Local
 repo/package sources are registered with `context source add repo [YYYYMMDD] --module <module> --local <path>`;
@@ -286,16 +295,16 @@ prose align. Once a document structure draft exists, keep that current human
 gate and do not switch workflows mid-review.
 
 For monorepos, the date is one registration batch and every selected package is
-a module under it. Stable codegraph paths omit that batch date and therefore
-look like `knowledge/codegraph/module-a/...` and
-`knowledge/codegraph/module-b/...`. Date/module remains in phase ids and
+a module under it. Stable codeindex paths omit that batch date and therefore
+look like `knowledge/codeindex/module-a/...` and
+`knowledge/codeindex/module-b/...`. Date/module remains in phase ids and
 repo source refs. Use the whole repo/subspace
 only for inspection when it contains multiple modules. If the user chooses
 `packages/button`, register it with `--module button` under the same date and
 write `extractTs({ source: source("20260712", "button"), ... })`. Do not use
 `include: ["packages/button/src/**"]` to choose a package from a larger source;
 `include` only filters files inside the selected source. Repo module names are
-project-wide codegraph identities; refresh an existing module through its
+project-wide codeindex identities; refresh an existing module through its
 original date/module selector instead of reusing its name under a later date.
 
 For a non-standard package, configure source-relative `entries` on `extractTs`;
@@ -318,17 +327,17 @@ context source inspect <date>/<module> --format json
 context run <extract-phase-id> --dry-run --format json
 ```
 
-After the preview, run codegraph extraction normally unless the user explicitly
+After the preview, run codeindex extraction normally unless the user explicitly
 asked for CI/CD automation. The first normal run requires Review for all code
 candidates. Subsequent normal runs require Review only for added, changed, or
 removed symbols; unchanged approved symbols stay approved. After each result,
-run `context status --format json`. `continue-codegraph-batch` only requests
+run `context status --format json`. `continue-codeindex-batch` only requests
 workspace re-evaluation. Open Review only when
 `workflow.current.gate.id=knowledge-review`; otherwise execute the current
 route.
 
 For a non-interactive pipeline, use `context run <extract-phase-id>
---auto-promote --format json`. This flag applies only to codegraph, applies its
+--auto-promote --format json`. This flag applies only to codeindex, applies its
 deterministic deltas, refreshes deterministic close when needed, runs verify,
 and fails the command if close or verify fails. Read `autoPromotion.close` and
 `autoPromotion.verify` before continuing. Package build remains explicit: when
@@ -354,7 +363,7 @@ tsconfig/jsconfig `baseUrl` and `paths`, so do not ask users to rewrite `@/`
 imports solely for Context. Explain the concrete output shape:
 
 ```text
-knowledge/codegraph/<module>/symbol/<slug>.md
+knowledge/codeindex/<module>/symbol/<slug>.md
 ```
 
 If the module or resulting path shape looks wrong, stop and repair the

package/docs/guides/lark-resources.md

@@ -33,6 +33,13 @@ resources remain explicit in the capture report. Unknown non-empty XML blocks
 stay auditable in the raw XML and receive a warning; the CLI does not infer
 their meaning.
 
+Document and resource reads share one access identity. Context first uses the
+user identity; it falls back to the bot identity only when user credentials
+are unavailable, never when the source denies permission or reports missing
+scopes. This prevents a capture from mixing document text read by one identity
+with attachments read by another. A bot fallback is reported in the capture
+result and remains subject to the bot's own access boundary.
+
 ## Storage lifecycle
 
 Resources have three distinct locations:

package/docs/guides/package-outputs.md

@@ -105,8 +105,8 @@ capture reports are never distributed as reader assets. See
 [Lark Resource Materialization](./lark-resources.md).
 
 The same inventory exposes `structure.relationship_coverage`. It records
-whether selected codegraph pages have current source-backed AST relationship
-metadata, how many codegraph views were selected, and how many package-visible
+whether selected codeindex pages have current source-backed AST relationship
+metadata, how many codeindex views were selected, and how many package-visible
 edges were emitted. An empty edge list is therefore explicit evidence of a
 coverage state, not permission to invent a dependency.
 
@@ -130,7 +130,7 @@ Current collection mapping:
 
 | Internal collection | Package path | Role |
 |---|---|---|
-| `codegraph` | `wikis/codegraph/` | Structured code entities and relationships. |
+| `codeindex` | `wikis/codeindex/` | Source-backed code indexes with optional structured relationships. |
 | `business` | `wikis/business/` | Structured business entities and relationships. |
 | `product` | `wikis/product/` | Structured product entities, behavior, and relationships. |
 | `architecture` | `guides/architecture/` | Architecture explanations and design narratives. |

package/docs/reference/code-extractors.md

@@ -98,7 +98,7 @@ configuration problem, not a Review decision.
 
 If no current capability can parse the source reliably, stop at configuration
 and report the missing generic capability. Do not silently emit an empty
-codegraph or reuse an unrelated parser.
+codeindex or reuse an unrelated parser.
 
 ## Plan Before Parsing
 
@@ -108,7 +108,7 @@ application, adapter, CLI/tool, monorepo container, derived source,
 authoritative contract source, or unknown.
 A hybrid module may declare several `moduleTypes` and several behavior `facets`;
 keep one primary `moduleType` for concise reports. Record inspected paths in
-`moduleTypeEvidence`, then read all matching Route-recommended files below
+`moduleTypeEvidence`, record every Markdown file actually read in `documents`, then read all matching Route-recommended files below
 `resources/semantic/code-index/templates/` and combine them into one plan.
 After that, choose exactly one closed output profile: `module-map`,
 `application-map`, `protocol-index`, `service-boundary`, `runtime-map`,
@@ -130,8 +130,9 @@ selected symbol and permits one owning index unit per source. Use it for an
 intentional granular public reference. Use `extractCustom()` for module-level
 aggregation, registries, protocol indexes, cross-module flows, or multiple
 candidate owners over one source; each candidate declares its `module` and
-evidence-scoped `sections`. Each section's typed coverage and exact evidence is
-checked against the output profile during preview. Resolve repositories from
+at least one evidence-scoped `section`; there is no page-level Markdown
+fallback. Each section's typed coverage and exact evidence is checked against
+the output profile during preview. Resolve repositories from
 the extractor context's `sources[].absolutePath`, never from a
 machine-specific checkout path. Cross-module flow output must also emit
 source-backed structured edges. Generated clients/models, mirrored sources, legacy

package/docs/reference/package-templates.md

@@ -41,7 +41,7 @@ kbPackage({
 llmsPackage({
   name: "component-lib-llms",
   template: "src/package-templates/llms",
-  select: { include: ["codegraph/component-lib/**"] },
+  select: { include: ["codeindex/component-lib/**"] },
 });
 ```
 
@@ -259,7 +259,7 @@ its pages instead of producing one index per path segment.
 The generated
 `dist/<package-name>/wikis/` tree is the required default
 KB entry surface. Internal collections are mapped into OKF roots during build:
-`codegraph`, `business`, and `product` go to `wikis/`; `architecture`, `sop`,
+`codeindex`, `business`, and `product` go to `wikis/`; `architecture`, `sop`,
 `faq`, `decision`, and `incident` go to `guides/`; `standards` and `test` go to
 `rules/`; and `feats` goes to `feats/`. Treat `wikis/` as the structured
 entity-and-relationship layer. Guides and rules may explain, operationalize,
@@ -307,17 +307,25 @@ wants project-specific behavior beyond knowledge lookup.
 
 ## Context OKF Profiles
 
-Approved Markdown under `knowledge/` is the production source of truth:
+Approved Markdown under `knowledge/` and its deterministic
+`knowledge/structure.yaml` projection form the authoring source of truth:
 
 - top-level YAML frontmatter uses OKF fields such as `type`, `title`,
   `description`, `tags`, `timestamp`, and `resource`;
-- Context production metadata such as `sources`, `node_type`, `visibility`,
-  `code_symbols`, relationship records, and `candidate_fingerprint` also lives
-  at the top level;
+- each Markdown page keeps reader fields, stable page identity, `sources`, and a
+  small recovery capsule (`resource`, `node_type`, containment fields, and
+  relationship mode);
+- large or repeated machine state such as complete `code_symbols`, code
+  evidence, relationship records, candidate fingerprints, and optimization
+  decisions lives once in the corresponding `structure.yaml` view record;
+- Context readers hydrate that machine state in memory before verify, audit,
+  revision, or build. Do not copy a compact page as a new page without using a
+  Context authoring command;
 - do not nest Context production metadata under `context`; fields such as
   `context.sources` and `context.code_symbols` are not part of the 0.6 profile;
 - section provenance lives in `<!-- context:section ... source_ref="..." -->`
-  comments;
+  comments. When a Section needs more than one citation, the CLI preserves the
+  complete set in its adjacent `context:source_refs` block;
 - do not add frontmatter `source_refs`; page-level provenance is derived from
   section source refs when needed;
 - do not add `context` or `schema` fields.
@@ -340,7 +348,7 @@ src-N#span:<heading-hint> L<start>-<end>@<span-hash>
 
 The code symbol form includes the source-relative file so same-name symbols in
 different files resolve to one exact symbol-index row. Consumers should still
-treat the complete `source_ref` as opaque. Production codegraph pages keep
+treat the complete `source_ref` as opaque. Production codeindex pages keep
 `candidate_fingerprint` at the top level and do not duplicate this evidence in
 `code_origin`.
 
@@ -392,8 +400,8 @@ current closed state.
 
 Before writing output, `context build` validates that rendered template paths
 are safe, unique, and do not collide with copied knowledge paths. For example,
-a template file that renders to `wikis/codegraph/foo.md` is rejected if
-selected knowledge such as `knowledge/codegraph/foo.md` maps to that same OKF
+a template file that renders to `wikis/codeindex/foo.md` is rejected if
+selected knowledge such as `knowledge/codeindex/foo.md` maps to that same OKF
 output path. Rename the template file or use `select.exclude` when the
 collision is intentional.
 

package/docs/reference/project-api.md

@@ -29,7 +29,7 @@ the date:
 ```text
 knowledge/<collection>/<slug>.md
 knowledge/<collection>/<containment>/<slug>.md  # only for an intentional hierarchy
-knowledge/codegraph/<module>/symbol/<slug>.md
+knowledge/codeindex/<module>/symbol/<slug>.md
 repo:<date>/<module>#symbol:...
 file:<date>/<module>/<document>#span:...
 lark:<date>/<module>/<document>#span:...
@@ -41,12 +41,12 @@ dist/<source-name>-kb/...
 Choose the module boundary before extraction. In a monorepo, register each
 confirmed package/subdirectory under the same date batch. A repo root that
 resolves to multiple modules is for inspection; it is not an extraction unit.
-Approved codegraph paths use the stable module name; the date remains only in
+Approved codeindex paths use the stable module name; the date remains only in
 source selectors, phase ids, and evidence refs:
 
 ```text
-knowledge/codegraph/module-a/...
-knowledge/codegraph/module-b/...
+knowledge/codeindex/module-a/...
+knowledge/codeindex/module-b/...
 ```
 
 For prose Views, provide a stable filename `slug` and omit `path`; the CLI
@@ -57,7 +57,7 @@ it is not a required source/module wrapper.
 
 The registry stores this as one date entry containing several `modules` entries,
 and materializes each module at `sources/repo/<date>/<module>`.
-Repo module names are project-wide codegraph identities and therefore cannot be
+Repo module names are project-wide codeindex identities and therefore cannot be
 reused under another date batch. Refresh an existing module through its original
 date/module selector.
 When a repo module and the Context workspace share the same Git root, the CLI
@@ -402,7 +402,7 @@ alignProse({
 ```
 
 `collection` is an internal knowledge classification, not a package directory.
-Package build maps `codegraph`/`business`/`product` to `wikis/`,
+Package build maps `codeindex`/`business`/`product` to `wikis/`,
 `architecture`/`sop`/`faq`/`decision`/`incident` to `guides/`,
 `standards`/`test` to `rules/`, and `feats` to `feats/`. The complete output
 contract is documented in [Package Outputs](../guides/package-outputs.md).
@@ -592,7 +592,7 @@ Extract exported TypeScript / TSX symbols into draft candidates:
 ```ts
 extractTs({
   source: componentLib,
-  collection: "codegraph",
+  collection: "codeindex",
 });
 ```
 
@@ -601,7 +601,7 @@ Options:
 | Field | Meaning |
 |---|---|
 | `source` | `source("date", "module")` for one repo module |
-| `collection` | Code extraction uses `"codegraph"` |
+| `collection` | Code extraction uses `"codeindex"` |
 | `include` | Optional glob list inside the selected source; default is `["src/**/*.{ts,tsx}"]` |
 | `mode` | `"exports"` (default) traces public exports from automatic or configured entries; `"scan"` uses every file matched by `include` as an entry root |
 | `entries` | Optional source-relative entry files for `"exports"` mode. They override `package.json` entry detection and live only in the Context project configuration |
@@ -614,7 +614,7 @@ An explicit index unit records production intent rather than parser settings:
 ```ts
 extractTs({
   source: componentLib,
-  collection: "codegraph",
+  collection: "codeindex",
   indexUnits: [{
     id: "component-public-api",
     inputSources: ["20260712/component-lib"],
@@ -623,6 +623,7 @@ extractTs({
     moduleTypes: ["sdk-library"],
     facets: ["public-api", "plugin-extension"],
     moduleTypeEvidence: ["package.json exports and src/index.ts public entry"],
+    documents: ["README.md", "docs/public-api.md"],
     outputProfile: "public-api-reference",
     responsibility: "Document stable exported component contracts.",
     entries: ["src/index.ts"],
@@ -649,6 +650,9 @@ behaviors such as routing, protocol consumption, events, persistence, plugins,
 release, or cross-module chains. `moduleTypeEvidence` records the inspected
 paths that support the classification. Classify first, then read the matching
 Route-provided code-index templates, and only then finish the extraction plan.
+`documents` contains exact source-relative Markdown paths read for that plan;
+Context compares it with discovered module documents instead of treating a
+source-code comment as documentation coverage.
 `lifecycle` is `"authoritative"`, `"generated"`, `"mirrored"`, `"legacy"`,
 or `"vendored"`; derived sources normally use `"provenance-only"` rather
 than duplicating reader-facing pages. These are generic project facts, not
@@ -674,7 +678,7 @@ editing the source repository:
 ```ts
 extractTs({
   source: componentLib,
-  collection: "codegraph",
+  collection: "codeindex",
   include: ["src/**/*.ts"],
   entries: ["src/api.ts"],
 });
@@ -734,7 +738,7 @@ remain report signals and do not create another Gate.
 Phase id shape:
 
 ```text
-extract:<source-name-or-repo>:codegraph
+extract:<source-name-or-repo>:codeindex
 ```
 
 Codegraph extraction has two execution policies:
@@ -745,7 +749,7 @@ Codegraph extraction has two execution policies:
   the Agent re-evaluates `context status --format json`; only
   `workflow.current` decides whether Review is now required.
 - `context run <phase-id> --auto-promote` is the explicit CI/CD path. It is valid
-  only for `phase.extract.ts` codegraph phases, applies deterministic code deltas
+  only for `phase.extract.ts` codeindex phases, applies deterministic code deltas
   without Review, refreshes deterministic close when approved knowledge changed,
   then runs project verification. Close or verification errors make the command
   fail; JSON output reports applied/materialized/removed counts plus a `close`
@@ -757,7 +761,7 @@ other semantic knowledge. Agents must not infer a human gate from a phase-local
 result. Human gates and their inspection/resolution Actions are exposed only by
 `workflow.current`.
 
-Approved codegraph sections use the local evidence form
+Approved codeindex sections use the local evidence form
 `src-N#symbol:<file>:<symbol>:<kind>@<digest>`. The file segment makes reverse
 lookup exact when multiple files contain the same symbol name, kind, and digest;
 the complete ref remains opaque to agents. New pages keep only top-level
@@ -773,7 +777,7 @@ aggregated repository protocol:
 extractCustom({
   id: "extract:service:protocol",
   sources: [service],
-  collection: "codegraph",
+  collection: "codeindex",
   indexUnits: [{
     id: "service-protocol",
     inputSources: ["20260811/service"],
@@ -844,6 +848,12 @@ least one source-backed structured edge. `context status` therefore treats this
 pending code extraction target, and Review can verify snapshot freshness
 without a placeholder `extractTs` phase.
 
+Each `sections[].markdown` value is Section body content only; do not copy the
+template heading into it. Context renders `sections[].title` and rejects nested
+reader headings at the SDK boundary so empty template chapters cannot leak into
+knowledge. Evidence `symbol` and `kind` are canonical-ref tokens and cannot
+contain `:` or `@`; exact qualified signatures remain reader-facing prose.
+
 `indexUnits` is also the batch scale and ownership contract. Candidate
 `module` must match one declared unit id or output owner. Older callbacks that
 omit `indexUnits` remain compatible: Context groups candidates by `module` and
@@ -873,6 +883,21 @@ output profile. Coverage is based on source-backed evidence paths, not Markdown
 page count, so one aggregate page can pass while an entry-only static module
 card cannot.
 
+For a single-source index unit, Context also scans every represented language
+family and Markdown/MDX file after the unit's declared exclusions. The adapter's
+`eligibleFileTargets` and `eligibleLoc` must cover that independent baseline.
+Configuration files may be evidence, but a hand-picked evidence list cannot be
+reused as the source or LOC denominator. Cross-module-flow units remain scored
+against their declared entry, protocol, operation, and handoff boundaries rather
+than treating several repositories as one source-code page.
+
+The same baseline discovers conventional sibling page entries, route-register
+calls in Go router files, and exported receiver operations when a Go handler is
+the declared service source of truth. Every discovered identity must appear in
+the target-symbol and boundary denominators. An aggregate page may summarize
+these identities, but an adapter cannot list one representative sibling and
+silently omit the rest.
+
 The extractor returns knowledge semantics (`nodeRef`, rendered Markdown,
 Review summary and source-backed evidence). It must not write `knowledge/`,
 `.tmp/context-runtime/lifecycle/candidates.jsonl`, extraction fingerprints or
@@ -893,9 +918,9 @@ import { indexGoRepository } from "@c4a/extract-go";
 import { extractCustom } from "@c4a/context";
 
 extractCustom({
-  id: "extract:service:codegraph",
+  id: "extract:service:codeindex",
   sources: [service],
-  collection: "codegraph",
+  collection: "codeindex",
   extract: async ({ projectRoot }) => {
     const facts = await indexGoRepository(resolveServiceCheckout(projectRoot));
     return { candidates: buildServiceCandidates(facts) };
@@ -921,7 +946,7 @@ and its evidence coverage auditable before candidate writes.
 Declare the review step for a collection:
 
 ```ts
-reviewValidity({ collection: "codegraph" });
+reviewValidity({ collection: "codeindex" });
 ```
 
 Declare one review gate for all current draft collections:
@@ -933,7 +958,7 @@ reviewValidity({ scope: "all" });
 Phase id:
 
 ```text
-review:codegraph:validity
+review:codeindex:validity
 review:all:validity
 ```
 
@@ -959,7 +984,7 @@ continue wording does not invoke it.
 
 The gate is batch-scoped: prose waits for every planned View across all active
 structure slots and every declared `pendingStructureTargets` item in the round;
-codegraph waits for every pending extract phase in the confirmed module round.
+codeindex waits for every pending extract phase in the confirmed module round.
 Candidate count/hash therefore describes the complete current batch rather than
 one page, source slot, or module. Deterministic close later merges all active
 slots into `knowledge/structure.yaml`, retains only their source, collection,
@@ -989,13 +1014,13 @@ const sample = source("20260712", "sample");
 
 customPhase("custom:20260712/sample:review", async (ctx) => {
   await ctx.ensureSources({ source: sample });
-  await ctx.extract.ts(extractTs({ source: sample, collection: "codegraph" }));
-  await ctx.review.html(reviewValidity({ collection: "codegraph" }));
+  await ctx.extract.ts(extractTs({ source: sample, collection: "codeindex" }));
+  await ctx.review.html(reviewValidity({ collection: "codeindex" }));
 });
 ```
 
 Custom phases are an orchestration escape hatch. Use `extractCustom()` instead
-when project code needs to publish codegraph candidates. The supported runtime
+when project code needs to publish codeindex candidates. The supported runtime
 helpers are:
 
 - `ctx.ensureSources(...)` for repo source readiness.

package/index.d.ts

@@ -1,12 +1,12 @@
 import type { PackageNavigationDefinition, PackageSelectDefinition } from "./contracts.js";
 import type { PhaseDefinition, PhaseResourceReference } from "./phases.js";
 import type { ProjectSourceDefinition } from "./sources.js";
-export type { CodegraphCollection, DocumentMainlineCollection, EntityStatus, KnowledgeCollection, MainlineCollection, MarkdownTransform, FileCaptureProcessorDefinition, OkfRoot, PackageKind, PackageNavigationDefinition, PackageSelectDefinition, TopLevelNamespace, } from "./contracts.js";
+export type { CodegraphCollection, CodeIndexCollection, DocumentMainlineCollection, EntityStatus, KnowledgeCollection, MainlineCollection, MarkdownTransform, FileCaptureProcessorDefinition, OkfRoot, PackageKind, PackageNavigationDefinition, PackageSelectDefinition, TopLevelNamespace, } from "./contracts.js";
 export { assertDocumentMainlineCollection, assertKnowledgeCollection, assertMainlineCollection, assertOkfRoot, assertTopLevelNamespace, DOC_MAINLINE_COLLECTIONS, DEFAULT_PACKAGE_NAVIGATION, KNOWLEDGE_COLLECTIONS, MAINLINE_COLLECTIONS, OKF_ROOTS, TOP_LEVEL_NAMESPACES, } from "./contracts.js";
 export { assertDocumentEvidenceSectionMetadata, DOCUMENT_COMPILE_ACTION_SCHEMA_VERSION, DOCUMENT_EVIDENCE_SECTION_VALIDATION_STAGES, DOCUMENT_SECTION_CONTENT_MODES, DOCUMENT_STRUCTURE_SCHEMA_VERSION, } from "./documentEvidence.js";
 export type { DocumentEvidenceSectionMetadata, DocumentEvidenceSectionValidationOptions, DocumentEvidenceSectionValidationStage, DocumentSectionContentMode, } from "./documentEvidence.js";
 export { alignProse, captureFile, captureLark, compileProse, CODE_INDEX_CAPABILITIES, CODE_INDEX_COVERAGE_KINDS, CODE_INDEX_LIFECYCLES, CODE_INDEX_MODULE_FACETS, CODE_INDEX_MODULE_TYPES, CODE_INDEX_OUTPUT_PROFILES, customPhase, extractCustom, extractTs, ExtractTsConfigurationError, NO_ENTRY_DETECTED, requiredCodeIndexCoverage, mdxJsonDocs, reviewValidity, } from "./phases.js";
-export type { AlignProsePhaseDefinition, CaptureFilePhaseDefinition, CaptureLarkPhaseDefinition, CompileProsePhaseDefinition, ContextPhase, ContextPhaseContext, CustomPhaseDefinition, CustomCodeCandidateDraft, CustomCodeCandidateEdge, CustomCodeCandidateSection, CustomCodeCandidateReview, CustomCodeEvidence, CustomCodeExtractionContext, CustomCodeExtractionResult, CustomCodeExtractor, CodeIndexCapability, CodeIndexCapabilityGap, CodeIndexCoverageKind, CodeIndexInspectionAdapter, CodeIndexInspectionContext, CodeIndexInspectionFinding, CodeIndexInspectionFindingKind, CodeIndexInspectionResult, CodeIndexLifecycle, CodeIndexModuleFacet, CodeIndexModuleType, CodeIndexOutputProfile, CodeIndexUnitPlan, ExtractCustomPhaseDefinition, ExtractTsPhaseDefinition, PhaseDefinition, PhaseResourceReference, ReviewValidityPhaseDefinition, ReviewValidityScope, } from "./phases.js";
+export type { AlignProsePhaseDefinition, CaptureFilePhaseDefinition, CaptureLarkPhaseDefinition, CompileProsePhaseDefinition, ContextPhase, ContextPhaseContext, CustomPhaseDefinition, CustomCodeCandidateDraft, CustomCodeCandidateEdge, CustomCodeCandidateSection, CustomCodeCandidateReview, CustomCodeEvidence, CustomCodeExtractionContext, CustomCodeExtractionResult, CustomCodeExtractor, CodeIndexCapability, CodeIndexCapabilityGap, CodeIndexCoverageKind, CodeIndexInspectionAdapter, CodeIndexInspectionContext, CodeIndexInspectionFinding, CodeIndexInspectionFindingKind, CodeIndexInspectionInventory, CodeIndexInspectionResult, CodeIndexLifecycle, CodeIndexModuleFacet, CodeIndexModuleType, CodeIndexOutputProfile, CodeIndexUnitPlan, ExtractCustomPhaseDefinition, ExtractTsPhaseDefinition, PhaseDefinition, PhaseResourceReference, ReviewValidityPhaseDefinition, ReviewValidityScope, } from "./phases.js";
 export { allSources, DEFAULT_FILE_SOURCES_REGISTRY_PATH, DEFAULT_LARK_SOURCES_REGISTRY_PATH, DEFAULT_REPO_SOURCES_REGISTRY_PATH, loadSourcesRegistry, resolveSourceReference, source, } from "./sources.js";
 export type { DocumentSourceDefinition, DocumentSourceReference, DocumentSourceType, FileSourceDefinition, FileSourceReference, FileSourceRegistryEntry, LarkSourceDefinition, LarkSourceReference, LarkSourceRegistryEntry, LoadSourcesRegistryOptions, ProjectSourceDefinition, RepoProjectSourceDefinition, RepoSourceDefinition, RepoSourceReference, RepoSourceRegistryEntry, RepoSourcesRegistry, SourceCollectionReference, SourceDefinition, SourceReference, SourcesRegistry, SourceType, } from "./sources.js";
 export type TemplateVarValue = string | number | boolean | null | Record<string, unknown> | readonly Record<string, unknown>[];

package/index.js

@@ -6931,7 +6931,7 @@ var DOC_MAINLINE_COLLECTIONS = [
   "incident",
   "test"
 ];
-var MAINLINE_COLLECTIONS = ["codegraph", ...DOC_MAINLINE_COLLECTIONS];
+var MAINLINE_COLLECTIONS = ["codeindex", "codegraph", ...DOC_MAINLINE_COLLECTIONS];
 var TOP_LEVEL_NAMESPACES = [...MAINLINE_COLLECTIONS, "feats"];
 var OKF_ROOTS = ["guides", "rules", "wikis", "feats"];
 var KNOWLEDGE_COLLECTIONS = TOP_LEVEL_NAMESPACES;
@@ -7158,6 +7158,9 @@ function normalizeIndexUnit(unit, field) {
     ...unit.moduleTypeEvidence === undefined ? {} : {
       moduleTypeEvidence: unit.moduleTypeEvidence.map((item, index) => requiredIndexText(item, `${field}.moduleTypeEvidence[${index}]`))
     },
+    ...unit.documents === undefined ? {} : {
+      documents: [...new Set(unit.documents.map((item, index) => normalizeExtractEntry(requiredIndexText(item, `${field}.documents[${index}]`))))]
+    },
     outputProfile: requiredIndexEnum(unit.outputProfile, `${field}.outputProfile`, CODE_INDEX_OUTPUT_PROFILES),
     responsibility: requiredIndexText(unit.responsibility, `${field}.responsibility`),
     entries: unit.entries.map((entry, index) => requiredIndexText(entry, `${field}.entries[${index}]`)),
@@ -7377,8 +7380,8 @@ var compileProse = (definition) => {
 };
 var extractTs = (definition) => {
   const sourceDefinition = bindSourceType(definition.source, "repo", "extractTs source");
-  if (definition.collection !== "codegraph") {
-    throw new TypeError(`extractTs collection must be codegraph: ${definition.collection}`);
+  if (definition.collection !== "codeindex" && definition.collection !== "codegraph") {
+    throw new TypeError(`extractTs collection must be codeindex or legacy codegraph: ${definition.collection}`);
   }
   const sourceId = sourceDefinition.kind === "source.collection" ? sourceDefinition.type : sourceDefinition.name;
   const mode = definition.mode ?? "exports";
@@ -7390,11 +7393,12 @@ var extractTs = (definition) => {
   }
   const entries = definition.entries === undefined ? undefined : [...new Set(definition.entries.map(normalizeExtractEntry))];
   const defaultSourceName = sourceDefinition.kind === "source.collection" ? sourceDefinition.type : sourceDefinition.name;
+  const defaultOutputOwner = defaultSourceName.split("/").at(-1) ?? defaultSourceName;
   const exportedOnly = definition.exportedOnly ?? mode === "exports";
   const indexUnits = (definition.indexUnits ?? (sourceDefinition.kind === "source.collection" ? [] : [{
-    id: defaultSourceName,
+    id: defaultOutputOwner,
     inputSources: [defaultSourceName],
-    outputOwner: defaultSourceName,
+    outputOwner: defaultOutputOwner,
     moduleType: mode === "exports" ? "sdk-library" : "unknown",
     moduleTypes: [mode === "exports" ? "sdk-library" : "unknown"],
     facets: mode === "exports" ? ["public-api"] : [],
@@ -7448,8 +7452,8 @@ var extractCustom = (definition) => {
     throw new TypeError("extractCustom id must be a non-empty phase id");
   if (definition.sources.length === 0)
     throw new TypeError("extractCustom sources must contain at least one repo source");
-  if (definition.collection !== "codegraph") {
-    throw new TypeError(`extractCustom collection must be codegraph: ${definition.collection}`);
+  if (definition.collection !== "codeindex" && definition.collection !== "codegraph") {
+    throw new TypeError(`extractCustom collection must be codeindex or legacy codegraph: ${definition.collection}`);
   }
   const sources = definition.sources.map((sourceDefinition) => bindSourceType(sourceDefinition, "repo", "extractCustom source"));
   const indexUnits = (definition.indexUnits ?? []).map((unit, index) => normalizeIndexUnit(unit, `extractCustom indexUnits[${index}]`));
@@ -11744,7 +11748,7 @@ var parseRepoSourcesRegistry = (input, registryPath, absolutePath) => {
         assertSourceName("repo", entry.id, registryPath);
       const existingNamespace = moduleNamespaces.get(entry.name);
       if (existingNamespace !== undefined && existingNamespace !== namespace) {
-        throw new TypeError(`Duplicate repo module ${JSON.stringify(entry.name)} across date batches ${existingNamespace} and ${namespace} in ${registryPath}; repo module names are project-wide codegraph identities`);
+        throw new TypeError(`Duplicate repo module ${JSON.stringify(entry.name)} across date batches ${existingNamespace} and ${namespace} in ${registryPath}; repo module names are project-wide code-index identities`);
       }
       moduleNamespaces.set(entry.name, namespace);
       const name = `${namespace}/${entry.name}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context",
-  "version": "0.6.18",
+  "version": "0.6.19",
   "type": "module",
   "description": "Declarative SDK for Context knowledge sources, workflows, review, and package outputs",
   "license": "MIT",

package/phases.d.ts

@@ -1,8 +1,8 @@
-import { type FileCaptureProcessorDefinition, type KnowledgeCollection, type MarkdownTransform, type PackageKind, type PackageSelectDefinition, type DocumentMainlineCollection } from "./contracts.js";
+import { type FileCaptureProcessorDefinition, type CodeIndexCollection, type KnowledgeCollection, type MarkdownTransform, type PackageKind, type PackageSelectDefinition, type DocumentMainlineCollection } from "./contracts.js";
 import { DOCUMENT_COMPILE_ACTION_SCHEMA_VERSION } from "./documentEvidence.js";
 import { type CodeIndexCoverageKind, type CodeIndexInspectionAdapter, type CodeIndexUnitPlan } from "./codeIndexPlan.js";
 export { CODE_INDEX_CAPABILITIES, CODE_INDEX_COVERAGE_KINDS, CODE_INDEX_LIFECYCLES, CODE_INDEX_MODULE_FACETS, CODE_INDEX_MODULE_TYPES, CODE_INDEX_OUTPUT_PROFILES, ExtractTsConfigurationError, NO_ENTRY_DETECTED, requiredCodeIndexCoverage, } from "./codeIndexPlan.js";
-export type { CodeIndexCapability, CodeIndexCapabilityGap, CodeIndexCoverageKind, CodeIndexInspectionAdapter, CodeIndexInspectionContext, CodeIndexInspectionFinding, CodeIndexInspectionFindingKind, CodeIndexInspectionResult, CodeIndexLifecycle, CodeIndexModuleFacet, CodeIndexModuleType, CodeIndexOutputProfile, CodeIndexUnitPlan, } from "./codeIndexPlan.js";
+export type { CodeIndexCapability, CodeIndexCapabilityGap, CodeIndexCoverageKind, CodeIndexInspectionAdapter, CodeIndexInspectionContext, CodeIndexInspectionFinding, CodeIndexInspectionFindingKind, CodeIndexInspectionInventory, CodeIndexInspectionResult, CodeIndexLifecycle, CodeIndexModuleFacet, CodeIndexModuleType, CodeIndexOutputProfile, CodeIndexUnitPlan, } from "./codeIndexPlan.js";
 import type { DocumentSourceDefinition, DocumentSourceType, FileSourceDefinition, FileSourceReference, LarkSourceDefinition, LarkSourceReference, RepoProjectSourceDefinition, SourceCollectionReference, SourceDefinition } from "./sources.js";
 export type PhaseResourceReference = {
     kind: "source";
@@ -64,7 +64,7 @@ export type ExtractTsPhaseDefinition = {
     reads: readonly PhaseResourceReference[];
     writes: readonly PhaseResourceReference[];
     source: RepoProjectSourceDefinition;
-    collection: "codegraph";
+    collection: CodeIndexCollection;
     include: readonly string[];
     mode: "exports" | "scan";
     entries?: readonly string[];
@@ -82,7 +82,9 @@ export type ExtractTsPhaseDefinition = {
 export interface CustomCodeEvidence {
     source: string;
     file: string;
+    /** Stable canonical-ref token. Do not include ':' or '@'; keep exact signatures in Section prose. */
     symbol: string;
+    /** Stable canonical-ref token. Do not include ':' or '@'. */
     kind: string;
     digest: string;
     line?: number;
@@ -106,6 +108,7 @@ export interface CustomCodeCandidateSection {
     id: string;
     kind: CodeIndexCoverageKind;
     title: string;
+    /** Reader-facing Section body only. Context renders the heading from title. */
     markdown: string;
     evidence: readonly CustomCodeEvidence[];
 }
@@ -114,9 +117,8 @@ export interface CustomCodeCandidateDraft {
     kind: string;
     visibility: string;
     module: string;
-    markdown?: string;
-    /** Evidence-scoped aggregate sections used to prove output-profile coverage. */
-    sections?: readonly CustomCodeCandidateSection[];
+    /** Required evidence-scoped sections used to render the page and prove output-profile coverage. */
+    sections: readonly CustomCodeCandidateSection[];
     evidence: readonly CustomCodeEvidence[];
     review: CustomCodeCandidateReview;
     edges?: readonly CustomCodeCandidateEdge[];
@@ -141,7 +143,7 @@ export type ExtractCustomPhaseDefinition = {
     reads: readonly PhaseResourceReference[];
     writes: readonly PhaseResourceReference[];
     sources: readonly RepoProjectSourceDefinition[];
-    collection: "codegraph";
+    collection: CodeIndexCollection;
     indexPlan: "declared" | "inferred";
     indexUnits: readonly CodeIndexUnitPlan[];
     inspect?: CodeIndexInspectionAdapter;
@@ -239,7 +241,7 @@ export declare const compileProse: (definition: {
 }) => CompileProsePhaseDefinition;
 export declare const extractTs: (definition: {
     source: RepoProjectSourceDefinition;
-    collection: "codegraph";
+    collection: CodeIndexCollection;
     include?: readonly string[];
     mode?: "exports" | "scan";
     entries?: readonly string[];
@@ -250,7 +252,7 @@ export declare const extractTs: (definition: {
 export declare const extractCustom: (definition: {
     id: string;
     sources: readonly RepoProjectSourceDefinition[];
-    collection: "codegraph";
+    collection: CodeIndexCollection;
     indexUnits?: readonly CodeIndexUnitPlan[];
     inspect?: CodeIndexInspectionAdapter;
     extract: CustomCodeExtractor;

package/templates/package-templates/kb/AGENTS.md

@@ -18,7 +18,7 @@ Selected OKF root directories such as `{{wikisRoot}}/`, `{{guidesRoot}}/`,
 `{{rulesRoot}}/`, and `{{featsRoot}}/` follow an OKF-compatible Context profile:
 OKF fields and Context extension fields stay at the top level, and no `context`
 or `schema` field is emitted. Root mapping:
-`{{wikisRoot}}/` maps from structured `codegraph`, `business`, and `product` knowledge;
+`{{wikisRoot}}/` maps from structured `codeindex`, `business`, and `product` knowledge;
 `{{guidesRoot}}/` maps from `architecture`, `sop`, `faq`, `decision`, and `incident`;
 `{{rulesRoot}}/` maps from `standards` and `test`; `{{featsRoot}}/` maps from `feats`. Treat
 `{{wikisRoot}}/` as the entity-and-relationship layer; guides and rules may

package/templates/package-templates/kb/skills/knowledge-query/SKILL.md

@@ -29,7 +29,7 @@ as evidence rather than relying on memory or frontmatter summaries.
 
 | Root | Use |
 |---|---|
-| `{{wikisRoot}}/` | Structured entities and relationships from codegraph, business, and product knowledge. |
+| `{{wikisRoot}}/` | Structured entities and relationships from codeindex, business, and product knowledge. |
 | `{{guidesRoot}}/` | Architecture, procedures, FAQs, decisions, incidents, and troubleshooting. |
 | `{{rulesRoot}}/` | Standards, constraints, acceptance criteria, and test scenarios. |
 | `{{featsRoot}}/` | Feature knowledge when selected into the package. |

package/templates/package-templates.zh-CN/kb/AGENTS.md

@@ -14,7 +14,7 @@
 
 包内可能包含以下 OKF 根目录：
 
-- `{{wikisRoot}}/`：结构化实体和关系，对应 codegraph、business、product。
+- `{{wikisRoot}}/`：结构化实体和关系，对应 codeindex、business、product。
 - `{{guidesRoot}}/`：架构、流程、FAQ、决策和故障记录。
 - `{{rulesRoot}}/`：标准、约束、验收条件和测试场景。
 - `{{featsRoot}}/`：被选择进入包内的功能知识。

package/templates/package-templates.zh-CN/kb/skills/knowledge-query/SKILL.md

@@ -20,7 +20,7 @@ description: 查询 {{displayName}} 中经过审核、可追溯来源的知识
 
 | 根目录 | 用途 |
 |---|---|
-| `{{wikisRoot}}/` | 来自 codegraph、business、product 的结构化实体和关系。 |
+| `{{wikisRoot}}/` | 来自 codeindex、business、product 的结构化实体和关系。 |
 | `{{guidesRoot}}/` | 架构、流程、FAQ、决策、故障和排障说明。 |
 | `{{rulesRoot}}/` | 标准、约束、验收条件和测试场景。 |
 | `{{featsRoot}}/` | 被选择进入包内的功能知识。 |