playwright-typescript-framework

Three different stories in one run -- worth separating, same as the last real run on this repo: 1) Seeded, not real: "Cart management" failing on the line subtotal is this run's deliberate seed on the `demo` branch (the assertion was changed to expect unitPrice×4 instead of ×3 -- see the diff at commit e17386d). Not a product bug. 2) Real and now confirmed recurring: the axe-core WCAG 2 AA color-contrast violation on products/cart/checkout (the shared "~/qa-sandbox" breadcrumb, #6d68cf on #0a0a11, 4.25:1 vs. the 4.5:1 minimum) showed up again in this run -- same signatures as the last real triage of this repo, completely independent of anything seeded here. Still unfixed. 3) Real and new: Admin Panel records search doesn't filter at all -- searching "Priya" returns all 8 rows instead of the 1 matching row, consistently across retries (not a timing flake). First time this one's been seen.

This run mixes one real product bug with a batch of unrelated environment flakiness -- worth telling apart before triaging either. The real bug: axe-core flags a serious WCAG 2 AA color-contrast violation on the products, cart, and checkout pages (3 signals, all from the shared "~/qa-sandbox" breadcrumb component). It renders at #6d68cf on a #0a0a11 background, a 4.25:1 contrast ratio against the 4.5:1 minimum. Same component, same fix, three pages -- not three separate bugs. The rest (11 signals) is a shard-3-shaped environment outage, not a code or test bug: apiRequestContext POST timeouts to playground.krishanchawla.com/api/auth/login and page.goto cancellations, spread across otherwise-unrelated specs (admin login, admin records, cart management, checkout, and a second pass of the accessibility suite itself) -- every one of them hit the same host in the same run window and failed the same way. That's the target environment being unreachable during this shard, not something to debug in the test code.