Repository navigation
test(web): wire local demo and real-stack browser checks - #792
Draft
behinddwalls wants to merge 3 commits into
Draft
behinddwalls wants to merge 3 commits into
behinddwalls wants to merge 3 commits into
Conversation
## Summary ### Why? The complete demo needs one local/CI entry point and real-stack coverage after the page changes are independently reviewable. ### What? Add the Compose overlay, Make targets, required web CI jobs, Bazel-built E2E service images, Python stack runner, Playwright/axe coverage, and local documentation. Restore the complete workspace check suite now that every page is present. ## Test Plan Passed all ten web unit/type/lint/generation/package checks and the production Next standalone build, plus repository formatting, lint, tidy, and Gazelle checks. The final tree is byte-for-byte identical to the original web-ux snapshot. The existing real-stack browser failure at the git-change heading remains unchanged; this split does not include a bug fix.
## Summary ### Why? Local startup, documentation, and real-stack tests must use the same demo credentials and protect the previously failing Git change navigation. ### What? Default the demo password to test, update printed/documented credentials and readiness configuration, and cover change-history reloads, pinned versions, and literal percent escapes. ## Test Plan Passed formatting, Gazelle, lint, module tidy, BUILD synchronization, all web checks, the E2E runner unit test, and all four Playwright/axe real-stack tests.
## Summary ### Why? The change-history scan limit only failed with more than 500 queue requests, which the small demo fixture did not exercise. ### What? Seed a busy fake queue with matching changes on both sides of the scan boundary and verify continuation, snapshot reload, live refresh, and accessible page navigation. ## Test Plan Passed the verification-branch web checks, all four real-stack Playwright/axe tests, formatting, lint, module tidy, and Gazelle checks.
This was referenced Oct 6, 2026
behinddwalls
added this pull request to stack #794
October 6, 2026 21:02
behinddwalls
removed this pull request from stack #794
October 6, 2026 22:08
This branch has not been deployed
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.
Summary
Why?
The reference host needs reproducible local startup and real-stack verification, not only unit coverage.
What?
Wire the web Compose overlay, Make targets, local documentation, required CI jobs, Bazel-managed OCI inputs, and the Python-owned Playwright/axe runner. Align local and browser-test credentials to test/test. Add regression coverage for encoded Git routes and paginated change history in a busy fake queue, including continuation, reload, live refresh, and accessibility.
Test Plan
Repository-native validation passed:
make test(141 targets),make lint,make check-tidy, andmake check-gazelle. The web generation, lint, typecheck, unit/component, and package-consumer checks passed on the complete stack. All five real-stack Playwright/axe tests passed on the complete stack. The busy-queue regression creates more than 500 queue requests and verifies older matching submissions remain reachable.Stack