---
name: a-commit-that-says-cells-will-red-names-the-cells-to-run
description: golden red #272 r1 2026-09-08 — W2's commit message predicted "cells that assert a raw spool will red, each repinned"; nobody ran them post-W2, my targeted W2/W3 legs skipped the spt e2e crate; three pre-existing cells with a stale denominator, not never-executed ones
metadata:
  type: feedback
---

#272's first golden (run 34239258523, 2026-09-08) went red on three PRE-EXISTING `spt` e2e cells that had last passed at W1. W2's commit message (92715374) said outright that every send now pre-composes a typed envelope and "cells that assert a plain send spools a RAW body will red, and each one gets named and repinned" — and then zero commits touched those test files, because my W2 and W3 gate batteries ran targeted legs that never included `cargo nextest run -p spt` in full, and the thin-CI unit job runs libs only. The never-executed list (172 added cells) was correct and none of the reds was on it: the population I failed to run was the CONSUMERS of the changed seam, not the cells the change added. A second, sharper defect rode the same gap: the new splice re-emitted `type` (doubled attr), and W2's own unit cell could not see it because `ParsedEvent::attr` returns the first match — a cell that reads the first of something never counts it.

**Why:** a targeted leg is a claim that the untargeted cells cannot see the change. A commit that predicts reds has REFUTED that claim in writing for the crates it names; the never-executed list covers what was added, and only a run of the seam's consumers covers what was changed under them.

**How to apply:** at every wave gate, grep the lane's commit messages for "will red" / "repin" / "consequence" and run every crate named or implied IN FULL on both OSes before the gate verdict; when a change alters what a shared composer/renderer emits, run the e2e crate of every CLI edge that reads it. When a regression cell is written for an emitted string, assert a COUNT (occurrences of the attr) not a first-match lookup. Related: [[a-column-that-reads-one-value-on-every-row-is-a-broken-extractor]], [[open-the-subindex-before-running-a-gate]].