[PM seat] domain:drivers — ⏳ vacant

[claude]

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

单写手规则:只有在任座位 PM 编辑本贴正文;接管/移交 = 改正文 + 一条审计评论。空缺争用:动手前重拉正文、审计评论时间戳先到先得、写后回读。活性判定惰性(会话座位查最近产出评论,>24h 无产出可回收)。

范围

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

当前 PM

🟢 GitHub os-zhuang · session session_01VoxQqG5FiUHZKCST7KDoZC · 2026-08-12 ~18:5xZ 接任,经 /pm-dispatch drivers 从空缺接管。上一任:huangyiirene(08-11 ~04:2x → 08-12 ~18:4x,9 PR 全 MERGED / 零 REWORK);再上一任:os-zhuang(08-08→08-11,16 PR)。

巡逻线:上一任下班时已撤;本任期已自行武装(在飞 ≤45 分钟 / 待命 60–70 分钟)。当前 pending:trig_01V7fmYDbMhd1dQTAS8FYXcd(19:49Z)—— 继任者接管时删掉它,否则是孤儿定时器。

⚠️⚠️ 平台事实:座位轮换会跨 GitHub 账号,跨账号的 dev 会话彼此不可见

本仓的座位roster 横跨至少三个 GitHub 账号(huangyiirene / os-zhuang / hotlong)—— 维护者 2026-08-12 明确:「前任和你不是一个 github 账户」。⇒ 跨账号交接是常态,不是边缘情况。

实测(本任期):#8138 的 dev 会话 session_018m2pbEYn9s7mg4Y9Dvey62 建在上一任 huangyiirene 名下,从本席读 get_session 返回 failed to get session: the requested resource was not found,而该会话 35 分钟前刚被它自己的 PM 读作 RUNNING。⇒ 那是账号作用域,不是死亡信号。

两条纪律由此而来:

• ⛔ not found 永不读作「dev 已死」。 判死只认正向证据(探针回包、宿主回报 stopped、超本车道实测基线且连续静默)。误判的代价是往可能活着的 worktree 里塞第二个 agent。
• ⛔ 归档义务不可转移:archive_session / SendMessage / poke 三条路同源失效。下班的 PM 自己归档自己的 dev 会话,别留给继任者(他做不到)。若必须留活会话,就连同「这张卡仍归我」一起写明。
• ⇒ 跨账号场景下,draft-PR-early + 报告落 issue 评论从「加速器」升级为唯一通道:派发令里那句「报告必须发到 issue 上,不论有没有 PR」⛔ 永不省略(标记为 os-dev-report 的 HTML 注释评论;⚠️ 注意直接把该注释写进 issue 正文会被 sanitizer 静默吞掉,写成行内代码也不行 —— 只在派发令里描述它)。

已立 #8187(finding)提两行 references 事实表修改。⚠️ 该 finding 的动机卡虽已另有归属,平台事实本身不受影响,已在卡上注明勿按「已被超越」定级。

⚠️ 在飞与 owed

• finding: after the #7598 Q1=B ruling, a read scope with a driver-refused field reference answers 400 from the driver — which cuts across #5367's attribution argument on that one path #7929(本任期第 1 轮派发,本席唯一在飞)—— security,维护者裁决 B「driver-sql 的 INVALID_FILTER 停止回显 $field 操作数」。mode:subagent / model: opus / 分支 claude/issue-7929-withhold-field-operands。⚠️ PM 实测把文件面从裁决点名的 1 个 error builder 扩到 3 个(crossFieldComparisonError / 裸引用 builder / uncompilableFieldReferenceError,全部经 unsupportedFilterError 出栈),该扩展以机制假设身份进派发令,dev 可证伪。⚠️ 已知未验前提:裁决说「全文进 server-side log」,但没人核过 driver-sql 在该 seam 有没有 log sink —— 已作为 fork 明写进派发令,⛔ 禁止 dev 自造日志子系统。finding: the #7929 read-scope disclosure is NOT analytics-only — an RLS $field filter injected by the security middleware discloses the same policy column on the ordinary CRUD path, and predates #7598 #7988 pm:blocked 在本卡上:pins 覆盖 CRUD 面则随本 PR 关闭(需第二行 Fixes #7988 + 在 finding: the #7929 read-scope disclosure is NOT analytics-only — an RLS $field filter injected by the security middleware discloses the same policy column on the ordinary CRUD path, and predates #7598 #7988 留言);若故意收窄,必须去 finding: the #7929 read-scope disclosure is NOT analytics-only — an RLS $field filter injected by the security middleware discloses the same policy column on the ordinary CRUD path, and predates #7598 #7988 说明,否则它会静默空等。
• ⛔ measure: try to reproduce #6522's overlay-index-drift flake under contention — the arm the 0/67 run never exercised #8138 不是本席的卡。 维护者 2026-08-12 指令(原话:「8138 前任会继续跟进」)—— 归上一任 huangyiirene,assignee 与认领均在其名下,它持有该 dev 会话的活句柄。本席 ⛔ 不复核、不关卡、不探活、不归档,⛔ 不因为它还开着就把它捡回 owed 清单。跨账号铁律:assignee 不是你 ⇒ 永不碰。

⚠️⚠️ 配额:七天窗告警(影响派发策略,非本车道特有)

上一任交接时 dev 会话读数 rate_limit_info: {rateLimitType: "seven_day", status: "allowed_warning"},reset 约 2026-08-17。与本仓 agent 日常撞的五小时墙不是一回事:五小时墙会自愈(#7853 实例),七天墙不会,且预算全席共用。

⇒ 派发判据为「值不值得花这份预算」而非「有活就派」:长循环 / 高 token 卡(复现循环、全包重跑)优先级下调;⛔ 不为「显得在干活」而派测量卡。在预算告警期内,「无可派」是正确终态,不是失职。
⇒ 本任期第 1 轮据此只派 #7929 一张:live 信息泄露 + 裁决已在手 + 落点收敛在单文件 seam,是本车道当前唯一明确值这份预算的形状。

⚠️ #5499 冻结的真实范围(本贴曾写错,已更正)

本贴此前称 #5499「已全面解除」—— 过宽,被维护者裁决 5261729371(#6915)证伪:「⛔ 不做处置 A…#5499 投资冻结继续有效」。

正确读法:两道解冻(5249019855 / 5252526378)的范围是清账 / 对齐既有能力,不是重开能力投资。⇒ 对 driver-memory / driver-mongodb 的新能力投资仍受门控;能穿过冻结的形状是「消除静默失败模式」。分诊侧「新单一律挂 hold」的规则确已退役,但形如能力投资的卡,派发前须取裁决。driver-sql 不在冻结内。

实例:#6915 的 dev 自行把该裁决用到实现决定上(不为对称造 batch 路径);#7956 判定「测量 driver 不是投资 driver」,故可在 #7872 held 期间执行。

⚠️ 「7498 插队」= #7398(08-10 号码笔误,已消耗);真实 #7498 属 devx 车道

Ledger

上一任期(08-11→08-12)🏁 check:driver-conformance 由 36 covered / 4 DEBT 推到 40 covered / 0 DEBT / 0 exempt 并保持(LEDGER = [])—— 本任期任何 driver 卡的派发令都要求 dev 前后各读一次该数。

上一任 9 PR 全 MERGED、零 REWORK;另 2 张纯测量卡(#7956 已交付关闭,#8138 在飞)。解冻批(mongodb)5 张:#7528 / #7550 / #7579 / #7590 / #7625。#7723(69fde55)双 Fixes 关 #6814 + #6682。#7852(9bf4dd0)Fixes #7117。#7869(b313fde)Fixes #7853。#7924(45d5bd2)Fixes #6915,裁决 5261729371 处置 B。#7956(closed,无 PR)。

⚠️ #7956 的测量结论(易被凭印象误引,勿改写)

• 形状是「两个阵营 + 一个洞」:SQL 家族六种值全部以 ADR-0112 INVALID_FILTER/400 拒收,且是两个独立实现各自走到同一措辞;driver-memory 与 driver-mongodb 任何层都无策略(mingo 答 0 行、BSON 编辑文档)。
• ⚠️ 五个 driver 列只有三个独立实现 —— driver-sqlite-wasm 与 driver-turso local 都继承 SqlDriver 的 filter 编译器。把那张表的一致性当五方佐证会高估证据。(本任期 finding: after the #7598 Q1=B ruling, a read scope with a driver-refused field reference answers 400 from the driver — which cuts across #5367's attribution argument on that one path #7929 再次用到这条:三个 SQL driver 共用一个拒收 seam,所以单点修复即可覆盖。)
• ⚠️ 上一任给 spec 席的门措辞是错的,已更正([PM seat] domain:spec — 🟢 os-zhuang (wave 3: Batch D in flight; landing chain draining) #6017 5264816958):BigInt 不可 JSON 表示却在五分之四的 driver 上被接受。真实收敛集 = 「可 JSON 表示的字面量 + bigint + Date」。
• 最坏格子:driver-mongodb × 隐式等值 { qty: undefined } → 编码成 {}(空过滤器),唯一朝放大方向失败的格子。

仍持有 / 待裁(⛔ 均有明确 hold,勿重复评估)

• finding: SqlDriver's #3821 recovery ladder widens an unresolvable projection to every field #7589 — needs-user-decision(5264126890),本车道最快能解锁真实修复的一张。三形状分属三车道:A flow config schema 收口(domain:spec)/ B engine.ts:6996-7001 头段过滤收口(objectql;删掉的是理由为假的检查)/ C driver ladder 里把 dotted 从容忍中切出(本席)。B、C 可叠加;上一任建议 B 为主、C 为后续。hold 的两个重启条件已由上一任实测满足(5263464190)。⚠️ 该卡不带 domain:drivers 标签,整车道查询看不见它 —— 靠本贴记住。
• driver-memory has no policy for an unsupported comparand TYPE: a BigInt crashes with a raw mingo TypeError, and four other types silently answer zero rows #7872 — 分诊判 held。重启 (a) = spec 席对门的决定([PM seat] domain:spec — 🟢 os-zhuang (wave 3: Batch D in flight; landing chain draining) #6017,⛔ 不催);(b) = 分歧矩阵,已由 measure: how each driver answers the six non-JSON comparand types (#7872 restart condition b) #7956 满足。
• Turso remote:带 id/conflictKeys 但没匹配上的 upsert 仍会静默写入 NULL 自增号(#6944 拒绝闸门覆盖不到的那条腿) #7099 — ⚠️ 旧记「等 TursoDriver remote 面根本不生成自增号:RemoteTransport.create 自建 INSERT,auto_number 只是个 TEXT 列 #6944 disposition A」已过期:TursoDriver remote 面根本不生成自增号:RemoteTransport.create 自建 INSERT,auto_number 只是个 TEXT 列 #6944 于 08-09 走处置 B 关闭(PR fix(driver-turso): refuse auto_number writes on the remote transport (#6944) #7089)。Turso remote:带 id/conflictKeys 但没匹配上的 upsert 仍会静默写入 NULL 自增号(#6944 拒绝闸门覆盖不到的那条腿) #7099 是该闸门漏掉的那条腿,且有维护者亲自确认的 hold(5248480983)。重启 = 用户报告该腿,或下一个 Turso 批次。
• flaky: sql-driver-overlay-index-drift.test.ts 「stays silent on the SECOND boot, when the runtime ledger starts empty again」偶发判红 #6522(两度 HOLD;重启 = 该签名踢中合并队列一次 —— measure: try to reproduce #6522's overlay-index-drift flake under contention — the arm the 0/67 run never exercised #8138 正在补它缺的证据,但那张卡归前任)、drivers(sql): 共享 canonical 修复表达式把「裸数字文本」当儒略日读,backfill 会把这个误读写进盘里(观察项) #6009(pm:on-hold p3)、ADR-0053 D-E3：mongo 的遗留形态是永久态，但它既无 backfill 也无读修复——#4191 storage-form 轴最尖的一格无法闭合 #4220(标签为 pm:on-hold;本贴旧称「决策箱」—— 以标签为准)。
• DevPlugin 的 bare catch 把任何 driver 构造失败都报成「not installed」(#6915 实测) #7926 属别车道(现状说明 5262921865,⛔ 不认领)。packages/spec prose still calls driver-memory's $contains fold open after #7723 closed it #7854 已由 spec 席改路由 domain:spec-surface。[裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 / $regex on driver-sql is not a regex — it compiles to a substring LIKE, so it both over-matches and silently matches nothing #4706 是 tracking 锚点。
• finding: the #7929 read-scope disclosure is NOT analytics-only — an RLS $field filter injected by the security middleware discloses the same policy column on the ordinary CRUD path, and predates #7598 #7988 现 pm:blocked 在 finding: after the #7598 Q1=B ruling, a read scope with a driver-refused field reference answers 400 from the driver — which cuts across #5367's attribution argument on that one path #7929 上(domain:identity 标签,但落点随 finding: after the #7598 Q1=B ruling, a read scope with a driver-refused field reference answers 400 from the driver — which cuts across #5367's attribution argument on that one path #7929 的 driver 侧修复)。

Session-operational notes for a successor

• ⛔⛔ 写后回读不是形式:本任期一次编辑里 sanitizer 静默吞掉了正文中的 HTML 注释标记,另一次审计评论写了没做的事(声称已更新 assignee,实际只改了 title + body)。两者都只能靠回读发现,「API 返回 200」≠「落地内容正确」,也 ≠「你写的是真的」。
• ⛔⛔ RE-ARM FAILURE ≠ RE-ARM DONE:MCP 断连 = 失败,ToolSearch 重载重试至真实 fire_at;arm 后回读。改了状态就要改定时器文本 —— 过期的祈使句会让下一枪去做已经不该做的事。
• ⚡ 五小时墙:撞墙是正向死因,不是 unreliable,且会自愈(driver-memory's AnalyticsResult.sql loses a RegExp operand to {}, so the pipeline dump shows no pattern at all #7853:22:54Z 被打死,00:10Z 墙解除后自行复活跑完)。墙内只重挂,墙后先读 GitHub(可能已自愈交付)再决定 poke。派发令写一句「撞墙可续跑、别重开分支」有用。⚠️ 七天墙不同,见配额节。
• SendMessage 对云会话不可达(ListAgents 空)⇒ poke 走 create_trigger(persistent_session_id) + fire_trigger + delete_trigger。⚠️ 前提是会话在本账号名下 —— 跨账号连 poke 都不成立,见顶部事实节。
• 空字段签名:先核成员资格(push 探针最强 —— 向 PR 分支推空提交,被拒且理由为 merge queue ⇒ 在队且分支未污染),未入队才 disable/enable 翻转一次。
• ⚠️ 队列条目会坏死(test(spec): register sys_api_key in SINGLE_RECORD_WRITE_ONLY (queue-blocking) #7803:在队 75 分钟无投机分支)⇒ 单次翻转。⚠️ check-run 镜像会卡死(job 全绿仍 in_progress)⇒ actions_get(get_workflow_job) 读 job 层真值,rerun_workflow_run 处置。⚠️ runner TLS 抖动(红在 Checkout repository)⇒ 重排一次,PR 留痕。
• Check Changeset 会因 ADR-0087 而红:changeset 头带 ! 就必须有答复行([finding] ADR-0087 台账没有「完备性」门禁:已发生的退役漏登记时全仓全绿,只有人工能发现(#6011 即如此) #6148 门)。⚠️ 该门要求回答问题而非贴标记。
• 已知 flaky:metadata-fs watcher tests are merge-queue flaky, and #7208's 20s deadline hardening did NOT fix it — the event is suppressed, not late #7282(metadata-fs watcher),rerun 一投即绿。
• 共享损害会撞车:Queue-blocking: #7769 opened update on sys_api_key without bulk — api-methods-batch-conformance fails every merge-queue (full-suite) build #7793 本席立卡止血 test(spec): register sys_api_key in SINGLE_RECORD_WRITE_ONLY (queue-blocking) #7803,另一席并行立 main is red for every PR that touches packages/spec: #7769 gave sys_api_key update without bulk, and the conformance scan that catches it lives in a package #7769 never touched #7802 → fix(spec,platform-objects): register sys_api_key's deliberate no-batch decision, unblocking every spec PR (#7802) #7818 抢先落地,main 停摆 ~2.5 小时。立卡前先 search_issues 打测试名搜同签名。
• verify-don't-trust:上一任期 dev 十二次测量修正 PM / 卡片 / 先例 / 自己,十二次全对。 三分区派发令是机制保障 —— 把 PM 读数明标为「须实测的假设」,证伪即成功。两次最有价值的证伪推翻的是发起该次派发的前提本身。PM 复述结论时同样会传播错误,而且会传播进别人车道。记录必须能被更正,更正必须发到收信人那里,不能只在自己卡上改。
• 派发前对 origin/main 亲核卡片断言:本任期 finding: after the #7598 Q1=B ruling, a read scope with a driver-refused field reference answers 400 from the driver — which cuts across #5367's attribution argument on that one path #7929 即实例 —— 裁决点名一个 error builder,git grep 到三个。裁决写的是落点的「一个例子」,不是落点的「全集」;卡片与裁决都描述当时的仓。
• 分诊 Routine 未覆盖时可自补分级(driver-memory's AnalyticsResult.sql loses a RegExp operand to {}, so the pipeline dump shows no pattern at all #7853 / measure: how each driver answers the six non-JSON comparand types (#7872 restart condition b) #7956 / measure: try to reproduce #6522's overlay-index-drift flake under contention — the arm the 0/67 run never exercised #8138 先例):查重 + 锚点重验 + 分级理由三项写进认领评论。
• hold 卡的重启条件可以主动去满足(finding: SqlDriver's #3821 recovery ladder widens an unresolvable projection to every field #7589 / driver-memory has no policy for an unsupported comparand TYPE: a BigInt crashes with a raw mingo TypeError, and four other types silently answer zero rows #7872 / measure: try to reproduce #6522's overlay-index-drift flake under contention — the arm the 0/67 run never exercised #8138 先例)。⛔ 但 hold 本身只有写它的人能解,除非条款自陈「条件满足即重启」。
• 只读的路由判断是 PM 自己的活;需要执行的测量该派卡(driver-memory has no policy for an unsupported comparand TYPE: a BigInt crashes with a raw mingo TypeError, and four other types silently answer zero rows #7872 自测 vs measure: how each driver answers the six non-JSON comparand types (#7872 restart condition b) #7956 派卡)。
• 环境:mongodb-memory-server 代理 403(已 curl 复验);driver-memory 在-process,套件是真执行。
• skip-changeset 按 check name 最新 run 判定;标签写后回读;调度器晚 3–8 分钟;git fetch 会移动 main;跨席声明先例六次([PM seat] domain:spec-surface — 🔀 merged into #6017 #6298×2、[PM seat] domain:devx — 🟢 qq9340100(跟合并中,五张已 armed) #6023、[PM seat] domain:spec — 🟢 os-zhuang (wave 3: Batch D in flight; landing chain draining) #6017×3)。

---

迁移注记:自 #4604 座位表迁移(2026-08-06);本贴即该座位唯一权威。

[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

[os-zhuang]

交接审计 — os-zhuang 卸任(2026-08-11 ~04:0xZ)

维护者 2026-08-11 指示「新项目经理会接手」。本评论仅作交接存档,状态以正文为准(座位贴单写手协议)。

交接点:in-flight ZERO。 无在派 dev 会话、无 open PR、无排队条目、无孤儿订阅、无未归档云卡。与 2026-08-08 接手时同样是干净的切点。

项	值
在任	2026-08-08 → 2026-08-11 04:0xZ
会话	session_01Hg9Pkg5nDedCRihRsdeCdX
任期落地	16 PRs MERGED(08-09 ×12,08-10 ×4),另 #6522 无 PR 关闭(测量结论)
末次实测	03:3xZ:domain:drivers 14 open · 队列空 · origin/main 211abdbd6
巡逻 tick	已解除武装(trig_01Tsk7vgcpb7jTLVhgfwrbR1 删除)——接任者自行 arm

08-11 是纯待命段:零派发、零落地,三条只读记录。 车道确实空(自 08-10 18:4xZ 起 14 open 一格未动),不是没找。三条记录分别是 #6522 的过期理由更正(5247751272)、#7177 的不派理由入卡(5248086029)、#7501 的落点判据(5248698620)。三者都不改标签、不重定级——定级是分诊的职权。

给接任者的三个最高优先提示(展开见正文):

1. ⚠️ 「7498 插队」= 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,不是今天新建的 pm-dispatch SKILL: require a four-lens analysis block on every needs-user-decision card #7498。 那是 08-10 的号码笔误,已消耗完毕并落地(PR fix(driver-sql): refuse scalar-comparison operators on JSON/multi-value columns instead of answering silently wrong #7415)。今天 02:58Z 真的出现了一张 pm-dispatch SKILL: require a four-lens analysis block on every needs-user-decision card #7498(devx 车道,pm-dispatch SKILL),两者无关,本座位未碰。前任还就此多问了维护者一句——答案本就写在座位卡上,属多余动作,记下来免得重演。
2. ⛔ 本车道内标签 ≠ 授权,直到 [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 的七秒批量翻转事件解决(已报 [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 5237773754)。[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 是同类形状的新样本:分诊晋级理由本身站得住,但没有权衡站点所在的包——12 个站点里 11 个在 [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 冻结的 driver-mongodb。
3. ⛔⛔ re-arm 失败不等于 re-arm 完成。 08-10 19:45Z→00:34Z 座位空 armed 约 4h49m,起因是 MCP 断连时 send_later 连续失败而该轮静默收尾。代价为零仅仅因为当时 in-flight 为零。

本任期两条自我更正,一并留档:座位卡旧版的 #7177「9/10 frozen」应为 11/12;#7501 上 scale → precision 的别名一度看着像烟枪,查证后作废(那条属 CurrencyConfigSchema,与字段级别名表不冲突)。dev 在本任期内 10 次证伪 PM 声称的前提且每次都对——预先定价的派发事实按构造是 verify-don't-trust,这条请一并继承。

座位现为 🔵 空缺待接管。接任者按协议:改正文 + 一条审计评论,写后回读。

---

Generated by Claude Code