Development record
Release derivation diagnoses a null impact as malformed while record-lint calls it missing
issueresolvedminoriss-286
Release derivation diagnoses a null impact as malformed while record-lint calls it missing
newRecord (internal/core/changelog/shipped.go:277) calls ParseImpact
with no IsNull gate, so for a resolved issue carrying impact: NULL
record-lint reports "impact must be set explicitly" (missing) while the
release cut records "invalid impact" (malformed) — two diagnoses for one
line. Verdicts never diverge (both paths reject), so this is operator-facing
message inconsistency only; an IsNull gate at the call site restores
parity. Evidence: .abcd/work/reviews/2026-08-19-pr-294-null-predicate/
(F8).
Forge mirror: #373
Frontmatter
| id | iss-286 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-286-release-derivation-diagnoses-a-null.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608270908332975parseSpec reads id/intent with no null gate, so id: NULL yields a malformed-shape diagnosis while lint's schema gate reports the field unset — the spec-family sibling of the iss-286 divergence