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_stress_judge_loadbearing.py

@@ -14,17 +14,18 @@ tests`` hit only unrelated files).
 **THE ORDER'S (a) WAS VACUOUS AS WRITTEN, AND THAT IS MEASURED.** The order defines grounded as
 "a must_cite path was OPENED *or* CITED". But on the S2c navigation path ``run_project`` stamps
 ``citations = bundle_citations(bundle)``, which is ONE CITATION PER CONTEXT FILE - the whole corpus.
-Measured on n100-2023: 446 context files, 446 citations, and **6 of 6 fasit paths already "cited"
-before a single model call**. A judge honouring the order literally would be a gate that can only
-be green, which is the repo's own vacuous-gate class, inside the gate built to stop it. So
+Measured on a requirements base during development: 446 context files, 446 citations, and **6
+of 6 fasit paths already "cited" before a single model call**. A judge honouring the order
+literally would be a gate that can only be green, which is the repo's own vacuous-gate class,
+inside the gate built to stop it. So
 ``grounded`` counts a CITATION only when the citation list is NARROWER than the base (a declared
 pre-pass cut); a whole-base list is reported as such and carries nothing. Both halves are reported
 either way, so the operator can read which one fired - the deviation is stated, never silent.
 
 **(b') was checked for the same vacuity and is CLEAN.** ``bundle_citations`` snippets are concept
-BODIES, and the ``ref``/``title`` live in FRONTMATTER: measured 0 of 446 n100 bodies contain
-``Krav 4.1.2-1``. So the snippet arm can carry (b') without being satisfied by construction, and
-the order's definition is kept. Which half fired is still reported.
+BODIES, and the ``ref``/``title`` live in FRONTMATTER: measured 0 of 446 bodies of that base
+contain its ``Krav 4.1.2-1``. So the snippet arm can carry (b') without being satisfied by
+construction, and the order's definition is kept. Which half fired is still reported.
 
 **A denominator, always** (Verifiseringsloven ansikt 4): every verdict names how many tool calls,
 citations and approach rows it saw. An outbox with no artefacts RAISES rather than reporting
@@ -60,7 +61,7 @@ from portfolio_optimiser import stress
 _GOOD = "krav/N1/id-good.md"
 _OTHER = "krav/N1/id-other.md"
 _REF = "Krav 1.2.3-4"
-_TITLE = "Krav 1.2.3-4 Rundkjoringer"
+_TITLE = "Krav 1.2.3-4 Sikkerhetskopier"
 
 
 def _minibase(root: Path) -> Path:
@@ -272,8 +273,9 @@ def test_a_opening_some_other_document_does_not_ground_it(tmp_path: Path) -> Non
 
 
 def test_b_a_whole_base_citation_list_cannot_ground_an_approach(tmp_path: Path) -> None:
-    """Measured on n100-2023: 446 context files, 446 citations, 6/6 fasit paths 'cited' before
-    any model call. Honouring the order literally would make (a) green by construction."""
+    """Measured on a requirements base: 446 context files, 446 citations, 6/6 fasit paths
+    'cited' before any model call. Honouring the order literally would make (a) green by
+    construction."""
     verdict = _judge(tmp_path, tool_calls=[])
     row = verdict.approaches[0]
     assert row.cited == (_GOOD,), "the path IS in the citation list"
@@ -331,8 +333,8 @@ def test_e_a_measure_that_names_nothing_is_carried_only_by_a_narrowed_snippet(
 def test_e_a_whole_base_snippet_does_not_name_the_concept(tmp_path: Path) -> None:
     """P18/C2 (PM decision, P16 § 6.2). ``bundle_citations`` stamps EVERY context file before any
     model call, so a mark found in a whole-base snippet is evidence about what the base contains,
-    not about what this run said. Measured on r761: the process number ``12.1`` stands in the
-    bodies themselves, so that row came back ``named`` for a run that never named it.
+    not about what this run said. Measured on a process catalogue: the process number ``12.1``
+    stands in the bodies themselves, so that row came back ``named`` for a run that never named it.
 
     The pair with the arm above is the discriminator: the SAME snippet, the same mark, and the only
     difference is the scope."""
@@ -660,10 +662,11 @@ def test_the_cli_refuses_to_guess_which_base_a_multi_base_outbox_is_for(
 # P21 B3: the judge reports what the run was ANCHORED on, which codes the project actually PRICES,
 # and WHICH falsifier caught the falsification arm.
 #
-# The measured reason. Rounds 1-4 all ran un-anchored — a vegnormal ships no ``cost-baseline.json``
-# and the only file loader read one out of the bundle — so stage 0 never spoke and the ``a4`` arm
-# fell, when it fell, on P7's grounding check. "It was refused" and "the stage that knows what this
-# project buys refused it" are different facts, and only the second is what anchoring bought.
+# The measured reason. Rounds 1-4 all ran un-anchored — a requirements base ships no
+# ``cost-baseline.json`` and the only file loader read one out of the bundle — so stage 0 never
+# spoke and the ``a4`` arm fell, when it fell, on P7's grounding check. "It was refused" and "the
+# stage that knows what this project buys refused it" are different facts, and only the second is
+# what anchoring bought.
 # --------------------------------------------------------------------------------------------