Repository navigation
frontend: research homepage from approved UI audit page 9 - #83
Merged
Merged
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
1 participant
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.
Match the research homepage to page 9 of the approved 前端 UI 重构方案.pdf: latest/archive/method/RSS navigation, the existing risk copy in a separate notice, three horizon conclusions, and a five-report recent list beside the latest report.
Use existing final_decisions and report dates/counts instead of invented recommendations or metrics. Empty recommendations are a valid outcome. The stronger 'signal below threshold, not missing data' explanation requires both required freshness sources to be explicitly present, valid and fresh, no quality warnings, and explicit watch/skip decisions in every horizon. Legacy, missing or unknown evidence links readers to the full report.
Only the homepage renderer/styles and presentation tests change. Report/archive content, recommendation calculations and publishing workflows remain unchanged. The method link uses the existing system design document.
Validation: 86 focused publisher tests pass. Windows full suite: 382 pass with the same 19 failures as pristine main (368 pass), without new failure IDs. Four Playwright viewports (1620x1125 matching the PDF proportions, 1280, 390 and 320px) pass navigation and empty/nonempty/missing-input/no-report states with no console errors or overflow. Preview reports pass the real advisory schema validation before rendering. Approved PDF and final screenshots were compared directly; native Linux CI remains required.