Repository navigation
Compact conversation actions and unify steering submission - #687
Merged
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.
Merge decision: ready — conversation actions stay reachable in compact headers, and steering receipts no longer squeeze the draft; targeted tests and browser fixtures support this bounded UI change.
User outcome
Consolidate secondary chat and message-exchange controls into a labelled Conversation actions disclosure. Keep conversation context and imported-conversation continuation available, and consolidate imports in conversation navigation.
Use one icon-only submit arrow with a user-scoped Queue/Steering default saved in this browser, Shift-click for the opposite action once, and named keyboard/touch alternatives in More actions. Steering keeps exact-attempt submission and idempotent retry behaviour. Short overlay notices are backed by reopenable activity and pending cancellation; long receipts do not participate in the composer's layout.
Task:
#V#task_agent_df8c267afe561609bb0d7db94fd97634. Michael's follow-up authorises implementation and publication, without deployment.Evidence
tests/browser/conversationActions.cjs: production template/CSS and interaction modules with deterministic transport at 1440×900, 375×812 and 667×375. Header disclosures, both defaults, Shift-click, newline preservation, cancellation and message-exchange actions pass. Draft widths before/after two long receipts remain 1230/1230, 249/249 and 541/541 CSS pixels.composerControls.cjspasses six desktop/touch/short-viewport profiles. Screenshots were visually inspected; local evidence is retained in.run/conversation-uiand.run/conversation-ui-neighbour.Ship boundary
Minimum criteria are reachable header and submission alternatives, useful draft width with long receipts, and preserved draft/attempt/retry behaviour. Lost drafts, accidental queue/steer routing, inaccessible actions or clipped recovery controls would block delivery. The browser-discovered short-desktop menu clipping was repaired and retested.
This is Tier 1 fixture-backed UI acceptance, with no live model calls or persisted Von mutations. Public authentication, physical mobile devices and cross-device preference synchronisation are not claimed. Existing terminal-receipt discovery after reload remains unchanged. No backend authority, workflow, database or deployment change is included.