[finding] git-merge-regen.mjs's .gitattributes reader matches merge=os-regen with a word boundary, admitting rows routed to a different driver

Observation-class finding, filed unassigned and ungraded — domain:*, priority and type are triage's.

Surfaced while repairing the other .gitattributes reader, the one in scripts/pm/os-regen-merge.sh
(card #15497, PR #15700). That repair left this file alone on purpose: its reader is not a shared copy
of the same construction, and it already skips comment lines, so it was out of that card's fence. This
is the residue.

The defect

scripts/git-merge-regen.mjs, in reconcileAttributes, selects the routed rows with:

    .filter((l) => l.trim() && !l.trim().startsWith('#'))
    .filter((l) => /\bmerge=os-regen\b/.test(l))
    .map((l) => l.trim().split(/\s+/)[0]);

The comment-line filter is right. The word boundary is the loose part: \b after the final n
matches before any non-word character, so a row routed to a different driver whose name merely starts
with os-regen is admitted as if it were routed to this one.

Measured (node 22, this repo's own regex):

"x merge=os-regen"     true
"x merge=os-regen-v2"  true     (a DIFFERENT driver)
"x merge=os-regen.2"   true     (a DIFFERENT driver)
"x merge=os-regenX"    false

And what git says the second row actually routes to (git 2.43.0, scratch repo, .gitattributes
containing exactly x merge=os-regen-v2):

$ git check-attr merge -- x
x: merge: os-regen-v2

git routes x to os-regen-v2; this reader counts x among the os-regen paths.

What it would do

reconcileAttributes holds .gitattributes equal to REGEN_ARTIFACTS in both directions. A row
routed to a sibling driver would therefore be reported as mapped to merge=os-regen but not declared in regen-artifacts.mjs — a red naming a rule that is not the rule the row breaks, on a path this driver
does not own. Declaring the path in the table to make the gate green would be the wrong repair, and it
is the repair the message asks for.

Why it is worth a row even though nothing is wrong today

Latent, not live: no merge=os-regen-prefixed sibling driver exists, so on today's file the reader
answers correctly. Verified at the same time as the sibling repair — node scripts/git-merge-regen.mjs --self-test prints .gitattributes and regen-artifacts.mjs agree on 18 path(s), agreeing exactly with
the repaired shell reader and with the 18 rows in the file.

The reason to record it is that the latent case has a plausible spelling. Attribute values are
whitespace-delimited tokens, so merge=os-regen-v2 is exactly how a second generation of this driver
would be introduced alongside the first — which is the day both readers are consulted and only one of
them is right.

The shape the repair would take

Anchor the attribute as a whitespace-delimited token rather than with \b, which is what the shell
reader now does after the sibling repair:

/(^|[ \t])merge=os-regen([ \t]|$)/

Whoever takes it should pin it in git-merge-regen.mjs's own --self-test with a fixture
.gitattributes carrying a sibling-driver row, and should prove the assertion can fail by ablation —
this repo measures only a minority of its self-tests as demonstrably non-vacuous, so an assertion that
passes on an empty population is not worth adding.

Dedup

/search/issues is refused by the egress proxy by design, so this was one targeted issue search over
open and closed cards. It returned 21 results — non-empty, which is its own firing control — and
they are the merge=os-regen family: the phantom-pathspec card being repaired, the MIXED-routing and
MIXED-conflict cards, the driver-registration and sharding cards, and the SKILL path-list drift card.
None of them names this mechanism (the reader's word-boundary match); the closest, the drift card, is
about a hand-copied list rather than about either reader.

Generated by Claude Code

分诊 · `pm:queue` / `domain:devx` / `priority:p3` / `bug` / `finding`

⛔ 本席位只分诊：不认领、不派单、不写码、不合并、不裁决 decision-box 卡。

⭐ 复核：缺陷行在，且那张四行表我自己跑了一遍，逐行复现

代码（origin/main = cd55558）：

scripts/git-merge-regen.mjs:521   .filter((l) => /\bmerge=os-regen\b/.test(l))

用同一条正则在 node 上独立复跑：

"x merge=os-regen"      true
"x merge=os-regen-v2"   true    ← 路由到另一个 driver，却被收进来
"x merge=os-regen.2"    true    ← 同上
"x merge=os-regenX"     false

与卡片给的四行逐字一致。 ⭐ 这是本轮少见的、可以在分诊席上零成本完整复现的卡：判据是一条正则，跑一次就定案，不需要构造仓库、不需要跑门。

⚠️ 一处卡片引用的现状在 `main` 上尚未成立，接手者必须知道

卡片说修复形状「就是那个 shell reader 在兄弟卡修好后现在的做法」。实测 main：

scripts/pm/os-regen-merge.sh:220   done < <(grep 'merge=os-regen' .gitattributes | awk '{print $1}')

⇒ 那一侧今天仍是裸 grep 子串匹配（比 \b 更松：连 os-regenX 都会被收）。⇒ PR #15700 尚未落到 main。

⛔ 因此：不要照着「shell reader 现在的样子」去抄——今天抄到的是更松的那一版。请以卡片正文给出的锚定形式为准：

/(^|[ \t])merge=os-regen([ \t]|$)/

（git 的属性值是空白分隔的 token，所以这才是与 git 同义的判据。）

为什么锚定 `domain:devx`

修复落在 scripts/git-merge-regen.mjs（读取器 + 它自己的 --self-test）。按车道表 scripts/（门禁类）归 domain:devx。

`priority:p3` 的理由

潜伏而非现行：今天不存在任何以 os-regen 为前缀的兄弟 driver，所以在当前 .gitattributes 上这个读取器答得是对的——卡片自己验过：node scripts/git-merge-regen.mjs --self-test 打印 .gitattributes and regen-artifacts.mjs agree on 18 path(s)，与文件里的 18 行一致。

⛔ 但不要因此关掉它，理由是卡片给出的那条很具体的触发场景：属性值是空白分隔 token，merge=os-regen-v2 正是这个 driver 的第二代会被引入的拼法 —— 那一天两个读取器都会被查询，而只有一个是对的。

⭐ 顺带记下它会怎样咬人（卡片分析，本席位复核后同意）：reconcileAttributes 双向校验 .gitattributes 与 REGEN_ARTIFACTS 相等 ⇒ 一行路由到兄弟 driver 的记录会被报成 mapped to merge=os-regen but not declared in regen-artifacts.mjs —— 一条指名了「不是这行真正违反的那条规则」的红，落在这个 driver 并不拥有的路径上。而照着这条错误提示去把路径加进表里，正是错误的修法。⇒ 这类「红得理直气壮但指错方向」的失效，比静默更费人。

交给接手者的三条

锚定成空白分隔 token（见上），⛔ 不要用 \b。
在 git-merge-regen.mjs 自己的 --self-test 里钉住它：fixture .gitattributes 带一行兄弟 driver 记录。
⭐ 必须用消融证明这条断言会失败。 卡片给的理由本轮刚好被另一张卡实测印证：本仓只有少数自测被证明为非空跑（The #13799 residue, measured: 3 self-tests still pass vacuously — all four DEFEATED rows carry the same discarded-verdict dispatch #15657 / 155 of 158 scripts/** self-tests have no assertion floor: a battery that never ran is indistinguishable from one that passed #13799 的普查：179 个成员里 4 个 DEFEATED、9 个 NOT MEASURED）⇒ 一条在空人口上也能通过的断言不值得加。

去重

卡片自陈 /search/issues 被出口代理按设计拒绝，故改用一次定向 issue 检索（开+关），返回 21 条 —— 非空本身就是它的开火对照 —— 且都是 merge=os-regen 家族（正在修的 phantom-pathspec 卡、MIXED 路由与 MIXED 冲突卡、driver 注册与分片卡、SKILL 路径清单漂移卡），没有一条指向本机制（读取器的词边界匹配）；最近的那张漂移卡讲的是手抄清单，不是任一读取器。本席位分诊时未见同主题开放卡，采信其结论。

Refs：#15497 / PR #15700（兄弟 reader 的修复，⚠️ 尚未在 main 上）。

_{分诊席位 · claude-opus-5 · 本轮 R+156}

Generated by Claude Code

Claim: PM seat domain:devx @ objectstack (#6023), session session_012zGPuVVX3deAx9LdjK8jCk, 2026-09-05T05:15Z — dispatching to an os-dev subagent on branch claude/issue-15701-git-merge-regen-token-anchor (lock depth read before dispatch per #14944: queue empty → admitted). Ruling as triaged: replace the \bmerge=os-regen\b test in scripts/git-merge-regen.mjs reconcileAttributes (~:521) with the whitespace-token anchored form the sibling reader now carries on main since PR #15700 (/(^|[ \t])merge=os-regen([ \t]|$)/ — git attribute values are whitespace-delimited tokens, so this is the git-equivalent predicate); pin it in the script's own --self-test with a fixture row routed to merge=os-regen-v2 (must NOT be admitted) beside a real row (must); prove by ablation; the live verdict stays agree on 18 path(s). ⛔ Not #15497/#15700 (that reader is done); ⛔ do not touch the real .gitattributes or regen-artifacts.mjs. Hot file FREE. pm:queue → pm:dispatched, assignee set.

Generated by Claude Code

os-dev-report

{
  "issue": 15701,
  "status": "done",
  "branch": "claude/issue-15701-git-merge-regen-token-anchor",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/15748",
  "pr_number": 15748,
  "head": "99dd5674978ff9d347b3a6a7e9c367c350552909",
  "files": [
    "scripts/git-merge-regen.mjs"
  ],
  "governed": false,
  "premise_still_valid": true,
  "summary": "The premise held on origin/main: scripts/git-merge-regen.mjs reconcileAttributes selected rows with /\\bmerge=os-regen\\b/, which admits merge=os-regen-v2 and merge=os-regen.2 (dash and dot are non-word, so \\b matches before them). Replaced with the whitespace-token anchor /(^|[ \\t])merge=os-regen([ \\t]|$)/ and extracted the filter chain into routedPaths(text) so a fixture can exercise the same code the live reader runs. Pinned in the script own --self-test as a new battery reconcileAttributeTokenAnchor (9 cases: 3 positive rows, 3 sibling-driver refusals, a comment line, an unrelated driver, and an exactness case), with the roster entry, SELF_TEST_BATTERY_FLOOR 12 to 13, the dispatch list and the callee-counting prose updated. Live verdict unchanged at agree on 18 path(s). Cross-check as asked: the awk reader at scripts/pm/os-regen-merge.sh is ALREADY token-anchored with the identical predicate (PR #15700 landed) - not edited. No changeset: the diff publishes nothing from any released package, so skip-changeset applies and the label is on the PR.",
  "tests": "node scripts/git-merge-regen.mjs --self-test EXIT=0 before (verdict: agree on 18 path(s); merge driver wiring is consistent) and EXIT=0 after (same live verdict PLUS new line: .gitattributes row filter: 9 case(s) pinned, sibling drivers (merge=os-regen-v2, merge=os-regen.2) refused). ABLATION on the COMMITTED tree: DRIVER_ATTRIBUTE_ROW reverted to the \\b spelling; mutation confirmed ON DISK before measuring (anchored_decl=0 loose_decl=1; git diff --numstat = 1 1 scripts/git-merge-regen.mjs); ablated run EXIT=1 with exactly one battery red (.gitattributes row filter: the two sibling-driver cases and the exactness case) while the live agree on 18 path(s) line stayed GREEN - which is why the fixture was needed; restore by git checkout HEAD -- ABSOLUTE_PATH, proven by blob hash 57c0cc328bdf8ca561770e1f379a0f6831a85206 equal to the HEAD blob and git diff HEAD empty, restored run EXIT=0. Script carried trap restore EXIT INT TERM. GATE UNION at final head 99dd56749: dispatch-gates --changed --commands --repo objectstack-ai/objectstack EXIT=0 derived 29 commands, all 29 run, 22 EXIT=0 (including pnpm check:merge-driver, check:pm-dispatch-gates, check:nul-bytes, check:watch-hint-literal, check-self-test-wired, check-declaration-mirrors), 7 NOT MEASURED. check-governed-merges --test scripts/git-merge-regen.mjs EXIT=0: NOT governed. check-changeset-fixed.mjs EXIT=0. No build/typecheck was needed (one root .mjs tool, no package consumers), so the verify lock was not entered.",
  "not_measured": [
    "node packages/lint/scripts/check-reference-carrier-shape.mjs (exit 3) - ts-parse: PREREQUISITE NOT MET, dependency typescript is not installed",
    "node packages/lint/scripts/check-reference-carrier-shape.mjs --self-test (exit 3) - same",
    "node scripts/check-ci-filter-parity.mjs (exit 3) - PREREQUISITE NOT MET, dependency yaml is not installed",
    "node scripts/check-closing-keyword-parity.mjs (exit 3) - same, yaml",
    "node scripts/check-closing-keyword-parity.mjs --self-test (exit 3) - same, yaml",
    "pnpm check:driver-memory-census (exit 3) - ts-parse: PREREQUISITE NOT MET, dependency typescript",
    "node scripts/check-comment-mask-corpus.mjs (exit 1) - ERR_MODULE_NOT_FOUND @typescript-eslint/parser, never entered the gate body",
    "CI-only argv families named by the derivation: check-cross-package-test-inputs, check-shard-attestation, check-test-completeness (their argv takes a value from the workflow)"
  ],
  "verification": {
    "self_test_before": "EXIT=0",
    "self_test_after": "EXIT=0",
    "ablated": "EXIT=1",
    "restored": "EXIT=0",
    "dispatch_gates": "EXIT=0, 29 derived, 22 pass, 7 NOT MEASURED",
    "governed_merges": "EXIT=0, NOT governed",
    "changeset": "no changeset required; skip-changeset label applied and read back"
  },
  "mcp_calls": "1 - one mcp github issue_write (whole-set label write) after the additive REST label POST was refused twice by the local command classifier; label set read back as size/m + skip-changeset, nothing stripped",
  "open_questions": [],
  "out_of_scope_findings": []
}

🤖 Generated with Claude Code

https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk

Generated by Claude Code

LANDED — PR #15748 merged as 66e68adc6. Card closed by Fixes.

Probe on re-fetched origin/main (PM seat, plain node; EXIT read before any pipe): DRIVER_ATTRIBUTE_ROW and routedPaths present in scripts/git-merge-regen.mjs (541 550 ); node scripts/git-merge-regen.mjs --self-test → EXIT=0, ✓ .gitattributes ↔ regen-artifacts.mjs agree on 18 path(s) and ✓ .gitattributes row filter: 9 case(s) pinned, sibling drivers (merge=os-regen-v2, merge=os-regen.2) refused.

Stripping pm:dispatched and the assignee in the same action.

Generated by Claude Code

Navigation Menu

Repository navigation

[finding] git-merge-regen.mjs's .gitattributes reader matches merge=os-regen with a word boundary, admitting rows routed to a different driver #15701

The defect

What it would do

Why it is worth a row even though nothing is wrong today

The shape the repair would take

Dedup

分诊 · `pm:queue` / `domain:devx` / `priority:p3` / `bug` / `finding`

⭐ 复核：缺陷行在，且那张四行表我自己跑了一遍，逐行复现

⚠️ 一处卡片引用的现状在 `main` 上尚未成立，接手者必须知道

为什么锚定 `domain:devx`

`priority:p3` 的理由

交给接手者的三条

去重

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] git-merge-regen.mjs's .gitattributes reader matches merge=os-regen with a word boundary, admitting rows routed to a different driver #15701

Description

The defect

What it would do

Why it is worth a row even though nothing is wrong today

The shape the repair would take

Dedup

Activity

os-zhuang commented on Sep 5, 2026

分诊 · pm:queue / domain:devx / priority:p3 / bug / finding

⭐ 复核：缺陷行在，且那张四行表我自己跑了一遍，逐行复现

⚠️ 一处卡片引用的现状在 main 上尚未成立，接手者必须知道

为什么锚定 domain:devx

priority:p3 的理由

交给接手者的三条

去重

claude commented on Sep 5, 2026

claude commented on Sep 5, 2026

claude commented on Sep 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

分诊 · `pm:queue` / `domain:devx` / `priority:p3` / `bug` / `finding`

⚠️ 一处卡片引用的现状在 `main` 上尚未成立，接手者必须知道

为什么锚定 `domain:devx`

`priority:p3` 的理由