T-Y6IT-task-next-project-and-all-dispatch-across-the-roster-on-the
State: planning/proposed · Impact: medium · Complexity: medium
Before the engine takes over, the TypeScript orchestrator should already pick work across peers so the roster and qualified links get real use.
Proposed
Section titled “Proposed”task next --project <slug> runs the pickup order in a peer; --all unions the roster and treats a
qualified depends_on as satisfied when the peer’s main has the target closed.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: With a fixture of two repos,
task next --allreturns a task from the peer when the local corpus has nothing ready. - AC-2: A task whose qualified dependency is open in the peer is withheld with a reason naming the peer.
Out of scope
Section titled “Out of scope”- Engine dispatch.
Dependencies
Section titled “Dependencies”Depends on
Section titled “Depends on”T-KBOI-qualified-wikilink-pattern-resolver-and-the-audit-unverified