@sema-agent/settings-schema 15.2.0 → 16.0.0

package/CHANGELOG.md

@@ -8,6 +8,143 @@
 
 ## Unreleased
 
+## 16.0.0 — 2026-10-30 — major:worker 的执行车道由单值改为有序车道集 `runtime.execution.lanes` · device 车道的设备入口 `DEVICE_RELAY_URL` 必需且有值文法 · 记忆持久面方言词 `tidb` → `mysql` · 退役模型面组拒码 `config.summarize_model_missing` · `HostStatus.ts` 判 RFC 3339(加可选 `heartbeatMs`)· 本地配置单读口 `FileConfigStore.read()`(过深的文档是文件层的拒)· 本地文件契约 `RemoteExecSpec` 的非空串字段:只含空白 = 空 ⇒ 拒 · 一次性迁移 SS-M12
+
+> 档位(按发版纪律):**major** —— 七处硬破坏(B1–B7,逐条三问在下),加性若干。发版纪律按消费方在**运行期**与**编译期**的可见性判档。
+> 每一件先写律:一件事只有一处说法、一种读法 —— 本版每条都是把「同一件事两种说法」收成一种,规则变少,不是变多。
+> 导出面:包根 +7(`DEVICE_RELAY_NONE` / `DEVICE_RELAY_RULE` / `deviceRelayFlaws` / `wsUrlFlaws` / `WS_URL_SHAPE_RULE` / `WsUrlFlaw` / `DIAL_ADDRESS_URL_FORBIDDEN_PARTS`)−1(`SUMMARIZE_MODEL_MISSING_CODE`);
+> `./fleet` −1(同名);`./node` +1(`FileConfigRead`)−2(`inspectBundle` / `BundleInspection`);导出面登记表合计 1468 → 1472 名。零别名、零双读、零过渡读法 —— 消费方的 tsc 红就是通知;存下来的数据另配一只一次性迁移 SS-M12。
+
+### BREAKING 清单(逐条三问 + 下游动作)
+
+**B1 · 执行车道:单值 `runtime.execution.lane` → 有序车道集 `runtime.execution.lanes`。**
+律:**一台 worker 声明的是它启用的车道集,不是一条车道** —— 根会话各自绑定其中一条,首项是缺省。
+形:`lanes` = 车道词的非空、去重有序表(`["k8s", "device"]`;首项缺省)。键归属按集判:`coords` / `secretRefs` 的每个键归表里**某一条声明的**车道
+(归表外车道 ⇒ 点名它属于哪条车道);每条声明的车道各自的必需键都要在场且非空白;多租户姿态(`requirePrincipal`)对每条不分租户的车道各拒一条(落在 `lanes` 的那一格);
+「只能一个副本」读车道表新列 `ExecutionLaneRow.singleReplica`(host、device 为真:会话的活挂在一个副本上)—— 声明了这种车道的 worker 副本数 > 1 拒一条、点名这些车道,写闸不再按 `host` 这个词判;
+`device ∈ lanes` ⇒ 要真开得出 SQL 池的店(同 15.x 的 device 规则)。旧单值 `lane` 是墓碑:读写两面拒,拒句点名新形与一次性迁移 SS-M12。
+保留名表里 `REMOTE_EXEC` / `REQUIRE_EXECUTION_LANE` 的归属字段改指 `runtime.execution.lanes`。
+**谁需要**:执行车道从「引擎进程的属性」降为「根会话的放置」之后,部署声明的是一台引擎启用哪几条车道(device 与 k8s 共存是第一个真实形),单值装不下。
+**谁受伤**:① 存下来的每一行 15.x workers(都带 `lane`)—— 整域读函数抛、`readWorkersRows` 扣下;② 按 `.lane` 读规格的代码(tsc 红);③ 渲染器:`REMOTE_EXEC` 改写成按序的逗号表(`lanes.join(",")`,首项缺省);
+④ 引擎侧:把 `REMOTE_EXEC` 当一个词读的引擎读不了两条车道的表 —— 引擎与渲染器须同窗改读有序表。
+**补偿**:跑一次性迁移(`npx @sema-agent/settings-schema migrate <config.d directory>` 或 `migrateStoredDocuments`):SS-M12 把 `lane: L` 改成 `lanes: [L]`,一元表的读法与旧单值逐位同。
+
+**B2 · device 车道的设备入口 `DEVICE_RELAY_URL` 是必需坐标,值有文法。**
+律:**设备拨哪里是部署的必填声明,只有两种合法值** —— 一个 ws(s) 绝对 URL(不带 userinfo / query / fragment:引擎把它逐字发布给设备,地址里没有凭据的位置),或字面 `none`(没有中继,设备拨引擎自己的地址)。
+车道表 device 行 `requiredEnv` = `["DEVICE_RELAY_URL"]`(此前它是 device 臂读而表漏登记的键;写在 env 逃生口里的 15.x 写闸照收)。值的唯一判官 `deviceRelayFlaws(value)`(包根,纯函数):合格 ⇒ `[]`,
+否则按判序交回 `not-ws-url` / `userinfo` / `query` / `fragment`;规则句 `DEVICE_RELAY_RULE`;`none` 只认这一种拼法。写闸按坐标文法表对有文法的坐标问它(拒句 `coords.DEVICE_RELAY_URL <规则> — found: <词>`,
+不回显值);值里认得出凭据形的片段照旧由坐标的密钥判据拒。缺席 / 空白走必需坐标的同一句(`lane "device" requires coords.DEVICE_RELAY_URL …`)。
+ws(s) 的形判官 `wsUrlFlaws` 与这个座位禁的部件集 `DIAL_ADDRESS_URL_FORBIDDEN_PARTS` 住在 URL 形判官模块(本包判 URL 的正则只在那一处)。`RESERVED_WORKER_ENV` 多一名 `DEVICE_RELAY_URL`。
+**谁需要**:引擎缺席即拒起;表不登记这一键,写闸、中心表单与部署清单就放行一台起不来的 device worker。
+**谁受伤**:存下来的 device 行没有这一键(SS-M12 拒、原行留着 —— 迁移不在 URL 与 `none` 之间替运维猜);把它写在 `env` 里的 15.x 行;任一处把它写成别的形状的值。
+**补偿**:给 device 行写 `coords.DEVICE_RELAY_URL`(经中继拨 ⇒ 那个 ws(s) URL;直拨引擎 ⇒ `none`)再跑迁移;写在 `env` 里的,SS-M12 搬进 `coords`(声明了 device 的行)或丢掉(没声明 device 的行:引擎从没读它)。
+**部署序:先补、后升级** —— 15.2.x 的写闸收 `env.DEVICE_RELAY_URL`(那时它不在车道表里),旧版本下先给每个 device 行补上,升级时 SS-M12 搬进 `coords`,没有读不出的窗。
+
+**B3 · 记忆持久面方言词 `tidb` → `mysql`(`MEMORY_ENGINE_BACKENDS` = `file` / `pg` / `mysql`)。**
+律:**MySQL 族那只 SQL 店只有一个字**,与店词 `store.backend: "mysql"` 同字。`runtime.store.memory.backend: "tidb"` 读写两面拒,拒句点名 `mysql` 与 SS-M12;方言与店的配对规则不变(`pg` 要 pg 店,`mysql` 要 mysql 店)。
+**谁需要**:同一件事三个字(店词、记忆方言、引擎内部的会话店值)让每个读者各自翻译。**谁受伤**:存下来写着 `tidb` 的行;部署环境里 `MEMORY_ENGINE_BACKEND=tidb`(引擎直接读本表的词,提货后拒起)。
+**补偿**:SS-M12 把存下来的 `tidb` 改写成 `mysql`(6.x 行的 `env.MEMORY_ENGINE_BACKEND=tidb` 由 SS-M4 一并写成 `mysql`);部署环境变量改写成 `MEMORY_ENGINE_BACKEND=mysql`。
+
+**B4 · 模型面组拒码 `config.summarize_model_missing` 退役(不重定义),写者计划助手的 `fix_first` 结局一并删。**
+律:**闭集里只列真会被铸出来的码**。角色席点名目录里没有的条目时,引擎把它读成未设席、按回退链落下一级,没有哪种读法因 summarize 悬空而拒组 —— 列着它就是说一件不成立的事。
+`MODEL_PLANE_REFUSAL_CODES` 五码(其余次序不动);`SUMMARIZE_MODEL_MISSING_CODE` 从包根与 `./fleet` 删。心跳 / `/health` 上若还带着它,读口按集外码丢掉(诊断键的失败方向 = 不说)。
+`planEnvModelTableWrite` 的结局删 `fix_first` 一臂:summarize 悬空照样写在回执里(`dangles`),要确认的写法照旧把它给用户看;`envModelTableWriteRefusal` 只收 `confirm` 计划。
+**谁需要**:按码渲染的消费方不再为一个不会出现的码写臂。**谁受伤**:import 这个常量或对 `fix_first` 分支的代码(tsc 红)。**补偿**:删那一臂;悬空的 summarize 从回执里读。
+
+**B5 · `HostStatus.ts` 判 RFC 3339 时刻(此前只判非空串)。** 加性同节:`HostStatus.heartbeatMs?`(正整数毫秒,上报方声明的心跳节律,与实例公告的同名字段同一个义;缺席 = 没声明,**没有缺省**;多久没报算不新鲜是中心的判,本包只给字段)。
+律:**注释说是时刻的字段就判成时刻**。**谁需要**:读方按时刻比较新鲜度;`Date.parse` 读成 NaN 的串不该过写闸。**谁受伤**:上报非 RFC 3339 时刻的宿主状态写入被拒。**补偿**:上报 `new Date().toISOString()` 形。
+
+**B6 · 本地配置的单读口 `FileConfigStore.read()`(`./node`)取代 `inspectBundle` / `BundleInspection`;过深的文档是一份文件层被拒的文档。**
+律:**一次读,一个结局**。`read(): Promise<FileConfigRead>`:每份文档只读一次 —— 文件层都读得进 ⇒ `{ kind: "effective", effective, warnings }`(effective 与严读 `getEffective()` 逐位同,读侧告警交成数据、不经 `onWarning`);
+有文档被拒 ⇒ `{ kind: "refused", refusals, version, warnings }`(拒单形、次序与版本与 15.2.0 的目录口同)。读得出却过不了闸域 schema 的拒照严读抛(不是文件层)。
+深度:一份文档嵌得比整棵目录的内容版本能算的深(根下 199 层)⇒ 文件层拒,闭集词 `CONFIG_DOCUMENT_REFUSAL_REASONS` 多一个 `too_deep`(墓碑仍在末位)—— 此前在算版本那一步抛,已收集的拒全部丢掉。
+严读(`getEffective` / `readBundle`)对过深的文档抛文件层那一句(点名文件路径);宽容读把它落进 `domainErrors`;一致性语料 c16 的本地腿拒在 `parse`(此前 `hash`)。
+**谁需要**:要「读得进就要 effective、读不进就要拒单」的本地读腿 —— 此前只能严读一次、抛了再问目录口一次,两读之间文档被修好时这一拍是过期诊断。
+**谁受伤**:import `inspectBundle` / `BundleInspection` 的代码(tsc 红);对 `ConfigDocumentRefusalReason` 穷举的 `switch`(多一个词,tsc 红);按「hash 层拒」认过深文档的读者。
+**补偿**:改调 `new FileConfigStore(root).read()`,按 `kind` 分两支;`switch` 补 `too_deep` 一臂。
+
+**B7 · 本地文件契约 `RemoteExecSpec`(`config.d/remote-exec.json`)的非空串字段:只含空白 = 空 ⇒ 拒。**
+律:**「空白」只有一种读法** —— 文件契约里每个非空串字段(沙箱镜像 / 命名空间 / 主机 / 用户名 / 设备序列号 / 工作目录 / 挂载路径 / shell / 模板 / 桶 … 共二十一处,此前凡拒空串的字符串字段)问的是写闸对必需坐标问的**同一只**判官 `isBlankCoordinate`:
+空串或只含空白(`trim()` 认的空白:空格 / 制表 / 换行 / 不换行空格 / 字节序标记 …)一律拒。此前同一个部署声明(沙箱镜像、命名空间)在写闸里「纯空白 = 缺」,在文件里却只拒空串、收下 `"  "` —— 同一个包里两种读法。
+空串与纯空白现在是**同一条拒、同一句话**(`must not be empty or whitespace-only — give it a real value (an optional key can simply be left out)`),issue 指到那一格,不回显值;
+此前空串的拒句是 zod 内建的 `too_small` 那一句,现在换成这一句 —— 被拒的集合只增不减,但句子与 issue 码变了。判官只判「是不是空白」:非空白的值(含前后带空白的)逐字承运,不 trim;NUL 仍是它自己的一句。
+**谁需要**:本地配置模式下引擎起服读 `config.d/remote-exec.json` 的部署 —— 把一个空白当镜像 / 命名空间去起容器或拉 pod,是起服之后才响的坏声明;同一件事写闸(workers 的必需坐标)早已拒。
+**谁受伤**:`config.d/remote-exec.json` 里把任一非空串字段写成纯空白的部署声明(病态输入):`loadRemoteExec` 抛(读文件的引擎起服拒)、`validateRemoteExec` / `parseRemoteExecDocument` 拒、`writeRemoteExec` 不落盘;
+按 zod 的 `too_small` 码认「空串」的 issue 读者(读码不读路径的)—— 空串的拒现在也是这一句 custom issue。
+**补偿**:删掉那一键(可选字段:缺席 = 缺省行为),或给真值(必填的 `image` / `namespace` / `host` / `username` / `serial`:只能给真值)。没有迁移 —— 空白值没有「正确的改写」,替运维猜只会把错藏起来。
+
+### 一次性迁移 SS-M12(workers 7.0–15.x 行 → 16.0.0 形)
+
+只认形、不认义、幂等:`lane: L` ⇒ `lanes: [L]`(moved,原位改名);`store.memory.backend: "tidb"` ⇒ `"mysql"`(rewritten);`env` 里的 `DEVICE_RELAY_URL` ⇒ 声明了 device 的行搬进 `coords`(moved),没声明的丢(dropped-inert)。
+拒且原行留盘(`readWorkersRows` 读时扣下):`lane` 与 `lanes` 并存、声明了 device 却把 `DEVICE_RELAY_URL` 写在 `secretEnv`(值读不到)或 `env` 与 `coords` 两处都写、改写后仍读不进的行(没有 `DEVICE_RELAY_URL` 的 device 行在内)。
+与 SS-M4 在同一个 workers 行步里做:先 SS-M12 改、再 SS-M4 改,两只都改完才用读侧那一只判一次(一行可以同时带 7.0+ 的单值车道与 6.x 的店字段;各判各的会互相卡死),
+改完读不进的那一张拒记在改了这一行的最新那只迁移名下;SS-M4 的产出直接是 16.0.0 形;窗 = 发布日 + 30 天,登记在 `ONE_TIME_MIGRATIONS` 一行。拒因里的指路点名**搬这个键的最新一只迁移**:`DEVICE_RELAY_URL` 指 SS-M12,其余车道 / 店键仍指 SS-M4(同一条命令跑整族)。
+
+### 文档
+
+随包文字说真话:7.0.0 的 workers 一次性抬升函数与它的文件子命令 11.0.0 就删了,llms 两档、接入档入口表、一致性门档的目录树与 README 仍有现在时的宣传 —— 改成「已删」并指向一次性迁移族;
+`FileConfigStore.getDomain` 的注释把纯空白文件算进缺席,实际读法抛(纯空白 = 半写,坏文件)—— 注释改真。
+
+### 钉
+
+新:`test/lane-set-16.0.0.test.ts`(车道集形 · 去重 / 空 / 墓碑 · 键归属按集 · 每条声明车道的必需键 · 多租户逐车道 · `singleReplica` 列 · device 店规则按集)、`test/device-relay-16.0.0.test.ts`(表行 · 判官真值表 · 写闸同答 · 凭据形片段 · 拒句不回显值)、
+`test/memory-backend-mysql-16.0.0.test.ts`、`test/summarize-code-retired-16.0.0.test.ts`、`test/host-status-heartbeat-16.0.0.test.ts`、`test/config-read-one-16.0.0.test.ts`(单读口 · 文件层拒交成数据 · 深度闸收进文件层 · 边界 199 / 200)、
+`test/one-time-migration-ss-m12-16.0.0.test.ts`、`test/docs-rot-16.0.0.test.ts`、`test/exec-str-blank-16.0.0.test.ts`(文件契约字符串叶子从 schema 现算 · 空串与纯空白同一句 · 与写闸必需坐标对拍六对 · 只拒不改 · 读写入口同答);随形改的旧钉逐格翻到新形(车道夹具一元表、拒因落点 `lanes.<i>`、方言词、码闭集、迁移 id 闭集、指路律读两只迁移的读数、目录口的钉经单读口交出、变异靶点随新拼法)。
+
+另:`docs/API-SURFACE.md` 随导出面重生成;一致性语料 c50–c68 / cli04 的输入改成车道集形(device 两条补 `DEVICE_RELAY_URL: "none"`)并重新加冕,c16 本地腿的拒层改 `parse`。
+
+**自 v15.2.0 起运行期代码有改动的公开导出(机器重算;上界 —— 可达 ≠ 一定变,不可达 ⇒ 一定不变;本版新增的导出不入表)**
+
+```text
+CONFIG_DOCUMENT_REFUSAL_REASONS [.]
+DOMAINS [., ./types]
+DOMAIN_SCHEMAS [., ./types]
+EXECUTION_LANES [., ./execution-lanes]
+FileConfigStore [./node]
+HostStatus [., ./types]
+MEMORY_ENGINE_BACKENDS [., ./execution-lanes]
+MODEL_PLANE_REFUSAL_CODES [., ./fleet]
+ModelPlaneRefusalCode [., ./fleet]
+NON_PORTABLE_DOMAINS [./conformance]
+ONE_TIME_MIGRATIONS [./one-time-migrations]
+ONE_TIME_MIGRATION_IDS [./one-time-migrations]
+RESERVED_WORKER_ENV [., ./types]
+RemoteExecSpec [., ./remote-exec]
+WorkerSpec [., ./types]
+WorkersConfig [., ./types]
+buildEffective [., ./config-fns]
+deriveLocalExpectation [./conformance]
+deriveWireExpectation [./conformance]
+domainFilePath [./node]
+emptyEffective [., ./config-fns]
+envModelTableWriteRefusal [.]
+foreignKeysOf [./conformance]
+isDomainName [., ./types]
+loadLocalConfig [./node]
+loadRemoteExec [./node]
+migrateConfigDirectory [./node]
+migrateConfigDocuments [./node]
+migrateEffectiveSnapshot [./one-time-migrations]
+migrateEnvModelsDecision [./node]
+migrateStoredDocuments [./one-time-migrations]
+parseDomain [., ./config-fns]
+parseDomainLoud [., ./config-fns]
+parseDomainSalvaged [., ./config-fns]
+planEnvModelTableWrite [.]
+readBundle [./node]
+readEffectiveWire [., ./config-fns]
+readModelRefusals [., ./fleet]
+readWorkersRows [.]
+resolveLegExpectation [./conformance]
+runConformance [./conformance]
+urlSeatPatterns [./one-time-migrations]
+validateDomain [./node]
+validateRemoteExec [./node]
+writeBundle [./node]
+writeDomainFile [./node]
+writeRemoteExec [./node]
+```
+
 ## 15.2.0 — 2026-10-29 — minor:文件层读不出 `config.d` 文档时契约自己交类型化的拒(`inspectBundle` + 闭集词 `CONFIG_DOCUMENT_REFUSAL_REASONS`)· 车道坐标判官 `isBlankCoordinate` 也从 `./execution-lanes` 子路径取(与包根同一只)· 安全合并规格 `memoryScopes` 行的 seam 显示串改叫 `MemoryEngine`
 
 > 档位(按发版纪律):**minor** —— 加性:新导出 7 个(包根 4:`CONFIG_DOCUMENT_REFUSAL_REASONS` / `ConfigDocumentName` / `ConfigDocumentRefusal` / `ConfigDocumentRefusalReason`;`./node` 2:`inspectBundle` / `BundleInspection`;`./execution-lanes` 1:`isBlankCoordinate`);

package/README.md

@@ -47,6 +47,40 @@ therefore shows only `zod`. Node built-ins only (`node:crypto`, `node:fs`).
 > zod 3, nested inside every zod-4 host). The move to zod 4 did not change what any schema accepts or produces —
 > the conformance corpus reads byte-identically on both — only the wording of validation errors (see CHANGELOG 11.0.0).
 
+## 升级指引:15.2.x → 16.0.0(BREAKING:执行车道集 · 设备入口必需且有文法 · 记忆方言词 mysql · 退役一只模型面组拒码 · 宿主状态时刻判形 · 本地配置单读口 · 文件契约的纯空白字段)
+
+- **改了什么**(逐条三问见 CHANGELOG 16.0.0):
+  ① worker 的 `runtime.execution.lane`(单值)换成有序车道集 `runtime.execution.lanes`(非空、去重,首项缺省);键归属、必需键、多租户与「只能一个副本」都按集判(后者读车道表新列 `singleReplica`);旧 `lane` 是墓碑。
+  ② device 车道的 `DEVICE_RELAY_URL` 进车道表必需栏,值只收 ws(s) 绝对 URL(无 userinfo / query / fragment)或字面 `none`;判官 `deviceRelayFlaws` / 规则句 `DEVICE_RELAY_RULE` / `DEVICE_RELAY_NONE` 在包根。
+  ③ `MEMORY_ENGINE_BACKENDS` = `file` / `pg` / `mysql`(`tidb` 退役,与店词同字)。
+  ④ `MODEL_PLANE_REFUSAL_CODES` 删 `config.summarize_model_missing` 与常量 `SUMMARIZE_MODEL_MISSING_CODE`;`planEnvModelTableWrite` 删 `fix_first` 结局(悬空的 summarize 留在回执里)。
+  ⑤ `HostStatus.ts` 判 RFC 3339 时刻;加可选 `HostStatus.heartbeatMs`(正整数毫秒,无缺省)。
+  ⑥ `./node`:`inspectBundle` / `BundleInspection` 删,单读口 `FileConfigStore.read()` → `FileConfigRead`;拒因闭集加 `too_deep`(过深的文档是一份文件层被拒的文档)。
+  ⑦ 本地文件契约 `RemoteExecSpec`(`config.d/remote-exec.json`)的非空串字段(镜像 / 命名空间 / 主机 / 用户名 / 序列号 / 工作目录 / 路径 …)对只含空白的值同空串一样拒 —— 问的是写闸对必需坐标问的同一只判官 `isBlankCoordinate`,空串与纯空白是同一句拒;接受的值逐字不变(不 trim)。
+- **存下来的数据**:跑一次一次性迁移 —— `npx @sema-agent/settings-schema migrate <config.d directory>`,或对中心的存量调 `migrateStoredDocuments` / `migrateEffectiveSnapshot`(`./one-time-migrations`)。
+  SS-M12 改写 15.x workers 行(`lane: L` ⇒ `lanes: [L]`;记忆方言 `tidb` ⇒ `mysql`;`env` 里的 `DEVICE_RELAY_URL` 搬进 device 行的 `coords` 或丢掉)。
+  **拒且原行留着**的行要人补:没有 `DEVICE_RELAY_URL` 的 device 行(写 `coords.DEVICE_RELAY_URL`:经中继拨 ⇒ 那个 ws(s) URL,直拨引擎 ⇒ `none`)、`lane` 与 `lanes` 并存的行、声明了 device 却把 `DEVICE_RELAY_URL` 写在 `secretEnv` 或 `env` 与 `coords` 两处都写的行(没声明 device 的行里它是惰性件,迁移丢掉)。
+- **部署环境**:`MEMORY_ENGINE_BACKEND=tidb` 改写成 `mysql`;device 车道的部署必须声明 `DEVICE_RELAY_URL`(URL 或 `none`)。
+- **部署序(device 行):先补、后升级** —— 15.2.x 的写闸把 `DEVICE_RELAY_URL` 当普通 env 收(它那时不在车道表里),所以可以在旧版本下先给每个 device 行写 `env.DEVICE_RELAY_URL`,
+  升级后 SS-M12 把它搬进 `coords`;不先补的 device 行升级后被迁移拒、原行留着,整域读函数读不出 workers 文档(按行读的 `readWorkersRows` 扣下那一行),直到补上为止。
+- **各消费方的读点**:
+
+  | 消费方 | 读点 | 动作 |
+  |---|---|---|
+  | server | 本地读腿:`getEffective` 抛了再问 `inspectBundle` 的两读 | 改调 `FileConfigStore.read()` 一次读,按 `kind` 分两支;拒因 `switch` 补 `too_deep` |
+  | server | 记忆方言:比较 `"tidb"` 的臂、目录行说明、`/v1/capabilities` 里报的记忆后端值 | 改 `"mysql"`(类型从本包来,tsc 红指路);能力面上的值随之改字,对外是 wire 改字 |
+  | server | 设备入口:自持的 `DEVICE_RELAY_NONE` 与 ws(s) 形判 | 改 import 本包 `DEVICE_RELAY_NONE` / `deviceRelayFlaws`,删自己那一份;缺席判交给车道必需键门(本表 device 行已含它) |
+  | server | `REMOTE_EXEC` 读成一个词 | 改读有序逗号表(首项缺省),与渲染器同窗;此前读不了两条车道的表 |
+  | server | 模型面组拒码 | 本包这一码的读点已为零,无动作 |
+  | web-admin | 渲染器 `REMOTE_EXEC = execution.lane`、向导与团队形对 `execution.lane` 的读 | `REMOTE_EXEC = lanes.join(",")`(`REQUIRE_EXECUTION_LANE=true` 不变);读 `lanes`(tsc 红指路) |
+  | web-admin | device 行表单 | 写 `coords.DEVICE_RELAY_URL`,提示读 `DEVICE_RELAY_RULE`、判读 `deviceRelayFlaws`;「撤中继」写 `none`,不是删键 |
+  | web-admin | 宿主状态写入口 `HostStatus.safeParse` | 上报方的 `ts` 须是 RFC 3339;`heartbeatMs` 可选,新鲜度窗公式在中心 |
+  | web-admin | 存量 workers | 跑 SS-M12(同一条迁移命令 / 函数) |
+  | cli | 自起引擎注的 `REMOTE_EXEC=host` | 一个词即一元表,无动作 |
+  | cli | 由本包车道表派生的「车道 → 必需键」 | 随表:device 多 `DEVICE_RELAY_URL`(无手抄一份,提货即生效;与钉版引擎的对拍随引擎版本) |
+  | 部署 | 车道清单 / compose 透传 | 随车道表重生成(device 多 `DEVICE_RELAY_URL`);`MEMORY_ENGINE_BACKEND=mysql` |
+  | server / 部署 | 本地配置模式:`config.d/remote-exec.json` 里的非空串字段(镜像 / 命名空间 / 工作目录 / shell / 主机 …)写成纯空白 | 16.0.0 起被拒 —— `loadRemoteExec` 抛、起服拒;出路 = 删掉那一键(可选字段)或给真值(必填字段);没有迁移 |
+
 ## 升级指引:15.1.x → 15.2.0(加性,零动作可升)
 
 三件,都是加性的,既有导出的答案逐位不变:
@@ -287,7 +321,7 @@ therefore shows only `zod`. Node built-ins only (`node:crypto`, `node:fs`).
   env-NAME ref. Every `provider` word is an execution-lane word (`EXECUTION_LANE_WORDS`, pinned at runtime and at
   compile time). **7.0.0** deleted the `remote-docker` variant: no engine read point ever ran it; a remote docker
   daemon is the `local-docker` lane pointed at it (`DOCKER_HOST`). **11.0.0**: retired lane VALUES have a tombstone,
-  `RETIRED_LANE_WORDS` (`[old, to, how]`, permanent, one hop); a worker spec's `runtime.execution.lane` or this file's
+  `RETIRED_LANE_WORDS` (`[old, to, how]`, permanent, one hop); a worker spec's `runtime.execution.lanes` entry or this file's
   `provider` naming one is refused with the way out (`retiredLaneWordRefusal(word)` is the one sentence; the issue code
   stays `invalid_value` / `invalid_union`).
 - **WorkerSpec execution lane + store (7.0.0, M-R2)** (`execution-lanes.ts`, also subpath `./execution-lanes`, + `types.ts`): the lane / store
@@ -297,53 +331,24 @@ therefore shows only `zod`. Node built-ins only (`node:crypto`, `node:fs`).
   `optionalSecretEnv`, copied from the engine with per-row coordinates), `STORE_BACKENDS`, `SESSION_BACKENDS`,
   `MEMORY_ENGINE_BACKENDS`. Web-admin's write gate (this package's `WorkerSpec.safeParse`), web-admin's env
   renderer and the engine's boot checks all read that one table, so they cannot drift. A worker declares
-  `runtime.execution = { lane, coords, secretRefs }` (non-secret coordinates as literals, secrets as host env-NAMEs,
-  keys ⊆ that lane's columns, required ones present and not blank — an empty or whitespace-only value counts as absent) and `runtime.store = { backend, session, memory,
+  `runtime.execution = { lanes, coords, secretRefs }` (16.0.0: an ordered, de-duplicated, non-empty lane set — the first one is the default;
+  non-secret coordinates as literals, secrets as host env-NAMEs, each key owned by a declared lane, every declared lane's required ones present
+  and not blank — an empty or whitespace-only value counts as absent; a coordinate with a grammar — `DEVICE_RELAY_URL`, a ws(s) URL or the
+  literal `none` — must also match it) and `runtime.store = { backend, session, memory,
   db? }` (+ `secretRefs.dbPasswordEnv`); an enabled worker must declare both. Cross-field refusals live in the
   schema as zod issues whose `path` names the field to change and whose message carries the way out: a
-  multi-tenant worker (`requirePrincipal`) on a lane that does not separate tenants (outlets computed from the
-  table), the `host` lane with more than one replica (`replicas` or `autoscaling.maxReplicas`), the `device` lane
-  without a SQL store that actually builds its coordinates (the engine's `device-durable-store`), SQL coordinates
+  multi-tenant worker (`requirePrincipal`) with a declared lane that does not separate tenants (one refusal per such lane; outlets
+  computed from the table), a lane whose row says `singleReplica` (host, device) with more than one replica (`replicas` or
+  `autoscaling.maxReplicas`), the `device` lane without a SQL store that actually builds its coordinates (the engine's `device-durable-store`), SQL coordinates
   without a SQL store (or the reverse), a memory backend that does not match the store, a multi-tenant worker
   without a SQL store, and the two session × store combinations the engine refuses at boot (`session: mysql` on a
-  `memory` store; a pg / tidb memory engine with `session: memory`). `WorkerSpec` is no longer a plain object schema — the worker-name rule is exported on its
+  `memory` store; a pg / mysql memory engine with `session: memory`). `WorkerSpec` is no longer a plain object schema — the worker-name rule is exported on its
   own as `WORKER_NAME`. `RESERVED_WORKER_ENV` (derived from a name → owning-field table) now reserves every
   env name those blocks produce, so the `env` / `secretEnv` escape hatches can no longer set a lane or a store.
-  Stored 6.x rows are lifted ONCE by `migrateWorkersDomain(doc)` (pure, idempotent; run it on the RAW workers
-  document before `parseDomain` — the 6.x fields are refused loudly by the 7.0.0 schema, not silently stripped)
-  or its file form `npx @sema-agent/settings-schema migrate-workers <workers.json> [--check]` (the package's
-  `bin`; writes only when every worker migrates). Workers it cannot lift (an enabled worker with no
-  `env.REMOTE_EXEC` — the migration never guesses a lane) come back in `refused` with the field to fix and the
-  `original` row verbatim — they are NOT in the migrated `doc`, so a caller that writes `doc` back must put each
-  `refused[].original` back at its `index` (or store it aside), or that worker's spec disappears. The final judgement
-  is per row (since 8.2.0 the same one for rows it rewrote and rows it left alone): every worker with a string name must read
-  as a one-row workers domain under the read side's own `WorkersConfig`, or it goes to `refused` — so each row of `doc`
-  reads on its own; what the whole-domain read can still refuse is a nameless entry (left as is) and the cross-row rules
-  (unique names / route prefixes).
-- **`migrate-workers` CLI: report shape + rejection signposts (7.0.1)** (`bin/settings-schema.mjs`, core in `cli.ts`):
-  `npx @sema-agent/settings-schema migrate-workers <workers.json> [--check]` prints exactly two lines on stdout (exit 0 / 1 / 3): line 1 is the
-  ONE conclusion line `outcome=<refused|applied|noop|pending> written=<true|false>`, line 2 is the JSON report (`event: "workers_domain_migrated"`,
-  `outcome`, `written`, `file`, the worker lists, `refused[]`). Only `applied` writes the file (`written` is derived from `outcome`; `pending` =
-  `--check` with changes). The list keys carry tense — `changed` / `dropped` exist **only when `written=true`**; when nothing was written
-  (refused / noop / pending) the same lists are `wouldChange` / `wouldDrop`, so a script that reads only stdout can never take a worker that was
-  not migrated for migrated. Exit codes are unchanged (0 applied or noop · 1 refused or the migrated document does not read as a 7.0.0 workers
-  domain, nothing written · 2 usage / unreadable / not JSON, empty stdout · 3 `--check` with changes).
-
-  | 7.0.0 stdout | 7.0.1 stdout |
-  |---|---|
-  | one JSON line | the conclusion line, then the JSON line (parse the **last** line) |
-  | `changed` (always) | `changed` when `written=true`, else `wouldChange` |
-  | `dropped` (always) | `dropped` when `written=true`, else `wouldDrop` |
-  | — | `outcome`, `written` |
-
-  **8.0.0**: `--check` and a real run go through ONE verdict (per-worker refusals → nothing to change ⇒ `noop` → the whole-domain final judgment →
-  changes); `--check` only decides whether the "changes" branch writes (`pending`) or not. A document the whole-domain judgment refuses (two workers
-  with one name …) is `outcome=refused` / exit 1 under `--check` too (7.x: `pending` / exit 3), and `refused[]` names the refused items in the
-  per-worker shape (`name` / `field` / `reason`; `name` is `null` for an entry that carries no string name) instead of being empty.
-
-  Rejections that a migration can lift carry ONE signpost sentence (a constant, `MIGRATION_SIGNPOST`): the seven deleted 6.x fields, and an
-  `env` / `secretEnv` key the migration moves or drops (the execution-lane keys incl. `REMOTE_EXEC` / `REQUIRE_EXECUTION_LANE`, and the store keys
-  `DB_BACKEND` / `MEMORY_ENGINE` / `MEMORY_ENGINE_BACKEND`). A reserved name the migration cannot move (`PORT`, `MODEL_*`, `MYSQL_*` …) carries none.
+  Stored rows of an older form are rewritten ONCE by the one-time migrations (`./one-time-migrations`: 6.x rows by SS-M4, 15.x rows by
+  SS-M12 since 16.0.0; the directory form is the package's `bin`, `npx @sema-agent/settings-schema migrate <config.d directory>`) — the
+  read side holds a row it cannot read (`readWorkersRows`) instead of lifting it on every read. The 7.0.0 one-off lift function and its
+  file subcommand were deleted in 11.0.0.
 - **Safety merge-spec** (`safety-merge-spec.ts`, subpath `./safety-merge-spec`): `SAFETY_MERGE_SPEC`, the ONE
   per-category merge/enforcement table every settings resolver reads (`mergeShape` / `minTrust` / `tighten` /
   `enforcement` / `fail`) — no consumer re-implements the merge law. 1.1.0 adds **member-level admission**:
@@ -484,7 +489,8 @@ therefore shows only `zod`. Node built-ins only (`node:crypto`, `node:fs`).
   identity) and `enabledEntryCount(doc)`. The env model table read once — `readEnvModelSlots` / `envModelTableDeclared` (`MODEL_ID` present and non-empty) /
   `buildEnvModelBaseline` — and the writer's plan `planEnvModelTableWrite({ env, target, decision, candidate, intent? })` (receipt by upstream id with landings
   `{name, id}`, `confirmKey` = the receipt's sorted JSON) with its one sentence `envModelTableWriteRefusal(plan)`. Group-refusal codes
-  `CATALOG_REPLACES_ENV_MODELS_CODE` / `SUMMARIZE_MODEL_MISSING_CODE` (tail of `MODEL_PLANE_REFUSAL_CODES`).
+  `CATALOG_REPLACES_ENV_MODELS_CODE` (tail of `MODEL_PLANE_REFUSAL_CODES`; the summarize code next to it was retired in 16.0.0 —
+  a role seat naming an entry the catalog does not serve reads as unset and falls back, so no reading refuses a model plane for it).
 - **Session web link** (`web-admin-session-url.ts`, main barrel): `webAdminSessionUrl(webBaseUrl, { worker, sessionId })` — the ONE
   template for a web-admin session link, `<webBaseUrl>/chat?agent=<worker>&session=<sessionId>`: both parts required (a link with only
   the session id lands on whichever worker the page picks and may not find it), each part `encodeURIComponent`-escaped, the base a
@@ -641,7 +647,7 @@ therefore shows only `zod`. Node built-ins only (`node:crypto`, `node:fs`).
   unchanged); `readModelRefusals(body)` reads either exit and narrows to `ModelRefusalsSignal` — the codes are CLOSED
   sets owned here, `MODEL_ENTRY_REFUSAL_CODES` (`config.model_no_brain`, `config.model_entry_invalid`) and
   `MODEL_PLANE_REFUSAL_CODES` (`config.default_model_missing`, `config.model_refused_name_minted`,
-  `config.model_route_endpoint_missing`, `config.gateway_fallback_without_primary`), and a code this package version
+  `config.model_route_endpoint_missing`, `config.gateway_fallback_without_primary`, `config.catalog_replaces_env_models`), and a code this package version
   does not know is dropped ("not said"). It is a diagnostic key, so its failure direction is "not said": an unknown
   code or a shape violation on the heartbeat never fails the announcement (the key drops to absent). Present ⇔ at
   least one reportable refusal; absence is read by the announced `version` — an engine that predates the key never
@@ -762,7 +768,7 @@ defaults. Each `config.d/<domain>.json` is exactly that domain's zod object.
 自 `1.0.0`(改名)起本包按**标准 semver** 发版;`0.x` 时代的「破坏性变更必 bump minor」规矩**已撤**
 (末条仅作历史注记)。判档看**消费方可见性**,不看 diff 大小:
 
-- **CLI 报告形的契约边界(7.0.1 起)**:`migrate-workers` 的 stdout = 结论行 + JSON;其中 `outcome` / `written` / `refused` 三字段是机读契约(再改按 minor),其余键与行形是诊断面,patch 可变(test 认定口径 2026-10-03:CLI 报告形不在 C-R197 包导出面)。机读请取最后一行解析。
+- **CLI 报告形的契约边界**:`migrate` 的 stdout = 结论行 + JSON;其中 `outcome` / `written` / `refused` 三字段是机读契约(再改按 minor),其余键与行形是诊断面,patch 可变(CLI 报告形不在包导出面)。机读请取最后一行解析。
 - **破坏性变更必 bump major**:字段/导出改名、改形(retype)、删除、默认值变更、校验收紧或放宽
   (例:`.passthrough()` → 默认 strip、宽读 → 严判)、枚举**重排**——凡是能让一个按上一版契约写的
   消费方在**运行期**变红、或让同一份配置解析出不同结果的改动;编译期同判,**唯一裁定例外** = 下一条的
@@ -778,7 +784,7 @@ defaults. Each `config.d/<domain>.json` is exactly that domain's zod object.
   但标记不豁免版号义务。每版 CHANGELOG 一节,git tag `v<version>` 同名。
 - **持久数据面的破坏性变更(例:7.0.0)**:类型 / API 面直接删改、零别名(消费方 tsc 红即通知);**存下来的数据**不会自己红,
   所以同版配三件:读到旧形即**响亮拒**(拒因指路迁移命令,不是被 zod 静默剥掉)、一只**一次性迁移**(纯函数、幂等、
-  表达不了就 refused 点名,不替运维猜)、以及一个**写明的删除窗**(7.0.0 的 `migrateWorkersDomain` 在 web-admin 接上迁移后的下一版删除)——
+  表达不了就 refused 点名,不替运维猜)、以及一个**写明的删除窗**(窗只登记在一次性迁移的登记表 `ONE_TIME_MIGRATIONS`;7.0.0 那一只一次性抬升函数已在 11.0.0 删)——
   绝不长成长命双读。
 - **历史注记(0.x 时代)**:0.x 下 `^0.7.0` 这类 range 只自动收 patch,故当年规矩是「破坏性必 bump
   minor,patch 只装 additive/修 bug/文档」。0.7.1(2026-07-10)曾携带两件预协调 BREAKING(撤 governance

package/conformance/VERSION

@@ -1 +1 @@
-15.2.0
+16.0.0

package/conformance/cases/c16-deep-nesting-205/expected.json

@@ -101,7 +101,7 @@
   },
   "localRoot": {
     "outcome": "rejected",
-    "stage": "hash",
-    "why": "本地腿的 version 是全量文件的内容哈希,200 层深度闸在它那里先炸;domains/wire 两腿不哈希"
+    "stage": "parse",
+    "why": "本地腿读的是文件:16.0.0 起一份文档嵌得比整棵目录的内容版本能算的深(根下 199 层)是这一份文档的文件层拒(`too_deep`,在读文档那一步),不再等到算内容哈希时才抛;domains/wire 两腿不读文件、不哈希"
   }
 }

package/conformance/cases/c16-deep-nesting-205/meta.json

@@ -1,5 +1,5 @@
 {
   "contributor": "contract",
-  "claim": "205 层嵌套的未知值:域解析照常(剥键扫描有深度上限,只报顶层那个键),但 local-root 腿的**内容哈希**有 200 层硬闸 ⇒ 它在 hash 层确定性地拒。同一份文档 domains/wire 两腿读得出、local 腿读不出 —— 这条差异必须是**报告里看得见**的,而不是某一腿悄悄回落。",
+  "claim": "205 层嵌套的未知值:域解析照常(剥键扫描有深度上限,只报顶层那个键),但 local-root 腿读文件:一份文档嵌得比整棵目录的内容版本能算的深 ⇒ 它在读文档那一步(文件层,parse)确定性地拒(16.0.0 前在算内容哈希那一步抛)。同一份文档 domains/wire 两腿读得出、local 腿读不出 —— 这条差异必须是**报告里看得见**的,而不是某一腿悄悄回落。",
   "firstRedOn": []
 }

package/conformance/cases/c50-s784-lane-host-legal/expected.json

@@ -65,7 +65,9 @@
                 "coords": {
                   "HOST_WORKSPACE_BASE": "/work"
                 },
-                "lane": "host",
+                "lanes": [
+                  "host"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,
@@ -108,7 +110,9 @@
                 "coords": {
                   "HOST_WORKSPACE_BASE": "/work"
                 },
-                "lane": "host",
+                "lanes": [
+                  "host"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,

package/conformance/cases/c50-s784-lane-host-legal/input.json

@@ -13,7 +13,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "host",
+              "lanes": [
+                "host"
+              ],
               "coords": {
                 "HOST_WORKSPACE_BASE": "/work"
               }

package/conformance/cases/c51-s784-lane-e2b-legal/expected.json

@@ -65,7 +65,9 @@
                 "coords": {
                   "E2B_TEMPLATE": "base"
                 },
-                "lane": "e2b",
+                "lanes": [
+                  "e2b"
+                ],
                 "secretRefs": {
                   "E2B_API_KEY": "HOST_E2B_KEY"
                 }
@@ -110,7 +112,9 @@
                 "coords": {
                   "E2B_TEMPLATE": "base"
                 },
-                "lane": "e2b",
+                "lanes": [
+                  "e2b"
+                ],
                 "secretRefs": {
                   "E2B_API_KEY": "HOST_E2B_KEY"
                 }

package/conformance/cases/c51-s784-lane-e2b-legal/input.json

@@ -13,7 +13,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "e2b",
+              "lanes": [
+                "e2b"
+              ],
               "coords": {
                 "E2B_TEMPLATE": "base"
               },

package/conformance/cases/c52-s784-lane-k8s-legal/expected.json

@@ -67,7 +67,9 @@
                   "K8S_RUNTIME_CLASS": "",
                   "K8S_SANDBOX_IMAGE": "registry.internal/sandbox@sha256:abc"
                 },
-                "lane": "k8s",
+                "lanes": [
+                  "k8s"
+                ],
                 "secretRefs": {
                   "K8S_TOKEN": "HOST_K8S_TOKEN"
                 }
@@ -114,7 +116,9 @@
                   "K8S_RUNTIME_CLASS": "",
                   "K8S_SANDBOX_IMAGE": "registry.internal/sandbox@sha256:abc"
                 },
-                "lane": "k8s",
+                "lanes": [
+                  "k8s"
+                ],
                 "secretRefs": {
                   "K8S_TOKEN": "HOST_K8S_TOKEN"
                 }

package/conformance/cases/c52-s784-lane-k8s-legal/input.json

@@ -13,7 +13,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "k8s",
+              "lanes": [
+                "k8s"
+              ],
               "coords": {
                 "K8S_SANDBOX_IMAGE": "registry.internal/sandbox@sha256:abc",
                 "K8S_NAMESPACE": "sandboxes",

package/conformance/cases/c53-s784-lane-ssh-legal/expected.json

@@ -67,7 +67,9 @@
                   "SSH_PORT": "2222",
                   "SSH_USER": "deploy"
                 },
-                "lane": "ssh",
+                "lanes": [
+                  "ssh"
+                ],
                 "secretRefs": {
                   "SSH_PRIVATE_KEY": "HOST_SSH_KEY"
                 }
@@ -114,7 +116,9 @@
                   "SSH_PORT": "2222",
                   "SSH_USER": "deploy"
                 },
-                "lane": "ssh",
+                "lanes": [
+                  "ssh"
+                ],
                 "secretRefs": {
                   "SSH_PRIVATE_KEY": "HOST_SSH_KEY"
                 }

package/conformance/cases/c53-s784-lane-ssh-legal/input.json

@@ -13,7 +13,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "ssh",
+              "lanes": [
+                "ssh"
+              ],
               "coords": {
                 "SSH_HOST": "deploy.internal",
                 "SSH_USER": "deploy",

package/conformance/cases/c54-s784-lane-adb-legal/expected.json

@@ -65,7 +65,9 @@
                 "coords": {
                   "ADB_SERIAL": "emulator-5554"
                 },
-                "lane": "adb",
+                "lanes": [
+                  "adb"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,
@@ -108,7 +110,9 @@
                 "coords": {
                   "ADB_SERIAL": "emulator-5554"
                 },
-                "lane": "adb",
+                "lanes": [
+                  "adb"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,

package/conformance/cases/c54-s784-lane-adb-legal/input.json

@@ -13,7 +13,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "adb",
+              "lanes": [
+                "adb"
+              ],
               "coords": {
                 "ADB_SERIAL": "emulator-5554"
               }

package/conformance/cases/c55-s784-lane-local-docker-legal/expected.json

@@ -66,7 +66,9 @@
                   "DOCKER_HOST": "tcp://docker.internal:2376",
                   "DOCKER_IMAGE": "registry.internal/sandbox:1"
                 },
-                "lane": "local-docker",
+                "lanes": [
+                  "local-docker"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,
@@ -110,7 +112,9 @@
                   "DOCKER_HOST": "tcp://docker.internal:2376",
                   "DOCKER_IMAGE": "registry.internal/sandbox:1"
                 },
-                "lane": "local-docker",
+                "lanes": [
+                  "local-docker"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,

package/conformance/cases/c55-s784-lane-local-docker-legal/input.json

@@ -13,7 +13,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "local-docker",
+              "lanes": [
+                "local-docker"
+              ],
               "coords": {
                 "DOCKER_IMAGE": "registry.internal/sandbox:1",
                 "DOCKER_HOST": "tcp://docker.internal:2376"

package/conformance/cases/c56-s784-lane-device-legal/expected.json

@@ -63,9 +63,12 @@
             "runtime": {
               "execution": {
                 "coords": {
+                  "DEVICE_RELAY_URL": "none",
                   "DEVICE_SUPERSEDE": "deny"
                 },
-                "lane": "device",
+                "lanes": [
+                  "device"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,
@@ -113,9 +116,12 @@
             "runtime": {
               "execution": {
                 "coords": {
+                  "DEVICE_RELAY_URL": "none",
                   "DEVICE_SUPERSEDE": "deny"
                 },
-                "lane": "device",
+                "lanes": [
+                  "device"
+                ],
                 "secretRefs": {}
               },
               "rateLimitRpm": 0,

package/conformance/cases/c56-s784-lane-device-legal/input.json

@@ -14,9 +14,12 @@
           },
           "runtime": {
             "execution": {
-              "lane": "device",
+              "lanes": [
+                "device"
+              ],
               "coords": {
-                "DEVICE_SUPERSEDE": "deny"
+                "DEVICE_SUPERSEDE": "deny",
+                "DEVICE_RELAY_URL": "none"
               }
             },
             "store": {

package/conformance/cases/c57-s784-g1-enabled-no-lane/meta.json

@@ -1,5 +1,5 @@
 {
   "contributor": "contract",
-  "claim": "G1:enabled 的 worker 没有 runtime.execution ⇒ 拒(拒因点名 runtime.execution.lane)。打「声明不了车道也能过闸、起服落进程内 stub、无手照回 completed」那条静默路(WA-49)。",
+  "claim": "G1:enabled 的 worker 没有 runtime.execution ⇒ 拒(拒因点名 runtime.execution.lanes —— 16.0.0 起车道集)。打「声明不了车道也能过闸、起服落进程内 stub、无手照回 completed」那条静默路(WA-49)。",
   "firstRedOn": []
 }

package/conformance/cases/c58-s784-g2-multitenant-host/input.json

@@ -14,7 +14,9 @@
           },
           "runtime": {
             "execution": {
-              "lane": "host"
+              "lanes": [
+                "host"
+              ]
             },
             "store": {
               "backend": "mysql",