J (Multica agent) 7493cb5e27 fix(comments): clarify 409 when a comment-triggered task posts a top-level comment (MUL-4417) ...

A comment-triggered task that posted a parentless top-level comment on its
own issue got a 409 whose message named the required parent id but never
said top-level comments are disallowed. Agents misread it as the issue being
locked and deleted good replies trying to reset. Keep the guard (agents must
reply under their trigger comment), but make the error self-explanatory and
document the constraint in the CLI --parent help. Add handler-level tests
pinning the rejected top-level case and the allowed reply-under-trigger case.

Refs GH #5266.

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

2026-07-12 13:44:13 +08:00

..

backfill_codex_usage_cache

MUL-3264: add Codex usage cache backfill

2026-06-18 13:34:10 +08:00

backfill_task_usage_hourly

MUL-2488 feat(timezone): Scheduling / Viewing two-layer timezone architecture (#2968)

2026-05-21 15:33:47 +08:00

migrate

test(migrate): concurrent migration race test using real Postgres (MUL-2956) (#3712)

2026-06-08 13:33:16 +08:00

multica

fix(comments): clarify 409 when a comment-triggered task posts a top-level comment (MUL-4417)

2026-07-12 13:44:13 +08:00

server

feat(labels): add scoped label management (#5279)

2026-07-12 03:46:08 +08:00