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

README.md

@@ -20,6 +20,15 @@ so the only thing that differs is the agent framework itself.
   bundle (OKF / LLM-wiki): one office building, one LED-retrofit measure, with a seed expert
   verdict encoding the realization gap and a golden-suite of expected validator outcomes. A
   small **dev fixture** for exercising the agentic loop; a realistic full-scale example comes later.
+- [`examples/nav-golden-hierarchy/`](examples/nav-golden-hierarchy/) and
+  [`examples/nav-golden-escape/`](examples/nav-golden-escape/) — the **nav-golden** fixture class:
+  `bundle/` in, `expected-read-context.md` out, exercising the navigation contract (method-spec §3
+  Step 1) with one positive case (hierarchy, dedup, cycle termination, verdict exclusion) and one
+  negative case (`..` and root-relative escapes, so a gate built on them can actually go red). Each
+  case documents itself in its own `README.md`. **Informative listing only** — no normative file
+  refers to this class, and the comparison rule is deliberately not pinned (each case's README
+  leaves a gate free to compare byte-exact or after trailing-whitespace normalization), so these
+  are not ground truth in the sense method-spec §7 uses the word.
 - [`skills/expert-reviewer/`](skills/expert-reviewer/) — the **expert-reviewer persona** as a
   framework-neutral Agent Skill: a `SKILL.md` persona prompt (energy-advisor / M&V role + the
   realization-gap methodology the validator cannot compute) and a canonical