Guard merchant search delivery and relevance - #36
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
nextcommerce-docs | 885e7d6 | Commit Preview URL Branch Preview URL |
Sep 04 2026, 02:15 AM |
|
Preview verification: /api/search returned HTTP 200 with application/json; charset=utf-8, X-Content-Type-Options: nosniff, Content-Encoding: br, and the intended one-hour cache policy. The measured compressed transfer was 661,553 bytes in 1.75s on a CF cache miss, within the 750 KB guardrail. Production should still be rechecked after merge. |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge All 4 issues from the previous review at
No new issues were found in the incremental diff. Files Reviewed (4 files)
Previous Review Summary (commit 0bcabf3)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 0bcabf3)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (5 files)
Reviewed by minimax-m3 · Input: 32.6K · Output: 5.9K · Cached: 352.6K |
Summary
/api/searchpayload explicitly as JSON with MIME-sniffing disabled so the edge can compress it correctlyVerification
npm run build— 286 routesnpm run check-search-budget— 4.85 MB raw; 0.44 MB local Brotli-11 estimatenpm run check-search-quality— all three representative queries passThe edge
Content-Encodingheader still needs to be confirmed after deployment; the local check intentionally treats Brotli-11 as a deterministic best-case budget estimate rather than proof of Cloudflare behavior.Closes #35