[PM seat] domain:drivers — 🟢 os-zhuang

[claude]

本贴是 domain:drivers 座位的唯一权威登记。 座位贴协议(维护者 2026-08-06 批准,自 #4604 单正文座位表迁移而来):索引 = label:pm:seat,总入口 #4604(指针页)。

单写手规则:只有在任座位 PM 编辑本贴正文;接管/移交 = 改正文 + 一条审计评论(评论只作交接存档,不承载状态)。空缺争用时:动手前重拉正文、审计评论时间戳先到先得、写后回读。活性判定(惰性,无心跳,仅接管冲突时评估):Routine 座位查调度器(last_fired/next_run),会话座位查最近产出评论时间戳,>24h 无产出即可回收(改正文 + 审计评论)。

范围

packages/drivers/driver-* (driver-memory / driver-mongodb / driver-sql / driver-sqlite-wasm / driver-turso)

Scope path refreshed 2026-08-08 by the incoming PM: the driver packages live under packages/drivers/ on today's main (the previous packages/plugins/driver-* spelling predated the move), and driver-turso is listed explicitly — it has been this lane's work since the split.

当前 PM(会话或 Routine ID)

GitHub os-zhuang · session session_01Hg9Pkg5nDedCRihRsdeCdX · took over 2026-08-08 (maintainer-initiated /pm-dispatch drivers)

说明

In office since 2026-08-08; handover audit in the comments. Predecessor session session_01WyvqvKMG6asi9aXjKE6xtx (registered 2026-08-05) posted its final ACCEPTs at 2026-08-08 06:28Z (#5702 → PR #6549, #6320 → PR #6517) and left zero in-flight dispatches — a clean handover point.

常设分诊指令(锚点 #5499,维护者 2026-08-05):driver-memory / driver-mongodb 族投入冻结——新单照常打 domain:drivers,但挂 pm:on-hold 引用 #5499,不入队;driver-sql 不受影响(formula 属 engine-core);影响 CI 判绿正确性的按 restore-invariant 例外升级

Ledger (wave closed 2026-08-10 ~12:1xZ — in-flight ZERO)

Tenure total: 15 PRs MERGED (12 on 08-09; 3 on 08-10: #7263→PR #7334 db12b888f, #7332→PR #7394 ef678d0f1, #7398→PR #7415 465a0fa0b). All dev cloud cards archived; zero orphan subscriptions; all issues closed/completed.

Also closed 08-10 without PRs, deliberately: #6522 accepted as measurement outcome (0 repro / 67 runs; back to finding, restart conditions armed) — the correct no-PR shape for a flake-measurement card.

Standing authorizations consumed this wave (all in session transcript + issue comments): 05:4xZ「drivers 任务全部可派,v17 只是优先」(widening — does NOT lift #5499); 09:4xZ「7498 插队」read as #7398 (typo; reading stated openly in claim comment 5238539590 — stands unless corrected).

热文件串行队 — packages/drivers/driver-sql/src/sql-driver.ts

Cross-round standing fact per the seat-card protocol; three cards landed in it on 08-10, zero collisions, region column is what made overlap-free dispatch possible:

order	card	region (content anchors, lines drift)	state
1	#7263	autonumber format sites (resolveAutonumberFormat substitution, 2 sites)	MERGED db12b888f
2	#7332	index introspection (introspectIndexes / getExistingIndexNames)	MERGED ef678d0f1
3	#7398	filter lowering (applyFilters / applyFilterCondition funnel + JSON-column gate)	MERGED 465a0fa0b

Queue currently EMPTY. Any new card touching this file: declare its region in the claim comment and check this table first.

Queue state at wave close (re-verify before acting — snapshots expire)

• Dispatchable: NONE. ⛔ Do not manufacture work.
• Turso remote:带 id/conflictKeys 但没匹配上的 upsert 仍会静默写入 NULL 自增号(#6944 拒绝闸门覆盖不到的那条腿) #7099 — settled, NOT dispatchable: needs a maintainer ruling on TursoDriver remote 面根本不生成自增号:RemoteTransport.create 自建 INSERT,auto_number 只是个 TEXT 列 #6944 disposition A (appetite trade-off; premise verified 08-10, pin landed at turso-remote-autonumber-refusal.test.ts:311, comment 5237754309).
• [finding][drivers] The object-in-query sweep of #6231 was source-only — 10 more sites of the same shape live in driver test files #7177 — low value: 9/10 sites frozen driver-mongodb; the object-sweep shape hits the engine-unknown-option.test.ts:183 landmine — read it first if ever dispatched.
• ⛔ [drivers] driver-memory / driver-mongodb disagree with the SQL family on count_distinct — the two AGGREGATION_CASES cells #6409 left open #6814 / [finding][drivers] driver-mongodb cannot take a structured GroupByNode at all — the object stringifies into a "[object Object]" $group._id #6850 — frozen under [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 regardless of labels: their pm:queue came from an unexplained bulk flip (07:07:57–07:08:04Z, seven-second window, no comment), contradicting triage's 08-09 23:24Z written grade. Reported on [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 (comment 5237773754). Labels ≠ warrant in this lane until that is resolved.
• On-hold under [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 (maintainer 08-10 01:1xZ ruling, unchanged): driver-memory 完全没有行级租户隔离(#3724 的未修姊妹面):多租户下静默不隔离 #6915, driver-memory's analytics generateSql() renders the LIKE family with NO wildcards, so the echoed statement is an EQUALITY the pipeline never ran #7117, [drivers] driver-mongodb's local AggregationInput still declares distinct?: boolean after the spec key was retired (#6815) #7052, drivers(memory, mongodb): the $contains family still folds case — the last two backends left on the wrong side of #4706 Q2 = A #6682, driver-mongodb 带着 #5328 的同一条缝:形状错误的 $between / 非数组 $and、$or / 非对象 $not 全被静默吞掉,且它的算子拒收没有 ADR-0112 信封 #5346, driver-mongodb 是 { field: {} } 唯一还在作答的后端:#5240 拍板拒收、#5327 已闸四家,mongodb 仍译成「字段深等于空文档」 #5376, ADR-0053 D-E3：mongo 的遗留形态是永久态，但它既无 backfill 也无读修复——#4191 storage-form 轴最尖的一格无法闭合 #4220, drivers(sql): 共享 canonical 修复表达式把「裸数字文本」当儒略日读,backfill 会把这个误读写进盘里(观察项) #6009.

Findings filed this wave, awaiting triage (⛔ this seat does not self-grade them)

• driver-sql: introspectIndexes swallows every error and returns a partial index list, which the drift differ then reports as missing indexes #7332-derived, resolved same day (blind catch → landed).
• Cross-lane notes posted read-only: De-fallback the engine's autonumber render path — read the declared {0000} default instead of parsing the empty string (#6555 half 2/3) #7262 (engine autonumber half — blocker landed + empty-string coverage gap measured); driver-sql: a declared operator on a multiple: true (JSON array) column silently answers wrong — $in/$eq always zero rows, $nin returns the rows it was asked to EXCLUDE #7398's report recorded three ruling-shaped residues: ask-2 visibility trade-off, driver-memory has NO working membership spelling at all (frozen), three-way cross-driver $in-on-array divergence (Filter Protocol question).

Session-operational notes for a successor

• Wake mechanism for parked cloud devs (proven 3×): create_trigger + persistent_session_id + run_once_at ≥2 min resumes with transcript intact; create_session discards it. review_ready ≠ reported — check the ISSUE.
• Scheduler fires 3–8 min late; exactly one pending patrol tick (check list_triggers before arming — post-compaction duplicate incident 07:00Z).
• Benign queue-red signature today: all-TIMEOUT live-dialect failures inside a co-queued group after 1400+ green; red group build followed by merge is the success sequence.
• Notes-21 empty-field AM signature appeared 3× today; all three queued anyway — signature alone is not the stall.
• Devs falsified stated PM/card premises 9 times this tenure, correct every time — pre-priced dispatch facts are verify-don't-trust by construction.

---

迁移注记:以上「范围 / 当前 PM / 说明」自 #4604 座位表逐字迁移(2026-08-06,经办 PM 会话 session_01GcjbQLUQKysMU9uXB34iyv);迁移时刻起本贴即该座位唯一权威,#4604 原行不再维护。

[os-zhuang]

Seat takeover audit — 2026-08-08.

• Incoming PM: GitHub os-zhuang, session session_01Hg9Pkg5nDedCRihRsdeCdX, started by the maintainer via /pm-dispatch drivers (maintainer-initiated handover entrance).
• Predecessor: session session_01WyvqvKMG6asi9aXjKE6xtx (registered 2026-08-05). Its final output was the ACCEPT pair at 2026-08-08 06:28Z — drivers: $regex 响亮拒收 + $icontains 各后端实现(#4706 裁决 B 案 · 驱动半边) #5702 (PR feat(drivers,objectql): $regex 响亮拒收 + SQL 族 $icontains 实现(#4706 裁决 B 案 · 驱动半边) #6549, MERGED 06:43Z) and drivers: distinct 的第三参在 memory 与 sql 上语义不同 —— 把 sql 那面的写法交给 memory,静默返回未过滤全集(运行期实测) #6320 (PR refactor(driver-sql)!: distinct 的第三参收成裸 FilterCondition (#6320) #6517, MERGED 03:38Z). Ledger verified empty at takeover: zero domain:drivers + pm:dispatched open issues, zero open PRs touching packages/drivers/**.
• Body edits in the same stroke as this comment: title/assignee/当前 PM triple updated; scope path refreshed to packages/drivers/driver-* (the packages moved from packages/plugins/), driver-turso listed explicitly.
• Standing instructions carried over unchanged: [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 driver-memory / driver-mongodb investment freeze (triage routing note kept verbatim in the body).

Read-back verification of the body edit passed (entities and session IDs intact).

---

Generated by Claude Code

[os-zhuang]

Lane status 2026-08-09 09:0xZ — 11 merged today, and now zero dispatchable cards

Posting this as one consolidated read because the lane has stopped for reasons that live in three different threads, and each is a decision someone else owns.

Merged today (11), each through an independent step-7 gate

#6518 · #6402 · #6394 · #6577 · #6543 · #6409 · #6401 · #6792 (bee5ffe66) · #5495 (7d1ff752b) · #6754 (51f2bb8c3) · #6943 (45e711ad2)

All eleven dev cards archived; zero idle containers.

The board now: 14 open, 0 dispatchable

State	Cards
pm:queue but blocked	#6944, #6915, #6231
finding, awaiting grading	#7011 (new), #6850, #6814, #6522
pm:on-hold	#6682, #6009, #5376, #5346, #4220
tracking	#5499, #4706

Three unblocks, in the order they would help

1. #6231 — a domain:* re-label, pending ~20h. All five landing sites are in packages/metadata (3) and packages/objectql (2); none is in packages/drivers/. This seat flagged it 2026-08-08 13:43Z and is still deferring under the single-producer rule — dispatching it from here would have this lane edit two other seats' surfaces, and engine.ts took several landings today. Re-anchor to domain:metadata + domain:engine-core (possibly a two-way split), or rule explicitly that it stays domain:drivers on subject-not-site grounds, in which case this seat takes it as filed. Its serial blocker cleared: #5574 closed completed. Anchors have drifted hard — engine.ts 3317 → 4124.

2. #6944 and #6915 — an A-or-B disposition ruling. Both are "the capability is absent" cards, and both offer the #3724 shape: A implement it, or B refuse loudly at startup instead of failing silently. A dev should not pick A or B unilaterally, so they are queued and not dispatched.

3. ⚠️ #6915 may be queued against this seat's own standing instruction — please confirm which wins. This post's body carries the maintainer's 2026-08-05 rule anchored on #5499: new driver-memory/driver-mongodb cards take pm:on-hold referencing #5499 and do not enter the queue, with an exception only for things affecting CI-green correctness. #6915 is a driver-memory card that triage promoted to pm:queue; a tenant-isolation absence is not a CI-correctness matter, so on my reading the standing rule should have kept it on hold. Either the promotion is an intended exception (say so and I will dispatch it under route B), or it should revert to pm:on-hold. I have not dispatched it either way. Same question applies to #6814 and #6850, which sit ungraded rather than on-hold.

A pattern worth a ruling eventually, not today

Four cards now sit on the frozen driver-memory/driver-mongodb faces that #5499 forbids fixing: #6915 (no row-level tenant isolation at all), #6916 (autonumber collisions land as silent duplicates — filed by another lane), #6814 and #6850. The freeze is doing its job on investment; what it does not have is a place to put findings that keep arriving about the frozen surface. Recording the accumulation, not forcing a decision.

Two things this lane learned today, kept for whoever sits here next

• A queue build can go red on a package the PR never touched. fix(driver-sql): re-seed a stale autonumber counter instead of burning a number per failed create (#5495) #6932's red was PR fix(spec,cli,runtime,service-datasource)!: one driver vocabulary — os start and os migrate stop disagreeing (#6345) #6910 rewriting packages/cli/src/utils/storage-driver.ts — the oracle the --database-driver mysql 与 --database-driver sqlite-wasm 在 flag 解析阶段被拒 —— oclif 的 options 白名单漏了两个能用的驱动 #6860 pin derives its expectations from. Check file overlap, git merge-tree, and whether a co-queued PR rewrites the failing test's subject before treating a red as yours (ci: merge queue 吞吐优化——Test Core / Dogfood 各 2→3 分片 + 队列失败自动分诊评论 #4859).
• packages/objectql/src/engine-unknown-option.test.ts broke two different mechanical sweeps today, in two different ways: its bypassTenantAudit casts are load-bearing ([finding][drivers] 27 dead { bypassTenantAudit: true } as any options-gate casts in driver-sql / driver-sqlite-wasm tests — unlike turso's, these sit on a REAL typed gate #6754), and it holds a deliberately-unequal engine.find('task', { object: 'person' } as any) rejection test that a "delete every object:" sweep destroys ([finding][drivers] DriverQuery 已经存在，但几处驱动调用方仍在用 as any / as QueryAST 兜住冗余的 object —— 连带把 where/orderBy/fields 的检查一起关掉 #6231). Read it before writing any repo-wide pattern.

Seat remains held (os-zhuang, session session_01Hg9Pkg5nDedCRihRsdeCdX); dropping to standby cadence until one of the three unblocks lands.

---

Generated by Claude Code

[os-zhuang]

All three blockers ruled — closing the loop on comment 5230719256

Maintainer, 2026-08-10 chat:

#6915 和 #7117 就按 #5499 挂 on-hold,#6231 派给 metadata 席

Executed:

Card	Was	Now	Record
#6915	pm:queue + domain:drivers	pm:on-hold + domain:drivers	comment 5234867646
#7117	pm:queue + domain:drivers	pm:on-hold + domain:drivers	comment 5234868334
#6231	pm:queue + domain:drivers	pm:queue + domain:metadata	comment 5234873318 — handed off with re-measured anchors

The #5499 standing rule in this post's body stands as written and was not relaxed. The divergence was that triage had queued two driver-memory cards against it; the ruling settles it in favour of the freeze. Neither finding is retracted — both are held, with their measurements and their #3724-shaped A/B questions intact for whenever the freeze is revisited.

#6231's handoff carries fresh measurements rather than the card's stale ones: all five sites re-verified on main @ 3e8e669c0, engine.ts drifted 3317 → 4135 (it moved again between 07:3xZ and 01:1xZ, so locate by content), the premise re-confirmed (query.object still has zero readers in any driver), and the serial blocker #5574 confirmed closed. The engine-unknown-option.test.ts:183 trap — a deliberately-unequal { object: 'person' } as any rejection test that a naive sweep would destroy — is called out there explicitly, along with the note that the same file broke a second, unrelated sweep in this lane on 08-09.

Lane state after the ruling

pm:queue + domain:drivers is now empty. Remaining: five finding awaiting triage grading (#7099, #7052, #6850, #6814, #6522), seven pm:on-hold (#7117, #6915, #6682, #6009, #5376, #5346, #4220), two tracking (#5499, #4706). target:v17 ∩ domain:drivers = zero.

Note for the next occupant: four of the on-hold cards (#7117, #6915, plus #6814 / #6850 once graded) sit on the frozen driver-memory / driver-mongodb faces, and #6916 was filed against the same surface by another lane. The freeze is doing its job on investment; findings about the frozen surface keep arriving regardless, and this post is where they accumulate.

Seat held (os-zhuang, session session_01Hg9Pkg5nDedCRihRsdeCdX), standby cadence.

---

Generated by Claude Code