feat: hive setup data model and API (Beute L1)

Each colony can now hold its hive setup (Ist-Zustand) as validated
JSON with an append-only change log:

- catalog: hive systems and part types with dimensions, placement
  rules and state fields; Liebig-Zander 10 seeded with fixed ids
  (owner's equipment incl. Bausperre, Futterzarge, Nassenheider)
- pure domain module (operations, validator, derived facts) with
  shared JSON fixtures the frontend runs too
- API: catalog (hive-systems:manage), setup create/change/history/
  state at a day (colonies:read/update), 409 HIVE_CONFLICT with the
  current state, idempotent writes, HiveChanged event
- inspections can carry hive ops saved in the same transaction
- backup export/import of the new tables (backup wins per colony)
- docs: ARCHITECTURE section 13, Annahmen 95-100

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

ApiCore-Frontend/src/lib/system/labels.spec.ts

@@ -82,4 +82,8 @@ describe("DOMAIN_EVENT_LABELS completeness", () => {
       TskReferenceDayReached: "TSK-Stichtag erreicht",
     });
   });
+
+  it("names HiveChanged", () => {
+    expect(DOMAIN_EVENT_LABELS.HiveChanged).toBe("Beute geändert");
+  });
 });

ApiCore-Frontend/src/lib/system/labels.ts

@@ -62,6 +62,7 @@ export const DOMAIN_EVENT_LABELS: Record<string, string> = {
   ColonyMoved: "Volk umgesetzt",
   ApiaryChanged: "Stand geändert",
   TskReferenceDayReached: "TSK-Stichtag erreicht",
+  HiveChanged: "Beute geändert",
 };
 
 /** The oldest open event is this old (seconds) before the worker counts as stuck. */