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>

tests/test_cost_baseline_flag_loadbearing.py

@@ -1,13 +1,13 @@
-"""P21 DEL A - the PROJECT carries the price, so a run against a road normal can be anchored.
+"""P21 DEL A - the PROJECT carries the price, so a run on a requirements base can be anchored.
 
 **The measurement this closes.** Four paid stress rounds (P16/P18/P19/P17b/P20) ran ENTIRELY
 un-anchored. The cause is one line: the only file loader reads ``cost-baseline.json`` out of the
-BUNDLE directory (``okf.load_optional_cost_baseline``), and no vegnormal ships one — N100, N200,
-N500 and R761 are knowledge, and knowledge carries requirements, never amounts. The validator's
-stage 0 — the one stage that can tell an invented cost line from a line this project actually buys
-— was therefore skipped in every single one, and ``validated`` could not mean what it says: P20
-G1/G2 measured real R761 process numbers (``12.11`` three times on Søråsen, ``1.1.1`` on Lindås)
-validating with amounts nobody had anywhere.
+BUNDLE directory (``okf.load_optional_cost_baseline``), and no requirements base or process
+catalogue ships one — they are knowledge, and knowledge carries requirements, never amounts. The
+validator's stage 0 — the one stage that can tell an invented cost line from a line this project
+actually buys — was therefore skipped in every single one, and ``validated`` could not mean what it
+says: P20 G1/G2 measured real process-catalogue numbers (``12.11`` three times on one set,
+``1.1.1`` on another) validating with amounts nobody had anywhere.
 
 ``--cost-baseline FILE`` is PM decision (e), taken over three alternatives P20 wrote down: (a)
 refusing every requirement-shaped code un-anchored would make the one realistic context set
@@ -220,8 +220,9 @@ def test_the_bundle_loader_still_parses_through_the_same_seam(tmp_path: Path) ->
 
 
 def test_cli_requires_a_knowledge_base(tmp_path: Path, capsys: pytest.CaptureFixture[str]) -> None:
-    """(h) On the road path the baseline IS ``Project.cost_items``, so a file there is a second
-    source for one fact with nothing to break the tie (``--require-cost-baseline``'s reason)."""
+    """(h) On the reference-project path the baseline IS ``Project.cost_items``, so a file there is
+    a second source for one fact with nothing to break the tie (``--require-cost-baseline``'s
+    reason)."""
     rc = run.main(["P1", "--docs-dir", "docs", "--cost-baseline", _schedule(tmp_path, RIGG=1000.0)])
 
     assert rc == 1
@@ -313,7 +314,7 @@ def test_cli_wiring_anchors_the_dry_run_and_says_so(
     assert "Cost baseline: NONE in the bundle" in before
     assert "Cost baseline: 2 lines from" not in before
 
-    schedule = _schedule(tmp_path, RIGG=1000.0, ASFALT=250.0)
+    schedule = _schedule(tmp_path, RIGG=1000.0, LISENS=250.0)
     assert run.main([*argv, "--cost-baseline", schedule]) == 0
     after = capsys.readouterr().out