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/templates/who.html

@@ -186,6 +186,13 @@
       </li>
       {{end}}
     </ol>
+    <!-- Only once the run is over: while it's still walking, this column IS the
+         report, and a link to a second copy of it is just a way to lose the
+         reader. Revealed in place when a run ends under an open tab. -->
+    <a id="who-runlog-report" href="{{.RunLog.ReportURL}}"
+       class="mt-4 inline-flex items-center gap-1.5 text-sm font-semibold text-theme-adventure hover:opacity-80 transition{{if not .RunLog.ReportURL}} hidden{{end}}">
+      <span aria-hidden="true">📜</span> The full report <span aria-hidden="true">→</span>
+    </a>
   </section>
 
   {{if .HasHistory}}
@@ -483,6 +490,19 @@
     });
     list.replaceChildren(frag);
     if (pinned) list.scrollTop = list.scrollHeight;
+
+    // The run can end between two polls, which is exactly the moment the report
+    // becomes worth offering. href is set from the payload rather than built here
+    // so the page never invents a URL for a run Pete won't serve.
+    var report = document.getElementById('who-runlog-report');
+    if (report) {
+      if (log.ReportURL) {
+        report.href = log.ReportURL;
+        report.classList.remove('hidden');
+      } else {
+        report.classList.add('hidden');
+      }
+    }
   }
   (function () {
     var list = document.getElementById('who-runlog');