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>

CHANGELOG.md

@@ -171,7 +171,7 @@ container, and it is the first release whose artefacts are published alongside i
 - The shared expert-reviewer persona's canonical example verdict is worded domain-neutrally
   ("i tilsvarende anlegg" rather than "i kontorbygg"), pulled from the upstream commons repository.
   The walkthrough prints that `rationale` verbatim, so the wording was a building-type justification
-  read out over a road-lighting project; it could not be fixed downstream, because overriding the
+  read out over an energy project; it could not be fixed downstream, because overriding the
   text locally would re-stub the very artifact the shared skill exists to make load-bearing. The
   `marker` value is byte-unchanged, and the pinned transcript fixture was regenerated against a
   prediction written before the pull — the printed line is clipped at a fixed width, so the swap
@@ -266,7 +266,7 @@ First tagged release. There is no prior release, so the entries below describe w
   Before this, every stage reasoned only about numbers the proposal itself supplied, so an internally
   consistent hallucination cleared the whole gate. Validation, never repair: the proposal is
   rejected, never silently corrected to the baseline. The argument is **optional** (`None` reproduces
-  the earlier behaviour) but both run paths set it — the road path always, the bundle path only when
+  the earlier behaviour) but both run paths set it — the reference path always, the bundle path only when
   the bundle ships a `cost-baseline.json`, since a pre-amendment bundle is legitimately unanchored.
   A baseline that exists but is malformed raises on both loaders rather than reading as "no
   baseline". Method caps are looked up in an injectable `METHOD_CAPS` registry, so a second measure