What’s new

What's new in 0.5.5

0.5.5 moves the team's definition out of the project and into the registry (~/.config/team/team-config/). Run team migrate once in each project: it imports .agents/team.yaml, verifies the import, and moves the file to the Trash (--keep-file keeps it). From then on, team config get|set|unset|edit edits the team. Approvals are signed over one canonical team record, so they stay in force across the move. See UPGRADE-0.5.5.md.

A team that names an entity and no session: now runs in the session <entity>-<project>; team check names the move, and the team is approved again once.

Clients gain the observer, operator, manager and developer grant bundles, replies through team reply and team messages --client, and a pane guard that refuses client commands inside a team pane. A seat stopped at a usage wall reads as blocked: quota, and team pause can pause one seat.

Downgrading to 0.5.3 after a team has been migrated is NOT supported: 0.5.3 reads only the file. Keep the file with team migrate --keep-file if you may need to go back.

The full list is in CHANGELOG.md.

Every change, release by release, is in the changelog.