U17 — Per-template attribute extra-price override + multi-select reworkPROD

Summary

Status

11/11 prod · 51/51 regression = 62/62 · shipped

Commit

nix-cafe acedcb7 · nix-outdoor-sales-backend be268ed

Files

6 modified + 2 new · 1 migration · ~640 LOC net

Migration

cafe.product_template_attribute_line_value_rel.price_extra_usd_override NUMERIC(12,2) NULL

Two-layer data model

Effective extra price in every read path: COALESCE(rel.price_extra_usd_override, av.price_extra_usd). Null override = use global default.

What ships

• Multi-select dropdown replaces the all-values chip-toggle row on /cafe/products/[id]. Native <details>/<summary> open/close + scrollable checkbox list. Summary header reads "N of M selected".
• Read-only summary chip row below the picker shows ONLY the selected values (not all available) with their effective per-template extra price + a small white dot marker when the price is an override (vs the global default).
• Configure button per attribute line → links to /cafe/products/[id]/attributes/[lineId]. Disabled with a "Configure (save first)" placeholder for unsaved new lines.
• New per-product Configure page (server component + client) with Odoo-shape Value | Exclude For | Extra Price | [Save] table. Extra Price column is inline-editable; placeholder shows the global default like 1.99 (default); blank input clears the override. Per-row Save calls setLineValueExtraPriceOverrideAction (gated on nix_cafe.settings.edit; validates non-negative ≤999 with 2dp). On success: local state patches; "Override saved · global default $X.XX" hint appears.
• Read paths COALESCE: lib/pos/attribute-pairs.ts resolves override ?? global per row → POS variant picker now shows the per-template effective price.
• Import respects per-template isolation: lib/db/product_import.ts writes the per-row diff to rel.priceExtraUsdOverride instead of mutating av.price_extra_usd globally. Two templates sharing the same attribute keep their own per-template extras.
• Survivor preservation: setTemplateAttributeLines reads existing overrides keyed by ${attributeId}:${valueId} BEFORE the wipe-and-reinsert, then re-applies them when surviving (attr, value) pairs land in the new rel rows. Without this, every "Save attributes" click would clear all per-template overrides.
• AttributeValuePopover DELETED from the per-product surface (~130 LOC). Global value edits now happen exclusively on /cafe/settings/attributes (U15-C admin); per-template overrides happen on the new Configure page. One obvious way to do each thing.

11/11 prod checks ✓

Screenshots (click to enlarge)

Mid-Gate finds

• cafe.product_template has no list_price_usd column. First prod test attempt INSERT failed with "column list_price_usd does not exist." Schema mirror in schema.ts doesn't have it either; the local probe inserted a key Drizzle silently dropped (the .mjs runtime path doesn't enforce values() type strictness). Base price actually lives on product_product.price_usd (variant-level). Trivial fix.
• mkdir-before-redirect burned a 5th time on the fresh prod-u17 dir. Existing durable rule covers it.
• Wrangler token expired (Cloudflare API 9109) so couldn't confirm deploy via wrangler deployments list; just ran the prod test directly — the testid assertions would have failed if the deploy wasn't live, but they passed first attempt on the warm Worker.
• No Hyperdrive cache trap this time — the DAOs that actually face stale-read risk (getTemplateWithLinesById, getLineWithEditableValues) are already db.transaction-wrapped. The Configure page round-trip read-after-write also benefits from dynamic = "force-dynamic" + revalidate = 0.

Architectural notes

• Separate column, not column reuse: U17 added a NEW column rather than repurposing price_extra_usd on the value row. Two reasons: (a) "null = use default" semantics is explicit; (b) Configuration › Attributes admin keeps editing the global default without surprise behavior across all products using the same value.
• Survivor preservation is load-bearing: without it, every "Save attributes" click on the parent product page would silently wipe all per-template overrides on that template. Validated by a dedicated Gate 1 DAO probe.
• Configure button disabled for unsaved lines is deliberate — the lineId only exists after the first Save Attributes click. The placeholder "Configure (save first)" tells admins the path without a broken link.
• Exclude For column rendered as — in the Configure page. Odoo's per-combo exclusion model (e.g. "ICE excluded when paired with FRAPPE") is in scope for a v2 follow-up.
• Cosmetic-vs-functional split: U17 deletes the per-value pencil dialog from the product page; that pencil was the load-bearing mutation point that violated Narong's mental model. Global value name + global default-price edits stay on /cafe/settings/attributes (U15-C admin) where they belong.

Regression sweep — 51/51 ✓