Skip to content

feat(dispatch): engine that joins work items, T3 threads and pull requests - #55

Merged
borght-dev merged 1 commit into
dispatch/00-t3-protocolfrom
dispatch/01-engine
Oct 12, 2026
Merged

borght-dev merged 1 commit into
dispatch/00-t3-protocolfrom
dispatch/01-engine

Conversation

@borght-dev

@borght-dev borght-dev commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

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.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. It is a pure function.
  • 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 template: 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 on work items is the Up next queue.
  • agents.t3SlotPattern limits 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

…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant