@c4a/context-cli 0.6.1 → 0.6.3

package/providers/context/resources/manuals/guides/package-outputs.md

@@ -0,0 +1,267 @@
+---
+id: context.sdk.package-outputs
+kind: procedure
+mediaType: text/markdown
+---
+
+# Package Outputs
+
+Package outputs are generated folders under `dist/`. They turn approved
+knowledge from `knowledge/` into a shape that another consumer can install,
+read, or import.
+
+Package output is a human decision gate. Do not add package declarations until
+the user chooses the intended consumer and output shape.
+
+Package build consumes approved and closed knowledge. If status reports that
+close is required, run deterministic close before build. Current close derives
+`knowledge/structure.yaml`, persists approved edge projection, and runs the
+final verify gate without rewriting approved Markdown. References, changelog,
+package index, and section fingerprint rebuilds are not current close output.
+
+## Recommended First Output: Agent Knowledge-Base Package
+
+Choose an agent knowledge-base package first when the knowledge should help
+Coding Agents work with the project. After the user chooses this semantic
+output shape, implement it with `kbPackage()`.
+
+Typical output:
+
+```text
+dist/<package-name>/
+├── AGENTS.md
+├── skills/
+│   └── knowledge-query/
+│       └── SKILL.md
+└── wikis/
+    ├── index.md
+    └── ...
+```
+
+Choose this when the user wants:
+
+- agent-facing guidance generated from the reviewed knowledge;
+- a package that can be installed as an agent knowledge base;
+- a starting point that can later be refined into task-specific skills.
+
+The underlying `kbPackage()` declaration requires a template containing at
+least one `SKILL.md` and `wikis/index.md`.
+The default `src/package-templates/kb/` template is only a starting point.
+Inspect the generated `dist/<package-name>/` before calling it usable.
+
+KB packages use flat package-relative knowledge roots:
+
+```ts
+kbPackage({
+  name: "component-lib-kb",
+  template: "src/package-templates/kb",
+});
+```
+
+The package name already identifies the surrounding build folder, so the
+output does not repeat it inside each root:
+
+```text
+skills/knowledge-query/SKILL.md
+wikis/index.md
+guides/...
+rules/...
+feats/...
+others/assets/...
+```
+
+Do not ask for another distribution namespace. Older workspaces may still
+contain `distribution.knowledgeNamespace`; Context accepts that legacy input
+without using it to shape the package.
+
+Skill names are separate. Ask whether the author wants a short optional Skill
+prefix, then maintain the complete final template directory name directly—for
+example `skills/android-query/SKILL.md`. Package-root layout never renames a
+Skill.
+
+The default `knowledge-query` Skill is a complete generic query entry. It
+carries the structure-first query discipline: start from OKF directory indexes, use
+`context-build-inventory.json` edge records for package-visible relationships,
+inspect page `sources` / `context:section` source_ref metadata, cite
+page/section evidence, and report explicit gaps when the package does not cover
+a requested fact. It does not treat direct grep over bundled OKF root
+directories as the primary discovery path. When indexes do not narrow the
+scope, or a candidate page is too large to read directly, its bundled
+`scripts/search.mjs` provides deterministic BM25 ranking over mechanically
+bounded Markdown chunks. Search results are leads; page bodies and typed edge
+records remain the evidence. Its final template-author section
+requires package authors to replace or edit the generic routing when the
+package needs project-specific terminology, entry points, known limits, or
+task workflows. Authors may explicitly accept the generic default when it is
+intentionally sufficient.
+
+When approved pages reference materialized document resources, Context keeps
+their production copies in content-addressed `knowledge/assets/` paths. Build
+copies only the resources selected by package pages to `others/assets/` and
+rewrites relative Markdown links. Source audit XML and capture reports stay in
+the production workspace; they are not 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
+edges were emitted. An empty edge list is therefore explicit evidence of a
+coverage state, not permission to invent a dependency.
+
+The generated `wikis/` directory is the default OKF root and follows the C4A OKF
+Profile. Internal production collections are mapped into package OKF roots such
+as `wikis/`, `guides/`, `rules/`, or `feats/`; when selected, `context build`
+copies them into the package and generates root-aware directory indexes for them
+as needed. Selected OKF roots always have an index; smaller child directories
+are folded into their nearest generated ancestor index by default. These roots
+contain consumer-oriented Markdown with reader-facing frontmatter and no Context
+lifecycle comments. Node identity, source metadata, code symbol lists,
+relationship records, generated-child records, and candidate fingerprints are
+kept out of each page. `context-build-inventory.json` maps distributed paths to
+approved knowledge paths and exposes package-visible structure; exact Section
+evidence remains in the mapped `knowledge/` page. The package root is an agent
+package; the OKF-compatible interchange surface is the selected OKF root
+subtrees under `dist/<package-name>/`. The required template entry and final
+output path are both `wikis/index.md`.
+
+Current collection mapping:
+
+| Internal collection | Package path | Role |
+|---|---|---|
+| `codegraph` | `wikis/codegraph/` | Structured code entities and 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. |
+| `sop` | `guides/sop/` | Procedures and runbooks. |
+| `faq` | `guides/faq/` | Question-oriented explanations and troubleshooting. |
+| `decision` | `guides/decision/` | Decision records and trade-off narratives. |
+| `incident` | `guides/incident/` | Incident timelines, response, and follow-up. |
+| `standards` | `rules/standards/` | Normative standards and constraints. |
+| `test` | `rules/test/` | Validation rules, scenarios, and acceptance checks. |
+| `feats` | `feats/` | Feature capability records. |
+
+`wikis/` is the structured entity-and-relationship layer. `guides/` and
+`rules/` may explain, operationalize, or constrain that knowledge; their
+placement does not create a relationship unless Context includes a typed edge.
+
+`index.md` is reserved for OKF bundle and directory indexes. Source documents
+may be named `index.md`, but generated concept pages must use a non-reserved
+name such as `index-page.md`; `context build` rejects copied knowledge that
+occupies `wikis/**/index.md`.
+
+`src/package-templates/kb/wikis/index.md` is the bundle entry page template.
+Tell the user it can be edited before build to describe the package scope,
+intended users, and query guidance.
+
+The default root index is a usable generic entry, not a project-specific
+information architecture.
+It links directly to pages in small child directories and to a child
+`index.md` when that directory exceeds the configured navigation threshold.
+The default threshold is 50 selected knowledge pages. Use Handlebars variables such as
+`knowledgeGroups`, `knowledgeItems`, and `knowledgeTree` when a project needs
+custom navigation. Before customizing it, read
+`node_modules/@c4a/context/docs/reference/template-variables.md`.
+
+Newly initialized generic templates must be replaced, edited, or explicitly
+accepted before the first build. `context status` exposes that choice as a
+package template Review Gate. Use only the revision-bound command returned by
+that Route to accept an unchanged generic default; edit files under
+`src/package-templates/` when customizing. Context compares file digests and
+records the decision without evaluating the meaning of template prose.
+
+Template paths are rendered before selected knowledge is copied. A rendered
+template path must not collide with a selected knowledge path. If the build
+reports a collision, rename the template file or exclude that knowledge path
+with `select.exclude`.
+
+Template prose must not become a second knowledge source. If a template
+describes package coverage, scope, known gaps, or known limits, it must cite
+approved knowledge, `context-build-inventory.json`, or rendered structure data
+inside the package. Otherwise `context build` reports a template-boundary
+diagnostic. Repair the template under `src/package-templates/`; do not patch
+`dist/` as the durable fix.
+
+KB package index links are also checked. `context build` validates every
+selected OKF root index and generated child `index.md` so relative links and
+OKF bundle-root absolute links resolve inside `dist/<package-name>/`. Broken
+index links are fixed by editing the template, approved knowledge path, or
+package declaration and rerunning `context build`; do not patch `dist/`
+directly as the durable fix.
+
+## Alternative Output: LLM Text
+
+Choose an LLM text bundle when the user wants a single text bundle for model
+context, RAG import, or manual reading. After the user chooses this semantic
+output shape, implement it with `llmsPackage()`.
+
+Typical output:
+
+```text
+dist/<package-name>/
+└── llms.txt
+```
+
+Choose this when the user wants:
+
+- one consolidated text file;
+- a format that is easy to copy, index, or upload elsewhere;
+- no agent skill packaging yet.
+
+## Skip Package Output
+
+The user may choose to stop after approved Markdown. In that case, keep
+`packages: []` and do not run `context build`.
+
+Approved knowledge still lives in:
+
+```text
+knowledge/
+└── ...
+```
+
+## How To Ask The User
+
+When `workflow.current.reason_code` is `route.package.output-required`,
+explain the choices with the output tree. Do not ask the user to pick from
+unexplained labels.
+Use the host's native multi-choice tool when available. If unavailable, fall
+back to a short Markdown A/B/C question. The option labels should be:
+agent knowledge-base package, LLM text bundle, and skip package output for now.
+
+Recommended question shape:
+
+```text
+The reviewed knowledge is approved. The next decision is how to package it.
+
+Recommended: agent knowledge-base package
+dist/<name>-kb/
+├── AGENTS.md
+├── skills/knowledge-query/SKILL.md
+└── wikis/
+    ├── index.md
+    ├── <group-page>.md
+    └── <large-group>/index.md
+
+This is best if agents should use the knowledge as a reusable knowledge base.
+
+Alternative: LLM text bundle
+dist/<name>-llms/
+└── llms.txt
+
+This is best if you need one text bundle for model/RAG import.
+
+We can also skip package output for now and keep only knowledge/.
+
+Which one should I declare first?
+```
+
+If the user chooses the Agent knowledge-base package, explain that its OKF
+roots are flat within `dist/<package-name>/`; do not ask for a second namespace.
+Ask whether its Skills need a short prefix. The author maintains final Skill
+names independently from package paths.
+
+Do not offer `both` as a shortcut. If the user wants multiple outputs, add one
+package first, verify the shape, then add another package after confirmation.
+The default adaptive index policy avoids one-page directory indexes. Configure
+`kbPackage().navigation` when a package needs a different inline-entry
+threshold or a fully expanded index at every directory.

package/providers/context/resources/manuals/reference/package-templates.md

@@ -0,0 +1,378 @@
+---
+id: context.sdk.package-templates
+kind: procedure
+mediaType: text/markdown
+---
+
+# Package Templates
+
+Packages project approved knowledge into `dist/<package-name>/`.
+
+For the user-facing decision process, read
+[Package Outputs](../guides/package-outputs.md) first. This reference only
+documents the API and template behavior.
+
+## Package Factories
+
+```ts
+import { llmsPackage, kbPackage } from "@c4a/context";
+```
+
+### `kbPackage`
+
+```ts
+kbPackage({
+  name: "component-lib-kb",
+  template: {
+    path: "src/package-templates/kb",
+    vars: { displayName: "Component Library KB" },
+  },
+  select: {
+    collections: ["architecture", "sop"],
+    okfRoots: ["wikis", "guides"],
+    include: ["architecture/component-lib/**", "sop/component-lib/**"],
+    exclude: ["**/internal/**"],
+  },
+  navigation: {
+    foldDirectoryIndexes: true,
+    maxInlineEntries: 50,
+  },
+});
+```
+
+### `llmsPackage`
+
+```ts
+llmsPackage({
+  name: "component-lib-llms",
+  template: "src/package-templates/llms",
+  select: { include: ["codegraph/component-lib/**"] },
+});
+```
+
+## Required Fields
+
+| Field | Required | Meaning |
+|---|---:|---|
+| `name` | yes | Lowercase path-safe package name. Output goes to `dist/<name>/`. |
+| `template` | yes | Project-relative template directory or `{ path, vars }`. |
+| `select` | no | Approved knowledge selector. Omit to include all approved knowledge. Supports internal `collections`, OKF `okfRoots`, and `include` / `exclude` path patterns relative to `knowledge/`. |
+| `navigation` | no | KB directory-index policy. Defaults to `{ foldDirectoryIndexes: true, maxInlineEntries: 50 }`. |
+| `distribution` | no | Legacy input accepted from older workspaces. It no longer changes package paths and should not be added to new declarations. |
+
+`template` is required. Do not call `kbPackage({ name })` or
+`llmsPackage({ name })`.
+
+## Flat Package Roots
+
+`name` identifies the package boundary under `dist/`. Context does not repeat
+that name inside the package's knowledge roots.
+
+Templates keep a logical, consumer-neutral layout:
+
+```text
+skills/knowledge-query/SKILL.md
+wikis/index.md
+guides/...
+rules/...
+feats/...
+```
+
+For `name: "component-lib-kb"`, `context build` writes:
+
+```text
+skills/knowledge-query/SKILL.md
+wikis/index.md
+guides/...
+rules/...
+feats/...
+```
+
+The builder maps copied knowledge, generated indexes, links, and inventory
+records into these roots without rewriting Markdown prose or inferring a
+downstream registry identity. New declarations should omit `distribution`.
+Older declarations that still contain `distribution.knowledgeNamespace` remain
+loadable, but the value does not change output paths or the build fingerprint.
+
+Use `{{wikisRoot}}`, `{{rulesRoot}}`, `{{guidesRoot}}`, or `{{featsRoot}}` in
+Skill templates so references share the package-root contract. These variables
+render to the flat root names above.
+
+Each rendered Skill must live at `skills/<skill-name>/SKILL.md`, and its YAML
+frontmatter `name` must equal `<skill-name>`. Use `{{skillName}}` in custom
+Skill templates. Skill names are author-maintained: when a short prefix is
+useful, rename the template directory to the complete final name, such as
+`skills/android-query/`; Context does not derive it from
+the package name.
+
+## Template Variables
+
+Templates are rendered with Handlebars. Variables are available in both file
+contents and file paths.
+
+Built-in variables:
+
+| Variable | Meaning |
+|---|---|
+| `{{packageName}}` | Package name from the declaration. |
+| `{{packageKind}}` | `kb` or `llms`. |
+| `{{knowledgeNamespace}}` | Legacy configured namespace when an older workspace still declares one; otherwise empty. Do not use it for new output paths. |
+| `{{namespacedKnowledge}}` | Always `false`; retained only so older templates remain renderable. |
+| `{{skillName}}` | Current author-maintained Skill directory name. |
+| `{{skillPath}}` | Current Skill's final package-relative `SKILL.md` path. |
+| `{{wikisRoot}}`, `{{guidesRoot}}`, `{{rulesRoot}}`, `{{featsRoot}}` | Final package-relative OKF root paths. |
+| `{{displayName}}` | Display name. Defaults to a title-cased `packageName`; override with `template.vars.displayName`. |
+| `{{knowledgeCount}}` | Number of selected approved Markdown files. |
+| `{{knowledgeTimestamp}}` | Latest `timestamp` from selected approved Markdown, or `1970-01-01T00:00:00.000Z` when empty. |
+| `{{knowledge}}` | Concatenated selected approved Markdown bundle. |
+| `{{approvedKnowledge}}` | Alias for `{{knowledge}}`. |
+| `{{knowledgeItems}}` | Array of selected approved knowledge page metadata for loops. |
+| `{{knowledgeGroups}}` | Selected approved knowledge pages grouped by OKF root and first directory segment; each item also exposes `internal_collection`. |
+| `{{knowledgeTreeNodes}}` | Nested path tree for custom navigation. |
+| `{{knowledgeTree}}` | Markdown tree preview. |
+| `{{knowledgeItemsMarkdown}}` | Markdown page list. |
+| `{{knowledgeGroupsMarkdown}}` | Markdown navigation for the current index: direct page links for folded directories and links to generated indexes for expanded directories. |
+
+Custom variables come from `template.vars`.
+
+For loops, conditionals, comments, and record fields, read
+[Template Variables](./template-variables.md).
+
+## Template Examples
+
+Installed examples:
+
+```text
+node_modules/@c4a/context/templates/package-templates/kb/
+node_modules/@c4a/context/templates/package-templates/llms/
+```
+
+Workspace convention:
+
+```text
+src/package-templates/
+├── kb/
+│   ├── AGENTS.md
+│   ├── wikis/
+│   │   └── index.md
+│   └── skills/
+│       └── knowledge-query/
+│           ├── SKILL.md
+│           └── scripts/
+│               └── search.mjs
+└── llms/
+    └── llms.txt
+```
+
+`kbPackage()` is for an agent knowledge-base package. The package still uses a
+`skills/` folder internally because Claude/Codex consume reusable agent
+instructions from that convention. Its template must contain at least one
+`SKILL.md` file and `wikis/index.md`. A template with only `AGENTS.md` is a
+placeholder document package, not a usable kb package, and `context build`
+rejects it.
+
+The default kb template includes:
+
+- `skills/knowledge-query/SKILL.md`, a reusable skill that teaches agents to
+  query copied knowledge pages structure-first, cite page/section evidence, use
+  `context-build-inventory.json` edge records for package-visible
+  relationships, and report gaps instead of inventing unsupported answers. The
+  build inventory also exposes `structure.relationship_coverage` so a consumer
+  can distinguish an observed zero-edge result from unknown relationship
+  coverage. The
+  default entry OKF root is `wikis/`; packages that select additional internal
+  collections expose
+  `guides/`, `rules/`, or `feats/` indexes when those roots are selected.
+- `skills/knowledge-query/scripts/search.mjs`, a dependency-free BM25 fallback
+  for exact terms, mixed keyword queries, and large Markdown indexes. It chunks
+  mechanically, returns inspectable paths and line ranges, and never replaces
+  source-backed relationship evidence.
+- `wikis/index.md`, the editable OKF bundle entry page for the generated
+  `dist/<package-name>/wikis/` directory.
+
+During `context build`, the root `wikis/index.md` is rendered from the template.
+The builder always provides an index for every selected OKF root. With the
+default navigation policy, smaller child directories are folded into their
+nearest generated ancestor index, so a short collection can link directly to
+its pages instead of producing one index per path segment.
+
+## OKF Directory Indexes
+
+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`,
+`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,
+or constrain that knowledge, but directory placement alone does not establish
+a relationship.
+
+Default navigation rules:
+
+- `wikis/index.md` is the required default bundle index. Other selected OKF
+  roots always use their own `<okf-root>/index.md`.
+- With `foldDirectoryIndexes: true`, a non-root directory gets its own
+  `index.md` only when its descendant knowledge-page count is greater than
+  `maxInlineEntries`. The default threshold is `50`.
+- A folded directory is not discarded. Its pages are listed in the nearest
+  generated ancestor index, grouped by their relative directory path.
+- The threshold counts selected knowledge pages in the path tree. It does not
+  inspect Markdown line counts, headings, or content semantics.
+- Set `foldDirectoryIndexes: false` to generate an `index.md` for every
+  directory, matching the fully expanded navigation shape.
+- A generated directory index uses OKF frontmatter with `type: Knowledge
+  Directory`, `title`, `description`, `tags`, `timestamp`, `resource`,
+  `package`, `package_kind`, and `knowledge_count`.
+- Directory indexes list generated child indexes first, then pages from folded
+  paths.
+- `context build` validates links in OKF root indexes and generated
+  child `index.md` files. Relative links must resolve to files inside
+  `dist/<package-name>/`; broken links are reported as
+  `package/index-link-invalid`.
+- If a project needs curated default navigation, edit the template-owned
+  `wikis/index.md`. Template files or copied knowledge pages that collide with
+  an index path selected by the current navigation policy are rejected during
+  build/status preflight.
+
+The generated templates are complete generic defaults. Before publishing,
+package authors should replace or edit `src/package-templates/kb/**` when the
+package needs project-specific skills, prompts, routing rules, terminology, or
+package instructions. If the generic behavior is intentionally sufficient,
+explicitly accept the unchanged default through the package-template Review
+Route. Do not add a package-name Skill by default; add one only when the user
+wants project-specific behavior beyond knowledge lookup.
+
+## Context OKF Profiles
+
+Approved Markdown under `knowledge/` is the production 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;
+- do not nest C4A extension 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;
+- do not add frontmatter `source_refs`; page-level provenance is derived from
+  section source refs when needed;
+- do not add `context` or `schema` fields.
+
+Package knowledge pages under `dist/<package-name>/` use a consumer projection.
+They retain reader-facing fields such as `title`, `type`, `description`, `tags`,
+`timestamp`, and custom non-lifecycle fields. Node identity, `resource`,
+`sources`, Section evidence comments, and build-only fields are omitted from the
+page. `context-build-inventory.json` records the distributed path, approved
+knowledge path, node identity, source summary, and package-visible structure.
+Maintainers return to the mapped `knowledge/` page for exact `sources` and
+`source_ref` attribution. `knowledge/` is never rewritten by this projection.
+
+Accepted section `source_ref` forms:
+
+```text
+src-N#symbol:<file>:<symbol-id>:<kind>@<digest>
+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
+`candidate_fingerprint` at the top level and do not duplicate this evidence in
+`code_origin`.
+
+`#span:` refs retain source snapshot line ranges for human review, diffing, and
+stable re-pinning. They resolve against committed file/lark document snapshots,
+not the code symbol index.
+
+The kb package root may contain agent files such as `AGENTS.md` and `skills/`.
+The OKF-compatible surface is the selected `wikis/`, `guides/`, `rules/`, and
+`feats/` subtrees.
+
+## Build Behavior
+
+`context build`:
+
+1. Selects approved Markdown from `knowledge/`.
+2. Renders all files from `template.path`.
+3. Projects selected approved Markdown into consumer-oriented package pages.
+4. For `llmsPackage`, appends selected knowledge to `llms.txt` when the template
+   does not already use `{{knowledge}}` or `{{approvedKnowledge}}`.
+5. Writes deterministic package inventory such as
+   `context-build-inventory.json`.
+6. Writes output under `dist/<package-name>/`.
+
+`context-build-inventory.json` records what was selected and why. Each selected
+file includes `selected_by` entries such as `{ "kind": "collection" }` and a
+`production_metadata` object for selected page-level production fields. Child
+and relationship records use the inventory's canonical structure projection,
+`{ "kind": "okf_root" }`, `{ "kind": "include" }`, or
+`{ "kind": "default" }`. The inventory also exposes package-visible typed
+edges under `structure.edge_records`; these records are filtered to edges whose
+endpoints are present in the selected package. Use those edge records for
+relationship citations inside the package instead of assuming the workspace
+`knowledge/structure.yaml` file is bundled.
+
+For KB packages, the inventory records `package.distribution` as
+`layout: "flat"`, `knowledge_namespace: null`, and the four package-relative
+OKF roots. Selected file and group records expose both the logical `okf_root`
+and final `okf_root_path`, so consumers do not need to infer paths.
+
+Build expects approved knowledge to be closed when the project has source-bound
+document knowledge. When `workflow.current.reason_code` is
+`route.close.projection-stale`, run the exact returned close command. Current
+close derives
+`knowledge/structure.yaml`, persists approved edge projection, and runs the
+final verify gate. References, changelog, package index, and section
+fingerprint rebuilds are not current close output; build only packages the
+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
+output path. Rename the template file or use `select.exclude` when the
+collision is intentional.
+
+After writing KB output, `context build` checks selected OKF root `index.md`
+files and generated child directory indexes. If an index link is broken, fix
+the package template, approved knowledge path, or directory index generation,
+then rerun `context build`; do not patch `dist/` directly as the durable fix.
+
+If a template describes package coverage, scope, known gaps, or known limits,
+it must cite approved knowledge, `context-build-inventory.json`, or
+explicitly rendered structure data. Otherwise build reports a
+template-boundary diagnostic. Keep factual claims in approved knowledge and
+structure; templates only package and route that material.
+
+After build, inspect the output shape. `context build` and `context verify`
+validate protocol structure; they do not decide whether the selected knowledge
+is meaningful enough for the user.
+
+## Select Patterns
+
+Package selection is evaluated in this order:
+
+1. `collections` filters by internal approved collection, for example
+   `architecture`, `sop`, `standards`, or `feats`.
+2. `okfRoots` filters by output root after OKF mapping: `wikis`, `guides`,
+   `rules`, or `feats`.
+3. `include` patterns are matched against approved paths relative to
+   `knowledge/`.
+4. `exclude` patterns remove matches after the previous filters.
+
+Path patterns are relative to `knowledge/`.
+
+```ts
+select: {
+  collections: ["architecture", "sop"],
+  okfRoots: ["wikis", "guides"],
+  include: ["architecture/component-lib/**", "sop/component-lib/**"],
+  exclude: ["**/internal/**"],
+}
+```
+
+If `include` is omitted, all approved knowledge is included unless excluded.
+When `collections` or `okfRoots` are present, a file must pass those filters
+before include/exclude path matching is considered.