Files
multica/server
J 88bcbc9328 fix(agent): renumber Kiro credit migrations to 137/138 after rebase
Rebasing onto main pulled in migration 136_runtime_profile_add_traecli
(#4972), which collides with this branch's 136_task_usage_credits. The
migration loader keys on the full basename so both would apply, but a
duplicate 136 prefix is confusing and out of convention.

Bump the two credit migrations above main's highest number:
- 136_task_usage_credits        -> 137_task_usage_credits
- 137_task_usage_hourly_credits -> 138_task_usage_hourly_credits

Lexical apply order is preserved (137 creates task_usage.credits before
138 backfills task_usage_hourly), and neither had been deployed, so no
recorded schema_migrations version changes. Also updates every code and
comment reference (daemon.go, dashboard.go, task_usage.sql[.go],
agent.ts, runtimes/utils.ts, issue-detail.tsx) and renames the
regression test to TestKiroCreditsMigration138EnqueuesDirtyKeys. The
136-to-traecli reference in agent.go is intentionally left at 136.

Refs: MUL-4091, GH #4943.
Co-authored-by: multica-agent <github@multica.ai>
2026-07-06 18:18:17 +08:00
..