fix(db): resolve V44 migration collision before identity rollout

[XiaoSeS]

Context

PR #561 reserves Flyway V44 for the compliance metadata index, while the unified identity changes currently on big-main also start at V44 and continue through V47. A database that has already applied #561 V44 cannot start the big-main image because Flyway resolves a different V44 checksum.

This is an upgrade blocker for the identity rollout. Flyway repair is not an acceptable fix because the two V44 migrations create different database objects.

Related: #561, #640, #646, #649, #650, #651.

Scope

• retain the V44 compliance index migration unchanged as a compatibility reservation, without importing the rest of feat(compliance): add compliance version mapping and audit snapshots #561
• renumber the unreleased unified identity migrations from V44-V47 to V45-V48
• update Flyway targets, PostgreSQL contract tests, migration guardrails, scripts, and documentation
• preserve validation for both a fresh V43 database and a database that already contains the reserved V44 migration
• validate the final big-main image against a real PostgreSQL 16 upgrade path

Acceptance

• a V43 database migrates through the reserved V44 and identity V45-V48 successfully
• a database with the exact feat(compliance): add compliance version mapping and audit snapshots #561 V44 checksum validates and migrates to V48 without Flyway repair
• identity Binding V2 and profile/provisioning PostgreSQL suites pass
• full backend and GitHub CI gates pass
• the exact big-main merge image starts successfully in the shared test runtime
• main is not modified as part of test integration

Non-goals

• merge or otherwise adopt the remaining feat(compliance): add compliance version mapping and audit snapshots #561 feature implementation
• weaken Flyway validation or ignore missing migrations
• rewrite already published main history

[github-actions]

Issue Triage

• Route: triage/needs-info
• Priority: priority/p1 (3.7/5)
• Effort: effort/s (2/5)
• Confidence: 2/5
• Risk: high
• Analysis Mode: rules-only

Why

• Touches core SkillHub workflows (publish).
• Contains urgency signals (blocker, cannot).
• Text suggests a bounded change (text, documentation).

High-Risk Signals

• Mentions sensitive areas (migration).

Next Action

• Wait for more detail, then rerun triage after the author edits the issue or comments /retriage. Missing: .

---

问题分流结果

• 路由: triage/needs-info
• 优先级: priority/p1 (3.7/5)
• 修复投入: effort/s (2/5)
• 信息完整度: 2/5
• 风险: 高
• 分析模式: rules-only

原因

• 涉及 SkillHub 核心流程（publish）
• 包含紧急信号（blocker, cannot）
• 文本显示改动范围较可控（text, documentation）

高风险信号

• 提到敏感区域（migration）

下一步

• 等待补充更多信息；作者更新 issue 或评论 /retriage 后重新分流

[XiaoSeS]

修复 PR #653 已通过完整 CI 和共享测试环境验证，并合入 big-main（merge commit 4d462b3f），尚未进入 main。

验证确认：既有 #561 V44 checksum 保持不变，V45–V48 顺序迁移成功；应用健康，核心记录数与 Redis 数据保持。该 Issue 暂时保留，待统一提升到 main 后关闭。

[XiaoSeS]

Consolidating the unified identity work back into the parent tracking issue #628 and design PR #630 per maintainer direction. Closing this split delivery item so follow-up discussion and acceptance stay in one place.