v0.4.18

Design-lane BDD coverage for backend write rules + Pass-2 shift-left canon, and readable dashboard test tiles.

• BDD-coverage gate (serviceRuleTaggedE2eReason, in the live spec-gate guard): a mutating api_contract (POST/PUT/PATCH/DELETE) referenced only by E2E ACs — with no API-layer AC — hard-blocks the spec gate, because the behavior analyst then has no backend slice and the write rule ships with 0 BDD tests. Structured (api_contract_id → method + AC layer), conservative/fail-open.
• Architect canon: a backend write rule needs its own API AC (not only E2E); never author an AC that presupposes an unresolved open_decisions[] entry (data-model open decisions resolved at architecture time).
• Spec-author canon: pin a cross-cutting data fact once as a feature-level ## Data semantics; producing-AC coverage — a state a reader story consumes needs a producing AC in the write story (incl. a nullable field's null case).
• Dashboard: readable test tiles — abbreviated type pills (BDD / FIT / E2E / COMP), client=E2E (no bare CLIENT), wider tiles, wrapping top row, and a robust full-record hover card.

Live-proven on F1 (stockflow-example, --only design): the write rule went from 0 → 14 behavior tests and design-lane re-routes from 3 → 0, all reflects + reconcile passing. Consort-only (pins scm-utils unchanged).