feat(ui): share adapter-neutral conversation presentation - #1385
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Align the ongoing browser conversation with the existing launch composer and establish an adapter-neutral presentation boundary. Pi is the only live adapter in this change.
Included increments
Design decision
Share presentation, not execution protocols or persisted messages. The launch page retains its runtime/credential selectors in slots. Existing-session settings remain in Settings rather than adding unsupported inline model or attachment actions. Remove permanent Idle/WebPi chrome from the top bar; keep active/failure state visible. Narrow layouts preserve composer width and local output scrolling. Native disclosure, keyboard focus and reduced motion are retained.
Verification
Boundary touch
UI presentation and UI polling lifecycle only. No backend protocol, credential, trading, persistence, dependency or runtime-retention change. No new adapter integration. Browser acceptance did not send prompts to the user's existing sessions.
Acceptance
Draft for maintainer visual review; not merge authorization. Follow-up adapters can reuse these components by normalizing their content and supplying supported operations.
Sidebar selection follow-up