You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(web): earbuds show phone specs (1 inch screen, 1GB RAM, 64GB ROM, cameras); Watch Ultra 2 shows 5G #1142
Source: these values are in master_products.specifications, ram_gb, storage_gb, has_5g (GET /api/v1/rate/products/<slug>), apparently filled by the spec enricher into the phone template.
Not a duplicate of #1123 (that one is the stored model_key, samsung:galaxy-buds3-pro:64gb).
Proposed fix
Web: render the spec groups per category. For earbuds, use audio groups (drivers, codecs, ANC, battery, connectivity, water resistance) and never show screen size, refresh rate, ppi, RAM, ROM or camera rows; drop the "xGB RAM · yGB" chip on earbud cards. For smartwatches, show "LTE"/"Cellular" rather than "5G" and treat has_5g as phones/tablets only.
Data: clear the phone-only fields on earbud masters (ram_gb, storage_gb, display.* numerics) and set Watch Ultra 2 has_5g false. That is a Production data change: propose the SQL for JOY's approval (AGENTS.md 0.1). If the enricher lives in DOS/Rate-Services, open a follow-up there so it stops writing phone fields for earbuds.
Acceptance
No earbud page or card shows a screen, refresh rate, ppi, RAM, ROM or camera value.
[Agent: Audit] Release: filed from the live sweep #1131; research only, no code started. Status Ready on Project #9. The next session may take it over with node scripts/ops/board.mjs 1142 --status in-progress --agent <Nick> --take-over, citing this comment. Evidence was gathered on Production c23ab85b on 2026-10-27; re-check the live numbers before fixing, since crawls change them.
[Agent: Web] Claimed (take-over per the Audit release comment above). Plan: per-category spec templates on the product page and cards (earbuds: audio groups only, no screen/RAM/ROM/camera rows; smartwatches: no 5G), tests per template, and a trace of which writer stored the phone fields (importer here vs Rate-Services). Any data cleanup will be a SQL proposal only.
[Agent: Web] Writer trace: the phone-shaped values come from this repo's importer, not from Rate-Services code. AiSpecEnricher asked the LLM for the phone ten-group schema for every category, and EntityMatcher stored it (Tier 3 insert and enrichMasterProductById). Rate-Services only runs that engine through vendor/rate; a read-only check found no writer of its own for ram_gb, has_5g or specs. The fix in #1163 covers both the display and the importer writes, and reaches the crawler on the next vendor/rate bump. The stored-row cleanup is a SQL proposal in the PR body. Remaining surfaces (/compare, leaderboard, export, API) are in #1166.
Activity
JOY commentedon Oct 27, 2026
[Agent: Audit] Release: filed from the live sweep #1131; research only, no code started. Status Ready on Project #9. The next session may take it over with
node scripts/ops/board.mjs 1142 --status in-progress --agent <Nick> --take-over, citing this comment. Evidence was gathered on Productionc23ab85bon 2026-10-27; re-check the live numbers before fixing, since crawls change them.JOY commentedon Oct 27, 2026
[Agent: Web] Claimed (take-over per the Audit release comment above). Plan: per-category spec templates on the product page and cards (earbuds: audio groups only, no screen/RAM/ROM/camera rows; smartwatches: no 5G), tests per template, and a trace of which writer stored the phone fields (importer here vs Rate-Services). Any data cleanup will be a SQL proposal only.
fix(web,importer): review round 1 for category spec templates (#1142)
JOY commentedon Oct 27, 2026
[Agent: Web] Writer trace: the phone-shaped values come from this repo's importer, not from Rate-Services code.
AiSpecEnricherasked the LLM for the phone ten-group schema for every category, andEntityMatcherstored it (Tier 3 insert andenrichMasterProductById). Rate-Services only runs that engine throughvendor/rate; a read-only check found no writer of its own forram_gb,has_5gor specs. The fix in #1163 covers both the display and the importer writes, and reaches the crawler on the nextvendor/ratebump. The stored-row cleanup is a SQL proposal in the PR body. Remaining surfaces (/compare, leaderboard, export, API) are in #1166.fix(web,importer): per-category spec templates for earbuds and watches (
JOY commentedon Oct 28, 2026
[Agent: PO] Done: released to production in promote PR #1181 (main 6be33d7);
verify-livepassed (database ok, 5 routes 200).fix(web): apply category spec templates to compare, leaderboard, expo…