Team-aware relay routing release: instant tracker events now carry the workspace team, so several boards of the same tracker can each hold their own relay registration and dispatch only to that exact team, and the shared workspace .env can namespace credentials per team.
Added
- Team-scoped tracker relay registrations (DEV-114):
devintern worker connect <tracker> --team <name>registers a board under its stable team name, and each tracker/team pair gets its own idempotent ingest URL. Relayedtask.changedenvelopes now carry the team and dispatch only to that exact workspace team, so two boards with overlapping task keys never collide. When several teams share a tracker,--teamselects one (auto-selected when only that team uses the tracker); unknown or removed teams are logged, skipped, and acknowledged so they cannot stall the stream, while legacy team-less buffered envelopes keep the source-only path when the tracker maps to one unambiguous source. Team-aware routing requires the matching relay control plane: a new CLI against an old relay fails team-scoped registration with an actionable upgrade message, and old team-less registrations remain supported - Per-team credentials in the shared workspace
.env: variables can be namespaced as<TRACKER>_<TEAM>_<SETTING>(for exampleJIRA_PLATFORM_URL,JIRA_PLATFORM_EMAIL,JIRA_PLATFORM_API_TOKEN), projected onto the tracker’s normal variable names only for that team;JIRA_<TEAM>_URLalso maps toJIRA_BASE_URL. Team names are uppercased with punctuation replaced by_, and a team’senv_fileand inline[teams.env]still take precedence