Jiang Bohan bd00736c37 fix(cli): detect assignee flag presence via Changed, not value-emptiness ...

`pickAssigneeFromFlags` previously branched on `flag value != ""`, so
explicitly passing an empty UUID silently routed through the "no flag set"
path:

  multica issue list --assignee-id ""        # listed every issue
  multica issue create --assignee-id ""      # created an unassigned issue
  multica issue subscriber add --user-id ""  # subscribed the caller

This is exactly the failure mode the strict-UUID flag was added to prevent —
a script interpolating `--assignee-id "$MAYBE_UUID"` against a missing env
var should fail loudly, not silently degrade to a different operation.

Switch the picker (and the assign-command top-level guard) to use
`Flags().Changed`, so an explicit empty value reaches `resolveAssigneeByID`
/ `resolveAssignee` and surfaces a clear "expected a canonical UUID" /
"no member or agent found matching" error.

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

2026-05-06 13:02:52 +08:00

..

cmd

fix(cli): detect assignee flag presence via Changed, not value-emptiness

2026-05-06 13:02:52 +08:00

internal

feat(cli): add --assignee-id / --to-id / --user-id for unambiguous targeting

2026-05-06 12:54:17 +08:00

migrations

…

pkg

refactor(quick-create): exempt git-describe daemons from CLI gate (#2108)

2026-05-06 09:00:11 +08:00

go.mod

…

go.sum

…

sqlc.yaml

…