fix(chat): keep the overflow menu reachable on settled complete Goals - #1554
Open
kingxiao630 wants to merge 1 commit into
Open
fix(chat): keep the overflow menu reachable on settled complete Goals#1554kingxiao630 wants to merge 1 commit into
kingxiao630 wants to merge 1 commit into
Conversation
A completed Goal hid both the lifecycle action and the overflow menu, so goals.clear had no entry point and the completed ribbon stayed on screen forever. Suppress interactions only while the final task is still settling; once idle, restore the Edit/Remove menu so owners can clear the completed Goal. Refs TokenRhythm#1447
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.
Scope
Fixes the completed-Goal dead end in the chat Goal ribbon (#1447, Bug 1). When a Goal reached
complete, the ribbon hid both the lifecycle action and the overflow menu, sogoals.clearhad no UI entry point and the completed notice stuck to the conversation forever.Change: suppress interactions only while the final task is still settling (same condition the "Finalizing result" label already used). Once the Goal is idle, the overflow menu stays reachable with Edit goal / Remove goal, so owners can clear a completed Goal through the existing
clearGoalconfirm →goals.clearRPC path.Non-goals: Bugs 2 (Jump-to-Latest oscillation) and 3 (minimap targeting) from #1447 are intentionally not addressed here; they need virtualizer coordination changes and deserve focused follow-ups.
Branch
Base branch: main
Target exception: N/A
Issue
Linked issue: Refs #1447
(Refs, not Fixes, because this PR resolves Bug 1 of 3 in that report. The issue can follow its normal closing flow once the remaining scroll/navigation bugs are addressed.)
Release Note
Release note: Web UI — completed Goal ribbons now keep their overflow menu reachable so completed Goals can be cleared; interaction lockup now applies only while the final task is still settling.
Tests
Ruff: N/A (Web UI only)
Pytest: N/A (Web UI only)
Build:
npm --prefix opensquilla-webui run buildpasses (typecheck + all architecture guards + artifact verification).Regression tests: added
GoalRibbon.test.ts:keeps the overflow menu reachable on a settled complete Goal— idlecompleteGoal shows no "Finalizing result" label, exposes the "Goal actions" trigger, and Remove goal emitsclearonce.does not reopen the overflow menu when a complete Goal is still settling— acompleteGoal with an unsettled task keeps hiding the trigger andopenMenu()stays a no-op (guards theopenMenuguard change).renders an unsettled complete Goal as non-interactive finalizationunchanged and passing.Notes:
npx vitest run src/components/chat/GoalRibbon.test.ts src/views/ChatView.goal-outcome.test.ts→ 25 passed.The default test path remains offline, deterministic, credential-free, and safe for forks.
Maintainer Live Check
Maintainer live check: no
Surface: N/A
Safety
No secrets, local-only artifacts, private prompts/transcripts, channel identifiers, AI session artifacts, non-public fixtures, or tests/_private/ contents are committed.
Third-Party Origin
Third-party origin: none
Documentation Changes