Squashed 'shared/' changes from 7aa53fc..a2b57d2

a2b57d2 docs(plan): V1 — «de 5 linjene» var ikke homogene; :214 er ikke en literal
d63e45d docs(plan): okf-versjonssjekken utført — hypotesen falsifisert på to stale premisser
ef31dda docs(plan): V1 §4.2 — pin + id + sitering avgjort, og ratifiseringsgaten funnet
35220f7 docs(plan): V1 §4.1 — serialiseringsformen er bundet av :158, så 6 sider er invariant
8a7d430 docs(plan): operatøren avgjorde V1 (O2) og B1 (O1) — B1 utført, V1 gated
f306c7b docs(plan): V1 §5.1 — konsument-kostnaden målt @ 8a14137, O3-raden priset
ab0ea8f docs(plan): innboksrunden — V1 utvidet med tre målte funn, §7.2-siteringen ref-bundet
84a3010 docs(plan): §7.2 — MCP-spørsmålet er avgjort av frossen tekst, S2.2 og S2.4 er ugated
e984d51 docs(plan): D-B ankret, D-A#3s årsak er repo-avhengig, V1 utvidet med oppstrøms-evidens
3de702b docs(plan): V1 §6 — rekkevidde-forbeholdet korrigert, og funnet under funnet
249425b docs(plan): amendment-underlag — D-A#3s ÅRSAK rettet, drift ikke avvik
4876970 docs(plan): V1-underlag — generated-feltets form etter OKF v0.2
3f18ca7 docs(plan): B1/D4 operator question — nav-golden's normative status, four costed options
29ad8ca docs(plan): amendment-underlag — frossen tekst per køpunkt, med målt fasit-effekt
a67a243 docs(plan): ordering-axes ruling — three distinct axes, as an interpretation record
381d9e5 docs(plan): guard adoption plan pins no version — v0.2 header was stale
54ca0ff docs(plan): D3 ratified — status vocabulary landed in coord register
fe6b998 docs(plan): D3 status vocabulary — canonical 7-token set for roll-up register
c66ccc3 docs(plan): D2 register-form fix — two-output model resolves ÅS#5
b641741 docs(examples): nav-golden fixture class — bundle → read-context goldens
9801d35 docs(spec): method-spec §3 Step 1 — Q3 navigation contract (hierarchy)
bfa5a9b docs(spec): ingest-spec — land ratified D1 stamp model
5f046ab docs(plan): Q3 finding — method-spec §3 silently forbids hierarchical bundles
a013e8b docs(plan): F1 direction — free-text sources belong in ingest-spec door A
84191c6 docs(plan): record commons↔implementation-repo coordination boundary
cae9972 docs(plan): llm-ingestion-guard adoption — planned at future untrusted ingest boundaries

git-subtree-dir: shared
git-subtree-split: a2b57d20fc0953c19776c21ce1311f234386a590

examples/nav-golden-escape/README.md

@@ -0,0 +1,27 @@
+# nav-golden-escape — negative navigation golden (the gate must be able to go red)
+
+Per catalog's requirement that step 0's gate must be able to **fail** (a gate that can
+only pass proves nothing), this negative case makes a conformant navigator and a naive one
+**provably diverge**. It is the counterpart to `nav-golden-hierarchy` (the positive case).
+
+`bundle/index.md` links one valid sibling and three escaping / trap targets:
+
+| Link | Class | Conformant outcome |
+|---|---|---|
+| `valid.md` | in-bundle | returned |
+| `../SHOULD-NOT-BE-READ.md` | `..` escape (the decoy really exists, one level up) | skipped; decoy never read |
+| `../../../../etc/passwd` | deep `..` escape | skipped |
+| `/etc/passwd` | root-relative **trap** | skipped |
+
+The trap is the load-bearing one. Under the ratified rule, a leading `/` denotes the
+**bundle root**, so `/etc/passwd` resolves to `{bundle}/etc/passwd` (no such file → skip),
+NOT the filesystem path. A naive implementation that reads `/` as filesystem-absolute opens
+the real `/etc/passwd` — a path-traversal breach. This case fails for any implementation
+that raises, reads the decoy, or leaks `/etc/passwd` content; it passes only when the
+read-context is exactly `valid.md`.
+
+The malformed-target sub-class (an embedded null byte, other invalid path components) is
+covered by the method-spec §11 **Navigation boundary** seam as a unit test — a literal null
+byte does not belong in a committed text fixture. (See the relocated finding
+`docs/plan/2026-07-20-funn-portfolio-optimiser-nullbyte.local.md` for the concrete
+null-byte reproduction that motivates the seam.)

examples/nav-golden-escape/SHOULD-NOT-BE-READ.md

@@ -0,0 +1,6 @@
+---
+type: project
+title: "Decoy — MUST NOT be read"
+---
+
+This file sits ONE level above `bundle/`, outside the bundle. If its text ever appears in a read-context, the navigator resolved a `..` escape and breached the bundle boundary. It MUST never be reached.

examples/nav-golden-escape/bundle/index.md

@@ -0,0 +1,12 @@
+---
+type: index
+okf_version: 0.1
+title: "Nav-golden — escape / boundary case"
+---
+
+Nav-golden escape case. Every link but the first escapes the bundle or is a root-relative trap; a conformant navigator skips them all, reads none of them, raises nothing, and still returns the one valid sibling.
+
+- [Valid sibling](valid.md)
+- [Parent escape](../SHOULD-NOT-BE-READ.md)
+- [Deep escape](../../../../etc/passwd)
+- [Root-relative trap](/etc/passwd)

examples/nav-golden-escape/bundle/valid.md

@@ -0,0 +1,6 @@
+---
+type: project
+title: "Valid sibling"
+---
+
+The only in-bundle target. A conformant navigator returns exactly this file.

examples/nav-golden-escape/expected-read-context.md

@@ -0,0 +1,10 @@
+Nav-golden escape case. Every link but the first escapes the bundle or is a root-relative trap; a conformant navigator skips them all, reads none of them, raises nothing, and still returns the one valid sibling.
+
+- [Valid sibling](valid.md)
+- [Parent escape](../SHOULD-NOT-BE-READ.md)
+- [Deep escape](../../../../etc/passwd)
+- [Root-relative trap](/etc/passwd)
+
+## project: Valid sibling
+
+The only in-bundle target. A conformant navigator returns exactly this file.

examples/nav-golden-hierarchy/README.md

@@ -0,0 +1,34 @@
+# nav-golden-hierarchy — hierarchical navigation golden
+
+Fixture class **nav-golden** (commons-owned, per the D4 step-0 split): `bundle/` in,
+`expected-read-context.md` out. Unlike the ingest-golden class (ingest-spec §11,
+extraction-shaped: `manifest.json` → `expected-bundle/`), a nav-golden case is
+**bundle → read-context** — the only shape that can express the load-bearing property
+"two conformant implementations MUST produce an identical read-context from the same
+bundle" (method-spec §3 Step 1).
+
+This **positive** case exercises every decision the Q3 navigation contract pins:
+
+| Decision (method-spec §3 Step 1) | How this bundle exercises it |
+|---|---|
+| Hierarchy allowed; escape, not depth, forbidden | `a/`, `a/b/` are navigated; nothing escapes |
+| Link syntax: leading `/` = bundle root, else relative | `index.md`: relative `overview.md` + root-relative `/a/index.md`; `a/index.md`: relative `b/index.md` + root-relative `/overview.md` |
+| Depth-first, first-seen order | render order is `overview` → `doc-a` → `doc-b` |
+| Dedup on resolved path | `/overview.md` (from `a/`) resolves to the already-seen `overview.md` → one entry |
+| Cycle termination | `a/b/index.md` links back to `/a/index.md` (already seen) → stops |
+| One segment per level | each index links only its immediate children |
+| Missing `index.md` binds the root alone | `c/` has no `index.md` and nothing links `c/orphan.md`; it is simply unreachable, not an error |
+| Verdict exclusion = type check per reached file, recursive | `a/verdict-nested.md` is reached but excluded |
+| Flat render regardless of depth | nested concepts render as the same `## {type}: {title}` sections; no level heading; nested index bodies are navigation, not content, and are not rendered |
+
+**Traversal trace:** `index.md` (its body is the leading summary) → `overview.md` →
+`/a/index.md` → `a/doc-a.md` → `a/verdict-nested.md` (reached, excluded) → `a/b/index.md`
+→ `a/b/doc-b.md` → `/a/index.md` (seen, deduped) → `/overview.md` (seen, deduped).
+Unreachable: `c/orphan.md`.
+
+**Serialization** the gate compares against: the root index body verbatim, then each
+**non-index** concept as `## {type}: {title}` + blank line + the file body, sections
+separated by one blank line, file ending in exactly one trailing newline. The spec does
+not pin whitespace beyond this shape; a gate MAY compare byte-exact or after
+trailing-whitespace normalization. **Only the root index body is the summary** — nested
+index bodies (`a/index.md`, `a/b/index.md`) are navigation and do not appear.

examples/nav-golden-hierarchy/bundle/a/b/doc-b.md

@@ -0,0 +1,6 @@
+---
+type: reference
+title: "Doc B"
+---
+
+Level-2 concept reached depth-first, deepest in the traversal.

examples/nav-golden-hierarchy/bundle/a/b/index.md

@@ -0,0 +1,8 @@
+---
+type: index
+okf_version: 0.1
+title: "Subsection B index"
+---
+
+- [Doc B](doc-b.md)
+- [Back to A](/a/index.md)

examples/nav-golden-hierarchy/bundle/a/doc-a.md

@@ -0,0 +1,6 @@
+---
+type: methodology
+title: "Doc A"
+---
+
+Level-1 concept reached depth-first after Overview.

examples/nav-golden-hierarchy/bundle/a/index.md

@@ -0,0 +1,10 @@
+---
+type: index
+okf_version: 0.1
+title: "Section A index"
+---
+
+- [Doc A](doc-a.md)
+- [Nested verdict](verdict-nested.md)
+- [Subsection B](b/index.md)
+- [Overview again](/overview.md)

examples/nav-golden-hierarchy/bundle/a/verdict-nested.md

@@ -0,0 +1,8 @@
+---
+type: verdict
+title: "Nested verdict — must be excluded"
+decision: approved
+description: "A verdict file at a nested level. A conformant navigator reaches it (dedup marks it seen) but MUST exclude it from the read-context — recursively, not only at the root. This is the leakage surface a graph-based exclusion would miss."
+---
+
+This body MUST NOT appear in the read-context.

examples/nav-golden-hierarchy/bundle/c/orphan.md

@@ -0,0 +1,6 @@
+---
+type: project
+title: "Orphan — unreachable"
+---
+
+Directory `c/` has no `index.md`, and nothing links to this file. A link-following navigator never reaches it; a directory-walking one wrongly would. It MUST be absent from the read-context, and its parent directory's missing `index.md` MUST NOT be an error (that rule binds the bundle root alone).

examples/nav-golden-hierarchy/bundle/index.md

@@ -0,0 +1,10 @@
+---
+type: index
+okf_version: 0.1
+title: "Nav-golden — hierarchical navigation case"
+---
+
+Nav-golden hierarchical case. This bundle exercises depth-first traversal, both link forms (root-relative and relative), recursive verdict exclusion, resolved-path de-duplication, cycle termination, and the root-only binding of the missing-index rule.
+
+- [Overview](overview.md)
+- [Section A](/a/index.md)

examples/nav-golden-hierarchy/bundle/overview.md

@@ -0,0 +1,6 @@
+---
+type: project
+title: "Overview"
+---
+
+Root-level concept reached by a relative link.

examples/nav-golden-hierarchy/expected-read-context.md

@@ -0,0 +1,16 @@
+Nav-golden hierarchical case. This bundle exercises depth-first traversal, both link forms (root-relative and relative), recursive verdict exclusion, resolved-path de-duplication, cycle termination, and the root-only binding of the missing-index rule.
+
+- [Overview](overview.md)
+- [Section A](/a/index.md)
+
+## project: Overview
+
+Root-level concept reached by a relative link.
+
+## methodology: Doc A
+
+Level-1 concept reached depth-first after Overview.
+
+## reference: Doc B
+
+Level-2 concept reached depth-first, deepest in the traversal.