Skip to content

fix: normalize legacy connection keys (AXI-134) - #76

Merged
Codename-11 merged 1 commit into
mainfrom
codex/axi-134-migrate-legacy-connections
Jul 20, 2026
Merged

Codename-11 merged 1 commit into
mainfrom
codex/axi-134-migrate-legacy-connections

Conversation

@Codename-11

@Codename-11 Codename-11 commented Jul 20, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • atomically normalize all historical AgentConnection ac_* ids to CUID-shaped primary keys while cascading relational references
  • preserve immutable legacyId aliases and rewrite typed conflict payloads plus dedupe keys
  • accept connection ids as opaque bounded identifiers during rolling deployment
  • keep delivery ownership fail-closed and isolate decision-materialization failures to one candidate run

Root cause

AXI-129's Victor mention runs reached the managed-runtime ownership gate, but the runtime connection still used its historical ac_* key. The typed DELIVERY_CONNECTION_CONFLICT payload required a Prisma CUID, so validation rolled back parking and failed the recurring dispatch sweep until the watchdog stalled the run.

Validation

  • rollbacked local SQL migration fixture across connection aliases, runs, run events, Delivery sessions, participants, action payloads, and dedupe keys
  • pnpm prisma validate
  • pnpm lint (pre-existing warnings only)
  • pnpm typecheck
  • focused Vitest: 34/34
  • full serial Vitest: 1,480 passed, 12 skipped

Forge issue: AXI-134

@Codename-11
Codename-11 merged commit fa43bbb into main Jul 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant