@ycodium-ai/plugin-team 0.2.3510 → 0.2.3566

package/README.md

@@ -1,28 +1,38 @@
 # @ycodium-ai/plugin-team
 
-Manage a project's team members, choose a lead, and give that lead a goal. The **Teams**
-project workbench tab on Web and Desktop opens a conversation for each agent member and sends the lead
-a brief for splitting and assigning the work.
+Manage a project's team members and run teams. The plugin registers three views on the team page:
+**Board** (one team's work items on its own team page; every team as a lane at the project level),
+**Members** and **Handbook** (project level). It has no page of its own: teams are opened from a conversation, as
+described below.
 
 This plugin is bundled with Ycodium as `core.team` and is enabled by default.
 It has no separate installation step in a bundled checkout. Enabling the plugin exposes the tab;
-disabling it removes the tab and commands. The lead and goal facts stay in the host event log,
+disabling it removes the views and commands. The lead and goal facts stay in the host event log,
 and enabling it again rebuilds their state. Existing conversations remain in the conversation list.
 
-A project's team is its active agent members, 1–8 of them, kept in the host's project members: the
-tab adds, edits, removes and restores them as you, and records you as the author. People can be
+A project's team is its active agent members, at least one and no upper bound, kept in the host's project members: the
+Members view adds, edits, removes and restores them as you, and records you as the author. People can be
 members too but take no part in a goal. Names must be distinct after trimming surrounding spaces and
 ignoring capitalization. One local agent member must be the lead; the plugin stores only that choice.
-A roster saved before members lived in the host keeps working until you import it from the tab. On
-mobile the plugin's page lists the members read-only. The lead of the current goal can also add, change,
+A roster saved before members lived in the host keeps working until you import it from the Members
+view. Each member row shows the teams the member is on, and marks a remote agent as one whose approvals are
+handled on its own machine. The lead of the current goal can also add, change,
 remove and restore agent members with the `team_create_member`, `team_update_member`,
 `team_remove_member` and `team_restore_member` tools; the plugin writes those changes and keeps who asked
 in its own facts.
 
+A team can also be opened from any ordinary conversation: once the person has agreed to a plan there, the
+agent calls `team_open`, and that conversation becomes the team's lead and its group chat. The team is one
+work line with one goal; every local agent member gets its own full-access conversation under the lead's,
+and is woken with what was said in the lead conversation since it last looked. The lead changes who is on the
+team with `team_set_members` and reads everything it needs to plan with `team_roster_overview`.
+Archiving the conversation stops the team and unarchiving carries it on. Project-level goals started before teams
+existed are unchanged and are not moved into this shape; their items sit in the Board view's "No team" lane. The
+page no longer starts new goals. The details are in the
+[team plugin](../../docs/internals/team-plugin.md#teams-on-a-work-line) page.
+
 Keep the project's board and project memory switches on so the lead can create work items and
-assign them to members. Starting another goal asks for confirmation; the previous
-goal's conversations keep running. If starting fails midway, Retry completes the same request
-without creating duplicate conversations or sending the lead another first turn.
+assign them to members; the Members view has both switches.
 
 Work can be assigned to a member as well as to a conversation. The assignment wakes the conversation that runs
 for that member in the current goal, and the member starts it by moving it into progress. A member who joins
@@ -34,7 +44,7 @@ A new agent member, and one whose machine or model changed, first passes a short
 conversation (or, for a remote agent, a message that wakes it on its own machine) that reads the project's
 handbook and reports the release it read through the plugin's `team_trial_done` tool. Until then it is woken
 for no work and cannot start any, and a goal cannot start with a lead that has not passed. A person can retry
-a failed trial run or skip it from the Teams page; when skipping is the right call is in the
+a failed trial run or skip it from the Members view; when skipping is the right call is in the
 [user guide](../../docs/user/teams.md#when-to-skip-a-trial-run). Trial runs have been verified in real sessions with Claude Code only, on this machine and
 on a remote seat; the release check was not exercised, and the other providers have not been verified. The
 provider-by-provider table is in the [team plugin](../../docs/internals/team-plugin.md#trial-run) page.
@@ -42,7 +52,7 @@ provider-by-provider table is in the [team plugin](../../docs/internals/team-plu
 Starting a goal also puts the goal on the board as a work item assigned to the lead, recorded
 with this plugin as its author. The lead does no item itself, merging and pushing included; when
 everything the goal waits on is finished, it checks the results and marks the goal item done,
-and the goal bar shows that item's state.
+and the team's Board view shows that item's state.
 
 Member conversations start without messages; each gets its first one when work is assigned to its member.
 The project board shows up to 500 work items,
@@ -50,13 +60,13 @@ supports creation and assignment to the project's members, and moves cards betwe
 by dragging or using the card menu.
 Open a card's details to read its description, follow dependencies, reply to comments, and see who changed it.
 It does not provide sorting or filters.
-Mobile does not render the project workbench seat.
+On mobile the team page shows one view at a time.
 The plugin declares `work.read`, `members.read`, `work.writeAsPerson`, `communication.read` (to show
-people's names in history), the `project.workbench.tab` UI seat, and
+people's names in history), the `team.view` UI seat, and
 command dispatch permission for creating conversations, starting the lead's first turn, creating or
 updating work items, posting comments, adding, changing, removing and restoring project members, and
 archiving and stopping the trial-run conversations it opened itself.
-Work items, comments and members you change in the tab are recorded as yours, with this plugin shown as
+Work items, comments and members you change in the views are recorded as yours, with this plugin shown as
 the source.
 
 Implementation and command shapes: [team plugin](../../docs/internals/team-plugin.md).
@@ -68,7 +78,7 @@ and `test` scripts. Focused tests from the repository root:
 
 ```sh
 vp test run plugins/team/src/domain/roster.test.ts plugins/team/src/commands.test.ts plugins/team/src/board.test.ts plugins/team/src/detail.test.ts
-vp test run plugins/team/src/ui/TeamTab.test.tsx plugins/team/src/ui/GoalBar.test.tsx plugins/team/src/ui/Board.test.tsx plugins/team/src/ui/ItemDetail.test.tsx
+vp test run plugins/team/src/ui/BoardView.test.tsx plugins/team/src/ui/MembersView.test.tsx plugins/team/src/ui/HandbookView.test.tsx plugins/team/src/ui/Board.test.tsx plugins/team/src/ui/ItemDetail.test.tsx
 ```
 
 ## License