[zhaozhaozz]

The navigation now calls the existing test dashboard E2E and removes the Release validation and Operations pages. Existing report return links keep working through #tests.

• Remove both pages, their renderers, and their dedicated styles. Old #releases, #ops, and unknown bookmarks recover to the overview rather than showing an empty page.
• Preserve the overview's release summaries. Version-build links lead to CI; release details and branch information link to GitHub, leaving no links to removed pages.
• Rename report return links, update the page documentation, and bump the main bundle cache version to 20261019.1.
• Keep collection queries and stored snapshot/history data unchanged.

Validation

Tested commit: 032cb7a720576bdc420c8b1a1f1ee4ab1c9b18f4.

Check	Result
python3 -m unittest discover -s tests	156 passed
node --check static/app.js and node --check static/real-e2e.js	PASS
Repository-pinned Playwright suite	25 passed, 1 unchanged baseline failure
git diff --check	PASS

E2E conclusion

PASS for the requested navigation; FAIL for the full suite due to an existing score-chart assertion.

Scenario	Expected behavior	Actual result
Navigate every retained page	Seven tabs, E2E label, no release/operations page or JavaScript errors	PASS
E2E at 1440px and 390px	E2E is active, content is readable, no document horizontal overflow	PASS
Follow existing HTML report return links	Return to the correct E2E case/branch via #tests	PASS
Open removed/unknown hashes, initially or during navigation	Recover to the overview with a valid URL	PASS
Open overview release links	Link to CI or GitHub rather than removed tabs	PASS
Existing Real E2E score-chart journey	Find a .score-failed marker	FAIL on both the unchanged baseline and this branch

The failing journey was reproduced with the baseline's original static/app.js, static/index.html, and static/style.css at ffaea5608fbd8951cb1b9f5cd5297ea8d6dfbed1: expected one .score-failed, received zero. The baseline currently emits .score-x markers. This PR leaves the scoring implementation and those assertions unchanged, rather than masking the pre-existing failure.

Screenshots below use isolated fixture data. No live collection or production deployment was triggered.

Desktop

390px