Repository navigation
fix(harness): preserve scoped history and Terminal focus [SAP-3292] #1040
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
ynadge
wants to merge
1
commit into
assistant-visibility-reconciliation
from
assistant-history-scope-and-focus
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@sapiom/harness": patch | ||
| --- | ||
|
|
||
| Preserve scoped mixed history, per-workspace refresh ordering, and explicit Terminal focus. |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Aliased workspaces split mixed history
For symlinked workspaces,
reviewedAssistantTerminalrejects the Terminal belonging to the reviewed Assistant. AssistantHistory.list returnsrealpathpaths, while sessions retain their launch spelling. The mixed row loses its Terminal action and appears as separate history.Learn more
Assistant history canonicalizes every requested and returned cwd with
realpath. Terminal sessions retain the path normalized bypath.resolve, which does not resolve symlinks. The new exact string comparisons therefore treat two spellings of the same directory as different scopes across both the rail and review pane.Example: A session starts in
/work/current, wherecurrentis a symlink to/repos/acme. Its Terminal session keeps/work/current, but its Assistant entry uses/repos/acme. Opening that Assistant shows no Terminal action, and history displays two rows instead of one mixed row.Recommended fix: Give both history sources the same server-issued canonical cwd before comparing them. Apply the same identity rule in
reviewedAssistantTerminal,reviewedTerminalSummary,assistantByStudio, and the row-level Terminal lookup; browser-only lexical normalization cannot resolve symlinks.Was this helpful? React with 👍 or 👎 to provide feedback.