Follow-up: unify persistence model; reconcile platform version

[jet-pang]

Deferred from the review fix (#55, merged) — left as // TODO(#55).

• Dual blocking + reactive persistence — the service runs both Hibernate ORM/JDBC and reactive Panache/pg-client. Audit every @Transactional method returning Uni (transaction scope closes before the async continuation), ensure blocking Panache is never reachable from event-loop threads, and pick one persistence model per subsystem. The two-pool 100-connection juggling is a symptom.
• Platform version reconcile — consumes aster-lang-platform:1.0.3 while the ecosystem release of record is 1.0.2; also Quarkus plugin 3.36.1 vs BOM 3.36.2. Reconcile (see aster-lang-platform#6).

Carved out of #55.

[jet-pang]

进度更新（2026-06-28）

✅ Platform version reconcile — 已解决

• 平台 catalog drift 已通过 ADR 0023（多模块发布治理）统一：settings.gradle 现 pin cloud.aster-lang:aster-lang-platform:1.0.7，消费生态版本 1.0.5，由 release-plan.json 单一事实源 + 各仓 drift gate 强制对齐。issue 描述的「消费 1.0.3 而 release of record 是 1.0.2」漂移已不复存在。
• Quarkus plugin vs BOM 也已对齐：build.gradle 插件 io.quarkus 3.36.2 == quarkus-bom:3.36.2，并加了锁定注释 // Quarkus plugin version MUST match the quarkus-bom version below (#57)。

⏳ Dual blocking + reactive persistence — 仍未做（保持 open）
架构级审计，需逐个核查 @Transactional 返回 Uni 的方法（事务作用域在异步续体前关闭）+ 确保阻塞 Panache 不可从 event-loop 线程触达 + 每子系统选定单一持久化模型。双池 100 连接是症状。此项不在本轮范围。

已勾选 platform-reconcile 子项；本 issue 保持 open 以跟踪 dual-persistence。