Repository navigation
feat(web): add queue directory and live request list - #789
Closed
behinddwalls wants to merge 2 commits into
Closed
behinddwalls wants to merge 2 commits into
behinddwalls wants to merge 2 commits into
Conversation
## Summary ### Why? Users need a queue entry point and a live request list that can refresh without timestamp-pinned URLs. ### What? Add queue-directory and searchable request-table library components, the demo queue routes, stale-snapshot presentation, and signed snapshot pagination. Keep resource IDs opaque and refresh the default trailing receipt window on each load. ## Test Plan Passed nine API/library/host check targets and the production Next standalone build, including queue/window component and cursor tests. Passed repository formatting, lint, module tidy, and Gazelle checks.
The pinned Next.js runtime supplies encoded route parameters, which must not be sent as queue identities to the gateway. URL-decode the queue segment once before removing the resource-path escape and validating the configured queue. Passed web checks and the real-stack browser suite.
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
Collaborator
Author
|
Superseded by a restructured web stack (shared platform package, mountable SubmitQueue module, framework-neutral host pipeline, and Next adapter), which will be published as a new stack. Closing this draft; the branch is kept. |
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?
Users need a queue entry point and a live, newest-first request list without fixed time bounds becoming stale in the URL.
What?
Add the initial queue directory and queue request page, rolling 24-hour receipt windows, stable signed pagination cursors, live refresh, and reusable request-list presentation. Decode queue names once at the Next.js routing boundary before passing the opaque identity to the gateway. This initial host configuration is replaced by gateway-backed queue discovery in the final PR.
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 queue navigation, newest-first requests, live refresh, and accessibility.Stack