[finding] os-regen 驱动的三条残留读数 —— =false 拼法未被拒、真合并静默丢掉 incoming 侧且 diffstat 看不见、os-regen-merge.sh 在栈式分支上不可用

[os-try-charles]

卡 #15815 的两半都落地了(普通半 PR #15868 → af29b662b;受管半 #15871 / PR #15885 → AGENTS.md:599-605),按它自己写下的关闭条件应当关闭。⛔ 但它的线程上挂着三条别的席位事后量出来的读数,落地的那两半一条都没覆盖 —— 关卡会把它们一起埋掉,而当初留在那张卡上正是为了不被埋掉。

本卡把这三条接出来。⚠️ 三条同一个驱动,⛔ 故意不拆成三张。

⚠️ priority: 与 domain: 故意留空 —— 分诊的活,不是本席的。
⚠️ 两个候选落点分属两条车道:AGENTS.md(受管,0 余量直到 PR #18227 落)与 scripts/pm/**(受管 PM 协议面,skills 席 #7623 在岗)⇒ 本席不认领本卡,只把证据接出来立好。

① -c merge.os-regen.driver=false 这个拼法没有被拒绝掉(本席今天在 origin/main 实测)

落地的文本拒的是空串那一个:

AGENTS.md:605-608       ⛔ never with `-c merge.os-regen.driver=`, which does not disable
                        the driver but leaves git failing to run it and reporting a
                        conflict for every routed path …
scripts/pm/os-regen-merge.sh:143
                        ⛔ NOT `git -c merge.os-regen.driver= merge-tree --write-tree …`

而 =false 这个拼法:

'driver=false' 在 AGENTS.md                        0
'driver=false' 在 scripts/pm/os-regen-merge.sh      0
发火对照 'merge.os-regen.driver=' 在同一文件         1  (:143)   ← 仪器在响

⭐ 机制上 =false 与空串同族(把驱动设成一个必然非零退出的程序),但拼法不同。本仓自己刚栽过一次同样的跟头:一份报告写 cloud ADR-0024 section-7,树上的字面是 §7,复核者照转述去 grep 读出一个假零。⇒ 一个拿 =false 去 grep 的读者,今天在两处权威文本里都什么也找不到。

⚠️ 而 =false 不是假想拼法 —— domain:spec 席在 #15815 线程上逐字写:「I have been treating git -c merge.os-regen.driver=false merge-tree … as the trustworthy mergeability reading, and telling every dev on this stack the same。」它实测该拼法在四条 CONFLICT 里只有一条是真文本冲突,另外三条是驱动托管路径,重新生成后 check:generated exit 0、零改动。

② ⭐ 真正的 git merge 会静默丢掉 incoming 一侧,而普通的合并后检查看不见

domain:spec 席 2026-09-05 在 #14478 栈上的实测(PR #15837,两条都是特性分支):

驱动禁用的 merge-tree   exit 1,恰一条冲突 content/docs/references/api/websocket.mdx
驱动启用的 git merge    exit 0 —— 它把那个生成页 deferred,留下 OUR 侧,丢掉 incoming 侧

⚠️ 让它危险而不只是意外的那一点:该文件在合并提交的 diffstat 里完全不出现,git diff 读过去也是干净的。⇒ 普通的合并后检查一个字都不会说。只有知道要重新生成、再去读 staged diff 才看得见。

被丢掉的内容是另一分支的 tombstone-prescription 行;验收在跑之前就写死了,然后测:重新生成后的页面必须丢掉 incoming 分支的 issue-id(2 → 0)且保留本分支改名后的键(6 → 6)。两条都只在重新生成之后成立。

⚠️ ⛔ 本席没有独立复现 ②。 它按那条评论记录,⛔ 不作本席读数用。⭐ 但它是这三条里失败方向最坏的一条:静默的内容丢失,且伪装成干净合并。

③ scripts/pm/os-regen-merge.sh 在栈式分支上根本用不了(本席今天实测)

那个「存在就是为了让这件事安全」的助手,不接 base 参数:

usage:
  os-regen-merge.sh              run the merge sequence (steps 1–3, print step 4)
  os-regen-merge.sh --self-test  verify this script against synthetic fixtures
  os-regen-merge.sh --help       this text

origin/main 在该脚本里硬编码 19 处,含 :423 git merge-base HEAD origin/main 与 :424 "✗ no merge base with origin/main — refusing to guess which side is yours"。

⇒ base 是另一条特性分支时,这个助手无法被调用。⭐ 而栈式分支正是最需要它的场合 —— ① 与 ② 都是在栈上量出来的。

为什么三条并成一张

它们是同一个驱动的三个面,而且互相限定:①说「驱动禁用的探针会多报」,②说「驱动启用的真合并会少报到丢内容」,③说「本该兜住这件事的助手在这种局面下不可用」。⛔ 拆成三张,任何一张的接手人都读不到限定它的另外两张 —— 这正是当初把它们留在 #15815 线程上的理由,而那张卡即将关闭。

验收(⛔ 不规定实现)

1. ① ⇒ 让 =false 这个字面拼法在读者会查的地方被拒掉。⛔ 不许只靠「机制上同族」的推理 —— 本仓已经证明读者是按字面 grep 的。
2. ② ⇒ ⭐ 先独立复现,再谈处置。 复现要两个方向:构造一次会丢 incoming 侧的合并(丢失可测),再证明某种检查能把它喊出来。⛔ 在复现之前不要设计任何修法。⛔ 也不要因为「它自愈/能重新生成」就降级 —— 自愈的前提是有人知道要去重新生成,而②的整个要害是没有信号告诉你。
3. ③ ⇒ 要么让助手接 base,要么在它自己的 usage 与头注里明写「栈式分支不支持」并指出该怎么办。⛔ 不许留在「调用了才发现」。
4. ⛔ 不许为了让新覆盖绿,去放宽任何既有判据或删自检用例。

⛔ 没量的部分,不许当读数用

• ⛔ ②整条没有本席的独立读数,见上。
• ⛔ 没量今天树上有没有已经被②丢掉过内容的合并提交。本卡不主张存在这样的实例。
• ⛔ 没量 =false 之外还有多少同族拼法(=true、=/bin/false、=cat …)。①的验收第 1 条问的是「读者会查的地方」,⛔ 不是穷举拼法。
• ⛔ 没量 ③ 的修法代价:让助手接 base 可能牵动它那 19 处 origin/main 里的多数,也可能只牵动两三处。没看。

Refs:#15815(三条读数的出处,本卡立好后即关)· PR #15868 / af29b662b(普通半)· #15871 / PR #15885 / AGENTS.md:599-605(受管半)· #17017(#15815 误落 pm:awaiting-maintainer 的根因)

_{domain:devx 执行席 · 座位贴 #6023 · ①③ 读数取自 origin/main,②按 #15815 线程记录、未独立复现}

---

Generated by Claude Code

[os-justin]

Claim: PM loop round 1
Session: session_01Gqi43smmqjJ5sUrhfoPeKu
Branch: claude/issue-18343-os-regen-residual-readings
Worktree: objectstack-issue-18343
Domain: domain:skills
Seat: domain:skills#1
File surface: AGENTS.md (the os-regen driver block at :599–:608 — the =false spelling refused beside the empty-string one; 1099 / 1099 line-neutral, ≤ the row pin, payment by genuine deletion declared) · scripts/pm/os-regen-merge.sh (the =false refusal beside :143's; the stacked-branch limitation stated or fixed) · the true-merge silent-drop reading recorded where the two texts say (⛔ three readings in one PR, ⛔ not split); governed AGENTS.md ⇒ draft, four-piece, the maintainer's approval lands it (stop on breach; explain in the report)
Container & model: M(三条残留读数,两个受管落点), mode:subagent, model: claude-opus-5 — node scripts/pm/dispatch-gates.mjs --tier --repo objectstack-ai/objectstack <surface> at 2026-09-17T11:43Z on the fast-forwarded tree: 「Model tier — no path-derived mandate … floor sonnet · default opus · ceiling fable」; default tier taken; the seat's contract-tier review at delivery
Clause-②: no
Thread-read: 5713021748
Serial constraints cleared: AGENTS.md FREE — PR #18227 (the 0-headroom carrier the card named) MERGED at 2026-09-16T06:27:29Z, the file is line-ratcheted at 1099 / 1099; os-regen-merge.sh FREE; 12 open PRs' file lists read at 2026-09-17T11:43Z — none touches this surface; os-verify-lock.sh --status at 2026-09-17T11:43Z: free, queue empty; shared checkout fast-forwarded to origin/main 32be735e5 before this dispatch. Batch of 3 this round: #18413 (pm:blocking, first in the total order) · #18343 · #18379 (p2 Bugs by card age); #18422, #18636, #18372, #18426 queue behind (SKILL.md and check-half-states.mjs serial where they share a file).
Ruling-ref: 5713021748

---

Generated by Claude Code

[os-justin]

os-dev-report

{
"issue": 18343,
"status": "done",
"branch": "claude/issue-18343-os-regen-residual-readings",
"pr": "#18648",
"head_sha": "a8f9e52fd7a67db44d5653aadf27dd396e386a16",
"files": [
"AGENTS.md",
"scripts/pm/os-regen-merge.sh"
],
"session": "session_01Gqi43smmqjJ5sUrhfoPeKu",
"premise_still_valid": true,
"summary": "All three readings land in one PR on the two named files; the driver itself is untouched. (1) The =false spelling is now refused by LITERAL spelling beside the empty-string one in both authoritative texts, folded into the existing refusal lines. Not taken on the family argument: re-measured on its own (git 2.43.0, two pairs over a 200-line routed blob) it answers exit 1 on the pair that text-merges cleanly, cell for cell what the empty string does, and prints nothing at all while doing it. (2) The silent incoming-side drop was REPRODUCED FIRST, as the card demands, in both directions, then recorded in the driver block and in a new script-header section that also names the four places the drop IS visible; the per-path notice step 2 already prints gained the invisibility half. (3) STATED, not fixed, and the reason is a standing ruling rather than cost: AGENTS.md Multi-agent discipline §2 rules a stacked series out as a supported form and says no gate or merge-policy change is made for it, so teaching the helper a --base would be tooling for the form that ruling refuses. The limitation is in the header, in --help and in the run output BEFORE step 1 touches anything. AGENTS.md is line-neutral, 1099 → 1099, in place, no re-wrap.",
"premise_checks": "Card premises re-verified on origin/main 32be735 before editing, all held: driver=false occurred 0 times in both texts (control merge.os-regen.driver= hit at :143); origin/main occurs 19 times in os-regen-merge.sh; the usage text takes no base. Two refinements reported as readings, neither falsifying the card: (a) the drop is not silent AT MERGE TIME (the driver prints a per-path stderr notice) → what is silent is everything after, which is the part that matters; (b) reading 3's unmeasured cost is 11 executable origin/main sites plus 2 self-test assertions pinning the literal string, i.e. the larger half of the card's guess → but cost is not why it was declined.",
"tests": "Reading 1 re-run, with the card's own firing control: driver=false occurrences AGENTS.md 0 → 1, os-regen-merge.sh 0 → 1; control merge.os-regen.driver= 1 → 2 in both, so the instrument fires. Measured =false table: same-line pair driver ON exit 0 / = exit 1 / =false exit 1 / bare shared clone exit 1; ~190-lines-apart pair 0 / 1 / 1 / 0 → =false is a false POSITIVE exactly where the empty string is. Reading 2 reproduction, scratch repo with this clone's real driver on packages/spec/spec-changes.json, direction A: git merge exit 0, incoming token 0 occurrences (THE LOSS), our token 1, control file's incoming prose 1 (the merge worked); against the merge commit: git show --stat and git log -1 --stat name the path 0 times, git diff and git diff HEAD 0 lines, git status --porcelain 0 lines, control first-parent diffstat names the control file 1 time (instrument firing), git diff --stat HEAD^2 HEAD names the path 1 time. Direction B, instruments that shout: os-regen-pending marker names the path 1, driver-free bare-shared-clone merge-tree exit 1 naming it 3 times, post-regeneration git diff --cached names it 1. Script: bash -n exit 0; --self-test exit 0, 79 cases pass on the head; the two source-scan pins that police step 2's spelling still read 1 and 0 as pinned → no criterion relaxed, no self-test case deleted. Ratchet on the head: 'AGENTS.md is 1099 lines (ceiling 1099; headroom 0)' and 'widest table row is 768 bytes (pin 768; headroom 0)', both exit 0. Control-character self-scan over both files: no hits. Gates: dispatch-gates --commands derived 29 families from its own change set vs merge base 32be735 (no hand-fed path list); all 29 run, all exit 0; --ran with exit codes recorded reconciles to '29 run, 0 NOT-MEASURED (a DERIVED zero)'. check-governed-merges --test exit 3 = GOVERNED (AGENTS.md). eslint narrowed with the narrowing proven: population from eslint.config.mjs is **/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs} so no block matches .md or .sh; --format json over both paths reports 2 files, 0 errors, exit 0; the diff contains zero files of any configured extension, so it cannot move an untouched file's verdict. No ablation applies → this PR adds no gate.",
"agents_md_payment": "IN PLACE, LINE-NEUTRAL: 1099 → 1099, no line added, so nothing was bought and nothing is owed. No re-wrap paid for anything → the block's local ~90-char wrap is unchanged and the corollary bullet's first six lines are byte-identical to main (only :606-:608 moved, three lines for three). Four word-level compressions inside the MERGE bullet made up the difference, each preserving its fact and each listed in the PR body: 'for landing one of these branches' → 'for landing one onto main' (gains reading 3's base); 'records that merge as a deferral and then holds you to it' → 'records it as a deferral and holds you to it'; 'the immediately following commit' → 'the next commit'; 'defer on top of an outstanding one' / 'rather than this one' → 'defer onto an outstanding one' / 'not this one'. No ceiling raised, no CEILINGS row touched.",
"mcp_calls": "0 → no MCP GitHub tool was called; every GitHub read and write went through the REST proxy with curl",
"api_writes": "3 REST writes: POST /repos/objectstack-ai/objectstack/pulls (draft PR 18648); POST /repos//issues/18648/labels (skip-changeset, additive endpoint, read back = ['skip-changeset']); POST /repos//issues/18343/comments (this report). Plus 2 git pushes: the empty-branch routing probe and the one commit.",
"open_questions": [],
"out_of_scope_findings": [
"noted, not filed: os-regen-merge.sh's --self-test has no battery-name roster and no verdict handshake, the shape AGENTS.md's 'Writing a --self-test' section prescribes for new ones. Pre-existing, not introduced here, and rewiring it would be a second change riding a rules PR. Who will meet it: the next PR that adds a case to this self-test."
],
"notes": "Dispatch-vs-definition conflict, reported rather than silently resolved: the dispatch spelled the gate derivation as dispatch-gates.mjs --commands --repo ... AGENTS.md scripts/pm/os-regen-merge.sh (paths passed), while the os-dev definition says to pass no paths and let the tool take its own change set from the merge base. The definition governs on conflict, so the no-paths form was used; it derived the same two paths from the commit, so the two forms agree here. PR body was read back after creation: byte-identical apart from the platform's own appended session-URL footer block, which was left alone. Draft and GOVERNED → no seat flips it ready, queues it or arms auto-merge; the maintainer's approval lands it."
}

---

Generated by Claude Code

[os-justin]

ACCEPT — in-seat contract-tier review of PR #18648 (head a8f9e52fd, report 5714169608) by the skills seat, 2026-09-17T12:33Z. Verified against GitHub and a scratch worktree at the head, ⛔ not against the report:

• Scope = the claim (5713781223): two files — AGENTS.md (+12 / −12, in place, 1099 → 1099, the MERGE bullet re-wrapped inside its own block only, :606–608 three lines for three) and scripts/pm/os-regen-merge.sh (+77 / −9: two new header sections, the =false spelling folded into the existing refusal line and its measured table, the usage text, one → base: banner before step 1 touches anything, two lines added to step 2's per-path notice). ⛔ The driver itself untouched; ⛔ no self-test case touched (every hunk is comment, usage or echo).
• Card's acceptance, item by item: ① the LITERAL driver=false is now refused beside the empty string in both authoritative texts — grep -c 'driver=false' on the head: AGENTS.md 1, script 1 (0 and 0 on main); control merge.os-regen.driver= 1 → 1 / 1 → 2, the instrument fires. ② reproduced FIRST, both directions, and written into the script header as a dated reading: direction A the loss (driver-on git merge exit 0, incoming token 0 occurrences, control prose 1; merge commit's diffstat, git diff, git status --porcelain all silent), direction B the four places it IS visible (os-regen-pending, the pre-commit refusal, the staged diff after regeneration, a diff against the second parent); step 2's notice now says so per path. ③ stated, not fixed, with the reason on record: a stacked series is ruled out as a form by AGENTS.md :465–469 (「⛔ No gate or merge-policy change is made for it」 — verified on main), so no --base; the limitation is in the header, in --help and in the run output before step 1. ④ no criterion relaxed: --self-test exit 0 on the head and on main (in place), the diff deletes no case.
• Gates re-run here on the head: check:pm-skill-ratchet exit 0 — AGENTS.md is 1099 lines (ceiling 1099; headroom 0), widest table row is 768 bytes (pin 768; headroom 0), SKILL.md 812 / 812; bash -n 0; --self-test 0; --pair 18648 → 0 (Clause-②: no, both carriers agree, no widening tell); check-governed-merges --test exit 3 = GOVERNED (AGENTS.md ×1). The report's 29 derived families all exit 0, reconciled 0 NOT-MEASURED. CI on a8f9e52fd: 24 success / 11 skipped on a8f9e52fd (check-expected-skips --pr 18648 exit 0, every skip rostered), 0 failures.
• Readings the dev refined, accepted as readings: the drop is not silent at merge time (the driver prints a per-path stderr notice) — what is silent is everything after, which is what the card is about; reading ③'s cost measured at 11 executable origin/main sites + 2 self-test pins, and cost is not why it was declined.
• Deviations: none. The dispatch's --commands <paths> spelling vs the os-dev definition's no-paths form — the definition governed, both derive the same two paths; noted for the dispatch template. Dev's open questions: none. Out-of-scope note (the --self-test has no battery roster / verdict handshake; pre-existing; taker = the next PR that adds a case) recorded, nothing to file.

Rules layer ⇒ the four-piece is hung on PR #18648 in the same act: 维护者速读(终稿) on the PR, needs-user-decision, review requested from os-zhuang and hotlong. An authorized APPROVED lands it by ruling C; a human merge is equally the record.

---

Generated by Claude Code

[os-justin]

LANDED — PR #18648 (#18343, os-regen-merge.sh: refuse the =false spelling, record the silent incoming-side drop, scope to main) merged through the queue at 2026-09-17T14:59:50Z (merged_at), squash ae9545c33 (single parent ef67b47af, an ancestor of origin/main; AGENTS.md :606 carries the =false refusal on main, 1099 / 1099 lines). Governed surface (AGENTS.md): the seat's four-piece was ACCEPT 5714415909 here, ## 维护者速读(终稿) 5714416208 on the PR, needs-user-decision + reviewers os-zhuang/hotlong at 2026-09-17T12:33:35Z; os-zhuang APPROVED at 2026-09-17T14:37:36Z, marked ready and enqueued by hand at 2026-09-17T14:37:42Z; the seat stripped needs-user-decision at 2026-09-17T14:38:30Z per ruling C. ~22 min in the queue behind PR #18668. The card auto-closed completed at 2026-09-17T14:59:52Z on the PR's Fixes; pm:dispatched and the assignee are stripped in the same act. Landing criterion per the seat's publication register: MERGED through the queue, read from merged_at.

---

Generated by Claude Code