commitlore-querylisted

# CommitLore query Four commands read the same underlying record set for one or more paths; `stale` reads it repo-wide. All of them read-only — none of them touch git state. ## Reading records for a path ``` commitlore context src/core/types.ts ``` ``` context for src/core/types.ts as of 2026-07-26T07:28:42.051Z — 2 limits, 5 ruled-out, 3 warnings, 16 other in 2 records (index, 2 commit record(s) scanned) limits r-c0f4e2 3d249cd3 npm gitlore is held by an active same-domain CLI, so the owner's first-choice name was not available r-b2e7f1 00d348d1 Parsing must delegate to git interpret-trailers -- reimplementing the block rules would drift from the rest of the git ecosystem ruled-out r-c0f4e2 3d249cd3 GitLore published as git-lore | the binary and search results still collide with the existing gitlore tool r-b2e7f1 00d348d1 line-matching Key: prefixes | prose containing a colon line parses as a record and feeds agents false context (verified B3) ... warnings r-c0f4e2 3d249cd3 [directive] ADR-0008 and ADR-0009 keep the literal string Annals on purpose -- mechanical substitution there destroys the decision trail ... other r-c0f4e2 3d249cd3 Blast: system ... ``` `context` is every active record touching the path, grouped by section, each line prefixed with its `Record-Id` and short commit sha. `limits`, `ruled-out`, and `warnings` return the same underlying records filtered to one key each — reach for those when only one kind of information