Every remote object keeps its raw form and how it reached us, for the client's details view

- ObjectRecord, one per stored remote object: the raw JSON (up to 256 KB, always hashed), delivered or fetched,
  refetched from origin or not, the activity that brought it (or caused the fetch), shared or personal inbox, the
  signature's key, algorithm and signed headers, received time, published and updated, the delivering activity's
  @context, and up to ten later revisions from Update.
- Delivery details travel from InboxReceiver through the inbox job to the handlers as Arrival.Current.
- A host is described from its NodeInfo when we first hear from it, at most weekly (DescribeInstance job), never when
  someone opens the details view.
- GET /api/privapub/v1/statuses/:id/provenance and /api/privapub/v1/instances/:host, with the extensions an object
  used detected from its raw form (044f quotes, interaction policies, contexts, proofs, Misskey fields, MFM, FEP-8967
  links, emoji, polls, language maps, url variants, Markdown content).

Checked live: a GoToSocial reply shows as delivered to the shared inbox, signed hs2019 with GoToSocial's fragment-less
key id, with its interaction policy detected, and gts.test is described as gotosocial 0.22.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB

docs/ROADMAP.md

@@ -426,9 +426,9 @@ it, raw where it doesn't.
   - A null `id`, a 200 `Tombstone`, a `Delete` before its `Create` (W9, W13).
 - **`Post.Kind`** plus typed payloads for article, video, audio, event, link, review and thread (INTEROP §4.1). The
   Mastodon API view of each kind: content, a card made from the object without fetching, attachments.
-- **Raw capture for the details view:** the object as received, how it arrived, the signature scheme and key, received
-  versus `published`, the extensions detected, and the origin's software (§4.3). Exposed at
-  `/api/privapub/v1/statuses/:id/provenance` and `/api/privapub/v1/instances/:host`.
+- **Raw capture for the details view** (done in v1.8.0): the object as received, how it arrived, the signature scheme and
+  key, received versus `published`, the extensions detected, and the origin's software (§4.3). Exposed at
+  `/api/privapub/v1/statuses/:id/provenance` and `/api/privapub/v1/instances/:host`. Checked live against GoToSocial.
 - **Routing by object type:**
   - `Accept`/`Reject`/`TentativeAccept` routed by what their object is (W6).
   - `ChatMessage` in as a direct message.