LOCAL COMMIT ONLY -- consortium-owned remote, never pushed from here. Two measurements that change the shape of the request, both taken against the running 5.10.8: 1. The mirrored (file-based) path already carries the DataCite fields. `owi-up/collectionName=main` yields 43 metadata keys per dataset, more than the live LEXIS path's 42, provenance included. So no sidecar migration is required -- the fields are in the sidecars written at pull time, and only the HTTP projection loses them. I had assumed the opposite. 2. Sidecar format is not uniform, so the fix must not assume a fixed shape. Across 585 mirrored `main` datasets on this one deployment: six distinct key sets, 33 to 43 keys, differing by `provenance`, `workflow_ex_id`/`workflow_id`, `fundingReferences` and `relatedIdentifiers`. One outlier at 33 keys is missing nearly all provenance. Per-field presence: creators 585/585, descriptions/publisher/publicationYear/rightsList 584/585, relatedIdentifiers only 381/585. `schema` is http://datacite.org/schema/kernel-4 on 584 and absent on one. Recorded as constraints: every field optional, no keying on a fixed key set or count, `schema` as the version marker where present with absence tolerated, and one malformed sidecar must not fail the listing. Migration of the sidecars is acceptable to us if owilix would rather normalise -- `remote reindex` is the natural place -- but must not be a precondition for reading the fields, since other installations have mirrors nobody will migrate. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019nPNpEG2QRnmjxxn5LeEb7