The complete open source platform to run your entire marketplace. Storefront, vendor panel, admin console, and integrations in one enterprise-grade platform you own.
Claude Progress -- Mercur.js
This is the session log and current-state tracker. Keep it short: prune old
session detail aggressively. The per-spec source of truth lives in
docs/specs/SPEC-*.md (status + Evidence) — this file is just the running log.
Current Verified State
- Repository root:
/Users/viktorholik/Desktop/mercur - Current branch:
feat/extendable-offer-tables-forms - Current version:
2.2.0-rc.1 - Standard startup path:
bun install && bun run dev - Standard verification path:
bun run build,bun run lint(oxlint),bun run test:integration:http -- <pattern> - Current blocker: none
Session — Store offers on the Medusa index engine (2026-11-03), branch feat/index-engine-store-offers
GET /store/offers goes through api/utils/list-offers.ts listOffers(): query.index with seller visibility
(seller.status = open, scheduled-closure dates) and product.status = published as index filters, query.graph
with the previous id-list prefetch when a filter isn't indexed (q) or the index is off. The index can only join
across modules through link tables, so offer_seller and offer_product are now writable links (isList on the
offer side) that createOffersWorkflow writes next to offer.seller_id / product_id; migration script
backfill-offer-links.ts seeds rows for existing offers after db:migrate syncs the tables. withMercur passes
utils/index-schema.ts (Medusa's product schema + Offer + Seller) as the index module's schema option. Shared
index helpers moved to api/utils/index-engine.ts. The detail route checks seller/product visibility from the
database (the index is async). Tests: store store-offers.spec 16/16 with helpers/wait-for-indexed-offers.ts;
http/offer vendor + store specs pass; order.spec / multi-seller-shipping-methods.spec 500 locally with the
nested-worktree awilix leak, not this change (CI is the source of truth).
Pre-existing, unchanged: the seller visibility rule hides a seller whenever closed_to is in the future, even
before closed_from, in both resolveVisibleSellerIds and store/sellers/middlewares.ts.
Session — Product lists on the Medusa index engine (2026-11-03), branch feat/index-engine-product-lists
GET /admin|/vendor|/store/products now go through api/utils/list-products.ts listProducts(). It uses
query.index when every filter key and the sort fall in the indexed whitelist, otherwise query.graph (categories,
tags, variant options, withDeleted, admin seller_id). count = estimate_count, exact when the page isn't full;
estimate_count is also returned. withMercur enables index_engine and injects @medusajs/index (direct dep
of apps/api, integration-tests, templates/basic api). product_seller link is filterable. Vendor list no longer
scans every seller's product_seller rows: visibility is own PRODUCT_ADD ids (draft/proposed), plus published with
no product_seller row, plus published id IN this seller's own rows. It's passed per engine through
ProductVisibility. The detail guard is one product query + the scoped authorship lookup. has_offer filters by
offer.product_id. New index IDX_product_change_created_by. Tests: vendor product.spec 17/17 (new graph-fallback
and count cases), admin product + product-publish-and-sku 26 pass (4 pre-existing skips), store product/ 18/18,
with deterministic index waits (helpers/wait-for-indexed-products.ts). Core tsc green; full bun run build not run.
Open risk: sellers created after boot never land in the index (seller.seller.created doesn't reach it), so
sellers.id filters are unusable. Production needs the Redis event bus for incremental index sync.
Follow-up (same day, same PR #1740): Medusa Caching Module. withMercur sets the caching flag and registers
@medusajs/medusa/caching, using the Redis provider when projectConfig.redisUrl is set (dep in apps/api +
template) and in-memory otherwise (tests). listProducts takes cache: { ttl, tags }, always tags
Product:list:* (automatic tags come from rows, so empty pages would otherwise never clear) and caps index-backed
entries at 5s: one event clears the cache and starts the async index sync, so a request in between re-caches the
pre-write state. Store 300s / admin 60s / vendor 60s + LinkProductSeller:list:* (link attach only clears that
tag). Invalidation tests: store 22/22, vendor 19/19, admin 26 pass.
Follow-ups (same day, same PR):
- Exact counts on admin/vendor via an ids-only index call; it's what
query.indexsends internally, minus pagination. Measured cost: 234ms vendor / 33ms admin at 20k. - Routing: plain lists go to
query.graph; the index is only used forproduct_seller/ sales channel / price filters. - Seller events: the service overrides now use
@InjectManager+@EmitEvents+@MedusaContext, soseller.seller.*is emitted and sellers reach the index. Deployments need one full index sync. - Previously no-op cache calls, now live:
- CI caught them (store-offers, offer-region-prices). Each got the link/list tag that actually clears.
- Membership checks are no longer cached.
- Open: tie ordering.
query.indextakes one sort key only, so there's noidtiebreak and paging can repeat or skip products whencreated_atties (on main too).
Session — Extendable offer tables, grid and form fields (2026-10-26), branch feat/extendable-offer-tables-forms
Panel extensions can now hide, replace, and add columns and fields beyond list pages, reusing the existing
custom-fields keys (no new config keys). list takes an optional zone and may be an array; useExtendableTable
takes zone (default "list"). forms[].fields keyed by a built-in id overrides it (null hides), through the
new <ExtendableFormField> and, for spreadsheet tabs, useExtendableGrid (cells come from the panel via
createDataGridExtensionColumn). Wired on offers: vendor variants / create-catalogue tables, the create
stock-and-prices grid, the edit drawer; admin variants / inventory tables. Core: POST /vendor/offers/batch
items accept additional_data, surfaced on offersCreated as offers_additional_data keyed by offer id.
Generators emit listZones, listColumnIds, formFieldIds. Tests: registry + grid unit specs (32 pass), SDK type
test, offer/vendor integration suites 7/7 (62 tests). bun run build green (13/13). Other pages still use
list-only extensions; follow the offer wiring to migrate them.
Follow-up (same day): product create (both panels) takes per-tab added fields, built-in overrides (title, subtitle,
handle, description, media, discountable, category/collection/type, tags; admin also sellers + global availability)
and an extendable variants grid. POST /vendor|admin/products variants accept additional_data, surfaced on
productsCreated as variants_additional_data keyed by variant id (the variant batch route still rejects it).
Untabbed forms fields now render on the first tab only and never become spreadsheet columns (exactTab), which also
fixes the create-offer grid. Vendor offer grids: edit-price takes added columns (saved via offersUpdated);
edit-stock, pricing, inventory-batch take overrides only (allowAdd: false). Vendor offer inventory table,
inventory detail location-levels / reservations inventory-item tables in both panels. Generator follows
use-*-columns imports and resolves constant zones. Tests: shared 37, SDK types, variant-sync specs, integration
11 suites (103 pass). Build green.
Unrelated finding, not fixed: the batch route drops condition_id when mapping items, though the validator
accepts it and the create form sends it. The admin ProductCreateAttributeSection (dimensions) is never rendered.
Follow-up 2: detail-page tables in both panels take list blocks: product variants, collection products,
category products (select stays first, actions last; collection/category also merge extension filters). Generator
now follows @<dir>/ alias column imports, so vendor list pages (product, order, customer, promotion, campaign,
payout, collection) finally get listColumnIds. Example configs in apps/vendor/src/custom-fields (offer, product,
collection, category) plus an offersCreated logging hook in apps/api. Generator specs 10/10 per panel, build green.
Known gap (pre-existing, all tables): added list filters render in the menu but their keys are not forwarded to the
API query, because each use*TableQuery reads a fixed key list. Not browser-verified.
Session — Magento integration gaps in core (2026-10-23), branch fix/magento-integration-gaps
Running the Magento connector against a live API (see the connector PRs #2–#5) exposed core behaviour the
integration had to work around. Fixed here: POST /store/carts now ignores an empty currency_code instead of
storing it and failing every later price calculation; the cart completion response lists the order group's child
orders with display_id, status and seller; an admin product created or updated as published emits
product.published (previously only /confirm did, so webhook subscribers never saw admin-published products);
createOffersWorkflow refuses offers on products restricted to other sellers or rejected
(validateOfferProductsStep); GET /admin/products?sku= filters variants instead of 500ing on Product.sku;
the plugin's event list drops order.shipment_created, which nothing emits. Tests: new
product/admin/product-publish-and-sku.spec.ts, three cases in offer/vendor/offer.spec.ts, one each in
offer/cart/cart.spec.ts and offer/order/order.spec.ts. bun run build green (13/13).
Session — Magento connector hardening sweep (2026-10-22), branches feat/magento-external-payment-capture (this repo) + feat/checkout-orders-indexer-platform (magento2-connector)
Session — Stripe connector (2026-10-22), branch feat/stripe-connector, worktree ~/Desktop/mercur-stripe-connector
Spec: docs/specs/spec-stripe-connector/ (local, gitignored; brief.md, research.md, blueprint.md, assert.md,
removals.md, deltas/D-001…D-012 all done). Scheduled payout pipeline in the shape of
Medusa's payment module.
- Core payout module is provider-agnostic:
pop_<identifier>_<id>registry (pop_system_defaultalways), ten-methodIPayoutProvider+AbstractPayoutProvider, new modelstransfer,settlement,adjustment,payout_provider,payout_checkpoint,payout_job_run,payout_notification, extendedpayout_account/payout(migrationMigration20261022120000),/hooks/payout/[provider](+ legacy alias). - Seven scheduled jobs (
packages/core/src/jobs), pipeline functions underworkflows/payout/pipeline, pure rules underworkflows/payout/utils(transfer factory, capture decision, settlement builder), workflows for transfer/reversal/payout dispatch, account sync, capture/cancel, operator notifications; admin routes for accounts, transfers, settlements, adjustments, jobs, status, captures, notifications; vendorpayout-accounts/me,transfers,settlements; public onboarding refresh. - Plugin
packages/plugins/stripe-connector(@mercurjs/stripe-connector-plugin): Stripe payment provider (manual capture, order-group metadata) + Stripe Connect payout provider, admin Finance → Stripe (tab per job), Settings → Stripe, seller/order widgets, vendor Settings → Stripe.packages/providersdeleted; docs rewritten. - Verified: core tsc + build, plugin server/admin/vendor tsc +
dashboard:build,bun testunit specs 35/35 (core utils + plugin provider), lint clean on touched files,payouts/vendor/*8/10 → racing subscriber removed (re-run pending), newpayouts/admin/payout-pipeline.spec.ts(fixes in progress). Gotchas: integration tests needpackages/plugins/magento2-connectorbuilt (test config loads its provider);bun run test:unitcan't resolve@swc/jestlocally, usebun test <dirs>; declaration emit needs an explicitReturnWorkflow<>annotation on workflows that returnwhen()results (TS2742). - Open: Stripe test-mode run by hand (assert.md § I); PR to
main.
Session — Medusa 2.22.0 upgrade (2026-10-22), branch chore/medusa-2-22
Every @medusajs/* pin moved 2.21.2 → 2.22.0 and every peer range >=2.21.0 → >=2.22.0 (packages,
providers, apps, integration-tests, root, and all three templates — they already tracked the workspace
line at 2.21.2, so they follow it; @medusajs/ui keeps its own 4.2.3 line). bun.lock refreshed.
Medusa 2.22.0 requires Node 22.22+, so the engines.node floor on core, the payout provider, the API
app and the templates is >=22.22.0; docs say Node 22.22+. Breaking change absorbed: 2.22.0 made
refundPaymentWorkflow replay-safe (medusajs/medusa#16964), which moved the hunk the payment-hooks patch
anchored on. Regenerated as @[email protected] (range 2.22.0–2.23.0);
the paymentRefunded hook now also carries is_replay so a ledger can skip a replay the way the credit
line and event are skipped. The other four patches apply unchanged; their ranges extend to 2.23.0.
test-utils dropped the inApp option, removed from both health.spec.ts. routes-manifest.json gained
/admin/customers/export. Verified locally: bun run build, bun run lint, patch unit specs 40/40,
payment/split-order-payments + order/admin/order-payment-status 16/16. Gotcha: after changing a patch,
rebuild core and jest --clearCache, or the transformer replays the old manifest from .medusa/server.
Session — Magento 2 connector, Part A (2026-10-21), branch feat/magento2-connector
Spec: docs/specs/SPEC-003-magento2-connector.md (local, in_progress). Design: Magento keeps
storefront, checkout, payment capture and 1P products; Mercur owns sellers, 3P offers, split orders,
commissions, payouts. Checkout drives a shadow Mercur cart (line items by offer_id, per-seller
shipping, pp_external_external session, complete).
- New plugin
packages/plugins/magento2-connector(@mercurjs/magento2-connector-plugin):magento_webhookmodule (endpoints + signed, retried deliveries),externalpayment provider,/admin/magento/*routes (webhooks CRUD, deliveries, redeliver, status, external refund), fan-out subscriber, retry/prune jobs, admin UI at/settings/magentobuilt withmercurjs dashboard:build. - Core:
deleted_atfilter +with_deletedforwarding on admin offers/sellers lists;order_group.metadata(+ migration) copied fromcart.metadata;integrationspermission key (core catalog + SDK). - Verified: turbo build 7/7, plugin admin tsc clean, oxlint clean, integration specs
magento2-connector/*9/9 andoffer/admin/offer-soft-delete1/1.test:unitcannot resolve@swc/jestlocally; registry spec left to CI. - Reviewed with the enterprise
medusa-reviewskill (Medusa eslint preset + exemplar diff) and fixed all findings: writes go through workflows with compensation and refetch, validation step instead of throw in transform, service underservices/withIMagentoWebhookModuleService, generated migration, typed responses, strict validators. Gate clean on plugin files; specs 10/10 after the refactor. - Part B pushed: github.com/mercurjs/magento2-connector (
mercurjs/magento2-connectorComposer package, modules Core/Process/Connector/OfferIndexer/Catalog/Settlement/Frontend/GraphQl). Lint + 13 unit tests green locally via a static PHP binary in the scratchpad (Homebrew PHP won't build on this macOS). Not yet run on a Magento install. - Next: dashboard Channel column/filter, roles preset once a roles module exists, Magento end-to-end run.
Session — Core hot-path performance (2026-10-21), branch perf/core-hot-path-optimizations, PR #1677
Technique catalog from the Medusa source in docs/PERFORMANCE.md (section 4 lists what this branch
applied, section 5 the remaining checklist). Fixed: checkout lock timeout/ttl/retention passed in ms
instead of s; cart lock skipped on the webhook-driven completion path; commission rates loaded once per
checkout via getCommissionLinesBatch; vendor single-product scoping no longer scans product_seller;
cache opt-in on reference reads; order-group SQL soft-delete joins; composite partial indexes on
order_group/offer/payout/review/commission_rule (+ migrations). Verified locally: core tsc, unit specs
4/4, commission-rates/admin/(commission-providers|commission-calculation) 15/15; other suites on CI.
Gotcha: the order module decorates totals only when a top-level total field (e.g. subtotal) is
selected, and needs items.* to derive line totals. Follow-ups listed in the PR body.
Session — Dashboard extensions, OS deltas D-001…D-005 (2026-10-20), branch feat/dashboard-layout-composer
Spec: docs/specs/spec-dashboard-extensions/ (local; docs/specs is gitignored), in_progress. PR #1674.
LayoutComposer(Medusa port, no edit mode) in@mercurjs/dashboard-shared; registry gained layouts, gates, layered preferences,getWidgetsForSections;resolveRouteOverridesgives overriding routesrenderDefault. SDK: every virtual module merges ordered layers (layers.ts), newlayouts/preferencesmodules,defineRouteConfig/defineLayoutConfig/defineLayoutPreferences.- Pilots on the composer: admin product detail, vendor offer detail (existing zone ids kept).
- Verified: SDK vitest 16/16, shared vitest 33/33, panel tsc no new errors vs baseline, admin/vendor/cli
packages build, both host apps
vite build. Docs pagereferences/panel-extensions/layouts.mdx. - Next: D-006 (rewrite the remaining 116 compound pages, public
/hooks+/components, peer deps), D-007 (CLI emits extension-targets for plugins, typed plugin routes), sidebars as composers.
Session — Seller ↔ Region assignment (SPEC-001), branch feat/seller-regions
Spec: docs/specs/SPEC-001-seller-regions.md. New region_seller link; linkSellerRegionsWorkflow;
seller creation (admin + vendor registration) links region_ids or the store default region.
Admin: POST /admin/sellers/:id/regions, POST /admin/regions/:id/sellers, GET /admin/sellers?region_id=,
seller.regions on retrieve. Vendor: /vendor/regions scoped to assigned regions; offer + shipping-option
prices validated against assigned regions (400). Admin UI: region detail Sellers section + add modal,
store detail Regions sidebar + add modal, Create Seller regions picker. Vendor UI: offer price grids gain
a column per assigned region (rules.region_id); offer pricing sections list region prices.
Verified: test:integration:http -- "regions|offer-region-prices|shipping-options/vendor|seller/(admin|vendor)/seller"
(10 suites, 238 tests). bun run build see spec Evidence. Not verified in a browser. Uncommitted.
Known pre-existing: admin validate-translations.spec.ts fails on sellers.* schema keys missing from
en.json (unrelated); bun run lint tsc noise in untouched files.
Session — Panel auth collision, branch fix/panel-auth-session-collision
Admin and vendor panels shared one API session cookie, so logging in to one logged the other out.
Both panels now keep their JWT in origin-local storage and send Authorization (+ x-seller-id
for vendor) via getAuthHeaders (exported from @mercurjs/admin / @mercurjs/vendor);
@mercurjs/client gained a headers option; POST /vendor/sellers/select returns seller_id and
only writes the session for session-authenticated callers. Host apps + templates/basic clients
updated. Verified: bun run build, test:integration:http -- panel-auth (2/2). Not verified in a
browser. Open risk: the messaging block's panel SSE (EventSource + withCredentials) can't
send a bearer header, so it falls back to polling until it gets a token-exchange flow.
Uncommitted.
Session — Admin Inventory (MER-139), branch feat/admin-inventory
Spec + audit: docs/specs/spec-3-admin-inventory/. Implemented (type-clean; deps built; lint
warnings pre-existing only): D-01 remove admin create-inventory-item flow; D-04 drop
"Details" suffix; D-06 Edit Attributes InlineTip; D-12 Manage-Qty warning InlineTip;
D-13 Edit Details flip (Title required / SKU optional); D-15 toast copy → Figma verbatim +
subtitle; D-18 Create Reservation warning InlineTip. Added all prompt/warning i18n keys and
regenerated the $schema.json inventory block (inventory subtree 66/66 parity).
Also done: D-16 delete item + delete level prompts (verbatim copy, {{location}} interp);
D-17 reservation delete two cases (discriminator reservation.line_item_id → unfulfilled-order
"Got it" info prompt vs deletable confirm); D-19 bulk "Edit stock levels" pre-confirm prompt;
D-14 adjust-qty empty-quantity message. Schema parity 67/67.
Also done (frontend, build-clean): D-02 Product + Store columns + reorder (In stock before
Reserved); list now requests +variants.product.title,+seller.name. D-03 filters =
SKU/Store/Location/Height/Width/MID code/Material (dropped Length/Weight/Requires-shipping) +
default sort title ascending (G3b); seller_id flows through the query. D-14 reservation
required-field messages (schema moved to buildCreateReservationSchema(t)). Fixed a pre-existing
AdminInventoryItemParams→AdminInventoryItemsParams typo.
All touched files type-clean (tsc --noEmit); remaining tsc errors are pre-existing
(@custom-types/* alias cascade + untouched inventory-metadata/inventory-stock-form).
Backend-remaining (needs running API — NOT verifiable in this worktree per project constraints):
- Admin
inventory-itemsroute override inpackages/coreso the Store filter (seller_idparam) is accepted and the Store column seller-link is guaranteed to resolve. (Store column may already resolve via global links infields; theseller_idfilter needs the override.) - D-05 Associated-offers sidebar (needs offer reverse-link on the inventory detail contract).
- D-07 bulk store-ownership gate; D-08 vendor notifications (subscribers); D-09/D-10 admin location scoping to the item's store.
- D-11 locations
…right-align — uses canonicalcolumnHelper.action; live visual check. Seedocs/specs/spec-3-admin-inventory/blueprint.mdfor the route-override plan.
Integration test (spin up to verify)
integration-tests/http/inventory/admin/inventory.spec.ts — type-clean (only jest-global noise
under standalone tsc, same as every spec). Run later with:
bun run test:integration:http -- inventory/admin/inventory. It seeds a seller + offer-backed
inventory item (stock location → shipping → product → offer) and asserts:
- Store column —
GET /admin/inventory-items?fields=+seller.nameresolves the seller link (should PASS; validates D-02 Store column). - Product via offer — offer inventory links to the offer, not the variant (memory
offer-inventory-not-on-variant), soinventory_item.variantsis EMPTY; the product is reached through the offer. Test assertsitem.offer?.product?.title. - seller_id filter — specifies D-03 backend; expected RED until the core route override lands.
⚠️ Finding to action: because offer inventory has no variant link, the current frontend Product
column (variants?.[0]?.product?.title in use-inventory-table-columns.tsx) will show - for
offer items. The list must reach Product through the offer instead. Test #2 confirms the exact
offer field/alias to use (verify offer vs offers when the suite runs), then update the column +
the list fields request accordingly.
Verify: bun install done; built @mercurjs/types|client|dashboard-shared; tsc --noEmit
touched-files clean (remaining errors are pre-existing @custom-types/* alias + workspace drift).
Session — Vendor Campaigns Figma Sync (branch feat/vendor-campaigns-figma-sync)
Spec: docs/specs/spec-1-vendor-campaigns/ (brief / blueprint / assert / deltas).
Implemented: D01 list Type column · D02 list Status column · D04 general row order
(Description before Identifier) · D05 configuration expiry warning · D06 merged
Spend+Budget into one Budget card (deleted campaign-spend/, updated detail sidebar +
skeleton) · D07 identifier tooltip · D08 no-limit helper text · D09 add-promotions tip
- plural add toast · D11 create validation (name/identifier required, spend-currency
refine, i18ncampaigns.validation.*) · D12 toast copy aligned to Figma (non-interpolated, pluralized add/remove; wired missing remove-promotion toasts).
Backend implemented (previously flagged as gated):
- D03 filters (frontend + backend) — extended
packages/core/src/api/vendor/campaigns/validators.ts(budget_type+status) and translated them inroute.tsGET intoquery.graphfilters (budget.type; starts_at/ends_at date ranges with$or … nullfor open-ended = active). Re-wired theuseCampaignTableFiltershook, query passthrough, and listfiltersprop. - D08 "Limit usage per" (frontend, backend already supported) —
Combobox(customer / email / promotion code) in create form-fields (usage-only); schema + defaults gainedbudget.attribute; submit sets typeuse_by_attributewhen an attribute is chosen (mirrors admin). BackendVendorCreateCampaignBudgetalready acceptsattributeand the workflow forwards it — no backend change needed. Detail Budget card renders the attribute label.
Tests:
integration-tests/http/campaigns/vendor/campaigns.spec.tsextended for D03/D08:budget_type=spend|usagefiltering (+ invalid value → 400),status=active| scheduled|expiredfiltering (incl. open-ended = active, scheduled excluded from active; + invalid value → 400), and ause_by_attributecreate withattributepersisting (D08). Not runnable in a fresh worktree (needs full install + Postgres); syntax-verified via TStranspileModule. Run in CI / installed checkout:bun run test:integration:http -- campaigns/vendor.
Still out of scope:
- D12 notification-drawer entry — backend notification template, out of UI scope.
Verification: vendor tsc --noEmit (root node_modules symlinked from main) shows
no NEW errors from these changes — remaining campaign errors are pre-existing/
environmental (unbuilt core route-map → CampaignDTO vs AdminCampaign,
@custom-types alias, DEFAULT_CAMPAIGN_VALUES enum). oxlint on changed files: no
new warnings. Full bun run lint + bun run build still owed in a fully-installed
checkout / CI (fresh worktree has no install).
- Active spec: (none in progress — pick the highest-priority unfinished
docs/specs/SPEC-*.md)
Session Log
Session: 2026-07-29 -- Admin Reviews (MER-152, SPEC-2)
- Goal. Promote reviews from the registry block into
@mercurjs/coreand build the admin reviews UI to match Figma (canvas40015049:1019815, BASIC/store reviews). - Backend.
packages/core/src/modules/review(model +statusenum + migration + service); links customer/order/seller/product;workflows/review(create/update/respond-add-once/delete- validate); admin/vendor/store API routes + validators + query-config + middlewares (registered
in all three aggregators).
MercurModules.REVIEW+ review DTOs added to@mercurjs/types.
- validate); admin/vendor/store API routes + validators + query-config + middlewares (registered
in all three aggregators).
- Admin UI.
pages/reviews/{review-list,review-detail,review-edit,review-respond,common}+hooks/api/reviews.tsx; route inget-route-map.tsx; sidebar entry after Stores;reviews.*i18n. List (Review ID/Rating stars/Content/Store/Customer/Date/Status badge/Response + Rating/ Status/Date filters), detail (two-column + Customer/Order/Store sidebar cards), Edit drawer (Status+Rating), Respond drawer (add-once), delete-action hook. - Block removed.
packages/registry/src/reviews/+registry.jsonentry + builtr/artifacts. - Verified. types+core build ✓, admin ESM bundle ✓,
tscclean on review files,oxlintclean. Addedintegration-tests/http/review/admin/review.spec.ts(runs in CI — worktree can't run it). - Next. CI integration run; migration apply on live DB; Figma visual parity; vendor-notify rule.
Session Log (prior)
Session: 2026-07-21 -- Vendor offer-targeted promotions (PR #1268)
Goal. Port the Medusa promotion-create form into the vendor panel and add offer-level targeting so a vendor's "Amount off offers" promotion actually discounts the vendor's offers at checkout. Branch
feat/vendor-offer-promotions.Key decision — how an offer is targeted.
ApplicationMethodTargetType(order/items/shipping_methods) is a hardcoded Medusa enum; offer is NOT a new target type. An offer is a line item, so target staysitemsand "offer" is a new rule attribute with value pathitems.metadata.offer_id. The store add-to-cart route already writesmetadata.offer_idonto the cart line; the promotion engine reads item-scope rules viapickValueFromObject, so matching needs no engine change — just the attribute + the metadata present in the compute context.offerreplacesproductin the vendor items-attributes (Figma dropdown = Offer/Category/Collection/Type/Tag). Rule-value dropdown useslabelAttr: "sku"(Offer has notitle); seller-scoped via theoffer.seller_idcolumn (there is nooffer_sellerpivot — the link is read-only on the column).Landed (backend, packages/core).
rule-attributes-map.ts(offer attr),rule-query-configuration.ts(offer→sku),rule-value-options/.../route.ts(offer branch: filter offers byseller_id),validators.ts(allowonceallocation),workflows/cart/utils/fields.ts(additems.metadatatocartFieldsForRefreshStepsso rules see it), and the root-cause fix inworkflows/cart/steps/prepare-adjustments-from-promotion-actions.ts.Bug found + fixed (affected ALL seller promotions). The seller-scoping of computed line-item adjustments compared
promotion.seller.idtolineItem.variant.product.seller.id. Master products are not seller-owned, so that value is empty and every seller-scoped line discount was silently dropped. Now resolved fromlineItem.offer.seller_id. This is why offer promotions produced 0 discount even though rule + metadata were correct.Landed (vendor panel).
templates.ts→ 3 Figma types (Amount off offers / Percentage off items / Buy X Get Y); submit handler no longer hard-codesapplication_method.type: 'percentage'and now sendsbuy_rules; addedis_tax_inclusiveswitch +onceallocation; schemavalueaccepts string|number; removed thecountry/productattribute hard-filter inrules-form-field.tsx, passedtarget_typeto the attributes hook, fixed a stalepromotion-create/...import →create/...; offer-basedrequiredProductRule; i18n keys.What was NOT done / owed. (1) Buy X Get Y is wired at the type/template level but its buy-quantity UX wasn't deeply exercised — verify buy_rules + apply_to_quantity flow. (2) Update-promotion / edit-rules drawer wasn't re-audited for the offer attribute. (3) The Confluence promotions doc still omits "Amount off offers" — not updated. (4) No automatic-promotion (non-code) cart test; only code-applied. (5) Vendor promotions area has ~11 pre-existing tsc errors (tsup/esbuild ships anyway) — left as baseline.
Also in the PR (not my work, per user request to commit all).
apps/vendor/.../store-setup.tsx(pre-existing),query-config.ts(limit/usedfields) andcreate-seller-promotions.ts(campaign linking) — unrelated, uncovered by these tests.Verified. Core + vendor builds clean.
test:integration:http— promotions store+vendor 37/37 pass (incl. cart E2E: targeted offer discounted 500 / discount_total 500; non-matching offer 0), offer/cart 8 pass (2 skipped), no regression.Next. Address owed items above; consider splitting the two unrelated files into their own PR.
Newest first. One entry per session, kept to a few lines: goal, what landed,
how it was verified, what's owed/next. Move durable facts into
docs/specs/SPEC-*.md Evidence or into memory — not here.
Template
Session NN: YYYY-MM-DD -- <spec / short title>
- Goal. One line.
- Landed. Key files/behavior (terse).
- Verified. build / lint / test result.
- Owed / next. What the next session should pick up.
Definition Of Done
A change is done only when:
- target behavior is implemented
bun run buildandbun run lintpass- a relevant integration test was run (for behavior changes)
- evidence is recorded in this file
- the repo remains restartable from
bun install && bun run dev