more testing

README.md

@@ -301,9 +301,10 @@ RELEASE="$RELEASE" OTEL_URL="https://otel.example.com" \
 ```
 
 The receiver stores uploaded maps under `OTEL_SOURCEMAP_DIR` (default
-`./sourcemaps`, `/sourcemaps` in the Kubernetes deployment). Upload maps for
-each release before investigating its errors. The API never returns map
-contents or original source files.
+`./sourcemaps`, `/sourcemaps` in the Kubernetes deployment). Maps are reloaded on start, so keep the directory on persistent storage. See
+`instrumentation.md` (*Source maps → Requirements checklist*) for everything a
+project needs for stacks to resolve. `GET /api/sourcemaps` lists loaded maps.
+The API never returns map files themselves.
 
 `build.sh` passes the release into the Docker UI build. If `OTEL_URL` is set,
 it also builds the matching UI locally and uploads all generated JavaScript
@@ -362,6 +363,18 @@ already points at it. The UI's Trends tab (and live issue updates) appear
 automatically once the stats endpoints answer; on file-store deployments the
 tab hides itself. SPA routes (/issues, /traces, /logs, /metrics, /trends,
 /setup) are served client-side by wouter and survive the OIDC login redirect.
+Selection lives in the URL too, so every step can be reloaded, stepped with
+back/forward, and shared (each detail view has a link chip that copies its
+permalink):
+
+| Path | Shows |
+| --- | --- |
+| `/issues/<issueId>` | one issue with its traces |
+| `/issues/<issueId>/trace/<traceId>` | the same, with a trace selected |
+| `/patterns/<patternId>[/<issueId>]` | a pattern card open, optionally reviewing one member |
+| `/traces/<traceId>[/<spanId>]` | a trace, optionally with a span selected |
+| `/rum/session/<sessionId>` | a RUM session |
+| `/rum/errors[/<errorId>]` | JS errors, optionally one error expanded (`errorId` is a hash of type + message) |
 
 Currently, the history buffer size is hardcoded to 100 entries. This can be made configurable in future versions.