multica

mirror of https://github.com/multica-ai/multica.git synced 2026-07-29 22:54:38 +02:00

Files

Jiang Bohan 8f6c5d2ac9 fix(cli): gate squad assignee resolution behind an allowed-kinds set (MUL-2165)

The earlier MUL-2165 fix taught resolveAssignee / resolveAssigneeByID to also
return (squad, ...), but those helpers are shared. Project lead and issue
subscriber callers were still using them, and their target schemas reject
squads — project.lead_type has a DB CHECK constraint
(server/migrations/034_projects.up.sql:10) and the subscriber handler's
isWorkspaceEntity switch only knows member/agent
(server/internal/handler/handler.go:414). So
`multica project create --lead "<SquadName>"` and
`multica issue subscriber add --user "<SquadName>"` would resolve to
(squad, ...) and surface as a 500/403 server-side instead of a clean
CLI-side resolution error.

Thread an assigneeKinds set through the resolver and the pickAssigneeFromFlags
helper. Issue create/update/assign/list pass `issueAssigneeKinds` (all three);
project lead and subscriber pass `memberOrAgentKinds`. The squads fetch is
skipped entirely when not allowed, and the not-found / no-match error wording
adapts to the allowed kinds so it never mentions a type the caller cannot use.

Co-authored-by: multica-agent <github@multica.ai>

2026-05-13 22:30:32 +08:00

cmd

fix(cli): gate squad assignee resolution behind an allowed-kinds set (MUL-2165)

2026-05-13 22:30:32 +08:00

internal

fix(cli): resolve squad assignees in issue create/update/assign (MUL-2165)

2026-05-13 22:14:33 +08:00

migrations

feat: implement Squad feature MVP (#2505 )

2026-05-13 18:46:20 +08:00

pkg

feat: implement Squad feature MVP (#2505 )