Problem
ReleaseSpecWarning only checks whether specs/release-process-spec.md was
touched alongside release-config changes — it cannot tell whether the spec
content actually reflects the change. The component carries the marker:
// TODO: evaluate whether the diff's changes are actually reflected in the spec document, not just whether the spec file was touched.
Proposal
A semi-deterministic gate in the review pipeline: when release config
changes, sample an LLM (the review already has provider wiring) with the
config diff and the spec, asking whether the spec still describes the
behavior; surface a finding when it does not. Deterministic trigger, model
judgment, advisory output — the middle layer between AGENTS.md rule 8 and
the file-level warning.
Problem
ReleaseSpecWarningonly checks whetherspecs/release-process-spec.mdwastouched alongside release-config changes — it cannot tell whether the spec
content actually reflects the change. The component carries the marker:
// TODO: evaluate whether the diff's changes are actually reflected in the spec document, not just whether the spec file was touched.Proposal
A semi-deterministic gate in the review pipeline: when release config
changes, sample an LLM (the review already has provider wiring) with the
config diff and the spec, asking whether the spec still describes the
behavior; surface a finding when it does not. Deterministic trigger, model
judgment, advisory output — the middle layer between AGENTS.md rule 8 and
the file-level warning.