feat(dashboard): add forward "what's next" signal + fix upcoming floor

The daily-file bill queue is a backward snapshot, so "upcoming" could only
resurface the latest past day (the 08-31 snapshot read as today's queue) and
there was no "what is scheduled next." leginfo bill status/history are
backward-only, so the genuine future-dated signal is the chambers' "upcoming
events" calendars.

- api.py: floor the "upcoming" view at *today* (not the DB max date) when no
  as_of is pinned; surface next_legislative_day + scheduled_events (next 7
  days) on /bills. Add _today_iso / _next_legislative_day / _scheduled_events,
  all degrading to a recess marker / [] (never 5xx).
- relational.py: schema v2 adds the scheduled_events table +
  store_scheduled_events (idempotent per-day refresh), load_scheduled_events,
  next_legislative_day.
- parsers.py: parse_events_page + classify_event_kind for the chamber events
  calendar; skip empty-title rows (decompose the <time> before the fallback).
- ingest.py + cli.py: --store-events lane (cache-first, recess-safe) that
  parses the calendar HTML into scheduled_events.
- sources.py + config.yaml: register assembly_events / senate_events
  (kind: events, empty_is_ok: true).
- run_ingest.sh: run the events lane after the daily-file lane as non-fatal
  (skippable via CALI_SCRAPER_SKIP_EVENTS=1); daily-file exit still gates cron.
- frontend: "Next legislative day" line + "What's next · next 7 days" band
  with honest recess empty states.
- DASHBOARD.md: document the forward signal + known limitations (leginfo
  backward-only gap, recess empty state, 08-31 snapshot is analysis-only).
- tests: 5 new API tests + 18 parse-events tests; 170 pass, 92% coverage.

config.yaml

@@ -70,6 +70,23 @@ sources:
         # an error. The scheduler must distinguish 404-no-file from 5xx-transient.
         missing_is_expected_404: true
 
+    # Forward-looking chamber calendar. Unlike the daily file (a backward
+    # snapshot) this page lists the *upcoming* hearings/floor sessions -- the
+    # only genuine future-dated signal. Empty during recess (a legitimate "no
+    # upcoming events" state, DESIGN section 6.1), not an error. Parsed into
+    # the scheduled_events table (schema v2) by `ingest --store-events`.
+    assembly_events:
+        kind: "events"
+        url: "https://www.assembly.ca.gov/events/upcoming"
+        chamber: "assembly"
+        empty_is_ok: true
+
+    senate_events:
+        kind: "events"
+        url: "https://www.senate.ca.gov/calendar"
+        chamber: "senate"
+        empty_is_ok: true
+
 # --- LLM analysis (spec §4, task t_950780e0) -----------------------------
 # Subject-matter tagging of bills via a configurable Ollama endpoint. The
 # endpoint + model are NEVER hardcoded: everything below is a config knob.