v0.13.0
ask --where: evidence-backed pointing
Evidence observations bind subjects to repo: locators; --where inverts that mapping into an answer surface (#137, #139, ADR 0068):
yarramate ask .yarramate/workspace.yaml --where "compiler"- Same free-text/subject-id seeding as every slice — no new grammar.
- The answer is each matched subject's verified code locations, with subject- and claim-level observations deduplicated and contradicted locations included and marked — a place known to disagree with intent is review signal, not noise.
- Every answer states its own coverage boundary: unobserved subjects listed by name, everything outside the model explicitly handed to the agent's own search tools. Verified pointers outrank derived pointers; the routing lives in the output, not in the reader's head.
- The engine stays out of the indexing business: no scanning, no inferred links, no ranking.
The cross-harness case study ships with the package
The model is the handover — one architecture, two AI harnesses, zero handoff, every claim with a commit, PR, or release attached — now lives in docs/, with a "Proven across harnesses" section in the README (which ships in this tarball, so the npm page leads with it).
CI
- codeql-action bumped 4 → 4.37.3 (#119).
Full changelog: v0.12.0...v0.13.0