Repository navigation
feat(web): add request summary and lifecycle history pages - #790
Draft
behinddwalls wants to merge 2 commits into
Draft
behinddwalls wants to merge 2 commits into
behinddwalls wants to merge 2 commits into
Conversation
## Summary ### Why? Queue entries need a focused request view with current status and inspectable lifecycle/build evidence. ### What? Add reusable Summary/History presentation, expandable event metadata and filters, copy controls, error/stale-state handling, and the queue-scoped request detail route. Keep shareable view selection and Next refresh integration in the host. ## Test Plan Passed nine API/library/host check targets and the production Next standalone build, including request component tests. Passed repository formatting, lint, module tidy, and Gazelle checks.
Request identity must reach the gateway unchanged even when its URL contains escaped characters. URL-decode queue and request segments once before removing resource-path escapes and reassembling the opaque request ID. Passed web checks and the real-stack request summary/history browser flow.
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?
A request row needs a readable detail URL and enough current-state and lifecycle/build history to explain the submission's progress.
What?
Add reusable request Summary and History views, ordered lifecycle/build events, history filters, readable queue-scoped request routes, and terminal-aware refresh. URL-decode request segments once before reassembling the opaque ID; keep gateway calls and Next.js navigation in the host.
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. The real-stack browser suite covers request summary/history navigation, event ordering/filtering, refresh behavior, and axe accessibility checks.Stack