Files
pulse/scripts/release_control
rcourtman 9c7cb9ed9b Require demand_evidence on candidate_lane registration
Every candidate_lanes record now carries demand_evidence: dated pointers
to the demand signals justifying the proposed lane (issues, discussions,
support threads, telemetry findings, or a demand-ledger entry in
pulse-pro/FEATURE_REQUESTS.md), or an explicit named-bet declaration for
maintainer-originated lanes with no external signal yet. The schema
requires the field, status_audit rejects missing or empty lists and
surfaces the evidence in the candidate_lanes and candidate_lane_queue
pretty blocks, and the canonical development protocol documents the
rule. No data migration needed; candidate_lanes is currently empty.
2026-08-24 15:59:32 +01:00
..
2026-03-18 16:06:30 +00:00
2026-03-19 10:06:39 +00:00