Resolve a BATCH of content references in ONE consent round (FILE_SHARING §7 /
UI_AS_APPS §8.7; "plan 12 §E"). When a
board opens with several embedded references, pass them all here: the host
coalesces them into a SINGLE consent prompt listing every target, instead of one
prompt per reference. Same relay gate and per-viewer semantics as
resolveContentRef (each ref's mount must already be held), applied to the
whole set — it is all-or-nothing: the user allows the batch or declines it.
Resolves { paths } with the STABLE absolute path of each ref, in input order.
Rejects with a SpaceError: forbidden (a referenced mount isn't held) or
cancelled (the viewer declined).
Resolve a BATCH of content references in ONE consent round (FILE_SHARING §7 / UI_AS_APPS §8.7; "plan 12 §E"). When a board opens with several embedded references, pass them all here: the host coalesces them into a SINGLE consent prompt listing every target, instead of one prompt per reference. Same relay gate and per-viewer semantics as resolveContentRef (each ref's mount must already be held), applied to the whole set — it is all-or-nothing: the user allows the batch or declines it.
Resolves
{ paths }with the STABLE absolute path of each ref, in input order. Rejects with a SpaceError:forbidden(a referenced mount isn't held) orcancelled(the viewer declined).const { paths } = await resolveContentRefs(board.references);