adventure: keep the facts, not just the sentence we made of them

gogobee already sends boss/opponent/zone/outcome/level on every dispatch.
renderAdventure melted them into prose and only the prose was persisted, so
"how many bosses has she downed" was answerable only by parsing English back
out of a headline.

adventure_events keeps the fact as fact. It's the one adventure table that's a
log rather than a snapshot: the roster answers where Josie is now and is
replaced every tick; this answers what she has ever done, which no snapshot
can. INSERT OR IGNORE on the guid because gogobee retries a fact whose ack it
lost, and this is the only adventure store where a duplicate is permanently
wrong — the roster forgives one by replacing itself, a double-counted kill is
in the tally forever.

On top of it the who page grows two public sections, counted from dispatches
that were already public: the record (tallies, per-boss and per-zone, realm
firsts, milestones) and the trail (the last 40 facts, each linking to the
dispatch that told it). One read feeds both — the pool is MaxOpenConns(1), so
six COUNT queries would serialize for an answer that fits in memory.

Only the trail is capped. A limit on the read would truncate a *tally* rather
than a list, and a veteran's kill count frozen at 40 reads as a fact instead of
a missing page. Only the subject of a fact earns a trophy: a duel you lost
still names you, and it belongs on your trail but not in your record.

Trophies count forward only. Every adventurer's past is prose in the feed and
can't be counted back out, so they show no record until they next do something
— a clean absence rather than a wall of zeroes.

No treasures: there's no loot fact on the wire, and inventory is current-state
with no history, so counting the vault would score a bought sword as a trophy.
Needs a fact type upstream.

internal/web/adventure.go

@@ -132,6 +132,30 @@ func (s *Server) handleAdventureIngest(w http.ResponseWriter, r *http.Request) {
 		http.Error(w, "insert failed", http.StatusInternalServerError)
 		return
 	}
+	// Keep the fact itself, not just the sentence we made out of it. The story row
+	// above is what people read; this is what the trophy case and timeline can
+	// count. Best-effort on purpose: a dispatch that published is published, and
+	// losing its structured twin costs a tally, not the news. Failing the request
+	// here would make gogobee retry a fact we already have a story for.
+	if err := storage.InsertAdventureEvent(&storage.AdvEvent{
+		GUID:       f.GUID,
+		EventType:  f.EventType,
+		Tier:       f.Tier,
+		Subject:    f.Subject,
+		Opponent:   f.Opponent,
+		Boss:       f.Boss,
+		Zone:       f.Zone,
+		Region:     f.Region,
+		Level:      f.Level,
+		Tally:      f.Count,
+		Outcome:    f.Outcome,
+		Milestone:  f.Milestone,
+		Actors:     f.Actors,
+		OccurredAt: occurredAt,
+	}); err != nil {
+		slog.Error("adventure ingest: event record failed", "guid", f.GUID, "err", err)
+	}
+
 	slog.Info("adventure ingest: published", "guid", f.GUID, "event_type", f.EventType, "tier", f.Tier)
 
 	// NoPush (cold-start backfill) means "never goes to Matrix". Suppressing only