J 80ffe259cf docs(channel): fix migration 124 rollout order and document self-host cutover ...

The previous ROLLOUT note shipped the new (channel_*) build before
running migration 124, so the channel_*-backed HTTP paths (installation
list/install/revoke, chat-session delete, member revoke) would 500 in
the window between new-pod boot and the deferred migration. Restate the
runbook around two explicit invariants — channel_* must exist before the
new build serves those paths, and the old/new hubs must never overlap —
and order the steps so channel_* is created first (park old hub -> snapshot
-> deploy parked new build -> unpark). Document that default self-host
(entrypoint migrate + single-replica Recreate) satisfies both invariants
automatically and needs no manual steps; only prd / multi-replica rolling
self-host needs the switch procedure. Clarify in main.go that the
hub-park switch is generation-agnostic (parks whichever hub the build
carries), which is what enables the preparatory release.

Refs MUL-3515

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

2026-06-23 22:00:20 +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(cli): guide remote setup callbacks (#4360)

2026-06-22 00:06:14 +08:00

server

docs(channel): fix migration 124 rollout order and document self-host cutover

2026-06-23 22:00:20 +08:00