You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jerry Holland edited this page Sep 29, 2026
·
3 revisions
Notes catalogs through the object session
With --git-session, notes discovery and note-blob reads share the invocation's
object process. Windows enables the session by default; --no-git-session keeps
the ordinary Git path available for comparison.
The traversal handles SHA-1/SHA-256 attachments, mixed flat and fanout layouts,
and Git's target ordering. Each listing resolves the mutable notes ref again.
Duplicate attachments, malformed or unavailable objects, and traversals exceeding
1,024 trees or 16 MiB delegate the complete listing to git notes list; no partial
catalog is returned. These are optimization budgets, not repository input limits.
Compare observable results with cst resolve list --json --git-session and
cst resolve list --json --no-git-session. Use --trace-git to inspect process
cost without printing note payloads. The retained benchmark remains the source
of automated regression limits; a process reduction alone does not qualify a
production latency budget.