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

..

migrate

feat(server): add readiness health endpoints (#1605)

2026-04-24 13:50:24 +08:00

multica

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

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

server

fix(server): persist ModelListStore across replicas via Redis (#2022)

2026-05-03 11:13:34 +08:00