feat: add per-chat queues and richer queue controls - #1
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
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.
What changed
Why
Real Chrome and Tampermonkey E2E testing exposed a localStorage read-modify-write race: simultaneous updates from different chat queues could overwrite the shared document and silently lose a prompt. Per-chat revisions now allow a stale writer to restore a newer scope instead of deleting it.
User impact
Users can safely run independent queues in multiple chats, edit and reorder pending prompts, retry failed items, and use improved keyboard and panel controls without mixing or losing queue entries.
Validation
npm run validateThe unrelated research document is intentionally excluded.