pub fn render_note_scoped(
ex: &Explanation,
source_base: Option<&str>,
body: Option<&str>,
scope: &VaultScope<'_>,
) -> VaultNoteExpand description
render_note, for one member of a workspace vault: identical except
that the note’s own name and every link it emits are resolved through scope
(see VaultScope).
With VaultScope::PROJECT this is render_note byte for byte, which is
how the single-project vault’s compatibility promise is kept by construction
rather than by a parallel code path that has to be kept in step.