Repository navigation
feat(dispatch): engine that joins work items, T3 threads and pull requests - #55
Merged
Merged
Conversation
…uests The model behind the Dispatch section, with no screen yet. - engine.ts builds the overview: every open item assigned to you with its T3 threads and its pull request, sorted into a bay (waiting on you, out of sync, agents working, up next, not started, paused, handed off), plus the slots and the open threads that belong to no item. - link.ts links threads to items through AB# references, branch names, linked pull requests and, for your own items, bare numbers. A manual link wins. - Suggestions follow the item's own workflow, so they work outside one process: a merged pull request suggests the resolved or completed state, an open one suggests the review state. - Pull requests come from GitHub when BorgDock polls them, so an item carries live checks instead of T3's snapshot. - items.ts loads my open items with their workflow in process order. - sync.ts polls the T3 hosts and Azure DevOps and rebuilds the overview when an input changes. The track star is the Up next queue. - agents.t3SlotPattern limits which T3 projects count as slots. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 12, 2026
borght-dev
added this pull request to stack #62
October 12, 2026 15:13
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.
Part 2 of 8 of Dispatch in BorgDock. The stack, bottom up: #54 → #55 → #56 → #57 → #58 → #59 → #60 → #61.
The model behind the Dispatch section. No screen yet.
What changed
engine.tsbuilds the overview: every open item assigned to you with its T3 threads and its pull request, sorted into a bay (waiting on you, out of sync, agents working, up next, not started, paused, handed off), plus the slots and the open threads that belong to no item. It is a pure function.link.tslinks threads to items throughAB#references, branch names, linked pull requests and, for your own items, bare numbers. A manual link wins.items.tsloads my open items with their workflow in process order.sync.tspolls the T3 hosts and Azure DevOps and rebuilds the overview when an input changes. The track star on work items is the Up next queue.agents.t3SlotPatternlimits which T3 projects count as slots. Empty takes every project.How I checked it
Unit tests for the engine, the linker, the item loader and the sync loop.
🤖 Generated with Claude Code