[iss-286] Release derivation diagnoses a null impact as malformed while record-lint calls it missing

[REPPL]

newRecord in the release derivation calls ParseImpact with no null gate, so impact: NULL is reported as 'invalid impact' (malformed) by the release cut but 'impact must be set explicitly' (missing) by record-lint — two diagnoses for one line. Verdicts agree (both reject); operator-facing message inconsistency only.

Canonical record: .abcd/work/issues/open/iss-286-release-derivation-diagnoses-a-null-impact-as-malformed-whil.md (severity: minor). Evidence: .abcd/work/reviews/2026-08-19-pr-294-null-predicate/.

---

This is a mirror of the canonical ledger record above; status truth lives in the repository ledger, and this issue is closed by a maintainer when the record resolves. Comments here are triaged into the ledger, not acted on directly.

[REPPL]

Closing directly on the forge, deliberately without importing into the ledger — this is the pilot's self-healing test: the next mirror pass must notice the canonical record is still open and reopen this.

[REPPL]

Mirror pass: the canonical record (iss-286-release-derivation-diagnoses-a-null-impact-as-malformed-whil.md) is still open in the ledger and no import recorded this closure, so this mirror is reopened. To close it, resolve the record in the ledger (or import the closure explicitly).