From d98498b70540eb5ca4c3b858cf534b1739af68d9 Mon Sep 17 00:00:00 2001 From: 1445043649 <> Date: Tue, 12 May 2026 22:07:34 +0800 Subject: [PATCH] =?UTF-8?q?docs(impl):=20T4.1=20=E2=80=94=20confirm=20alem?= =?UTF-8?q?bic=20baseline=20is=20not=20needed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit alembic heads/history both empty, versions/ dir empty: 0001 can be the first revision with down_revision=None. alembic_version table will be auto-created on first upgrade head. doctor.py needs no new check. Also records T4 preparation grep findings on _ensure_admin_user current behavior (open issue #3 resolved). Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/multi-tenant-redesign/03-impl/STATUS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/multi-tenant-redesign/03-impl/STATUS.md b/docs/multi-tenant-redesign/03-impl/STATUS.md index b30a5fef..359ba6b7 100644 --- a/docs/multi-tenant-redesign/03-impl/STATUS.md +++ b/docs/multi-tenant-redesign/03-impl/STATUS.md @@ -49,8 +49,8 @@ PR1 + PR2 + PR3 已 merge + **live 验证通过**（RDS 上 11 张表 = DeerFlow 详见 plan [关键开放问题](../../superpowers/plans/2026-05-10-stage-0-multi-tenant-foundation.md#关键开放问题执行-session-第一件事处理)： -1. **PR4 起会真正用到 alembic**——首个 revision 之前要不要加 baseline？plan agent 建议 0001 直接当首个 revision，`down_revision = None`。验证：跑 `cd backend && PYTHONPATH=. uv run alembic current` 看默认行为 -2. **`_ensure_admin_user(app)` 现状的孤立 thread 迁移逻辑**——PR4 / PR5 假设它能扩；先 grep `app.py` 看现状 +1. ~~**PR4 起会真正用到 alembic**——首个 revision 之前要不要加 baseline？~~ **✅ T4.1 (2026-05-12) 已验证**：`versions/` 空 + `alembic heads`/`history` 都空输出 → 0001 直接当首个 revision、`down_revision = None`，**不需要 baseline**。`alembic_version` 表首次 `upgrade head` 时自动建；现有 create_all() 已建好的 schema 不冲突（0001 只 ADD COLUMN）。`doctor.py` 不需要加自动检测 +2. ~~**`_ensure_admin_user(app)` 现状的孤立 thread 迁移逻辑**~~ **✅ T4 准备阶段 (2026-05-12) 已 grep**：`app.py:52` 当前只做两件事——(a) admin_count==0 时仅日志提示去 `/setup`，(b) admin 已存在时跑 LangGraph store 孤立 thread 迁移。**不自建 admin**。所以 T4.13 真实任务范围 = "admin 已存在但无 workspace"的 idempotent backfill 分支（plan 顶部"风险与缓解"段写的才对，task 措辞"建完 admin 顺带建"是误导，实际归 T4.8） 3. **PG 大版本对齐**（同上"用户必须跟进"#2） ## 下一步建议