Skip to content

v0.9.0 — review slices derive from git

Choose a tag to compare

@nabsha nabsha released this 01 Aug 10:25
c50a4fb

The review surface the second cross-harness dogfood asked for (ADR 0065) — with the slice derived from git rather than authored as tags.

  • ask <workspace> --changed <git-range>: the subjects whose declarations changed in the range, rendered as their connected-neighbourhood brief (or --budget digest / --json), plus an inline coverage note naming changed subjects that appear in no authored projection.
  • export markdown --changed <range> and export briefs --changed <range> --out <dir>: the same slice as a persisted review document or per-concept handoff bundle.
  • No new authored surface: records stay closed, a ref range is disposable by construction, and git diff remains authoritative for what changed. Authored review tags are deliberately deferred (#126) until a real cross-cutting need appears.

Typical review motion after an enrichment burst:

yarramate ask .yarramate/workspace.yaml --changed main..HEAD
yarramate export markdown --changed main..HEAD .yarramate/workspace.yaml --out review.md