fix(amazon): improve storefront fidelity and task grading - #115
Draft
jackjin1997 wants to merge 5 commits into
Draft
jackjin1997 wants to merge 5 commits into
jackjin1997 wants to merge 5 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Visual reference
Compared against https://www.amazon.com/ on 2026-09-13. Amazon campaign content and localization rotate dynamically, so this change targets stable structure and visual hierarchy rather than claiming pixel-identical promotional content.
Task contract
25,25.0, and25.00are accepted without weakening non-numeric filters128 GB, and recognizes every sort alias implemented by the UIWaterproof: Nois rejectedValidation
about:blank, and legal alternativesagent_demo/eval_judge.py --verifier Trueagainsta49afd9and passed; these are integration replays, not an independent agent success-rate claimCHANGES_REQUIRED; current head386ffdbf0869bd5d85adbea690d7a67f89f33287resolves their complete finding sets with regression coverageagent_demo/eval_judge.py --verifier Trueboth passed, and the before/after database snapshots were byte-identical9c8cb0c112259f07a6d62edfa2f7ee01f94ce3e3and validated all 1,408 managed membersbcd895293c6837a9f69ccf4e726dee28166005e3089eb939e782eced9768edc1cc6e3dafa4d392d35b9113545dd68889ee2bed79e72d5e56e1b1126ffe1f6d31Integration ordering
Upstream
mainadvanced after this draft was opened and now pins a newer HF asset revision containing the Kaggle and NVIDIA bundles. The only current GitHub merge conflict is.assets-revision. Do not resolve it by replacing the newer global asset line with this older review candidate. Merge HF PR #81 first, then sync the GitHub branch with currentmainand pin the HF merge commit, which will contain both the newer bundles and the unchanged reviewed Amazon archive.Not run
A full Docker image rebuild was not run because the host had 38 GiB free, below the 50 GiB safety floor for an unknown-peak full build. Runtime validation reused the existing canonical image with the final site and pinned asset mounted. After the second blind review, only the affected task-40 UI path was rerun; the other corrections are verifier-only and were covered by the 35-test regression matrix.