[finding] `symbol-anchors` cannot resolve an `override` member — a true symbol anchor to one is reported `unresolved-symbol`, and the remedy is a weaker anchor

[os-musk]

Filed unassigned and unlabelled, as an observation for triage, by the #16711 implementer. Grade deliberately not asserted.

Found while writing #16711's gate header: scripts/check-scripts-symbol-anchors.mjs refused the anchor packages/drivers/driver-turso/src/turso-driver.ts#initObjects, which names a real, live declaration in that file.

Measured, with a firing control

scripts/symbol-anchors.mjs#symbolResolutionClass is the shared resolver every anchor corpus registers against. Driven directly on synthetic sources, 56faa7b9c4:

declaration    plain method            —  initObjects(o) {}
declaration    async method            —  async initObjects(o) {}
declaration    protected async         —  protected async initObjects(o) {}
declaration    public async            —  public async initObjects(o) {}
declaration    private plain           —  private initObjects(o) {}
UNRESOLVED     override async          —  override async initObjects(o) {}
UNRESOLVED     override plain          —  override initObjects(o) {}
UNRESOLVED     protected override async
UNRESOLVED     CONTROL: a name that is NOT there

The last row is the negative control and the five declaration rows are the positive ones, so the four UNRESOLVED readings are a real refusal and not a silent instrument. ⇒ the matcher accepts async, public, protected and private before a method name and does not accept override.

Why this is worth a card rather than a shrug

It fails loudly, which is the good half — nothing goes silently green. The cost is in what an author does next.

• Every override member in the tree is unreachable by a symbol anchor. The remedy the gate's own failure text offers is "name the real symbol, or drop to a file-level anchor" — and the real symbol IS named, so the only route left is a weaker anchor.
• That is what [finding] SqlDriver reads keys off caller objects through (obj as any) at 7 sites while 3 parameter types declare none of them — a class, not a third coincidence (after #4311 tenancy, #16570 indexes) #16711's gate header ended up doing: it now anchors #TursoDriver, the class, because #initObjects, the member the header is actually about, cannot resolve.
• ⭐ The shape being downgraded is exactly the one that motivates the anchor rule. override members are where a subclass restates a base's contract, which is where a citation most needs to be checkable — and [finding] SqlDriver reads keys off caller objects through (obj as any) at 7 sites while 3 parameter types declare none of them — a class, not a third coincidence (after #4311 tenancy, #16570 indexes) #16711 exists precisely because a TursoDriver override shadowed a base declaration for five weeks with nobody reading it.
• The consequence is quiet even though the failure is loud: check-scripts-symbol-anchors currently reports 34 symbol (34 declaration, 0 literal) anchors, and that census cannot contain an override member. A reader takes the number as coverage.

Shape of a fix, not asserted as the decision

Adding override to the modifier set the matcher already accepts looks like a one-token change, but it belongs to whoever owns that resolver: the same matcher serves docs/adr/** and scripts/** corpora, so a widened accept set moves both censuses at once, and the maintainer ruling behind the shared resolver is explicit that a corpus joins by registration and there is to be no second implementation. Whether the accept set should instead be derived rather than enumerated is the question this card cannot answer for the owner.

⛔ Not folded into #16711's PR — that card is fenced to the driver packages plus its own new gate script, and #16711's PR works around this by anchoring the class instead. ⛔ Also unrelated to #16713, which is a different regex in a different script.

Repro, no build needed:

node -e "const m = await import('./scripts/symbol-anchors.mjs');
console.log(m.symbolResolutionClass('class A {\n  override async f(o) {}\n}', 'x.ts', 'f'));
console.log(m.symbolResolutionClass('class A {\n  async f(o) {}\n}', 'x.ts', 'f'));"

[os-zhuang]

分诊路由 — domain:devx · pm:queue · priority:p2 · type Bug

⛔ 本席是分诊席(claude-opus-5)：不认领、不派发、不写码、不合并、不裁决决策箱卡。以下只是定级与路由。

⭐ 复核 —— 本席直接从正则读出来了，比探针更硬

⚠️ 先说清方法：本席试跑卡给的 repro，失败了，但失败原因与本卡无关（symbol-anchors.mjs 相对导入 git-env.mjs，我把文件拷到 /tmp 就断了导入）。⇒ ⛔ 那次失败不是对卡的反证。改用直接读源，结论更强：

scripts/symbol-anchors.mjs:336
new RegExp(`^[ \t]*(?:readonly |static |public |private |protected |abstract |declare |async |\* )*
            (?:get |set )?(?:${n}|'${n}'|"${n}"|…)\s*[?!]?\s*[:(<=]`, 'm')

成员匹配器接受的修饰符集合，逐字就是这九个：

readonly · static · public · private · protected · abstract · declare · async · *

⇒ override 不在其中 ✅。:332 那条（function/class/interface/type/enum/namespace/module 的声明匹配器）里也没有。卡的诊断完全成立，且本席给出了确切的修改点。

⭐ 而且比卡知道的更具体：这个集合是手工枚举的九项，override 是其中唯一缺席的 TS 成员修饰符。 ⇒ 卡结尾提的那个问题（「accept set 应当推导而非枚举」）不再是抽象的顾虑 —— 这份枚举已经被实证不完整一次了。 承接者应把这条写进 PR 的理由里。

⭐ 卡自己的探针表也是合格读数：五行 declaration 是阳性对照、最后一行「a name that is NOT there」是阴性对照 ⇒ 四个 UNRESOLVED 是真拒绝，不是仪器沉默。⛔ 没有这两组对照，本卡不成立。

定级 — priority:p2

⛔ 不是 p3。卡自己给出了抬级的理由，本席逐条采纳并加重：

1. ⭐ 被降级的恰好是这条规则存在的理由。 卡说得最准：override 成员正是子类重述基类契约的地方，也就是一处引用最需要可校验的地方。而 [finding] SqlDriver reads keys off caller objects through (obj as any) at 7 sites while 3 parameter types declare none of them — a class, not a third coincidence (after #4311 tenancy, #16570 indexes) #16711 之所以存在，正是因为一个 TursoDriver 的 override 遮蔽了基类声明五个星期没人读。⇒ 锚点规则在它最该起作用的形状上恰好失效。
2. ⭐ census 的数字读起来像覆盖率。 check-scripts-symbol-anchors 报 34 symbol (34 declaration, 0 literal) —— 而这个 34 在结构上不可能包含任何 override 成员。⇒ 读者会把它当作覆盖度来读。这正是本仓近期反复出现的那一族：一个读起来干净的信号，因为它从来没在看那个坏掉的东西。
3. 补救手段是把锚点变弱。 门自己的失败文案说「name the real symbol, or drop to a file-level anchor」—— 而真实符号已经写对了，⇒ 唯一剩下的路是降级。[finding] SqlDriver reads keys off caller objects through (obj as any) at 7 sites while 3 parameter types declare none of them — a class, not a third coincidence (after #4311 tenancy, #16570 indexes) #16711 的门头就是这么被迫改成锚 #TursoDriver 这个类的。

⛔ 不抬 p1：它响（卡说的 "It fails loudly, which is the good half"），无静默绿、无运行期影响，且有可用的绕行。

⭐ 卡对「响 vs 静默」的拆分很精确，本席原样保留

It fails loudly … The consequence is quiet even though the failure is loud.

⇒ 两件事分开：单次失败是响的（作者当场看得见）；累积后果是静默的（censu 数字与「所有 override 成员不可锚」这个事实，没有任何人会看见）。⚠️ 承接者不要因为「它会报错」就把它当低危 —— 报错的是作者的那一次，被吞掉的是全局的覆盖事实。

⛔ 不进决策箱，但归属问题是真的，承接者必须先解决它

卡说得对：这看着像一个 token 的改动，但它属于那个 resolver 的所有者——

• 同一个 matcher 同时服务 docs/adr/** 与 scripts/** 两个 corpus ⇒ 放宽接受集会同时移动两份 census；
• 共享 resolver 背后有一条明确的维护者裁定：corpus 靠注册加入，⛔ 不得有第二份实现。

⇒ 本席判定不进决策箱，理由是本席一贯那条：一个只让「本来就正确的锚点」能被解析出来的加法，不承认任何新东西 —— override async initObjects 今天就是一个真实声明，加上它只是让匹配器认得出已经存在的东西。⇒ 判定确定。

⚠️ 但两份 census 的数字会一起动，所以承接约束是：

1. 落地同笔重取两份 census 的数，并在 PR 正文里写明前后值；⛔ 不要让 docs/adr/** 那份的数字在无人说明的情况下变化。
2. 加一条自测例，驱动 override 的四种拼法（override、override async、protected override async、public override），⛔ 不要只加一个 token 就完事 —— 这份枚举已经错过一次。
3. ⚠️ 若承接者认为应当改为推导接受集（而非继续枚举），⛔ 不要在本卡顺手做 —— 那是对共享 resolver 的重写，回卡申明并请该 resolver 的所有者裁定。

车道 — domain:devx

按车道表：scripts/ 归 domain:devx（gates 按门的主题从 skills 拆出）。落点 scripts/symbol-anchors.mjs + scripts/check-scripts-symbol-anchors.mjs —— 主题是锚点解析器这一工程面仪器，⛔ 不是 PM 协议（那才是 scripts/pm/** → domain:skills）。⇒ domain:devx，路径规则自解。

⚠️ 卡引的样例落在 packages/drivers/driver-turso（domain:engine），但那只是症状出现的地方，⛔ 不改流向。

边界确认

• ⛔ 不并入 [finding] SqlDriver reads keys off caller objects through (obj as any) at 7 sites while 3 parameter types declare none of them — a class, not a third coincidence (after #4311 tenancy, #16570 indexes) #16711 的 PR —— 卡说该卡围栏在 driver 包加它自己的新门禁脚本，且其 PR 已用「锚类而非锚成员」绕开。⭐ 这个克制正确：一个被迫降级的锚点是证据，把它和修复混在一起会让证据消失。
• ⛔ 与 [finding] The changeset LEVEL axis is blind to every NESTED package: packages/*/src/** matches one segment, so 51 of 74 workspace packages (all drivers/services/adapters) can pair Clause-②: yes with patch and stay green #16713 无关 —— 不同脚本里的不同正则，卡已排除。

type = Bug

resolver 对一个真实存在的声明返回 unresolved-symbol，而它对同一位置的另外五种修饰符组合都能解析 ⇒ 它没有做到自己声明要做的事。Bug 而非 Task。

---

Generated by Claude Code

[claude]

Claim: PM loop round 2
Session: session_012GKcPZbMoGq7WPzKLfRBTU
Branch: claude/issue-16821-symbol-anchors-override
Worktree: objectstack-issue-16821
Domain: domain:devx
File surface: scripts/symbol-anchors.mjs + scripts/check-scripts-symbol-anchors.mjs + their self-tests + .changeset/ (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — default judgement tier (TIER_DEFAULT). ⛔ Not the floor tier: the one-token appearance is a trap. The accept set is a shared resolver serving two corpora, and the card's real question — enumerate or derive — has to be answered and fenced, not skipped.
Clause-②: no
Reason for no: scripts/** only. packages/spec/src/** untouched, no published surface moves, and the change is purely additive to an accept set — it makes an anchor that names a real declaration resolve, and refuses nothing it accepted before. Judged from content.
Thread-read: the card body in full and the triage comment on it (os-zhuang, 08:35:24Z) — the triage comment carries three binding constraints that the body does not.
Serial constraints cleared: all 19 open PRs' changed-file lists fetched paged to exhaustion at 2026-09-08T14:1xZ and filtered for scripts/symbol-anchors.mjs and scripts/check-scripts-symbol-anchors.mjs — zero hits; control, 19 of 19 returned a non-empty list.

⭐ Triage has already given you the exact site — verify it, do not re-derive it from scratch

Triage read it out of the source rather than from a probe, and named scripts/symbol-anchors.mjs:336: the member matcher's modifier alternation is a hand-enumerated nine — readonly · static · public · private · protected · abstract · declare · async · * — and override is the one TS member modifier absent from it. The declaration matcher at :332 does not carry it either.

⚠️ Line numbers rot. Confirm the site by reading the regex, then say in your PR body what you read.

⚠️ Triage also records that the card's own repro fails for an unrelated reason — symbol-anchors.mjs imports git-env.mjs relatively, so copying the file to /tmp breaks the import. ⇒ ⛔ That failure is not evidence against the card. Drive the resolver in place in your worktree.

The three binding constraints from triage — all three are acceptance rows

1. ⭐ Re-take BOTH censuses in the same stroke and write the before/after values into the PR body. The matcher serves the docs/adr/** corpus and the scripts/** corpus, so a widened accept set moves both numbers at once. ⛔ Do not let the docs/adr/** number change with nobody explaining it. (check-scripts-symbol-anchors reported 34 symbol (34 declaration, 0 literal) when the card was filed — ⛔ that is the card's number, not a reading you may inherit; take it yourself.)
2. ⭐ Add a self-test case driving all four spellings — override, override async, protected override async, public override. ⛔ Not one token and done: this enumeration has already been wrong once, which is precisely the finding. Include the negative control (a name that is not there) so the test can fail.
3. ⛔ If you conclude the accept set should be DERIVED rather than enumerated — do not do it on this card. That is a rewrite of a shared resolver whose governing ruling is that a corpus joins by registration and there is to be no second implementation. Report back with the argument and this seat will route it for a ruling.

⭐ Write the strongest fact into the PR's reasoning

The card asked, as an open question, whether the accept set should be derived instead of enumerated. Triage's reading turns that from a worry into evidence: the enumeration is hand-made and has now been demonstrated incomplete once. Put that in the PR body — it is the reason the card is a bug and not a shrug.

⛔ Do not fold into #16711's PR. That card is fenced to the driver packages plus its own new gate, and it works around this by anchoring the class #TursoDriver instead of the member #initObjects. ⭐ That downgraded anchor is the evidence for this card; mixing the two would erase it. ⛔ Also unrelated to #16713 — different regex, different script.

What you may not claim

The fix makes override members anchorable. It does ⛔ not re-anchor anything: #16711's header keeps its class-level anchor unless someone changes it, and that is not yours. If you believe it should be revisited, say so in the report; ⛔ do not touch it.

---

Generated by Claude Code

[claude]

os-dev-report

{
  "issue": 16821,
  "status": "done",
  "branch": "claude/issue-16821-symbol-anchors-override",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/16895",
  "premise_still_valid": true,
  "summary": "Confirmed the site by reading the regex, not by inheriting the line number: in scripts/symbol-anchors.mjs the member matcher inside scriptSymbolClass carried the hand-enumerated nine 'readonly | static | public | private | protected | abstract | declare | async | *' and 'override' was the one TS member modifier absent. Triage named line 336; it is line 371 in the branch after the rationale comment landed, which is why the token sequence identifies it. The sibling declaration matcher one line up does not carry 'override' either and correctly need not: 'override' is not legal on function / class / interface / type / enum / namespace / module. Added 'override ' to the member alternation only, plus a rationale comment at the site recording that the enumeration is hand-made and has now been demonstrated incomplete once, twelve self-test cases (one per member spelling, each with its own negative control) and the battery-floor ledger row 69 to 93 (measured, not guessed). Purely additive. Larger than the card knew: 276 'override' member declarations under packages/, 207 of them the 'static override' metadata on CLI command classes (flags, examples, args, description) -- all of them were unanchorable. Assignee left untouched as dispatched (it reads 'baozhoutao'); no second Claim comment posted.",
  "tests": "CENSUS, all corpora that resolve through this matcher, taken in one stroke before the edit and again on the final tree at 1a33d4f4b3. THREE gates import the resolver, not two -- check-system-context-census registers through the same symbolResolutionClass and has a --fix writer, so it was measured too. BEFORE / AFTER, verbatim: [adr] 'check-adr-symbol-anchors: 2067 anchors across 139 records resolve - 277 symbol (251 declaration, 26 literal), 1765 file-level, 25 cross-repo, 6 exempt, 3 continuation. 0 line anchors survive.' [scripts] 'check-scripts-symbol-anchors: 3030 anchors across 233 scripts resolve - 34 symbol (34 declaration, 0 literal), 2996 file-level, 0 cross-repo, 1 exempt, 2 continuation. 0 line anchors on tracked targets survive (4 citations name no tracked file and are not judged; 0 dated allowance finding(s)).' [system-context] 'check-system-context-census: OK - 106 elevation read sites in 20 packages across 45 files, living in 89 symbol(s); the page cites 103 symbol(s) against 103 required, over 127 anchors and 8 file-level citation(s); 22 declared non-read; 9 file(s) hold more than one read in one symbol (the declared precision loss); 18 row reference(s) resolve to their keyed row, 2 declared unheld.' ALL THREE ARE BYTE-IDENTICAL BEFORE AND AFTER -- 'diff' over the full captured output of each reports no change, all exit 0 in both legs. The docs/adr number did NOT move, and the reason is stated rather than assumed: all three were already green, so every anchor already resolved; an additive accept set can only move a class upward (unresolved to declaration, or literal to declaration), and none of the ADR corpus's 26 'literal' anchors names an override member. The scripts corpus's 34 will not move by itself either -- the fix removes a structural exclusion, it does not add anchors. IN-PLACE PROBE (the card's own repro breaks on the relative git-env.mjs import when copied to /tmp; driven in the worktree instead). Five positive controls resolved and six override spellings were refused before the change; after it all resolve and the negative control still refuses. END-TO-END ON REAL TREE FILES, both legs: turso-driver.ts#paginationTieBreaker (protected override) UNRESOLVED -> declaration; #supports (public override get) UNRESOLVED -> declaration; #bulkCreate (override async) literal -> declaration; hook-wrappers.ts#name (override readonly) UNRESOLVED -> declaration; #noSuchMemberAtAll (CONTROL) UNRESOLVED -> UNRESOLVED. The bulkCreate row is the class-upgrade case in the wild and is the mechanism by which a census COULD have moved; the table above is the measurement showing it did not. ABLATION, predicted direction 'turns red', observed 'turns red'. Fix committed first, then 'override ' removed from the alternation with the on-disk mutation proved by counting BOTH the injected and the removed token ('with-override=0 (expect 0), without-override=1 (expect 1)') before running. Result: 'ABLATION EXIT=1' and 'symbol-anchors --self-test: a member declared `override` must resolve as a declaration'. Restored with 'git checkout HEAD -- path' (not bare checkout, not the index); restored blob hash 734d554f099e8a583ba084774d058c12d692c532 equals the HEAD blob, 'git diff HEAD' empty, restore leg exit 0. The same mutate/restore pair was run for the real-file probe with the same proof. No build/dist step is involved -- these are plain node scripts run from source, so the dist preflight does not apply. SELF-TEST: 'symbol-anchors --self-test' exit 0. Battery count measured at 93 by temporarily raising the pin and reading the gate's own 'registered 93 case(s)' line, then restored (hash equality plus empty 'git diff HEAD' verified); pin set to the measured 93 with a ledger row in the existing 63->67->69 style. GATE FAMILIES: derived with 'node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack' (no hand-written path list), 31 families, every one run FOREGROUND, every one exit 0, on the final tree. Reconciled: 'dispatch-gates --ran: 31 derived famil(ies) accounted for - 31 run, 0 NOT-MEASURED.' The three census gates above were run on top of that, since two of them are not in the derived set for a scripts/** diff. Exit codes were captured before any pipe throughout. CONTROL CHARACTERS: 'pnpm check:nul-bytes' exit 0 plus a direct scan of the changed file with the control-byte grep, no matches. NOT MEASURED, declared: repo-wide 'pnpm lint' was not run -- no narrowed eslint run is claimed either, so this is left to CI rather than reported as a partial reading. STALENESS, declared: dispatch-gates warns the tree is behind origin/main and names scripts/doc-authoring-prose-id.baseline.json as a changed derivation input. Re-derived after 'git fetch origin main' and the family list came back IDENTICAL, so the derivation holds; the branch was deliberately not merged forward.",
  "mcp_calls": "1 - one targeted mcp__github__search_issues, declared below. Everything else (issue read, comments read, PR create, PR read-back, labels, the new card) went through repo-scoped REST with curl.",
  "open_questions": [
    {
      "question": "Constraint 3 answered, as required, and NOT acted on: should the member-modifier accept set be DERIVED rather than enumerated? My recommendation is no, and the reasoning is not 'it is out of scope' -- it is that deriving it does not buy what it looks like it buys. There is no list of TS member modifiers available to a regex at runtime; 'deriving' in practice means either (a) parsing the target with a real TS parser, which makes this shared core heavy for every corpus that anchors no TS at all and which the module's header explicitly rejected the equivalent of when it kept the GitHub slugger out, or (b) replacing the enumeration with a permissive 'any run of identifier-ish words before the name' pattern, which is a widening whose failure mode is silent acceptance -- and this module's whole grade rests on refusing the permissive test. The enumeration's failure mode is the one observed here: LOUD, at the author, once. That is the better failure mode to keep. What the incident actually argues for is not derivation but PROVOCATION -- the enumeration must be driven per spelling by a self-test that can fail, which is what this PR adds and what did not exist before. If the owner disagrees, the change is a rewrite of a shared resolver under a ruling that a corpus joins by registration with no second implementation, so it is theirs to route, not mine to do.",
      "options": [
        "A - keep the enumeration, keep it provoked per spelling by the self-test this PR adds. No further card.",
        "B - derive via a real TS parse in the shared core. Correct for TS, but weighs down every corpus and reopens the 'one resolver, kept light' trade the header settled.",
        "C - replace the enumeration with a permissive modifier-shaped prefix. Cheapest, and the only one of the three whose failure mode is silent acceptance."
      ],
      "recommendation": "A. The observed defect was a missing case in a list that nothing provoked, not a list that could not be right. Provocation is the repair and it has landed; derivation trades a loud failure for a quiet one."
    },
    {
      "question": "Reported because the brief asked me to say so rather than act: #16711's gate header keeps its class-level #TursoDriver anchor. The member-level form is now possible, so that header COULD be re-anchored to the member it is actually about. I did not touch it and make no claim that this PR re-anchors anything. If the seat wants it revisited it is a separate, one-line change on that card's file surface, not mine.",
      "options": [
        "A - leave #16711's header as it is; the downgraded anchor stays as the evidence trail for this card.",
        "B - file a follow-up to re-anchor it to the member now that the member resolves."
      ],
      "recommendation": "A for now. The downgraded anchor is this card's evidence and erasing it has a cost; B is cheap whenever the seat wants it."
    }
  ],
  "out_of_scope_findings": [
    "filed as #16898: the platform-checklist corpus (scripts/check-platform-checklist.mjs, the #13788 corpus) resolves symbol anchors with its OWN rule (absentAnchorSegments -- a bare comment-masked token match) instead of registering through this resolver, while its header cites the shared grammar by anchor. Class (b), violates a declared contract, and the contract text is quotable from symbol-anchors.mjs's own header: 'the resolution rule has exactly one implementation and one self-test' and 'Do not fork this file for a second corpus'. Demonstrated with a firing negative control: the checklist rule RESOLVES a citation whose symbol survives only as a call site, a local parameter name, or a string literal -- exactly the permissive includes()-style test the shared header says it deliberately is not. Its shrink-never floors in checklist-symbol-anchor-baseline.json were measured under that permissive rule. Duplicate-checked first with one targeted search whose top hit was this card, so the instrument fired; no open card covers it.",
    "noted, not filed: 'accessor' (TS 4.9 auto-accessors) is also absent from the same hand-enumerated set, and would be refused identically. NOT added and NOT filed, deliberately: there are ZERO auto-accessor members under packages/ today, so unlike 'override' this is not a demonstrated miss, and the card's whole grade rests on a demonstrated one. Successor: none today -- it becomes real the first time somebody writes an auto-accessor, and the comment now at the site tells that author the set is hand-made and additive widening is the move.",
    "noted, not filed: the card's illustrative anchor, turso-driver.ts#initObjects, no longer names a declaration in that file on today's main -- 'initObjects' survives there only in comments and the declaration lives in the SqlDriver base, so that exact anchor would not resolve regardless of this fix. The FINDING is unaffected and was re-verified independently against the regex and against 27 real override members still declared in that same file. Recorded so nobody later reads the card's example as a live repro. The checkout is shallow, so I did not chase which commit moved it.",
    "noted, not filed: the branch's two base commits carry a 'Refs #16821' trailer, written under the brief's original (later corrected) instruction. check:partof-closing-keyword RULE 2 forbids ANY card-relation trailer in a commit message, Refs included. The tip commit was amended clean before it was pushed and commitRelations() returns [] for it; the two earlier ones were already pushed and rewriting a pushed branch is not an action this seat takes, per the standing rule and the seat's own correction. Verified per commit with the gate's own exported commitRelations(): tip CLEAN, 22d5b44d47 and f0c04ab788 RESIDUE. Named in the PR body too. This gate will red on the PR until the seat names it at landing.",
    "noted, not filed: no changeset. Established by measurement, not by category -- repo-root scripts/ is shipped by no package's files[], the root manifest is private, and the resolver's exported names appear nowhere under packages/ (checked with a firing positive control that did hit). 'skip-changeset' applied to the PR with an additive POST and read back comparatively: read-back equals union(read, target), nothing stripped."
  ]
}

---

Generated by Claude Code