adventure: give a finished run a report worth sharing

The liveblog answers "what is happening" — it is capped, it scrolls, and six
hours after a run ends it is gone, because the adventurer page is about now.
Nothing answered the question asked afterwards, usually by somebody who wasn't
watching: what WAS that run. So a dispatch announcing a clear or a death was a
paragraph about an outcome with no way back to what produced it.

The report is that way back. The whole log uncapped, the numbers rolled up, and
the single worst hit the party took pulled out of the middle where it otherwise
reads as one line among forty. It is stable for a fortnight, which is what makes
it a thing worth linking from a dispatch and worth sending to somebody.

It is assembled from the same beats through the same renderer as the liveblog.
A report that told a different story from the log it was built out of would be
the more convincing of the two and the less true.

The summary is the exception and the only prose on the channel: gogobee's model
reads the finished run back and says what it was about, which is a judgement no
template makes. It rides a summary beat rather than its own endpoint, so it
inherits the whole channel — idempotent, retried, impossible to attach to a run
that doesn't exist — and it passes the same class of guard a dispatch lede does
before it reaches a public page.

Visibility is the adventurer page's rule exactly, and that matters more here
than anywhere: the report outlives the log by a fortnight and is linked from a
public dispatch, so it is the surface most likely to still be reachable after
somebody opts out. Coming off the board closes it, including through links
minted days earlier.

Claude-Session: https://claude.ai/code/session_012bxpQQJDjC1mTtLN3VVtBQ

internal/web/server.go

@@ -102,7 +102,7 @@ func New(cfg config.WebConfig, sources []config.SourceConfig, postingEnabled boo
 		shared []string
 		pages  []string
 	}{
-		{"layout", []string{"_card"}, []string{"index", "channel", "weather", "bookmarks", "for-you", "status", "story", "who", "siege"}},
+		{"layout", []string{"_card"}, []string{"index", "channel", "weather", "bookmarks", "for-you", "status", "story", "who", "siege", "run_report"}},
 		{"games_layout", []string{"_chipbar"}, []string{"games", "games_door", "blackjack", "hangman", "solitaire", "trivia", "uno", "holdem"}},
 	}
 	tpls := make(map[string]*template.Template)
@@ -231,10 +231,14 @@ func New(cfg config.WebConfig, sources []config.SourceConfig, postingEnabled boo
 	mux.HandleFunc("GET /adventure/who/{token}", s.handleAdventureWho)
 	mux.HandleFunc("GET /api/adventure/who/{token}", s.handleAdventureWhoAPI)
 
-	// The expedition liveblog. Bearer-authed ingest and nothing else: the beats
-	// have no page of their own, they render inside the adventurer page under
-	// the map and ride that page's existing poll.
+	// The expedition liveblog. Beats arrive bearer-authed and render two ways:
+	// live, inside the adventurer page under the map, on that page's own poll —
+	// and afterwards as the run's own report, which is the artefact a dispatch
+	// links to and a player shares. Three segments, so the report never overlaps
+	// /adventure/{guid}, and its middle segment is a literal, so it never
+	// overlaps /adventure/art/{type} either.
 	mux.HandleFunc("POST /api/ingest/run", s.handleRunIngest)
+	mux.HandleFunc("GET /adventure/run/{run_id}", s.handleRunReport)
 
 	// The Siege war room. Ingest is bearer-authed like the roster; the page and
 	// its poll are public — the same exposure the board already has.