Polish app chrome and composer interactions#99
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.
Summary
Adds a round of interaction polish across the app chrome, sidebar, vault switcher, and AI composer so the UI feels more tactile and stable during common power-user flows.
What Changed
Why
This branch focuses on polish and hardening. A few controls were technically functional but felt flat, and the composer action row could visually jump during stop/queued-send states. The composer footer needed a small bounded refactor so the UI preserves layout while state changes crossfade cleanly.
Testing
npm run lintnpm run buildManual QA
Recommended checks: