v4.4.0

Changed

• beagle-analysis (planning guardrails): Added four fail-the-plan/spec guardrails to the planning workflow, derived from a post-mortem of two bugs in a single shipped feature (Osprey issue-124 retention) built through the beagle planning workflow. All four are hard gates, not advisory notes, and propagate into the downstream review paths (#140):
  • G1 Consumer/YAGNI gate — every new public API surface a plan introduces must name a production consumer in the same plan (a test is not a consumer); brainstorm-beagle gets the parallel spec-level check.
  • G2 Discriminating-assertion gate — a construct-a-false-pass-impl check in write-plan, plus a payload-preservation carve-out so YAGNI-for-tests no longer collapses structurally-distinct producers and the corrupted region.
  • G3 Composition check — brainstorm-beagle Prior Art Check step 5 escalates upstream/downstream data-transforming mechanisms to a Key Decision + spike, emitting a structured needs-spike-before-planning marker.
  • G4 Input-shape spike trigger — write-plan Task 0 gains the upstream-data-shape assumption trigger.
  • Propagated into the shared review checklists: spec-reviewer.md (imported by brainstorm-beagle self-review and resolve-beagle) gains Consumer (§8) and Composition (§9) review dimensions, and resolve-beagle gains both gap types in its latent-gap extraction table and self-review checklist.

Chore

• Repo tooling: Gitignore review tooling artifacts so local review scratch files stay out of the working tree. Repo infrastructure only; no installable plugin changes (#141)