Head: d487d6cb5e
Base: 0604547a3a
Fixture: identical restored 32767 nondeleted, nonarchived threads from before verification.
Command: vp run dev --no-seed
Source: lead-captured runtime-after.log; selected verbatim startup/recovery/HTTP 200 lines only.
Pairing URLs, credentials, and unrelated log records are omitted.

[22:44:11.472] INFO (#6497): Listening on http://127.0.0.1:15072
[22:44:14.339] INFO (#6494): V2 orchestration recovery completed
[22:45:41.763] INFO (#6496): Listening on http://127.0.0.1:15072
[22:45:45.572] INFO (#6493): V2 orchestration recovery completed
[22:46:12.875] INFO (#106063) http.span=10444ms: Sent HTTP response
  http.method: GET
  http.url: /api/orchestration/shell
  http.status: 200
[22:47:10.471] INFO (#204980) http.span=7389ms: Sent HTTP response
  http.method: GET
  http.url: /api/orchestration/shell
  http.status: 200

Authenticated same-origin browser fetch (http-probe.json):
GET /api/orchestration/shell with x-t3-orchestration-protocol: 2
status: 200
threadCount: 32767
response text length: 50363446
state: done

Scope: startup recovery and the shared server HTTP shell response succeeded at the failing fixture size. Browser rendering at this scale was not asserted. The initial preview evaluation timed out at 15 seconds; the asynchronous probe subsequently completed and its result was retrieved. These observations do not establish client rendering performance or a latency guarantee.