New listing job — J-0112

Design: references/ebay-planning/LISTING-BUILDER-DESIGN.md (approved 2026-08-29). Dedicated screen, superseding the new-listing slice of MR-031; the other five presets stay on scr-newjob.

What the fixture demonstrates

• Count and type are derived, never asked — 4 slots → 4 listings; SINGLE/BUNDLE/COMBO computed from slot contents.
• Collision check as the error-killer — L2 carries the resolved history of an operator SKU edit colliding with a live listing (the spreadsheet's swapped-fan-out bug class).
• Gate invalidation — packages are locked while drafts hold approval r2; editing reopens r3 and voids downstream image approvals.
• Prefill, not lock — the Memopryl shared set pre-fills L1–L3; L2 shows a detached custom lifestyle slot (ink underline = this listing only).
• Two claim gates — content gate cleared in drafts; the image claim check catches L2's "boosts memory in weeks" overlay.
• Partial push is normal — 1 of 4 ready; dry run is the default mode for a new batch.
• ShipStation sync is its own stage (MR-053) — stage 7, between Images and Final review. Two jobs per listing, stated separately: the API build (read-back proof, never a bare 200) and the two website-only settings the robot sets. Failure recovery lives on the failed row, not in Attention; Attention only links back.
• Cost telemetry — every generation logged with cost in the activity rail (REQ §13.1).

MR‑077 — stage 3 is the package rule stack, and package-builder.html is gone

Stage 3 was a fixed grid of four slots with hard-coded SKUs and prices. It is now the rule stack that makes the slots — Product Pool → Shape → Gift Pool → Base Prices → Price Ladder, and the listings they produce. The stack was built as its own screen (MR‑064 explored three designs, MR‑075 picked this one, MR‑076 added job pack sizes); that file is deleted rather than kept, because two screens that can each define a job's packages is precisely how they drift.

What the fold changed, and nothing else did. The standalone page's own header, breadcrumb and listing chip go — the stage already has a stepper and a job header. Its count now lands on the stepper's sub-label, which used to read a hard-coded 4 slots, and on the step footer. The lock gate survives: it is the listing builder's own rule, not the packages screen's, and the stack never had it.

Two counts that disagree, on purpose. The job header says 4 listings and the footer says the rules make more. Both are true: the job holds four approved listings — drafts, images, ShipStation and final review are all built on them — while the stack describes what a re-run would produce. That gap is exactly what the lock gate is about, so the footer names both rather than letting the header look stale. Open: the downstream stages' fixtures are still a four-listing job; rebuilding them against a 26-listing one is a separate round.

The sidebar collapses here now too, to the 58px icon rail, taken verbatim from catalog-product-setup.html rather than re-derived — the label survives as a native title while collapsed, because a CSS tooltip is clipped by .sb's own overflow.

Pack sizes are the open variant, on the harness bar: Account set only against + job sizes. Both branches share every node; only Add pack size and the per-row remove appear or do not.

MR‑078 — stage 2 searches the catalog, and the picked cards come off the same list

The Add another product field was a dead input under a dead heading. It now filters the account’s catalog as you type — name, brand, SKU and UPC, the four things its placeholder already promised — and a row adds that product to the panel as a card. Arrow keys move, Enter adds, Escape clears; the query and the focus survive an add, because picking three products out of one search should be three clicks and not three searches.

Every row carries its thumbnail. A supplement is recognised by its bottle long before its SKU, and two of these products are collagen. Only two have a catalog photo, so the rest fall back to the same four-letter initials block the cards already use — the fallback is the common case here, not the exception.

One list, both halves. The two cards the job started with are no longer hand-written markup: they render from the same fixture the search reads, marked picked. That is what makes removal honest — a product taken off the job goes back to being searchable, and every card’s × works, not just the ones added this session. Two lists would have meant a product could be in neither.

Gift‑eligible is a tick on the card. Rung 3 of the package stack has always said the flag is set “in the Products step” — the step had no such control, so the sentence described a screen that did not exist. It does now: one checkbox per card, and a product the catalog calls a giveaway (the Riot gift bag) arrives ticked, disabled and tagged catalog, because unflagging it is the catalog's decision and not this job's. Everything else about the gift — whether variants are built at all, and what they cost — stays in rung 3, where the maths is.

What it does not do. The search is fixture-local: adding a product here does not carry into stage 3’s Product Pool, which holds its own four-product fixture. Nothing is scoped by channel account either — a real catalog search would be, and would page. Sell similar is still a dead button.

MR‑084 / 085 — a per-unit price on every row, a ladder that shows margin, and a workspace that fits it

The Listings table carries Per unit beside Price — the price over the Units column next to it. It is the number a buyer compares across pack sizes, and until now the only place to see it was the ladder’s example column, which prices one product.

Rung 5 loses its net multiplier and gains a gross margin. 2.85× was the discount restated in a second notation: it said nothing the −5% beside it did not. Gross margin — (per unit − cost) / per unit — is the question the tier is actually being set against. Price and Per unit are two columns rather than a price with a subscript — the per-bottle figure is what the tiers are compared on, so it reads down its own column instead of trailing the pack price. The header carries no tooltip: the picker directly above it already reads Memopryl — $39.99 a bottle, $7.40 cost, and a tooltip that restates its own control is one more thing to keep true.

The example product is picked, not assumed. It was pool[0], so the margin the ladder implied moved when somebody toggled an unrelated product in rung 1, with nothing on screen to say why. A dropdown beside Model names it, and the choice supplies both numbers: the one-bottle price saved in rung 4, and the cost from the catalog — the same figure the Listings table’s Cost column already spends. No new fields and nothing typed. A product switched off in the Product Pool hands the example back to the first one still in it, and picking one prices nothing: it redraws two columns and writes to no record.

Gross margin is not the 35% floor sitting inches above it. That one is net — it also takes off shipping, the 13% fee and the ad rate (D21). The hint under the table says which is which, and the column takes no colour for being low; only a negative reads red, because that is unambiguous under either measure. This is MR‑083’s rule, kept deliberately identical on the screen where the two numbers can be seen at once.

Promoted listings becomes rung 6, Promotions. It was a stray checkbox under the ladder’s table, which read as a property of the ladder; it is a job-level fee decision that moves every margin in the table beside it. Its own rung says so, carries the state in the header count (off · 13% fee only), and leaves somewhere for the rest of the promotion levers to land.

The Packages table is deleted. Tare, material and postage are inputs to a number the Listings table already shows — Ship — and the Package column already names which box each row lands in. What only that card said now lives in the listings tooltip: package is picked by weight, Ship is postage + material at the static v1 USPS rate (MR‑047), and an over capacity row is priced at a box that cannot hold it, so its cost is understated. The data is unchanged — PKGS still drives every row’s package and postage; only the read-only display of it is gone.

The listings card is as tall as the rule stack, and only then scrolls. It was a fixed 640px window regardless of how much was in it. Now it grows with its rows up to the height of rungs 1–6 and scrolls past that, with the totals bar pinned under it. The cap has to come from the other column, which is why the two columns are a grid: the listings column is kept out of the row’s sizing (height:0) so the row is as tall as the rules, then fills it (min-height:100%). A short job still draws a short card — nothing is stretched to fill.

Every listings column sorts, and the two columns scroll independently (MR‑086). Each header is a real <button>, so the keyboard gets sorting for free; a second click reverses, build order breaks every tie, and # keeps the number the row was built with rather than renumbering — a listing is the same listing after a sort. Sorting reorders what is shown and touches no price, no rule and no record.

Stage 3 is a two-pane workspace, not a long page (MR‑087). The stage is exactly as tall as what is left of the viewport; each column scrolls itself, and the listings table scrolls inside its card under headers that never move. Rung 6 and row 52 are both reachable, and neither costs you the other.

Sticky was tried first and it failed in the one place that matters. MR‑086 pinned the listings card under the sticky header, which worked until the page scrolled past the rule stack’s own height: a sticky box can never leave its containing block, so the card was pushed up from below and took the column headers with it. Runway you cannot extend is not a fix, and the right answer was to stop scrolling the page at all here.

Two numbers are measured in script rather than hard-coded — the header’s height, because it wraps at narrow widths and a fixed offset would be wrong exactly when it matters, and the scroller’s free height, because 100vh overshoots by the harness bar and by the 60px of bottom padding the long stages need. Under 560px of workspace the stage gives up and scrolls the page instead: two slivers are worse than one page.

Open questions

Refinement round (MR-046)

• Live push gate — Live is styled destructive, the button label is mode-aware, and a confirm dialog restates account + manifest before any live write. Dry run stays one-click.
• Watch panel — after a live push the push card opens a read-only window into run B-0114 (APPLYING → RECONCILING → live + spot-checks); the cockpit still owns the run.
• View toggles — Drafts adds Compare (fields × listings); Images adds By listing (readiness-first). Same segmented-control idiom.
• eBay preview — per-listing buyer's-eye preview on Final review; deliberately approximate, marketplace chrome omitted.

Deliberately out of scope this round

• Per-slot benefits-angle overrides (Paul picked job-level only).
• Recipe picker UI — exactly one recipe exists ("standard supplement listing"); the chooser lands when a second recipe does.
• Post-push reconciliation surfaces — the watch panel is a read-only window; run cockpit / setup screens own the machinery.

This writes to eBay · Response Commerce (US) — a real seller account. Dry run costs nothing; live listings are public the moment they apply.

Going now — 1 listing

Not going — blocked