@drafthq/draft 3.5.1 → 3.5.3

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "draft",
       "source": "./",
       "description": "Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.",
-      "version": "3.5.1",
+      "version": "3.5.3",
       "author": {
         "name": "mayurpise"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "draft",
   "description": "Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.",
-  "version": "3.5.1",
+  "version": "3.5.3",
   "author": {
     "name": "mayurpise"
   },

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "draft",
   "displayName": "Draft",
   "description": "Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.",
-  "version": "3.5.1",
+  "version": "3.5.3",
   "skills": "./skills/",
   "agents": "./core/agents/",
   "author": {

package/core/templates/okf/ai-context-index.md

@@ -8,7 +8,7 @@ draft_init_mode: okf
 
 # {PROJECT_NAME} — AI Context Index
 
-> Index root for the OKF taxonomy bundle (`wiki/`). Read **Synopsis** for broad
+> Index root for the project wiki (`wiki/`). Read **Synopsis** for broad
 > tasks (they usually terminate here). For focused tasks, route through the
 > **Concept Map** to ≤N concept pages — each lists `x-grounded-paths`. This is
 > both the cheap broad-context path AND the progressive-disclosure entry point.

package/core/templates/okf/index.md

@@ -1,21 +1,17 @@
 ---
-type: Subsystem
-title: "{PROJECT_NAME} — Knowledge Bundle"
-description: >
-  Root index of the OKF taxonomy bundle. Start here, then route into
-  overview/, systems/, features/, reference/, or entrypoints/ via the
-  Concept Map. Open a concept only when its description matches the task.
-resource: .
-tags: [index]
-timestamp: "{ISO_TIMESTAMP}"
 okf_version: "0.1"
-okf_types_version: "0.1"
 ---
 
-# {PROJECT_NAME} — Knowledge Bundle
+<!-- OKF §6/§11: an index file carries NO concept frontmatter; the root index.md
+     may declare ONLY `okf_version`. The frozen concept-`type` vocabulary version
+     is tracked here in the body (not in frontmatter) so bumping it stays visible
+     without violating the index-frontmatter rule.
+     okf-types-version: 0.1 -->
 
-> OKF v0.1 bundle. One concept per file; cross-links form the graph. The
-> live call graph (`codebase-memory-mcp`) is the grounding source; this bundle
+# {PROJECT_NAME} — Wiki
+
+> Project wiki. One concept per file; cross-links form the graph. The
+> live call graph (`codebase-memory-mcp`) is the grounding source; this wiki
 > is the navigable serialization. `../ai-context.md` is the consumption entry point.
 
 ## Sections

package/core/templates/okf/section-index.md

@@ -1,25 +1,16 @@
----
-type: Subsystem
-title: "{SECTION_TITLE}"
-description: >
-  Section index. Lists every concept in this section with its one-line
-  routing description so an agent can pick the right page without opening
-  each one. {SECTION_PURPOSE}
-resource: .
-tags: [index]
-timestamp: "{ISO_TIMESTAMP}"
----
+<!-- OKF §6: an index file contains NO frontmatter. This page is a reserved
+     navigation index, not a concept — its Concepts table is tool-generated. -->
 
 # {SECTION_TITLE}
 
-> Section of the OKF bundle. Back to [bundle root](../index.md).
+> Section of the project wiki. Back to [wiki root](../index.md).
 
 ## Concepts
 
-<!-- One row per concept page in this section. `description` is the routing key
-     copied from each page's frontmatter. Regenerated on every init/refresh. -->
-
-| Concept | Type | Routing description |
-|---------|------|---------------------|
-| [{concept-a}]({concept-a}.md) | Module | {one-line routing desc} |
-| [{concept-b}]({concept-b}.md) | Feature | {one-line routing desc} |
+<!-- TOOL-OWNED: regenerated deterministically by okf-render-views.sh
+     (--section-indexes) from the concept pages in this directory. One row per
+     page; `description` is the routing key copied from each page's frontmatter.
+     Do not hand-edit between the markers — links here are guaranteed to resolve
+     because they are built only from files that actually exist. -->
+<!-- CONCEPT-MAP:START -->
+<!-- CONCEPT-MAP:END -->

package/integrations/agents/AGENTS.md

@@ -341,7 +341,7 @@ The tier-gated default rests on **maintainability/readability** (one navigable c
 1. `okf-plan-concepts.sh` ran and the expected/required/deferred counts were logged **before** any page was written (the concept boundary is a tool output, not an in-context guess).
 2. Every `required` entry in `concept-plan.json` has a non-stub page.
 3. `okf-validate-all.sh … --plan … --strict` exits 0 (structure + per-type quality + coverage all pass).
-4. `systems/coverage.md` was generated by tooling (verify the `<!-- okf:coverage-generated -->` marker) — no required package with `fan_in ≥ floor` is **MISSING**.
+4. `systems/coverage.md` was generated by tooling (verify the `<!-- okf:coverage-generated -->` marker) — **every** package/module the graph found is required by default (the fan-in floor only types Subsystem-vs-Module, it does not exempt), so none may be **MISSING**. Section `index.md` tables are regenerated by `okf-render-views.sh --section-indexes`, never hand-authored, so their links cannot dangle.
 5. On any failure: **do not** atomic-rename; surface `.state/validation-report.json`.
 
 > **Red flag:** writing concept pages without first running `okf-plan-concepts.sh`, or finishing generation while any `required` plan entry is unwritten, is a **completeness failure** — not a stylistic one.
@@ -3353,7 +3353,8 @@ Templates for each bundle page live in `core/templates/okf/` (`index.md`,
 ## Frozen `type` vocabulary
 
 Every concept carries a `type` from this frozen set (changing it churns every
-file; versioned via `index.md` frontmatter `okf_types_version`):
+file; versioned via the `okf-types-version` comment in the wiki root `index.md`
+body — OKF §6/§11 permit only `okf_version` in an index file's frontmatter):
 
 | type | Maps to | Home |
 |------|---------|------|
@@ -3379,6 +3380,16 @@ the task at hand?"), never a summary. Draft extensions are namespaced `x-` and
 ignored by generic OKF consumers: `x-grounded-paths`, `x-hotspot-score`,
 `x-callers`.
 
+**Meta pages are not concepts.** Index files (`wiki/index.md` and every
+`<section>/index.md`) carry **no concept frontmatter**: per OKF §6 an index file
+has no frontmatter, and per §11 the root `index.md` may declare **only**
+`okf_version`. The tool-generated `systems/coverage.md` is a non-reserved file, so
+OKF §9.1/§9.2 require it to carry a typed frontmatter block; it uses a descriptive
+`type: Report` and is exempt from the frozen vocabulary via `is_meta_page`
+(basename + the `<!-- okf:coverage-generated -->` marker). `okf-validate.sh`
+short-circuits all meta pages before the concept checks, so they are never
+vocab-checked or counted as concepts.
+
 ## Concept granularity (resolves open decision 1)
 
 Derive concepts from the graph, not by hand:
@@ -3398,17 +3409,21 @@ Derive concepts from the graph, not by hand:
 ```
 1. Survey        → existing draft init 5-phase + graph snapshot (graph-snapshot.sh)
 2. Plan          → DETERMINISTIC. okf-plan-concepts.sh derives the expected-concept
-                   set from the graph (every package with fan_in ≥ floor → required
-                   Subsystem/Module; entrypoints → required; below-floor / allow-defer
-                   → deferred with a reason) and writes draft.tmp/.state/concept-plan.json.
+                   set from the graph. EVERY package the graph knows about is
+                   required (fan_in ≥ floor → Subsystem; below floor → Module — the
+                   floor only types/orders, it never exempts); entrypoints → required;
+                   only --allow-defer matches are deferred (with a reason). Writes
+                   draft.tmp/.state/concept-plan.json.
                      okf-plan-concepts.sh --repo . [--scope PATH] \
                        [--manifest FILE] [--min-fan-in 2] [--allow-defer GLOB]... \
                        --out draft.tmp/.state/concept-plan.json
                    This replaces the old in-context concept enumeration — the boundary
                    of the work is now a tool output, not an LLM judgment, so modules
-                   cannot be silently dropped. LOG the counts (expected/required/
-                   deferred) BEFORE writing any page. `generated_order` is topo-ish
-                   (required + high-fan-in first) so forward cross-links resolve.
+                   and sub-modules cannot be silently dropped. (Legacy fan-in
+                   exemption is opt-in via --defer-below-floor.) LOG the counts
+                   (expected/required/deferred) BEFORE writing any page.
+                   `generated_order` is topo-ish (required + high-fan-in first) so
+                   forward cross-links resolve.
 3. Generate      → iterate concept-plan.generated_order; write ONE page per REQUIRED
                    entry, grounding each from the graph:
                      x-callers        ← graph-callers.sh --symbol <c>
@@ -3428,9 +3443,11 @@ Derive concepts from the graph, not by hand:
                            --plan draft.tmp/.state/concept-plan.json \
                            --path-index draft.tmp/.state/path-to-concept.json \
                            --strict --report draft.tmp/.state/validation-report.json
-                   It runs, in order: okf-validate.sh (structure + reverse index),
-                   okf-validate-quality.sh (per-type anti-stub / depth / mermaid lint),
-                   okf-coverage-check.sh (every required plan entry → real page).
+                   It runs, in order: okf-validate.sh (structure + reverse index +
+                   empty/untyped-page + leftover-template-token + dangling-link checks),
+                   okf-validate-quality.sh (per-type anti-stub / depth / per-section
+                   content / mermaid lint), okf-coverage-check.sh (every required plan
+                   entry → real page).
                    ANY layer failing ⇒ exit non-zero ⇒ DO NOT atomic-rename.
                    coverage.md (systems/coverage.md) is regenerated by the coverage
                    layer; it is tool-owned (marker <!-- okf:coverage-generated -->) —
@@ -3469,6 +3486,7 @@ regenerated on every init/refresh so they never drift from the bundle:
 ```bash
 okf-render-views.sh draft/wiki \
   --arch-out draft/architecture.md \
+  --section-indexes \
   --concept-map-into draft/wiki/index.md \
   --concept-map-into draft/.ai-context.md \
   --web draft/wiki/web/index.html
@@ -3476,6 +3494,11 @@ okf-render-views.sh draft/wiki \
 
 - `--arch-out` renders the linear `architecture.md` (banner + TOC + every concept
   page in canonical section order, frontmatter stripped, Mermaid preserved).
+- `--section-indexes` rebuilds each `<section>/index.md` concept table (between its
+  `CONCEPT-MAP` markers) from the pages that actually exist in that directory. This
+  is mandatory: section indexes are NOT hand-authored — building them from real
+  files is what makes their links impossible to dangle. Never write a section
+  index "Concepts" table by hand.
 - `--concept-map-into` rebuilds the routing table between the
   `<!-- CONCEPT-MAP:START -->` / `:END` markers from each concept's `title` +
   `type` + `description` (section `index.md` pages excluded).
@@ -22641,23 +22664,19 @@ List down alerting thresholds on those metrics:
 <core-file path="core/templates/okf/index.md">
 
 ---
-type: Subsystem
-title: "{PROJECT_NAME} — Knowledge Bundle"
-description: >
-  Root index of the OKF taxonomy bundle. Start here, then route into
-  overview/, systems/, features/, reference/, or entrypoints/ via the
-  Concept Map. Open a concept only when its description matches the task.
-resource: .
-tags: [index]
-timestamp: "{ISO_TIMESTAMP}"
 okf_version: "0.1"
-okf_types_version: "0.1"
 ---
 
-# {PROJECT_NAME} — Knowledge Bundle
+<!-- OKF §6/§11: an index file carries NO concept frontmatter; the root index.md
+     may declare ONLY `okf_version`. The frozen concept-`type` vocabulary version
+     is tracked here in the body (not in frontmatter) so bumping it stays visible
+     without violating the index-frontmatter rule.
+     okf-types-version: 0.1 -->
+
+# {PROJECT_NAME} — Wiki
 
-> OKF v0.1 bundle. One concept per file; cross-links form the graph. The
-> live call graph (`codebase-memory-mcp`) is the grounding source; this bundle
+> Project wiki. One concept per file; cross-links form the graph. The
+> live call graph (`codebase-memory-mcp`) is the grounding source; this wiki
 > is the navigable serialization. `../ai-context.md` is the consumption entry point.
 
 ## Sections
@@ -22761,31 +22780,22 @@ Entrypoint) require ≥1 valid Mermaid block and ≥2 x-grounded-paths.
 
 <core-file path="core/templates/okf/section-index.md">
 
----
-type: Subsystem
-title: "{SECTION_TITLE}"
-description: >
-  Section index. Lists every concept in this section with its one-line
-  routing description so an agent can pick the right page without opening
-  each one. {SECTION_PURPOSE}
-resource: .
-tags: [index]
-timestamp: "{ISO_TIMESTAMP}"
----
+<!-- OKF §6: an index file contains NO frontmatter. This page is a reserved
+     navigation index, not a concept — its Concepts table is tool-generated. -->
 
 # {SECTION_TITLE}
 
-> Section of the OKF bundle. Back to [bundle root](../index.md).
+> Section of the project wiki. Back to [wiki root](../index.md).
 
 ## Concepts
 
-<!-- One row per concept page in this section. `description` is the routing key
-     copied from each page's frontmatter. Regenerated on every init/refresh. -->
-
-| Concept | Type | Routing description |
-|---------|------|---------------------|
-| [{concept-a}]({concept-a}.md) | Module | {one-line routing desc} |
-| [{concept-b}]({concept-b}.md) | Feature | {one-line routing desc} |
+<!-- TOOL-OWNED: regenerated deterministically by okf-render-views.sh
+     (--section-indexes) from the concept pages in this directory. One row per
+     page; `description` is the routing key copied from each page's frontmatter.
+     Do not hand-edit between the markers — links here are guaranteed to resolve
+     because they are built only from files that actually exist. -->
+<!-- CONCEPT-MAP:START -->
+<!-- CONCEPT-MAP:END -->
 
 </core-file>
 
@@ -22805,7 +22815,7 @@ draft_init_mode: okf
 
 # {PROJECT_NAME} — AI Context Index
 
-> Index root for the OKF taxonomy bundle (`wiki/`). Read **Synopsis** for broad
+> Index root for the project wiki (`wiki/`). Read **Synopsis** for broad
 > tasks (they usually terminate here). For focused tasks, route through the
 > **Concept Map** to ≤N concept pages — each lists `x-grounded-paths`. This is
 > both the cheap broad-context path AND the progressive-disclosure entry point.

package/integrations/copilot/.github/copilot-instructions.md

@@ -341,7 +341,7 @@ The tier-gated default rests on **maintainability/readability** (one navigable c
 1. `okf-plan-concepts.sh` ran and the expected/required/deferred counts were logged **before** any page was written (the concept boundary is a tool output, not an in-context guess).
 2. Every `required` entry in `concept-plan.json` has a non-stub page.
 3. `okf-validate-all.sh … --plan … --strict` exits 0 (structure + per-type quality + coverage all pass).
-4. `systems/coverage.md` was generated by tooling (verify the `<!-- okf:coverage-generated -->` marker) — no required package with `fan_in ≥ floor` is **MISSING**.
+4. `systems/coverage.md` was generated by tooling (verify the `<!-- okf:coverage-generated -->` marker) — **every** package/module the graph found is required by default (the fan-in floor only types Subsystem-vs-Module, it does not exempt), so none may be **MISSING**. Section `index.md` tables are regenerated by `okf-render-views.sh --section-indexes`, never hand-authored, so their links cannot dangle.
 5. On any failure: **do not** atomic-rename; surface `.state/validation-report.json`.
 
 > **Red flag:** writing concept pages without first running `okf-plan-concepts.sh`, or finishing generation while any `required` plan entry is unwritten, is a **completeness failure** — not a stylistic one.
@@ -3353,7 +3353,8 @@ Templates for each bundle page live in `core/templates/okf/` (`index.md`,
 ## Frozen `type` vocabulary
 
 Every concept carries a `type` from this frozen set (changing it churns every
-file; versioned via `index.md` frontmatter `okf_types_version`):
+file; versioned via the `okf-types-version` comment in the wiki root `index.md`
+body — OKF §6/§11 permit only `okf_version` in an index file's frontmatter):
 
 | type | Maps to | Home |
 |------|---------|------|
@@ -3379,6 +3380,16 @@ the task at hand?"), never a summary. Draft extensions are namespaced `x-` and
 ignored by generic OKF consumers: `x-grounded-paths`, `x-hotspot-score`,
 `x-callers`.
 
+**Meta pages are not concepts.** Index files (`wiki/index.md` and every
+`<section>/index.md`) carry **no concept frontmatter**: per OKF §6 an index file
+has no frontmatter, and per §11 the root `index.md` may declare **only**
+`okf_version`. The tool-generated `systems/coverage.md` is a non-reserved file, so
+OKF §9.1/§9.2 require it to carry a typed frontmatter block; it uses a descriptive
+`type: Report` and is exempt from the frozen vocabulary via `is_meta_page`
+(basename + the `<!-- okf:coverage-generated -->` marker). `okf-validate.sh`
+short-circuits all meta pages before the concept checks, so they are never
+vocab-checked or counted as concepts.
+
 ## Concept granularity (resolves open decision 1)
 
 Derive concepts from the graph, not by hand:
@@ -3398,17 +3409,21 @@ Derive concepts from the graph, not by hand:
 ```
 1. Survey        → existing draft init 5-phase + graph snapshot (graph-snapshot.sh)
 2. Plan          → DETERMINISTIC. okf-plan-concepts.sh derives the expected-concept
-                   set from the graph (every package with fan_in ≥ floor → required
-                   Subsystem/Module; entrypoints → required; below-floor / allow-defer
-                   → deferred with a reason) and writes draft.tmp/.state/concept-plan.json.
+                   set from the graph. EVERY package the graph knows about is
+                   required (fan_in ≥ floor → Subsystem; below floor → Module — the
+                   floor only types/orders, it never exempts); entrypoints → required;
+                   only --allow-defer matches are deferred (with a reason). Writes
+                   draft.tmp/.state/concept-plan.json.
                      okf-plan-concepts.sh --repo . [--scope PATH] \
                        [--manifest FILE] [--min-fan-in 2] [--allow-defer GLOB]... \
                        --out draft.tmp/.state/concept-plan.json
                    This replaces the old in-context concept enumeration — the boundary
                    of the work is now a tool output, not an LLM judgment, so modules
-                   cannot be silently dropped. LOG the counts (expected/required/
-                   deferred) BEFORE writing any page. `generated_order` is topo-ish
-                   (required + high-fan-in first) so forward cross-links resolve.
+                   and sub-modules cannot be silently dropped. (Legacy fan-in
+                   exemption is opt-in via --defer-below-floor.) LOG the counts
+                   (expected/required/deferred) BEFORE writing any page.
+                   `generated_order` is topo-ish (required + high-fan-in first) so
+                   forward cross-links resolve.
 3. Generate      → iterate concept-plan.generated_order; write ONE page per REQUIRED
                    entry, grounding each from the graph:
                      x-callers        ← graph-callers.sh --symbol <c>
@@ -3428,9 +3443,11 @@ Derive concepts from the graph, not by hand:
                            --plan draft.tmp/.state/concept-plan.json \
                            --path-index draft.tmp/.state/path-to-concept.json \
                            --strict --report draft.tmp/.state/validation-report.json
-                   It runs, in order: okf-validate.sh (structure + reverse index),
-                   okf-validate-quality.sh (per-type anti-stub / depth / mermaid lint),
-                   okf-coverage-check.sh (every required plan entry → real page).
+                   It runs, in order: okf-validate.sh (structure + reverse index +
+                   empty/untyped-page + leftover-template-token + dangling-link checks),
+                   okf-validate-quality.sh (per-type anti-stub / depth / per-section
+                   content / mermaid lint), okf-coverage-check.sh (every required plan
+                   entry → real page).
                    ANY layer failing ⇒ exit non-zero ⇒ DO NOT atomic-rename.
                    coverage.md (systems/coverage.md) is regenerated by the coverage
                    layer; it is tool-owned (marker <!-- okf:coverage-generated -->) —
@@ -3469,6 +3486,7 @@ regenerated on every init/refresh so they never drift from the bundle:
 ```bash
 okf-render-views.sh draft/wiki \
   --arch-out draft/architecture.md \
+  --section-indexes \
   --concept-map-into draft/wiki/index.md \
   --concept-map-into draft/.ai-context.md \
   --web draft/wiki/web/index.html
@@ -3476,6 +3494,11 @@ okf-render-views.sh draft/wiki \
 
 - `--arch-out` renders the linear `architecture.md` (banner + TOC + every concept
   page in canonical section order, frontmatter stripped, Mermaid preserved).
+- `--section-indexes` rebuilds each `<section>/index.md` concept table (between its
+  `CONCEPT-MAP` markers) from the pages that actually exist in that directory. This
+  is mandatory: section indexes are NOT hand-authored — building them from real
+  files is what makes their links impossible to dangle. Never write a section
+  index "Concepts" table by hand.
 - `--concept-map-into` rebuilds the routing table between the
   `<!-- CONCEPT-MAP:START -->` / `:END` markers from each concept's `title` +
   `type` + `description` (section `index.md` pages excluded).
@@ -22641,23 +22664,19 @@ List down alerting thresholds on those metrics:
 <core-file path="core/templates/okf/index.md">
 
 ---
-type: Subsystem
-title: "{PROJECT_NAME} — Knowledge Bundle"
-description: >
-  Root index of the OKF taxonomy bundle. Start here, then route into
-  overview/, systems/, features/, reference/, or entrypoints/ via the
-  Concept Map. Open a concept only when its description matches the task.
-resource: .
-tags: [index]
-timestamp: "{ISO_TIMESTAMP}"
 okf_version: "0.1"
-okf_types_version: "0.1"
 ---
 
-# {PROJECT_NAME} — Knowledge Bundle
+<!-- OKF §6/§11: an index file carries NO concept frontmatter; the root index.md
+     may declare ONLY `okf_version`. The frozen concept-`type` vocabulary version
+     is tracked here in the body (not in frontmatter) so bumping it stays visible
+     without violating the index-frontmatter rule.
+     okf-types-version: 0.1 -->
+
+# {PROJECT_NAME} — Wiki
 
-> OKF v0.1 bundle. One concept per file; cross-links form the graph. The
-> live call graph (`codebase-memory-mcp`) is the grounding source; this bundle
+> Project wiki. One concept per file; cross-links form the graph. The
+> live call graph (`codebase-memory-mcp`) is the grounding source; this wiki
 > is the navigable serialization. `../ai-context.md` is the consumption entry point.
 
 ## Sections
@@ -22761,31 +22780,22 @@ Entrypoint) require ≥1 valid Mermaid block and ≥2 x-grounded-paths.
 
 <core-file path="core/templates/okf/section-index.md">
 
----
-type: Subsystem
-title: "{SECTION_TITLE}"
-description: >
-  Section index. Lists every concept in this section with its one-line
-  routing description so an agent can pick the right page without opening
-  each one. {SECTION_PURPOSE}
-resource: .
-tags: [index]
-timestamp: "{ISO_TIMESTAMP}"
----
+<!-- OKF §6: an index file contains NO frontmatter. This page is a reserved
+     navigation index, not a concept — its Concepts table is tool-generated. -->
 
 # {SECTION_TITLE}
 
-> Section of the OKF bundle. Back to [bundle root](../index.md).
+> Section of the project wiki. Back to [wiki root](../index.md).
 
 ## Concepts
 
-<!-- One row per concept page in this section. `description` is the routing key
-     copied from each page's frontmatter. Regenerated on every init/refresh. -->
-
-| Concept | Type | Routing description |
-|---------|------|---------------------|
-| [{concept-a}]({concept-a}.md) | Module | {one-line routing desc} |
-| [{concept-b}]({concept-b}.md) | Feature | {one-line routing desc} |
+<!-- TOOL-OWNED: regenerated deterministically by okf-render-views.sh
+     (--section-indexes) from the concept pages in this directory. One row per
+     page; `description` is the routing key copied from each page's frontmatter.
+     Do not hand-edit between the markers — links here are guaranteed to resolve
+     because they are built only from files that actually exist. -->
+<!-- CONCEPT-MAP:START -->
+<!-- CONCEPT-MAP:END -->
 
 </core-file>
 
@@ -22805,7 +22815,7 @@ draft_init_mode: okf
 
 # {PROJECT_NAME} — AI Context Index
 
-> Index root for the OKF taxonomy bundle (`wiki/`). Read **Synopsis** for broad
+> Index root for the project wiki (`wiki/`). Read **Synopsis** for broad
 > tasks (they usually terminate here). For focused tasks, route through the
 > **Concept Map** to ≤N concept pages — each lists `x-grounded-paths`. This is
 > both the cheap broad-context path AND the progressive-disclosure entry point.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drafthq/draft",
-  "version": "3.5.1",
+  "version": "3.5.3",
   "description": "Context-Driven Development for AI coding agents — install Draft into Claude Code, Cursor, Codex, or opencode.",
   "bin": {
     "draft": "cli/bin/draft.js"

package/scripts/tools/okf-coverage-check.sh

@@ -122,6 +122,17 @@ write_coverage_page() {
     mkdir -p "$BUNDLE/systems"
     local tmp; tmp="$(mktemp)"
     {
+        # OKF §9.1/§9.2: every non-reserved .md needs parseable frontmatter with a
+        # non-empty `type`. coverage.md is tool-generated and not a code concept, so
+        # it uses a descriptive (non-frozen) type; okf-validate.sh exempts it from the
+        # frozen-vocab check via is_meta_page (basename + the marker below).
+        echo "---"
+        echo "type: Report"
+        echo "title: Component Coverage"
+        echo "description: Coverage of required components by wiki pages — which are documented, stubbed, or missing."
+        echo "resource: ."
+        echo "---"
+        echo ""
         echo "<!-- okf:coverage-generated -->"
         echo "# Component Coverage"
         echo ""
@@ -130,14 +141,21 @@ write_coverage_page() {
         echo ""
         echo "| Component | Wiki page | Status | Fan-in |"
         echo "|-----------|-----------|--------|--------|"
-        local cid status fanin
+        local cid status fanin link
         while IFS=$'\t' read -r cid required reason ftype fanin; do
             [[ -z "$cid" ]] && continue
             if [[ "$required" == "true" ]]; then
                 if [[ -f "$BUNDLE/$cid" ]]; then
                     bl="$(body_lines "$BUNDLE/$cid")"
+                    # coverage.md lives in systems/; link relative to it. Concepts in
+                    # other sections (entrypoints/, reference/, …) need a ../ prefix,
+                    # otherwise the link dangles and fails structure validation.
+                    case "$cid" in
+                        systems/*) link="${cid#systems/}";;
+                        *)         link="../$cid";;
+                    esac
                     if [[ "$bl" -ge "$MIN_STUB_LINES" ]]; then
-                        echo "| \`${cid%.md}\` | [page](${cid#systems/}) | Full | ${fanin} |"
+                        echo "| \`${cid%.md}\` | [page](${link}) | Full | ${fanin} |"
                     else
                         echo "| \`${cid%.md}\` | ${cid} | **STUB (${bl} lines)** | ${fanin} |"
                     fi

package/scripts/tools/okf-plan-concepts.sh

@@ -38,6 +38,7 @@ MANIFEST=""
 MIN_FAN_IN=2
 OUT=""
 JSON=0
+DEFER_BELOW_FLOOR=0
 ALLOW_DEFER=()
 
 usage() {
@@ -54,8 +55,12 @@ Flags:
   --manifest FILE    Component list (one component per line; '#' comments; blanks
                      ignored). When present it is authoritative — every entry is
                      required and the graph is not consulted.
-  --min-fan-in N     Package fan-in floor for "required" (default: 2). Packages
-                     below the floor are deferred with a reason.
+  --min-fan-in N     Fan-in threshold that types a package as a Subsystem (>=N)
+                     vs a Module (<N) and orders it first (default: 2). By default
+                     EVERY graph package is required regardless of fan-in — the
+                     floor no longer exempts anything.
+  --defer-below-floor  Restore the old behavior: packages with fan_in < --min-fan-in
+                     are deferred (not required) instead of required-as-Module.
   --allow-defer GLOB Defer (don't require) components whose name matches GLOB.
                      Repeatable. Deferred entries still appear in the plan.
   --out FILE         Write the plan JSON here (default: stdout).
@@ -72,6 +77,7 @@ while [[ $# -gt 0 ]]; do
         --scope) SCOPE="$2"; shift 2;;
         --manifest) MANIFEST="$2"; shift 2;;
         --min-fan-in) MIN_FAN_IN="$2"; shift 2;;
+        --defer-below-floor) DEFER_BELOW_FLOOR=1; shift;;
         --allow-defer) ALLOW_DEFER+=("$2"); shift 2;;
         --out) OUT="$2"; shift 2;;
         --json) JSON=1; shift;;
@@ -150,8 +156,13 @@ plan_from_graph() {
             required=false; reason="allow-defer match"; type=Module
         elif (( fan_in >= MIN_FAN_IN )); then
             required=true; reason=""; type=Subsystem
-        else
+        elif [[ $DEFER_BELOW_FLOOR -eq 1 ]]; then
+            # Opt-in legacy behavior: low-fan-in packages are exempted.
             required=false; reason="fan_in $fan_in < floor $MIN_FAN_IN"; type=Module
+        else
+            # Default: every package the graph knows about is documented. Fan-in
+            # below the floor only demotes Subsystem→Module; it never exempts.
+            required=true; reason=""; type=Module
         fi
         add_concept "$name" systems "$type" "$name" "$fan_in" "$required" "$reason"
     done < <(echo "$arch" | jq -r '.packages[]? | [.name, (.fan_in // 0)] | @tsv')

package/scripts/tools/okf-render-views.sh

@@ -10,6 +10,9 @@
 #   2. Concept Map       — a routing table injected between the
 #      <!-- CONCEPT-MAP:START --> / <!-- CONCEPT-MAP:END --> markers in
 #      wiki/index.md (and optionally another index-root file).
+#   3. Section indexes   — (--section-indexes) each <section>/index.md concept
+#      table rebuilt from the pages that actually exist in that directory, so its
+#      links can never dangle (no more hand-authored, link-rotting indexes).
 #
 # Usage:
 #   okf-render-views.sh <BUNDLE_DIR> --arch-out <FILE> [--concept-map-into <FILE>]
@@ -25,6 +28,7 @@ BUNDLE=""
 ARCH_OUT=""
 WEB_OUT=""
 CMAP_INTO=()
+SECTION_INDEXES=0
 COVERAGE_REPORT=""
 VALIDATED_AT=""
 
@@ -39,6 +43,10 @@ Flags:
   --arch-out FILE          Write the rendered linear architecture.md here.
   --concept-map-into FILE  Inject the Concept Map between the CONCEPT-MAP markers
                            in FILE (repeatable: e.g. wiki/index.md and ai-context.md).
+  --section-indexes        Regenerate each section's <section>/index.md concept
+                           table (between its CONCEPT-MAP markers) from the pages
+                           that actually exist in that directory. Eliminates
+                           hand-authored, link-rotting section indexes.
   --web FILE               Write a self-contained, offline HTML viewer (single file:
                            all pages inlined, built-in markdown renderer, sidebar +
                            search). Double-click to open — no server, no internet.
@@ -56,6 +64,7 @@ while [[ $# -gt 0 ]]; do
     case "$1" in
         --arch-out) ARCH_OUT="$2"; shift 2;;
         --concept-map-into) CMAP_INTO+=("$2"); shift 2;;
+        --section-indexes) SECTION_INDEXES=1; shift;;
         --web) WEB_OUT="$2"; shift 2;;
         --coverage-report) COVERAGE_REPORT="$2"; shift 2;;
         --validated-at) VALIDATED_AT="$2"; shift 2;;
@@ -100,6 +109,17 @@ strip_frontmatter() {
     ' "$1"
 }
 
+# Human-facing title for a page: frontmatter `title`, else the first `# H1` in the
+# body, else the bundle-relative path. Index files are frontmatter-less under OKF
+# §6, so the H1 fallback keeps the rendered TOC / nav readable.
+page_title() {
+    local t; t="$(get_yaml_field "$1" title)"
+    if [[ -z "$t" ]]; then
+        t="$(strip_frontmatter "$1" | grep -m1 -E '^#[[:space:]]+' | sed -E 's/^#[[:space:]]+//')"
+    fi
+    printf '%s' "$t"
+}
+
 # Coverage-honesty banner, sourced from okf-coverage-check.sh's JSON report.
 # Silent when no report is supplied (keeps the view backward-compatible).
 emit_coverage_banner() {
@@ -134,7 +154,7 @@ render_architecture() {
         echo ""
         echo "# Architecture (Rendered View)"
         echo ""
-        echo "> **Generated** from the \`wiki/\` OKF bundle — do not edit by hand."
+        echo "> **Generated** from the \`wiki/\` bundle — do not edit by hand."
         echo "> The bundle is the source of truth; this is the single-document linear"
         echo "> view for onboarding. Regenerate with \`okf-render-views.sh\`."
         echo ""
@@ -150,7 +170,7 @@ render_architecture() {
                 echo "- **${sec}/**"
                 last_sec="$sec"
             fi
-            title="$(get_yaml_field "$BUNDLE/$rel" title)"
+            title="$(page_title "$BUNDLE/$rel")"
             [[ -n "$title" ]] || title="$rel"
             local anchor; anchor="$(printf '%s' "$title" | tr '[:upper:]' '[:lower:]' | tr -cs 'a-z0-9' '-')"
             anchor="${anchor#-}"; anchor="${anchor%-}"
@@ -174,10 +194,14 @@ render_architecture() {
 build_concept_map() {
     echo "| Concept | Type | Open it when… |"
     echo "|---------|------|---------------|"
-    local rel type title desc
+    local rel base type title desc
     while IFS= read -r -d '' page; do
         rel="${page#"$BUNDLE/"}"
-        [[ "$(basename "$rel")" == "index.md" ]] && continue
+        base="$(basename "$rel")"
+        # Meta pages are not routable concepts (reserved index/log + the typed,
+        # tool-generated coverage page).
+        [[ "$base" == "index.md" || "$base" == "log.md" || "$base" == "coverage.md" ]] && continue
+        grep -q '<!-- okf:coverage-generated -->' "$page" 2>/dev/null && continue
         type="$(get_yaml_field "$page" type)"
         [[ -n "$type" ]] || continue
         title="$(get_yaml_field "$page" title)"
@@ -192,6 +216,50 @@ build_concept_map() {
     done < <(find "$BUNDLE" -type f -name '*.md' -print0 | sort -z)
 }
 
+# First non-empty line of a page's `description` frontmatter (handles folded `>`).
+page_desc() {
+    awk '
+        NR==1&&/^---$/{fm=1;next} fm&&/^---$/{exit}
+        fm && /^description:/ { collect=1; sub(/^description:[[:space:]]*>?[[:space:]]*/,""); if($0!=""){print; exit} next }
+        fm && collect { sub(/^[[:space:]]+/,""); if($0!=""){print; exit} }
+    ' "$1"
+}
+
+# Build the per-section concept table (stdout) for a single section directory.
+# Links are bundle-section-relative (just the filename) so they resolve from the
+# section's own index.md. Only pages that actually exist are listed — so the
+# table can never point at a missing file.
+build_section_map() {
+    local dir="$1" f rel base type title desc
+    echo "| Concept | Type | Routing description |"
+    echo "|---------|------|---------------------|"
+    while IFS= read -r f; do
+        base="$(basename "$f")"
+        [[ "$base" == "index.md" ]] && continue
+        [[ "$base" == "coverage.md" ]] && continue
+        grep -q '<!-- okf:coverage-generated -->' "$f" 2>/dev/null && continue
+        type="$(get_yaml_field "$f" type)"
+        [[ -n "$type" ]] || continue
+        title="$(get_yaml_field "$f" title)"; [[ -n "$title" ]] || title="$base"
+        desc="$(page_desc "$f")"
+        echo "| [${title}](${base}) | ${type} | ${desc} |"
+    done < <(find "$dir" -maxdepth 1 -type f -name '*.md' | sort)
+}
+
+# Regenerate every <section>/index.md concept table from real pages.
+render_section_indexes() {
+    local sec dir idx
+    for sec in "${SECTIONS[@]}"; do
+        dir="$BUNDLE/$sec"
+        idx="$dir/index.md"
+        [[ -d "$dir" && -f "$idx" ]] || continue
+        local map_tmp; map_tmp="$(mktemp)"
+        build_section_map "$dir" >"$map_tmp"
+        inject_concept_map "$idx" "$map_tmp"
+        rm -f "$map_tmp"
+    done
+}
+
 # Inject the Concept Map between markers in a target file (path may be relative
 # to BUNDLE: links in the map are bundle-relative, so the target should resolve
 # them — wiki/index.md works directly; an index root above wiki/ should prefix).
@@ -277,7 +345,7 @@ HTML_HEAD
         while IFS= read -r -d '' page; do
             local rel title type
             rel="${page#"$BUNDLE/"}"
-            title="$(get_yaml_field "$page" title)"; [[ -n "$title" ]] || title="$rel"
+            title="$(page_title "$page")"; [[ -n "$title" ]] || title="$rel"
             type="$(get_yaml_field "$page" type)"
             printf '%s: {"title": %s, "type": %s, "md": %s},\n' \
                 "$(jq -Rn --arg v "$rel" '$v')" \
@@ -397,7 +465,10 @@ if [[ ${#CMAP_INTO[@]} -gt 0 ]]; then
     rm -f "$MAP_TMP"
 fi
 
+[[ $SECTION_INDEXES -eq 1 ]] && render_section_indexes
+
 [[ -n "$WEB_OUT" ]] && render_web "$WEB_OUT"
 
-[[ -n "$ARCH_OUT" || -n "$WEB_OUT" || ${#CMAP_INTO[@]} -gt 0 ]] || { echo "ERROR: nothing to do (pass --arch-out, --web, and/or --concept-map-into)" >&2; exit 1; }
+[[ -n "$ARCH_OUT" || -n "$WEB_OUT" || ${#CMAP_INTO[@]} -gt 0 || $SECTION_INDEXES -eq 1 ]] \
+    || { echo "ERROR: nothing to do (pass --arch-out, --web, --section-indexes, and/or --concept-map-into)" >&2; exit 1; }
 exit 0

package/scripts/tools/okf-validate-quality.sh

@@ -11,7 +11,8 @@
 # Pages in scope: any *.md whose frontmatter declares a frozen `type:`. Section
 # index.md pages, log.md, and the generated coverage page are excluded.
 #
-# Checks (per type): required H2 sections, min body lines, >=1 mermaid block
+# Checks (per type): required H2 sections AND real content beneath each (so a
+# present-but-empty heading fails as "shallow"), min body lines, >=1 mermaid block
 # (diagram types only), min x-grounded-paths, anti-stub patterns, unreplaced
 # template tokens, duplicate "What it is" paragraphs, and a syntax-only mermaid
 # lint (no Node, no headless browser).
@@ -88,6 +89,19 @@ grounded_count() {
 
 has_section() { grep -qE "^##[[:space:]]+$1([[:space:]]|$)" "$2"; }
 
+# Count non-blank content lines under a given H2 section (heading itself
+# excluded), stopping at the next H2. Used to fail a section that is present as a
+# heading but carries no real content — the classic "shallow" page.
+section_content_lines() {
+    local sec="$1" file="$2"
+    awk -v sec="$sec" '
+        $0 ~ "^##[[:space:]]+" sec "([[:space:]]|$)" { grab=1; next }
+        grab && /^##[[:space:]]/ { exit }
+        grab && /[^[:space:]]/ { n++ }
+        END { print n+0 }
+    ' "$file"
+}
+
 mermaid_block_count() { grep -cE '^[[:space:]]*```mermaid' "$1" || true; }
 
 # Syntax-only mermaid lint: catch the breakers that silently fail previewers
@@ -139,19 +153,22 @@ whatitis_hash() {
 ANTI_STUB='see architecture\.md|deferred to ref-docs|\bTBD\b|TODO:[[:space:]]*document|stub page|placeholder page'
 TOKEN_RE='\{[A-Z_]+\}'
 
-# Per-type policy. echoes: sections|min_lines|need_mermaid|min_grounded
+# Per-type policy. echoes: sections|min_lines|need_mermaid|min_grounded|min_section_lines
+# min_section_lines: minimum non-blank content lines required UNDER each named
+# section (0 disables the per-section depth check). This is what turns a
+# present-but-empty heading — the hallmark of a shallow page — into a failure.
 type_policy() {
     case "$1" in
         Subsystem|Module|Feature|Entrypoint)
-            echo "What it is;How it works;Used by;Blast radius;See also|25|1|2";;
+            echo "What it is;How it works;Used by;Blast radius;See also|35|1|2|2";;
         API|DataModel)
-            echo "What it is;How it works;See also|18|0|1";;
+            echo "What it is;How it works;See also|22|0|1|2";;
         Dependency)
-            echo "What it is;Used by|10|0|0";;
+            echo "What it is;Used by|12|0|0|1";;
         ADR|Runbook)
-            echo "|8|0|0";;
+            echo "|8|0|0|0";;
         *)
-            echo "|8|0|0";;
+            echo "|8|0|0|0";;
     esac
 }
 
@@ -172,13 +189,26 @@ while IFS= read -r -d '' page; do
     [[ -z "$type_val" ]] && continue   # not a concept page
     CHECKED=$((CHECKED + 1))
 
-    IFS='|' read -r sections min_lines need_mermaid min_grounded <<< "$(type_policy "$type_val")"
+    IFS='|' read -r sections min_lines need_mermaid min_grounded min_section_lines <<< "$(type_policy "$type_val")"
 
-    # Q-SEC: required sections.
+    # Q-SEC: required sections must be present. Q-SECLEN: the NARRATIVE sections
+    # ("What it is" / "How it works") must carry real prose beneath the heading —
+    # a heading with nothing under it is the classic shallow stub. List sections
+    # ("Used by", "See also", "Blast radius") are legitimately terse, so the
+    # depth bar only applies to the narrative ones.
     if [[ -n "$sections" ]]; then
         IFS=';' read -ra secs <<< "$sections"
         for s in "${secs[@]}"; do
-            has_section "$s" "$page" || fail "$rel" "Q-SEC" "missing required section '## $s'"
+            if ! has_section "$s" "$page"; then
+                fail "$rel" "Q-SEC" "missing required section '## $s'"
+            elif [[ "${min_section_lines:-0}" -gt 0 ]]; then
+                case "$s" in
+                    "What it is"|"How it works")
+                        scl="$(section_content_lines "$s" "$page")"
+                        [[ "$scl" -ge "$min_section_lines" ]] \
+                            || fail "$rel" "Q-SECLEN" "section '## $s' has $scl content lines < $min_section_lines (shallow)";;
+                esac
+            fi
         done
     fi
 

package/scripts/tools/okf-validate.sh

@@ -11,6 +11,11 @@
 #   2. Every concept page (any *.md whose frontmatter declares `type:`) carries
 #      all required OKF frontmatter keys: type, title, description, resource.
 #   3. Every declared `type` is in the frozen code-repo vocabulary (§4 of HLD).
+#   3a. Every non-meta *.md is a real concept: an empty or frontmatter-less page
+#      (a blank placeholder) fails — it would otherwise be invisible to the
+#      quality + coverage layers, which both key on `type`.
+#   3b. No page carries an unreplaced {ALL_CAPS} template token (catches leftover
+#      placeholders in hand-seeded index pages, which the quality layer skips).
 #   4. Every relative markdown cross-link ( ](path.md) ) resolves to a file that
 #      exists inside the bundle. External (http/https/mailto) and pure-anchor
 #      (#frag) links are ignored.
@@ -105,14 +110,53 @@ if [[ ! -f "$BUNDLE/index.md" ]]; then
     add_error "missing bundle root: $BUNDLE/index.md"
 fi
 
+# A page is "meta" (not a concept) if it is a section/root index, the change log,
+# or the tool-generated coverage page. Everything else MUST be a real concept —
+# an empty or frontmatter-less .md placeholder is a completeness failure, not an
+# invisible non-concept.
+is_meta_page() {
+    local base="$1" page="$2"
+    case "$base" in
+        index.md|log.md|coverage.md) return 0;;
+    esac
+    grep -q '<!-- okf:coverage-generated -->' "$page" 2>/dev/null && return 0
+    return 1
+}
+
+# Non-blank body line count (everything after the frontmatter block).
+nonblank_body_lines() {
+    awk 'NR==1&&/^---$/{fm=1;next} fm&&/^---$/{fm=0;next} !fm{print}' "$1" \
+        | grep -cE '[^[:space:]]' || true
+}
+
 # --- 2/3. Per-page frontmatter + type vocabulary ---
 while IFS= read -r -d '' page; do
     PAGE_COUNT=$((PAGE_COUNT + 1))
     rel="${page#"$BUNDLE/"}"
+    base="$(basename "$rel")"
+
+    # Meta pages are NOT concepts: reserved index.md/log.md (OKF §6/§7) carry no
+    # concept frontmatter, and the tool-generated coverage page uses a descriptive
+    # (non-frozen) type. Exempt them from the frozen-vocab + required-field + body
+    # checks, and don't count them as concepts. The template-token (§3b) and
+    # cross-link (§4) scans below still cover them.
+    if is_meta_page "$base" "$page"; then
+        continue
+    fi
 
-    # A page is a "concept" only if its frontmatter declares a type.
     type_val="$(get_yaml_field "$page" "type")"
-    [[ -z "$type_val" ]] && continue
+
+    # Empty / placeholder pages: a non-meta page with no type (or no body) slips
+    # past every downstream check (quality + coverage both key on `type`). Catch
+    # it here so a blank or stub file can never ship.
+    if [[ -z "$type_val" ]]; then
+        if [[ "$(nonblank_body_lines "$page")" -eq 0 ]]; then
+            add_error "$rel: empty page (no frontmatter type, no body) — every wiki page must be a real concept"
+        else
+            add_error "$rel: untyped page (missing frontmatter 'type:') — not a valid concept page"
+        fi
+        continue
+    fi
     CONCEPT_COUNT=$((CONCEPT_COUNT + 1))
 
     for key in title description resource; do
@@ -124,6 +168,24 @@ while IFS= read -r -d '' page; do
     if ! is_known_type "$type_val"; then
         add_error "$rel: unknown concept type '$type_val' (frozen vocab: $OKF_TYPES)"
     fi
+
+    # A typed concept page with no body is still a stub — fail it even though the
+    # depth/anti-stub bars live in the quality layer (this layer must stand alone).
+    if [[ "$(nonblank_body_lines "$page")" -eq 0 ]]; then
+        add_error "$rel: concept page has empty body"
+    fi
+done < <(find "$BUNDLE" -type f -name '*.md' -print0 | sort -z)
+
+# --- 3b. Unreplaced template tokens (any page, including index pages) ---
+# Quality checks skip index.md pages, so a leftover {SECTION_TITLE}/{PROJECT_NAME}
+# placeholder in a hand-seeded index would otherwise survive. Match {ALL_CAPS}
+# tokens (safe: real prose almost never contains them).
+while IFS= read -r -d '' page; do
+    prel="${page#"$BUNDLE/"}"
+    if grep -qE '\{[A-Z][A-Z0-9_]+\}' "$page" 2>/dev/null; then
+        tok="$(grep -oE '\{[A-Z][A-Z0-9_]+\}' "$page" | head -1)"
+        add_error "$prel: unreplaced template token '$tok'"
+    fi
 done < <(find "$BUNDLE" -type f -name '*.md' -print0 | sort -z)
 
 # --- 4. Cross-link resolution ---

package/skills/init/SKILL.md

@@ -221,7 +221,7 @@ The tier-gated default rests on **maintainability/readability** (one navigable c
 1. `okf-plan-concepts.sh` ran and the expected/required/deferred counts were logged **before** any page was written (the concept boundary is a tool output, not an in-context guess).
 2. Every `required` entry in `concept-plan.json` has a non-stub page.
 3. `okf-validate-all.sh … --plan … --strict` exits 0 (structure + per-type quality + coverage all pass).
-4. `systems/coverage.md` was generated by tooling (verify the `<!-- okf:coverage-generated -->` marker) — no required package with `fan_in ≥ floor` is **MISSING**.
+4. `systems/coverage.md` was generated by tooling (verify the `<!-- okf:coverage-generated -->` marker) — **every** package/module the graph found is required by default (the fan-in floor only types Subsystem-vs-Module, it does not exempt), so none may be **MISSING**. Section `index.md` tables are regenerated by `okf-render-views.sh --section-indexes`, never hand-authored, so their links cannot dangle.
 5. On any failure: **do not** atomic-rename; surface `.state/validation-report.json`.
 
 > **Red flag:** writing concept pages without first running `okf-plan-concepts.sh`, or finishing generation while any `required` plan entry is unwritten, is a **completeness failure** — not a stylistic one.

package/skills/init/references/okf-emitter.md

@@ -77,7 +77,8 @@ Templates for each bundle page live in `core/templates/okf/` (`index.md`,
 ## Frozen `type` vocabulary
 
 Every concept carries a `type` from this frozen set (changing it churns every
-file; versioned via `index.md` frontmatter `okf_types_version`):
+file; versioned via the `okf-types-version` comment in the wiki root `index.md`
+body — OKF §6/§11 permit only `okf_version` in an index file's frontmatter):
 
 | type | Maps to | Home |
 |------|---------|------|
@@ -103,6 +104,16 @@ the task at hand?"), never a summary. Draft extensions are namespaced `x-` and
 ignored by generic OKF consumers: `x-grounded-paths`, `x-hotspot-score`,
 `x-callers`.
 
+**Meta pages are not concepts.** Index files (`wiki/index.md` and every
+`<section>/index.md`) carry **no concept frontmatter**: per OKF §6 an index file
+has no frontmatter, and per §11 the root `index.md` may declare **only**
+`okf_version`. The tool-generated `systems/coverage.md` is a non-reserved file, so
+OKF §9.1/§9.2 require it to carry a typed frontmatter block; it uses a descriptive
+`type: Report` and is exempt from the frozen vocabulary via `is_meta_page`
+(basename + the `<!-- okf:coverage-generated -->` marker). `okf-validate.sh`
+short-circuits all meta pages before the concept checks, so they are never
+vocab-checked or counted as concepts.
+
 ## Concept granularity (resolves open decision 1)
 
 Derive concepts from the graph, not by hand:
@@ -122,17 +133,21 @@ Derive concepts from the graph, not by hand:
 ```
 1. Survey        → existing /draft:init 5-phase + graph snapshot (graph-snapshot.sh)
 2. Plan          → DETERMINISTIC. okf-plan-concepts.sh derives the expected-concept
-                   set from the graph (every package with fan_in ≥ floor → required
-                   Subsystem/Module; entrypoints → required; below-floor / allow-defer
-                   → deferred with a reason) and writes draft.tmp/.state/concept-plan.json.
+                   set from the graph. EVERY package the graph knows about is
+                   required (fan_in ≥ floor → Subsystem; below floor → Module — the
+                   floor only types/orders, it never exempts); entrypoints → required;
+                   only --allow-defer matches are deferred (with a reason). Writes
+                   draft.tmp/.state/concept-plan.json.
                      okf-plan-concepts.sh --repo . [--scope PATH] \
                        [--manifest FILE] [--min-fan-in 2] [--allow-defer GLOB]... \
                        --out draft.tmp/.state/concept-plan.json
                    This replaces the old in-context concept enumeration — the boundary
                    of the work is now a tool output, not an LLM judgment, so modules
-                   cannot be silently dropped. LOG the counts (expected/required/
-                   deferred) BEFORE writing any page. `generated_order` is topo-ish
-                   (required + high-fan-in first) so forward cross-links resolve.
+                   and sub-modules cannot be silently dropped. (Legacy fan-in
+                   exemption is opt-in via --defer-below-floor.) LOG the counts
+                   (expected/required/deferred) BEFORE writing any page.
+                   `generated_order` is topo-ish (required + high-fan-in first) so
+                   forward cross-links resolve.
 3. Generate      → iterate concept-plan.generated_order; write ONE page per REQUIRED
                    entry, grounding each from the graph:
                      x-callers        ← graph-callers.sh --symbol <c>
@@ -152,9 +167,11 @@ Derive concepts from the graph, not by hand:
                            --plan draft.tmp/.state/concept-plan.json \
                            --path-index draft.tmp/.state/path-to-concept.json \
                            --strict --report draft.tmp/.state/validation-report.json
-                   It runs, in order: okf-validate.sh (structure + reverse index),
-                   okf-validate-quality.sh (per-type anti-stub / depth / mermaid lint),
-                   okf-coverage-check.sh (every required plan entry → real page).
+                   It runs, in order: okf-validate.sh (structure + reverse index +
+                   empty/untyped-page + leftover-template-token + dangling-link checks),
+                   okf-validate-quality.sh (per-type anti-stub / depth / per-section
+                   content / mermaid lint), okf-coverage-check.sh (every required plan
+                   entry → real page).
                    ANY layer failing ⇒ exit non-zero ⇒ DO NOT atomic-rename.
                    coverage.md (systems/coverage.md) is regenerated by the coverage
                    layer; it is tool-owned (marker <!-- okf:coverage-generated -->) —
@@ -193,6 +210,7 @@ regenerated on every init/refresh so they never drift from the bundle:
 ```bash
 okf-render-views.sh draft/wiki \
   --arch-out draft/architecture.md \
+  --section-indexes \
   --concept-map-into draft/wiki/index.md \
   --concept-map-into draft/.ai-context.md \
   --web draft/wiki/web/index.html
@@ -200,6 +218,11 @@ okf-render-views.sh draft/wiki \
 
 - `--arch-out` renders the linear `architecture.md` (banner + TOC + every concept
   page in canonical section order, frontmatter stripped, Mermaid preserved).
+- `--section-indexes` rebuilds each `<section>/index.md` concept table (between its
+  `CONCEPT-MAP` markers) from the pages that actually exist in that directory. This
+  is mandatory: section indexes are NOT hand-authored — building them from real
+  files is what makes their links impossible to dangle. Never write a section
+  index "Concepts" table by hand.
 - `--concept-map-into` rebuilds the routing table between the
   `<!-- CONCEPT-MAP:START -->` / `:END` markers from each concept's `title` +
   `type` + `description` (section `index.md` pages excluded).