pub fn paths(store: &Store) -> Result<Vec<String>>Expand description
The cataloged asset paths, sorted ascending. The VCS-neutral list a harness
feeds into a .gitignore managed block or a sync-service exclude. db.md
itself never writes any ignore file.
Every emitted path is routed through the same containment guard scan,
verify, and status use — the module contract is that the guard applies
“wherever a path is read or resolved” (SPEC § Assets > Path safety). A
poisoned / hand-edited manifest path that escapes the store (absolute, or a
.. traversal — the merge=union-corruption state SPEC anticipates) is
OMITTED, so this list — which a harness pipes straight into a .gitignore
managed block or a sync-exclude — can never carry an out-of-store path. The
list analog of how verify counts an escaping record corrupt and status
counts it missing: a path that can’t be a real store member is left out.