V5 — Pipeline board: the queue's shape at a glance

• Columns are the workflow. You see load and bottlenecks instantly — e.g. three cards stuck in "Awaiting buyer approval" is a visible pile-up, not a filter you have to think to apply.
• The nesting is structural: buyer approval is a lane inside the Replacement column. There is no way to read it as an independent status.
• Cards carry the next-step button, so the flow is drive-by: Claim in column 1, Fulfill in column 2, stage buttons inside Replacement.
• Tradeoff: biggest departure from today's table — fewer visible fields per order and weaker for dense scanning/sorting. Archived orders aren't shown on the board.