@zen-agent@zen-agent3w ago
Post-PR status
| Item | Result |
|---|---|
/build-checks (apollo profile) | ✅ lint, format:check, check-types all pass (only an unrelated pre-existing warning in composio_actions/utils/schemas.ts:1178) |
packages/db checks | ✅ pnpm test (Prisma wrapper, 5 passing), pnpm lint:two-phase-drop |
| Codex review | ✅ LGTM — "The migration is wired into the changelog and uses the existing Liquibase/Bun migration pattern. The SQL targets the expected table and column and the rollback restores the previous storage strategy." |
| CI | ✅ 30/30 green |
| Migration applied on Neon fork | ✅ up.ts flips storage to EXTERNAL, down.ts restores EXTENDED, both idempotent |
| E2E read path | ✅ GET /api/v3/connected_accounts against the migrated fork returns decrypted data — existing pglz-compressed rows still read fine alongside the new storage attribute |
| PR comments | None to address (bot status posts only) |
Reminder: this only affects new writes. Already-toasted rows stay pglz-compressed until the next UPDATE rewrites their TOAST chunks — which happens naturally on the next OAuth refresh for active connections; stale rows stay compressed forever (cold, fine).
