research(ubiquiti): the store s own catalogue API has no Dream Wall Pro record - nine storefronts, controlled (#130) #2088

Merged
jaylouisw merged 1 commit from catalogue/1119-0422 into main 2026-11-19 04:33:16 +00:00
Owner

Refs #130

The Pro has been tested nine times as a page - /{store}/en/products/udw-pro returning 404 in every storefront Ubiquiti names. A 404 route can be a removed page in front of a row that still exists. This pass asked the commerce backend instead: store.ui.com is a Next.js front end over a GraphQL service, and its per-SKU lookup answers anonymously.

How it was reached. The product page exposes only preconnect https://ecomm.svc.ui.com; the operations are in the JS chunks. POST https://ecomm.svc.ui.com/graphql is live ({__typename} -> Query). Introspection is refused (400) and GraphQL validation errors are masked as N copies of Internal Server Error - the error count was used as an oracle to find the required inputs (limit, offset) and the lowercase storeId.

Controls, because a miss only means something if a hit is possible. This API serves retired rows and resolves old names:

slug result status historicalSlugs
udw FOUND, UDW (420W) SoldOut dream-wall, dream-wall-ea, udw, unifi-dream-wall
udm FOUND SoldOut unifi-dream-machine
udm-pro FOUND Available udm-pro, udm-pro-u
ucg-fiber FOUND Available -

The Pro, at the database, from all nine storefronts. The not-found error carries extensions.alternativeStores, the catalogues that do hold the SKU:

store udw (control) udw-pro
us FOUND SoldOut NOT_FOUND, []
eu/ca/br/jp/me/mx/tw/uk NOT_FOUND, 9 stores listed NOT_FOUND, []

The non-US control rows are the load-bearing ones: from eu the UDW is absent from that catalogue and the API lists all nine storefronts that have it. The same query for udw-pro lists nothing, from all nine. Five spellings tried - udw-pro, udwpro, udw-pro-us, dream-wall-pro, dreamwallpro - all miss with an empty store list.

Deliberately not overclaimed. This proves there is no catalogue row anywhere and that it is not a delisting (SoldOut rows are still returned). It does not prove the product never existed: the API purges rows (usg and uxg also miss), so "no record now" is not "never shipped" - and neither is a port count. The census fields remain unpublished and the request stays open.

New traps recorded: store.ui.com/robots.txt, /sitemap.xml and /products.json all 404 with the same 204,279-byte page (no product index, not Shopify); the list query storefrontProducts is unusable anonymously (four masked errors for every input), so this instrument is slug-at-a-time.

Files. research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md (new section) and scripts/ubiquiti-storefront-catalogue.js (reproducible probe, zero deps). No spec change: devices/ubiquiti/udw.json is untouched, since the vendor's machine-readable spec agrees with it and none of the Pro's fields exist to add.

Gates. syntax-check 437 files OK; audit-port-types no port contradicts its type; hardware-invariants 26/26; catalogue-hygiene 25/25; import-devices-capabilities 34/34; registry regenerated, already current (2,357 models).

Refs #130 The Pro has been tested nine times as a **page** - `/{store}/en/products/udw-pro` returning 404 in every storefront Ubiquiti names. A 404 route can be a removed page in front of a row that still exists. This pass asked the **commerce backend** instead: `store.ui.com` is a Next.js front end over a GraphQL service, and its per-SKU lookup answers anonymously. **How it was reached.** The product page exposes only `preconnect https://ecomm.svc.ui.com`; the operations are in the JS chunks. `POST https://ecomm.svc.ui.com/graphql` is live (`{__typename}` -> `Query`). Introspection is refused (400) and GraphQL validation errors are masked as N copies of `Internal Server Error` - the error *count* was used as an oracle to find the required inputs (`limit`, `offset`) and the lowercase `storeId`. **Controls, because a miss only means something if a hit is possible.** This API serves retired rows and resolves old names: | slug | result | status | historicalSlugs | |---|---|---|---| | `udw` | FOUND, `UDW (420W)` | `SoldOut` | `dream-wall`, `dream-wall-ea`, `udw`, `unifi-dream-wall` | | `udm` | FOUND | `SoldOut` | `unifi-dream-machine` | | `udm-pro` | FOUND | `Available` | `udm-pro`, `udm-pro-u` | | `ucg-fiber` | FOUND | `Available` | - | **The Pro, at the database, from all nine storefronts.** The not-found error carries `extensions.alternativeStores`, the catalogues that *do* hold the SKU: | store | `udw` (control) | `udw-pro` | |---|---|---| | us | FOUND `SoldOut` | NOT_FOUND, `[]` | | eu/ca/br/jp/me/mx/tw/uk | NOT_FOUND, **9 stores listed** | NOT_FOUND, `[]` | The non-US control rows are the load-bearing ones: from `eu` the UDW is absent from that catalogue and the API lists all nine storefronts that have it. The same query for `udw-pro` lists nothing, from all nine. Five spellings tried - `udw-pro`, `udwpro`, `udw-pro-us`, `dream-wall-pro`, `dreamwallpro` - all miss with an empty store list. **Deliberately not overclaimed.** This proves there is no catalogue row anywhere and that it is not a delisting (`SoldOut` rows are still returned). It does **not** prove the product never existed: the API purges rows (`usg` and `uxg` also miss), so "no record now" is not "never shipped" - and neither is a port count. The census fields remain unpublished and the request stays open. New traps recorded: `store.ui.com/robots.txt`, `/sitemap.xml` and `/products.json` all 404 with the same 204,279-byte page (no product index, not Shopify); the list query `storefrontProducts` is unusable anonymously (four masked errors for every input), so this instrument is slug-at-a-time. **Files.** `research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md` (new section) and `scripts/ubiquiti-storefront-catalogue.js` (reproducible probe, zero deps). No spec change: `devices/ubiquiti/udw.json` is untouched, since the vendor's machine-readable spec agrees with it and none of the Pro's fields exist to add. **Gates.** `syntax-check` 437 files OK; `audit-port-types` no port contradicts its type; `hardware-invariants` 26/26; `catalogue-hygiene` 25/25; `import-devices-capabilities` 34/34; registry regenerated, already current (2,357 models).
research(ubiquiti): the store's own catalogue API has no Dream Wall Pro record - nine storefronts, controlled (#130)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 12s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Docker build (pull_request) Successful in 18s
CI / Arm auto-merge (pull_request) Successful in 3s
0dd1745a68
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-19 04:33:05 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2088
No description provided.