test: add contract tests for CLI output parsing

Implement contract testing to catch CLI schema drift early:

Contract Test Suite (fixture_contract_tests.rs):
- parse_lore_me_empty_fixture: Validates LoreMeResponse on empty data
- parse_lore_me_with_activity_fixture: Real lore output with activity
- parse_br_list_empty_fixture: Empty beads list
- parse_br_list_with_beads_fixture: Real br output with beads

Fixtures (captured from real CLI output):
- fixtures/lore/me_empty.json: Synthetic empty response
- fixtures/lore/me_with_activity.json: Real 'lore --robot me' output
- fixtures/br/list_empty.json: Empty array []
- fixtures/br/list_with_beads.json: Real 'br list --json' output
- fixtures/br/bv_triage.json: Real 'bv --robot-triage' output

Fixture Regeneration:
- scripts/regenerate-fixtures.sh: Captures fresh CLI output
  - Run periodically to update fixtures
  - CI can diff against committed fixtures to detect drift

Why Contract Tests Matter:
MC depends on external CLIs (lore, br, bv) whose output format may
change. Contract tests fail fast when our Rust types diverge from
actual CLI output, preventing runtime deserialization errors.

The tests use include_str!() for compile-time fixture embedding,
ensuring tests fail to compile if fixtures are missing.

scripts/regenerate-fixtures.sh

@@ -0,0 +1,31 @@
+#!/bin/bash
+# Regenerate CLI output fixtures from real commands
+#
+# Run this periodically to ensure fixtures match actual CLI output format.
+# CI can compare fresh fixtures against committed ones to detect schema drift.
+
+set -e
+
+FIXTURE_DIR="src-tauri/tests/fixtures"
+
+echo "Regenerating CLI fixtures..."
+
+# lore fixtures
+echo "  Capturing lore --robot me..."
+lore --robot me > "${FIXTURE_DIR}/lore/me_with_activity.json" 2>/dev/null || {
+  echo "    Warning: lore command failed, skipping"
+}
+
+# br fixtures
+echo "  Capturing br list..."
+br list --json > "${FIXTURE_DIR}/br/list_with_beads.json" 2>/dev/null || {
+  echo "    Warning: br command failed, skipping"
+}
+
+# bv fixtures
+echo "  Capturing bv --robot-triage..."
+bv --robot-triage > "${FIXTURE_DIR}/br/bv_triage.json" 2>/dev/null || {
+  echo "    Warning: bv command failed, skipping"
+}
+
+echo "Done! Review changes with: git diff ${FIXTURE_DIR}"