Paul's tracking-sheet fields, plus what the catalog model can add. Rollups aggregate a version's Channel Listings.
MR-043 (v2) · column model ported verbatim from MR-035 in 00-wireframe.html
A product with two live formulas shows two rows. Vapofil appears as v2 incoming and v1 active, both under FP-104. v2 groups those siblings under one identity band — the image and product name print once, and the sibling row carries a drawn elbow plus its own version pill — so the repeat reads as the model, not as duplicated data.
The durable model stays product-grained (one immutable CP-id, versions hanging off it, REQ-4). This is a list-view grain only.
# Listings, Channels and Stale-by-version are aggregates across that version's Channel Listings. Raw per-listing values — sold, views, listed-by (MR‑027) — live on Product detail → Channel listings, never here. Creating listings is a Runs-side job (MR‑031), so there is no inline "add listing" on this screen.
1 · Does Actions stay pinned? It currently scrolls with the sheet at the far right. Pinning it right costs another ~90px of horizontal budget; leaving it un-pinned means a 21-column view needs a full scroll to reach Edit. Row click → detail is the escape hatch either way.
2 · Is the group band right when sorted? Sibling versions only band together while sorted rows stay adjacent (sorting by ID, Name, Brand or FP SKU). Sorting by, say, Updated splits them and the band silently disappears. Options: keep it (band is opportunistic), or force product-grouping and sort within groups.