fix(tui3): keep Home tasks in the displayed project - #1629
Closed
santoshkumarradha wants to merge 2 commits into
Closed
santoshkumarradha wants to merge 2 commits into
santoshkumarradha wants to merge 2 commits into
Conversation
santoshkumarradha
marked this pull request as ready for review
September 27, 2026 18:16
santoshkumarradha
added a commit
that referenced
this pull request
Sep 27, 2026
Member
Author
|
Superseded by the Santosh-authored consolidation #1632. The exact source revision and workflow recordings are included there. The aggregate remains draft pending final combined validation; this change has not yet merged into dev. Source history is preserved. |
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.
A
/tasktyped on Home in project B could run in project A after the command cleared its draft. Clearing rebuilt Home’s rows and moved the cursor to A’s newer conversation before the target was read. Ordinary messages read the target earlier. An engine/workspace mismatch check cannot catch this because the engine correctly answers for the already-wrong target.Capture the displayed target before consuming the slash draft, then pass it through the same conversation-opening implementation used by ordinary messages. A keyboard regression reproduces the task-only mismatch on current audit PR #1604 (
80aff6b9f); the plain-message control stays in B. Independent code review found no blocking issue.Validation on Spark at exact source/runtime
3cbffa975:internal/tui3package passed in two shards (141 seconds). Required GitHub CI is fully green.SHOPPING.mdon B’s retained task branch at commit611bc7e; only that report changed. B’s main branch stayed clean, and A’s tracked files, refs and unpublished edit remained identical.deepseek/deepseek-v4.1-flash, including auxiliary roles: 12 calls for A setup and 36 for B’s task/control. This used ordinary hosted chat with ask approvals and--one-model; Model Pool was disabled as the disclosed workaround for separately fixed fix(chat): defer independent pool judges in one-model runs #1610. It does not claim alternate model, remote-host or nondefault project-picker acceptance.Audited screenshots, GIF/MP4, both original terminal recordings, binary identity, model receipts and project-preservation proof are staged locally for the coordinator’s direct attachment. They are not yet public media links; no evidence commits were created for this batch.
This is a separate batch2 fix. It is not integrated into Santosh/dev or aggregate #1627, and no shared timer was changed.
Fixes #1466.