Make Thread Organizer use pinned threads as an inbox#11
Draft
brsbl wants to merge 2 commits into
Draft
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.
Summary
Turn Thread Organizer into an inbox workflow:
Root cause
The prior plugin only tracked threads created while it was loaded and defaulted to observe mode. Most existing threads therefore had no organizer state and received no lifecycle updates.
Startup reconciliation now snapshots the thread list, refreshes each thread before adoption, and runs as a host-managed background service so reloads cannot overlap plugin instances.
A follow-up live regression showed that ownership tracking incorrectly preserved manually pinned active threads. Pinning is now reserved for Inbox state, so active work is always unpinned.
Validation
npm run check --workspace bb-plugin-thread-organizernpm run hygienepassedThe repository-wide artifact command reaches Thread Organizer successfully but remains blocked by the existing missing
plugins/timeline-comments/dist/server.jsartifact.