refactor(examples): replace sector-specific example material with generic, fictitious examples

The context sets, the packaged knowledge bases and the example bundles are
replaced by one fictitious example set about IT operations in an invented
organisation: three context sets (serverrom-2027, driftsavtale-2027 and the
two-base drift-og-avtale-2027), two synthetic knowledge bases under
src/portfolio_optimiser/data/kunnskapsbaser and two example bundles under
src/portfolio_optimiser/data/bundles. Numbers, codes and structural values in
tests and fixtures are kept; names, ids and wording change. Dated measurement
documents that only recorded runs on the replaced material are deleted.

Gate figures measured on the new set are not comparable with earlier ones.
The exclusion gate from the previous commit is green: 0 tracked files hit
outside the shared/ subtree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/fase1-spikes/findings-b.md

@@ -41,12 +41,12 @@ a tautology — caught and rebuilt; see the Method note below.)
   reference projects. MAF **accumulates the shared conversation thread across `.run()`
   calls**: each run's participants receive the PRIOR projects' prompts and replies too.
   Measured (project ids visible per run, in order):
-  `[[FV42-GSV-E1], [FV42-GSV-E1, RV13-RAS-TP], [FV42-GSV-E1, RV13-RAS-TP, BRU-LAKS-REHAB]]`
+  `[[KONTOR-IT-E1], [KONTOR-IT-E1, NETT-SIKR-TP], [KONTOR-IT-E1, NETT-SIKR-TP, ARKIV-LAGR-MIGR]]`
   — strictly monotonic growth → run N is contaminated by runs 0..N-1 → **genuine state
   bleed (G2/B7)**.
 - **Fresh instance:** `fresh_workflow()` builds a new workflow + clean thread per run →
-  each participant sees ONLY its own project: `[[FV42-GSV-E1], [RV13-RAS-TP],
-  [BRU-LAKS-REHAB]]` → **zero cross-run contamination** (B7 mitigation works).
+  each participant sees ONLY its own project: `[[KONTOR-IT-E1], [NETT-SIKR-TP],
+  [ARKIV-LAGR-MIGR]]` → **zero cross-run contamination** (B7 mitigation works).
 - **Implication:** Fase 2 fan-out must build a fresh workflow/executor instance per
   project run (a factory like `fresh_workflow()`), never reuse a shared instance — a
   reused `Workflow` leaks one project's context into the next, which would corrupt

docs/fase1-spikes/findings-c.md

@@ -28,7 +28,7 @@ validated. A valid proposal (claim well under the feasible cap) returns a
 `ValidatedProposal` with the percentiles. **`self_repair` is capped** at `max_attempts`
 and hard-stops (verified it calls the generator exactly N times and no more, B4).
 
-### Worked example (project FV42-GSV-E1, codes 05.2 + 03.1)
+### Worked example (project KONTOR-IT-E1, codes 05.2 + 03.1)
 
 - Affected items' total ≈ **1 482 500 NOK**; 30% feasible cap ≈ **444 750 NOK**.
 - Claim **200 000** → `ValidatedProposal` with ordered P10/P50/P90 around the cap.