You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
queen: Team port piece 1 - roster statuses and task-graph validation in team_msg #13894
Owner, 2026-11-15: port the DSH Team plugin (packages/experimental/agent-team, tool-agent-team,
agent-team-profile, client-ui-agent-team in the deepseek-harness repository, about 3,650 source lines) to
t27, built by t27b. AGENTS.md, section "Agent domains, canonical ids and the Team port", records that the
port is not started and that its t27 home is the team message spec of the Queen (lead and mates, tags,
claims, stop rules already exist there). The owner's boundaries of 2026-11-13 hold: one piece at a time,
the .t27 spec before any host code, land only on green, one writer per file. This issue is piece 1 only:
the roster member statuses and the task-graph dependency validation, as pure functions with tests. The
journal, projection, lifecycle, tools and the window panel are later pieces, each with its own issue
(see #13862 for the window side).
Boundary
specs/queen/team_msg.t27
User Scenarios
Given a team task list where a task names a dependency that is missing, duplicated, itself, or part of a cycle, when the list is validated, then the model returns the matching refusal code and names the first offending task.
Given a roster member, when its status changes, then only the transitions among provisioning, running, inactive and failed that the source roster allows are accepted.
Requirements
FR-001: The spec MUST define the four member statuses (running, inactive, provisioning, failed) and a pure function that says whether a transition between two of them is allowed.
FR-002: The spec MUST define a pure validation of task dependencies that returns distinct codes for ok, missing, duplicate, self and cycle.
FR-003: The spec MUST reuse the existing dependency helpers of the same file where they fit and MUST NOT create a second spec for the team.
FR-004: Each of the five validation outcomes and each refused status transition MUST be held by a test with a negative control.
FR-005: The change MUST NOT add hand-written code in a non-t27 language.
Success Criteria
git diff --name-only origin/master lists 1 file besides seal and baseline files the gates require.
The spec's tests pass in CI with 0 failures and 6 or more new test blocks.
Activity
merge origin/master into team-port-piece1 (Refs #13894)