Bohan-J 44a82fda4d fix(runtime): return 500, not a 409 echo, when the update store fails ...

InitiateUpdate answered every UpdateStore.Create failure with a 409 carrying
err.Error(). The in-memory store only ever returns errUpdateInProgress, so this
looked safe — but the Redis store also wraps infrastructure failures as
"reserve active update: <dial error>" and "persist update request: <error>".

Surfacing 409 bodies in the CLI turns that into a user-visible leak of internal
addresses, and labels an outage as a conflict the caller could fix by retrying.
Classify instead: errUpdateInProgress keeps its 409 and its actionable message,
everything else is logged and answered with a 500 and fixed copy.

Also pins the prose-over-machine-code preference for validation bodies, which
the shared extractor applies to 400/422 as well as 409. Only the issue-table
endpoints are shaped that way and none is reachable from the CLI today, but the
change is intentional and should fail loudly if reverted.

MUL-5619

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

2026-08-03 13:29:06 +08:00

..

cmd

fix(subscribers): notify the human an agent files sub-issues for (MUL-5483) (#6209)

2026-07-31 16:52:17 +08:00

internal

fix(runtime): return 500, not a 409 echo, when the update store fails

2026-08-03 13:29:06 +08:00

migrations

fix(subscribers): notify the human an agent files sub-issues for (MUL-5483) (#6209)

2026-07-31 16:52:17 +08:00

pkg

fix(llm): make quick actions GPT-5.6 compatible (MUL-5573) (#6243)

2026-07-31 17:44:37 +08:00

go.mod

…

go.sum

…

sqlc.yaml

…