Bohan Jiang 72d5135bf0 fix(quick-create): subscribe requester to issues created via quick-create (#1924) ...

The agent runs the daemon CLI, so issue.creator_type is `agent` and the
issue:created event listener only auto-subscribes the agent — not the
human requester. Result: the requester gets a single completion inbox
item but never sees follow-up comments or updates on their own issue.

Subscribe the requester (reason=`creator`, the only matching value
allowed by issue_subscriber's CHECK constraint without a migration)
inside notifyQuickCreateCompleted, after the issue lookup succeeds and
before the inbox write. Best-effort: log on failure, don't block the
inbox. On success, publish subscriber:added so the UI stays in sync
with manual subscribe and the listener-driven path.

Adds two integration tests in cmd/server: success path subscribes the
requester; failure path (agent finished without creating an issue)
leaves no subscriber rows.

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

2026-04-30 13:19:34 +08:00

..

migrate

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

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

multica

fix(comments): unescape \n in agent task-completion output (#1850)

2026-04-29 17:05:17 +08:00

server

fix(quick-create): subscribe requester to issues created via quick-create (#1924)

2026-04-30 13:19:34 +08:00