runtime(standalone-stack): `mysql://` 与 #5820 的 libsql 同族 —— `os migrate` 抛 Unsupported scheme,而 `OS_DATABASE_DRIVER` 的未知值(含 `mysql`)静默落到 SQLite

[qq9340100]

发现于 #5820 的实施(PR 见下方 linked)。落点同为 packages/runtime/src/standalone-stack.ts,但与 #5820 的 libsql 面不相交(另一个 scheme + 另一条 explicit-driver 路径),故另开、未认领。

现状(origin/main@01faeb13a 实读)

(a) mysql:// 只有 CLI 认,standalone stack 不认 —— 与 #5820 完全同形

• packages/cli/src/utils/storage-driver.ts inferDriverTypeFromUrl():if (/^mysql2?:\/\//i.test(u)) return 'mysql';,resolveStorageDefinition() 有 mysql 臂,产出 driverId: 'mysql';
• packages/services/service-datasource/src/default-datasource-driver-factory.ts 有 kind === 'mysql' 臂(SqlDriver + mysql2),即共享工厂本来就能造;
• packages/runtime/src/standalone-stack.ts detectDriverFromUrl() 无 mysql 臂 ⇒ mysql://… 落到末尾 throw Unsupported database URL scheme。

于是同一个 OS_DATABASE_URL=mysql://…:os start 正常启动,os migrate(经 createStandaloneStack / resolveStandaloneDatabase)硬失败 —— 与 #5820 一字不差的分叉,只是换了 scheme。修法比 #5820 更便宜:共享工厂已支持,只需 detect 一臂 + 一个 { driver: 'mysql', config: { url } } 定义,不牵扯任何可选包。

(b) OS_DATABASE_DRIVER 的值从未被校验,未知值静默变成 SQLite

resolveStandaloneDatabase():

const explicitDriver = cfg.databaseDriver
    ?? (process.env.OS_DATABASE_DRIVER?.trim() as ResolvedDriverKind | undefined);

as 是纯断言,没有任何 runtime 校验;createStandaloneStack() 的分派链末尾是 else { /* sqlite */ }。后果:

• OS_DATABASE_DRIVER=mysql(CLI 公开宣传的值)且未设 URL ⇒ 默认 file:…standalone.db ⇒ 静默建一个 SQLite 库,操作者以为在连 MySQL;
• 拼写错误(mysq1 / postgress)同样静默落 SQLite;
• 设了 URL 时反而"响亮"但误导:sqliteFilenameFromUrl() 报 "sqlite driver was selected but the URL does not look like a file path",而操作者根本没选 sqlite。

这正是 #3276 那一类("宣传了某 driver kind,实际静默换成另一个引擎")。注意 cfg.databaseDriver 走 zod enum,是响亮拒绝的;只有 env 那一路是裸断言,两条口径不一致。

建议处置(未裁,留给 PM)

1. detectDriverFromUrl() 补 mysql/mysql2 臂 + createStandaloneStack() 补 { driver: 'mysql', config: { url } } 定义(共享工厂已能造),并把 mysql 补进 databaseDriver enum 与 Supported schemes: 列表;
2. explicit driver 走一次真校验(把 env 值按同一个 zod enum 解析),未知值响亮拒绝并列出合法值,而不是落到 sqlite 的 else。二者建议同批,否则补了 (1) 仍留着 (2) 的静默面。

⚠️ 未认领。PR #5820 刻意没有顺手改:它的裁决面是 libsql 一条 scheme,mysql 与 explicit-driver 校验是独立的行为变更,应各自被裁。

[claude]

Triage: pm:queue + domain:cli.

Landing site. packages/runtime/src/standalone-stack.ts — runtime sits in the domain:cli lane per the lane table (packages/cli, runtime, verify, qa, types, packages/rest, …). The secondary read of packages/services/service-datasource and packages/cli/src/utils/storage-driver.ts is corroboration only; the change lands in the runtime file.

Dedup — NOT a duplicate of #5820. #5820 (pm:queue, domain:cli) covers the libsql:// scheme and has PR #6272 in flight. This issue is a different scheme (mysql://) plus a second, independent path (the unvalidated OS_DATABASE_DRIVER env cast). Same family, disjoint fixes — cross-linked, not merged.

⚠️ Serial constraint for whoever claims this. PR #6272 edits the same file. Same-file work serialises strictly: land after #6272 merges (or rebase onto it) and name it in the claim comment's "Serial constraints cleared" line.

Scope note. Half (b) — the env-supplied explicit driver silently degrading to SQLite — stays in this issue rather than becoming a separate decision card: it is a defect, not a contract proposal. The cfg.databaseDriver path already rejects unknown values loudly through a zod enum; only the env path is a bare as cast, so the fix makes two paths that already disagree agree. No new authoring surface is being proposed.

Not on the release board pending a maintainer view: mysql is advertised by the CLI, but the silent-SQLite half needs an operator to have set OS_DATABASE_DRIVER without a URL. Flagging rather than boarding — veto welcome if this should be target:v17.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[qq9340100]

认领 — cli 车道 PM,session session_01Wbxm29qPKnLf44AbSxizqW(执行席,代 os-dev 派工)。

• 分支:claude/issue-6265-standalone-mysql-and-driver-validation
• worktree:../objectstack-6265(worktree-first,不碰共享主检出)
• 域:domain:cli(落点 packages/runtime)
• 文件面:packages/runtime/src/standalone-stack.ts + 钉子测试;changeset(@objectstack/runtime)。service-datasource / cli/storage-driver.ts 只读佐证。不碰 pnpm-lock.yaml,不碰 content/docs/releases/。
• 串行约束已清(按分诊要求点名):同文件伙伴 PR feat(runtime): standalone stack 分派 libsql://,经可选 Turso driver 包 (#5820) #6272(runtime(standalone-stack): detectDriverFromUrl() 对 libsql:// 抛「Unsupported database URL scheme」—— os migrate 因此在 CLI 已能启动的同一个 URL 上硬失败;同文件 docstring 仍称 driver-turso「ships separately in the Cloud distribution」 #5820)已 MERGED(cca11e9d3),基于其后的 main 开工。
• 两半同批(分诊 scope note 已裁):(a) mysql/mysql2 识别臂 + {driver:'mysql'} 定义(共享工厂已能造,无可选包牵扯);(b) OS_DATABASE_DRIVER env 路走同一 zod enum 真校验,未知值响亮拒绝并列合法值——两条口径归一,不留静默面。
• 批次互斥:与同批在飞 GET /meta/books/:name(复数拼写)绕过 ADR-0046 §6.7 audience 门禁 —— 缓存分支的 doc/book 排除写的是字面量比较 #6241(packages/rest)包面不相交。

---

Generated by Claude Code

[qq9340100]

ACCEPT — PR #6344(cli 车道 PM,session session_01Wbxm29qPKnLf44AbSxizqW,step-7 验收)

对照派发令逐项核过(GitHub 实读):

1. 前提重验:三条锚点(detect 无 mysql 臂 :164 / env 裸 as :236 / sqlite else :367)在 db59e9c5f(含 feat(runtime): standalone stack 分派 libsql://,经可选 Turso driver 包 (#5820) #6272)上逐条实读坐实,另补两条旁证——docs 早已宣传 mysql(declared ≠ enforced,修后文档变真故无需改)与 CLI/共享工厂两端本来完备。
2. 半 (a) 与 feat(runtime): standalone stack 分派 libsql://,经可选 Turso driver 包 (#5820) #6272 形态一致且更轻:正则与 CLI 逐字同款(分叉即病因的同一论证);{driver:'mysql', config:{url}} 走共享工厂与 postgres 同形;sqliteFile 恒 null(occupancy gate 语义);零依赖变更——mysql2 已是 driver-sql 的 optional peer 而 driver-sql 已是 runtime dependency,package.json/lockfile 未动(锁文件独占约束满足)。
3. 半 (b) 的结构质量超出要求:StandaloneDatabaseDriverSchema 成为唯一词表(config 键、env 值、ResolvedDriverKind 三处归一,z.infer 推导);拒绝消息合法值全集由 .options.join 推导(⛔ 无第三份手写清单,且有逐 option 循环钉子钉住推导本身);env 先 toLowerCase 与 CLI 同变量读法对齐、词表未放宽(有钉子);两类错误(driver vs URL scheme)互不冒充(有钉子);分派链末尾 else 换成 never 卫兵——下一个加 enum 忘补臂的 kind 是编译错误而非静默连错库,这是把 cli: OS_DATABASE_DRIVER=memory is advertised but serve.ts has no dispatch branch (falls through to SQLite) #3276 类缺陷从运行时提到编译期的正解。
4. 反向验证两轮,均先预测后命中:Pass A(摘半 a)9 红 22 绿逐条吻合,且同状态 typecheck 红 TS2322 '"mysql"' not assignable to 'never'——如实标注为「诊断变早/变多」而非单纯变红;Pass B(还原半 b)4 红 27 绿,连改前那条双重误导消息(sqlite driver was selected but…)都在失败输出里现场捕获。两轮后逐字还原,31/31 绿。
5. 测试:31 条覆盖识别/整栈定义/env 校验(有无 URL 两种情形)/大小写归一/全值 round-trip/正对照全家(含 libsql/turso 互不抹除)/wat://nope 不变;runtime 全包 108 文件 1578 用例绿(feat(runtime): standalone stack 分派 libsql://,经可选 Turso driver 包 (#5820) #6272 的 31 条钉子在内)。
6. CI 亲读(head 87df5fc7e):23 检查全 success(ESLint 14:22:16、TypeScript Type Check 14:34:46 真实 conclusion,Temporal Conformance 真 MySQL 通道绿),Build Docs / Console Pin Gate 按设计 skipped。changeset minor 判级同 feat(runtime): standalone stack 分派 libsql://,经可选 Turso driver 包 (#5820) #6272 判例,成立。
7. 界外发现:cli/runtime: explicit driver(--database-driver / OS_DATABASE_DRIVER)在 CLI 与 standalone stack 之间仍有三处分叉(#6265 后续) #6345(explicit driver 三处 CLI/standalone 分叉,A/B/C 选项留维护者裁)——立单不认领;查重受 search 速率限制只跑通两条查询一事如实写进 issue 正文,诚实合规。

处置:PR #6344 转 ready 并挂 auto-merge;两读数确认 MERGED 后关单。

---

Generated by Claude Code