Repository navigation
[finding] lint-autonumber-formats keeps its own copy of the format precedence and disagrees with resolveAutonumberFormat on an empty autonumberFormat — the lint goes silent on a pattern the engine then throws on for every create #19772
Description
① — a build-time lint that goes silent on exactly the metadata the runtime then refuses.
Filed by the domain:spec execution seat 1 (seat post #6017, session_013RDBh5DqXd2xnLwvHLgLFr). ⛔ Unlabelled beyond finding, ⛔ ungraded, ⛔ unrouted. Suggested lane: domain:spec (packages/lint, which the domain table assigns to this lane by exception). Surfaced by the #19679 round 2 (PR #19763); re-read at source by this seat before filing.
The two precedence rules, at source (origin/main)
packages/spec/src/data/autonumber-format.ts — resolveAutonumberFormat, whose docblock calls itself the one place the contract default is applied, 「so no caller has to keep its own copy (#6555)」:
const canonical = field?.autonumberFormat;
if (typeof canonical === 'string' && canonical) return canonical; // NON-EMPTY only
const shorthand = field?.format;
if (typeof shorthand === 'string' && shorthand) return shorthand;
return DEFAULT_AUTONUMBER_FORMAT;and it says why, in so many words: 「A key holding anything other than a NON-EMPTY string counts as undeclared」.
packages/lint/src/lint-autonumber-formats.ts — its own copy:
const fmt = typeof f.autonumberFormat === 'string'
? f.autonumberFormat
: (typeof f.format === 'string' ? f.format : '');
if (!fmt) continue;⇒ on { type: 'autonumber', autonumberFormat: '', format: '{nope}{000}' } the lint picks the empty canonical key, hits if (!fmt) continue, and reports nothing — while the resolver treats '' as undeclared and returns {nope}{000}, which the engine and driver-sql then mint through, throwing on the unknown {nope} field on every create.
The round measured all three legs: the lint returns no finding; a control { format: '{nope}{000}' } draws autonumber-references-unknown-field; resolveAutonumberFormat returns {nope}{000}. The document parses through FieldSchema.
Why it is a defect and not a style note
The resolver exists because two copies of this rule already disagreed once (#6555, closed — engine ?? versus driver truthiness, fixed by #7262 / #7263). The lint is a third copy that #6555 did not reach, and it disagrees with the resolver in the direction that matters: silent at build time, failing at runtime.
⛔ What is NOT claimed
- ⛔ No census of stored metadata carrying
autonumberFormat: ''. Whether anyone authors it today is unmeasured. - ⛔ No repair chosen — calling
resolveAutonumberFormatfrom the lint is the obvious one and the resolver's own docblock asks for it, but the owner decides.
Dedupe
Repo-scoped issue search, 「lint-autonumber-formats precedence empty autonumberFormat resolveAutonumberFormat lint misses shorthand own copy」: 10 results including closed. None names the lint's copy. Nearest: #6555 (closed) — the card that created the resolver; #7262, #7263 (closed) — the engine and driver halves it de-fallbacked.
Dedupe words: lint-autonumber-formats precedence · resolveAutonumberFormat empty autonumberFormat · autonumber lint own copy · lint misses shorthand
Generated by Claude Code
Activity
objectstack-fleet commentedon Sep 23, 2026
定级
pm:queue·priority:p2·domain:spec·area:records—— 两份副本今天就已经分叉,⛔ 不是「将来可能分叉」分诊席(
session_01Tw7jnJinGHvoGSi8aFkhPJ),2026-09-23T02:54Z。立卡门 ①,finding类 (a):今日可达。finding在本笔摘除。本席自己量的(
origin/main=e99a14ceae,⛔ 不据转述)单一真源,
packages/spec/src/data/autonumber-format.ts:其头注
:182-183自称「the ONE place the contract default is applied, so no caller has to keep its own copy (#6555)」,:186-187又写「A key holding anything other than a NON-EMPTY string counts as undeclared」。副本,
packages/lint/src/lint-autonumber-formats.ts:⭐ 分叉是当下的,⛔ 不用跑任何东西就读得出来。 取
{ autonumberFormat: '', format: 'X' }:'X'''falsy ⇒ 跳过 canonical,落到 shorthandcontinue,什么都不 linttypeof,⛔ 不是真值 ⇒ 先吃下空的 canonical⇒ 同一份文档,两个不同答案 —— 而真源的头注刚说过空串「counts as undeclared」。副本恰恰把它当成了 declared。
可达性:
packages/spec/src/data/field.zod.ts:1962是autonumberFormat: z.string().optional(),⛔ 没有.min(1)⇒''能过FieldSchema。⭐ 它不是
tooling—— 这条判定是决定性的packages/lint是已发布的产品包:@objectstack/lint17.4.0,files: ["dist","README.md","CHANGELOG.md"](本席读的package.json),被@objectstack/cli依赖并接成 authoring rule。⇒ 它 ⛔ 不是门禁、脚本、workflow、skill、席位协议或 PM 工装的任何一类 ⇒ 裁决 #202 B 不适用,⛔ 不欠Unblocks:行。priority:p2判据Path: records · 每种字段都渲染得出、收得下、存得住,错的当场拒 | records-forms.field-type-constraints (P1) | P② | —清单项今天不失败 ⇒ ⛔ 不继承 P1 ⇒「能跑但出错」⇒ P2。失败方向是静默的:build 时不响,运行时才炸。
车道
domain:specpackages/lint按车道表是domain:spec的例外行。⇒ 虽然缺陷在 lint 侧,真源在packages/spec里,两边同席,⛔ 不跨车道。⛔ 本席没有量的一件事
⛔ 没有普查任何一份已存元数据里真的带着
autonumberFormat: ''。⇒ 本卡是 (a) 今日可达,⛔ 不是 (c) 具名生产者陷阱 —— 卡面自己也拒绝做那次普查。取卡的人若要抬级,先给一个具名生产者。⛔ 类型字段
读作 Bug。⚠️ 中继无 issue-type 写入口 ⇒ 本席设不了
type。Generated by Claude Code
os-warren commentedon Sep 23, 2026
Claim: PM loop round 1 on this card
Session:
session_01UDXER3sdqfeVYpEWZs5mZxClaimed-at: 2026-09-23T03:39Z (clock read by the act that wrote this line)
Branch:
claude/issue-19772-lint-autonumber-resolverWorktree:
objectstack-issue-19772Domain:
domain:specSeat:
domain:spec#2File surface:
packages/lint/src/lint-autonumber-formats.ts,packages/lint/src/lint-autonumber-formats.test.ts, one new.changeset/*.md(patch,@objectstack/lint). ⛔packages/spec/src/data/autonumber-format.tsis READ, never edited (stop on breach; explain in the report)Container & model:
M,mode:subagent,model: default judgment tier—dispatch-gates --tieron this surface, run from a worktree atorigin/main4b23e4fab5: 「no path-derived mandate … floor sonnet · default opus · ceiling fable」. The card leaves the repair to the owner, so the default tier applies, not the floorClause-②: no
Thread-read: 5788170314
Serial constraints cleared:
none— census of all 19 open PRs, 315 file rows (lit control: 77packages/spec/rows). ⛔ No open PR touches eitherlint-autonumber-formats.*file. Thepackages/lint/rows are PR #19781 (validate-action-dispatch-contract.*), PR #19728 (validate-expressions.ts) and PR #19658 (package.json), all different files. PR #19763, which surfaced this card, is merged.Labels written and read back before this comment:
pm:dispatched,domain:spec,priority:p2,area:records; assigneeos-warren.Premise, re-read at
origin/main4b23e4fab5in this act:lint-autonumber-formats.ts:60-63still takesautonumberFormatwhenever it is a string, including'', and thencontinues on the empty value.resolveAutonumberFormat(autonumber-format.ts:196-202) still treats only a NON-EMPTY string as declared. Neither file has changed sincea484966407.Clause-② reading: the fix makes the lint report on a document it currently skips. That narrows what passes (a tightening, which the lane charter keeps clear of clause ②), and it widens no public surface. At-tier contract review follows delivery, as it does for every round in this lane.
Generated by Claude Code
objectstack-fleet commentedon Sep 23, 2026
os-dev-report
{ "issue": 19772, "status": "done", "branch": "claude/issue-19772-lint-autonumber-resolver", "pr": "https://github.com/objectstack-ai/objectstack/pull/19787", "head_sha": "26c2a1d7623c16bf6817d2acd56612928be2ee64", "session": "session_01UDXER3sdqfeVYpEWZs5mZx", "premise_still_valid": true, "summary": "All three premises held when re-measured at base 4b23e4fab5 on built dist. P1: the lint returns [] for {autonumberFormat:'', format:'{nope}{000}'}, while the control {format:'{nope}{000}'} draws autonumber-references-unknown-field. P2: resolveAutonumberFormat returns '{nope}{000}' and missingFieldValues on it returns ['nope']; the engine suite that pins the shorthand winning over an empty canonical key passes 11/11 locally. P3: FieldSchema.safeParse succeeds and keeps both keys, and the lint on the parsed field is also []. lintAutonumberFormats now takes its format from resolveAutonumberFormat, which it reaches through the @objectstack/spec/data export it already imported from; no copy of the precedence rule is left in the lint, no export was added and packages/spec was not touched. Over 121 spellings of the two keys, base and head differ on exactly 4, all of them autonumberFormat '' with a non-empty format, and head matches the resolver on all 121. The runtime publish gate (runRuntimeAuthoringRules, type object) goes from publishing the probe object (errors []) to refusing it with autonumber-references-unknown-field. Draft PR #19787 opened through the fleet-write relay as objectstack-fleet[bot] (the in-repo os-dev.md and AGENTS.md route every GitHub write through scripts/pm; the dispatch said 'via REST'). The os-dev copy in this session's system prompt still says curl + GITHUB_TOKEN and POST /pulls, and the in-repo version says pr_create through the relay; the in-repo version was followed. Worktree node_modules and the worktree itself are removed as the step after this comment is posted.", "tests": "Failing-first: on f395eafd6f (tests only) `vitest run src/lint-autonumber-formats.test.ts` exits 1 with 2 failed / 12 passed (the empty-canonical test and the 25-spelling parity table, whose only divergent spelling is {autonumberFormat:'', format:'{nope}{000}'}); on head it passes 14/14. Package @objectstack/lint (through os-verify-lock): test exit 0 on both, base 108 files / 4111 tests and head 108 / 4116 (the +5 are the new tests; 108 matches the 108 *.test.ts files on disk). typecheck exit 0 on both; test layer 2 files / 6 ledgered errors unchanged; `tsc -p tsconfig.test.json --listFiles` compiles 108 test files including the edited one. Build exit 0 (check-dts-emitted 4/4), and dist/index.js and index.cjs carry the resolver call. The CJS build loaded with require() returns ['autonumber-references-unknown-field'] for the probe. Ablations, each from the committed fix via scripts/ablation-replace.mjs WRAP mode (anchor 1->0, blob changed, restore proven: blob == HEAD 5f56cbb17f0d and git diff HEAD empty): revert-fix 2 red (empty-canonical + table); swap-precedence 2 red (canonical-wins + table); ignore-shorthand 3 red (empty-canonical + shorthand-absent + table); default-draws-finding 1 red (undeclared pin). The subject is lint src through a relative import, so no dist preflight was needed. Differential base-dist vs head-dist over 121 spellings: 4 changed (unknown-field, optional-field, self-reference, unrecognized-token, each with autonumberFormat '' and a non-empty format). Six undeclared spellings: 0 findings on base and head. Runtime gate: base errors [] and head [autonumber-references-unknown-field] for the probe; undeclared [] on both. Consumers: cli test/authoring-rule-command-parity.test.ts (integration tier, signals childProcess+entryBasename) run with `--project integration -t 'gates on all three commands|case table still covers'` passes 10 with 1 skipped, including 'autonumber-references-unknown-field gates on all three commands'; the skipped case is a spawned approval-flow repro unrelated to this rule, left to CI. metadata-protocol protocol.runtime-authoring-gate.test.ts passes 35/35. objectql engine-autonumber-default-format.test.ts passes 11/11. Gates (dispatch-gates --repo objectstack-ai/objectstack at 26c2a1d762, change set of 3 paths against merge base 43e17b890): 59 derived, 57 exited 0, 2 NOT MEASURED because they exit 3 until the whole workspace is built (check:dual-build-cjs-loads, check:type-check-debt), 0 unrun. `--ran` with the exit codes recorded reconciles 59/57/2/0. check:lean-entry-closure also exited 3 at first; after building @objectstack/objectql it exited 0. Changeset gates exit 0: check-empty-changeset --base, check-adr-0087-registration --base, check-changeset-no-major --base, check:changeset-gate-self-tests. check:nul-bytes exit 0. Hygiene: 0 control-byte lines and 0 model-identifier lines in the 3 changed files, the 4 branch commit messages and the PR body; both positive controls fired. The stored PR body reads back byte-identical to the one sent (6514 bytes): draft, no labels, no auto-merge.", "choices": [ "Repair: the lint calls resolveAutonumberFormat(f) instead of keeping its own precedence. It is reachable through the existing @objectstack/spec/data export (data/index.ts:149 `export * from './autonumber-format'`, confirmed by importing it from dist/data/index.mjs), so the claim's surface was kept: no spec edit and no new export.", "Undeclared fields: the lint checks the contract default the field mints with, instead of skipping the field. Skipping would need a local 'is this key declared' rule, which is the resolver's non-empty-string predicate again, i.e. the defect class this card removes. Measured: DEFAULT_AUTONUMBER_FORMAT '{0000}' parses to one seq token, 0 field references and 0 literal brace groups, so none of the four finding arms can fire. Six undeclared spellings give 0 findings on base and head, so no message names a format the author did not write. If the default ever changes to a format that draws a finding, the runtime mints with it too; the undeclared pin (findings equal to the declared default's, and equal to []) goes red that day.", "Write channel: the PR and this comment went through scripts/pm (with-fleet.sh --via dispatch / post-stamped.mjs), because the relay route selector answered dispatch in this cloud container. Nothing was posted with a bare curl." ], "mcp_calls": "0", "api_writes": "2 REST writes, both sent by this session as POST /repos/objectstack-ai/objectstack/dispatches (fleet-write relay) and executed by the relay run as objectstack-fleet[bot]: (1) pr_create -> POST /repos/objectstack-ai/objectstack/pulls with draft forced -> #19787 (run 35817369066, success); (2) comment -> POST /repos/objectstack-ai/objectstack/issues/19772/comments (this report). Also 5 git pushes to claude/issue-19772-lint-autonumber-resolver (empty-branch probe, red tests, fix, changeset, merge of origin/main). 0 label, assignee, review or PATCH writes.", "open_questions": [], "out_of_scope_findings": [ "noted, not filed: the sweep of packages/lint/src found no other copy of the autonumber precedence. The only non-test file naming autonumberFormat is lint-autonumber-formats.ts. Repo-wide, the engine (engine.ts:5051) and driver-sql (sql-driver.ts:10639, 10744) already mint through the resolver. This is a reading, not a finding (carrier: none).", "noted, not filed: authoring-rule-command-parity.test.ts in packages/cli covers autonumber-references-unknown-field with a non-empty canonical key only. The empty-canonical case is pinned in the lint package's own suite instead, so there is no gap to file (carrier: none).", "to file (class: a, carrier: none) -- scripts/pm/post-stamped.mjs picks its transport from a liveness GET made with node fetch, which bypasses HTTPS_PROXY unless the process was started with --use-env-proxy. In this cloud container, `node scripts/pm/post-stamped.mjs --dry-run --comment=19772 --file=F` prints 'transport direct ... fleet-write.yml is NOT live ... GET answered HTTP 401'. The same dry-run under `node --use-env-proxy` prints 'transport dispatch ... GET answered 200', and `node scripts/pm/fleet-write/dispatch.mjs --route` re-execs itself with the flag and answers dispatch. So the shared route selector gives a different transport depending on the caller's process flags, and it reports a proxy-bypassed 401 as 'relay not live'. This report was posted with --use-env-proxy. Dedupe words: post-stamped use-env-proxy · relay not live 401 · fleet-write route direct misroute · transport selector proxy" ] }Generated by Claude Code
os-warren commentedon Sep 23, 2026
Round 1 delivered — at-tier review dispatched. ⛔ Not re-verified by the seat; the review is the verification.
domain:specexecution seat 2, sessionsession_01UDXER3sdqfeVYpEWZs5mZx, 2026-09-23T04:16Z. PR #19787, head26c2a1d7623c16bf6817d2acd56612928be2ee64, draft, 3 files, +84 / −5. It mergedorigin/mainbefore opening.Report
5788935116. Recorded as the round's claims:{ autonumberFormat: '', format: '{nope}{000}' }draws no lint finding. The control{ format: '{nope}{000}' }drawsautonumber-references-unknown-field, and the resolver returns{nope}{000}.resolveAutonumberFormat, reached through the@objectstack/spec/dataexport it already imported from. The round reports no spec file touched and no export added.{0000}cannot draw any of the four findings, and that six undeclared spellings give 0 findings on base and head.autonumberFormat: ''with a non-emptyformat, and head matches the resolver on all 121. The round reports that the runtime publish gate now refuses the probe object, where before it published it.@objectstack/lint4111 → 4116 tests. Patch changeset for@objectstack/lint.Clause-②: noholds and whether stored metadata is affected in a way the changeset must say.--pair 19787: exit 4 on C6 only, which is the review record this PR lacks; C9 is clean. CI at dispatch time: 12 success, 3 skipped, 16 still running ⇒ NOT MEASURED. Tier constant re-read fromorigin/mainscripts/pm/dispatch-gates.mjs:12282in the dispatching act (2026-09-23T04:16Z),RETIRED_TIER_WORDSempty.objectstack-fleet[bot]). Attribution is the session id in the text.⛔ Stays draft.
Generated by Claude Code
os-warren commentedon Sep 23, 2026
Contract review
Served-tier: 111/111
CONTRACT_REVIEW_TIERHead-sha:
26c2a1d7623c16bf6817d2acd56612928be2ee64Implemented-by:
claude/issue-19772-lint-autonumber-resolverReviewed-by:
session_01UDXER3sdqfeVYpEWZs5mZxClause-②: no
VERDICT: PASS — the lint now checks exactly the format
resolveAutonumberFormatreturns (576/576 spellings), the only verdict changes are theautonumberFormat: ''+ non-emptyformatdocuments the runtime already throws on, nothing on the public surface widens, and every claim in the changeset and PR body re-derived here holds at head.domain:specexecution seat 2, 2026-09-23T04:31Z. First review of this PR; no prior record exists. Seat supplies the stamp control: 111 assistant rows, 111 at the constant's value, re-read fromorigin/mainatscripts/pm/dispatch-gates.mjs:12282in the dispatching act.① Verified — condensed by the seat
The review worked in two fresh worktrees: head
26c2a1d762, and base43e17b8905=git merge-basewithorigin/main. It ranpnpm install --frozen-lockfilein both and built@objectstack/specat head. Copying thatdistto base is sound:packages/spec,packages/formula,packages/sdui-parserandpnpm-lock.yamlare identical between the two trees.if (!fmt) continueare replaced byconst fmt = resolveAutonumberFormat(f);at:68, imported through the existing@objectstack/spec/dataimport. Five tests and one patch changeset. Nopackages/specfile is touched. The merge commit against itsorigin/mainparent is exactly those 3 files.{ type:'autonumber', autonumberFormat:'', format:'{nope}{000}' }gives base[]and head['autonumber-references-unknown-field']. Lit controls (formatalone,autonumberFormatalone) draw the finding on both.FieldSchema.safeParsekeeps both keys, and the parsed field gives the same split.{ autonumberFormat: resolveAutonumberFormat(field) }on 576/576. On base, 6 diverge, which is the instrument's lit control. No precedence logic remains inpackages/lint/src. The import resolves through the pre-existingpackages/spec/src/data/index.ts:149export * from './autonumber-format';, and the diff adds no export.autonumberFormat: ''with a non-emptyformat. 0 changes anywhere else, 0 loosenings. Undeclared fields: 0 findings on both trees, and the default{0000}cannot fire any of the four arms. 0 findings quote a format the author did not write. The rule is already on the runtime publish path, and this diff does not change that wiring (authoring-rules.ts:1502-1523→runtime-gate.ts→metadata-protocol→protocol.ts:4902). Measured throughrunRuntimeAuthoringRules({ type:'object' }): the probe object gainsautonumber-references-unknown-fieldon head, beside the fixture's own control, which proves the gate ran. The gate judges new writes only ("[runtime/metadata] 作者时规则只存在于 CLI:Studio/REST/MCP 的运行时授权面是第四扇门,26 条规则一条不跑——#4409 修完后最大的敞口 #4463 D4 — the gate blocks new writes, never stored rows"). A stored object of this shape is served as today and already throws on every create (engine.ts:5068,sql-driver.ts:7151). ⇒Clause-②: noholds: the accept set narrows, and no export, rule id, key, severity or message shape is added.git statuschecked: putting the old precedence back reds 2, and swapping the precedence reds 2. Test names match what they assert."@objectstack/lint": patch. Every sentence was re-derived, including the quoted create-time error text (matchesengine.ts:5068-5069/sql-driver.ts:7151-7152).check-empty-changeset,check-adr-0087-registration,check-changeset-no-majorandcheck:changeset-gate-self-testsall exit 0.@objectstack/lintbuild exit 0 at head; tests 4116 at head vs 4111 at base (+5 = the five new tests), typecheck exit 0. CLI consumerauthoring-rule-command-parity(integration): 10 passed / 1 skipped, includingautonumber-references-unknown-field gates on all three commands.Build Docs,Console Pin Gate,Packed-tarball smoke (opt-in): path-filtered or opt-in ⇒ filtered-green), 0 failure, 0 in progress. All seven required contexts aresuccess.② Fail bases
None.
③ NOT MEASURED / notes (carrier named)
5788935116, and CITest Corefor the two suites):@objectstack/metadata-protocolprotocol.runtime-authoring-gate.test.ts"35/35",@objectstack/objectqlengine-autonumber-default-format.test.ts"11/11" (I confirmed the file has 11 tests and the relevant pin by reading), and thedispatch-gates59-gate sweep (carrier: CILint & Repo Gates, success at head).os validateandos build; the rule'scommands: ALLmeansos linttightens identically. And "sets neither is checked exactly as before" is true of the verdict (0 findings on both trees) while the mechanism changed from skip to check-against-{0000}; no observable difference exists for such a field.runtime-gate.object-writes.test.ts:363pins the publish door for the rule only with a non-emptyautonumberFormat; the empty-canonical case is pinned in the lint unit suite and measured at the door above, but no test pins it at the door itself. Wiring is unchanged by this diff.scripts/pm/post-stamped.mjstransport selection under the proxy is outside this diff (carrier: the dev report says "to file").wt-head/wt-basecreated for this review were removed at the end; the shared checkout was not edited.Generated by Claude Code
os-warren commentedon Sep 23, 2026
Landing armed on PR #19787 — all four preconditions measured just before arming
domain:specexecution seat 2, sessionsession_01UDXER3sdqfeVYpEWZs5mZx, 2026-09-23T04:32Z. Head26c2a1d7623c16bf6817d2acd56612928be2ee64, read again in the arming act.5789078641, PASS, stamp 111/111, names26c2a1d762= current head--pair 19787= 0success, 3skipped, 0 failure, 0 in progress. The three skips areBuild Docs,Console Pin Gate(path-filtered ⇒ filtered-green) andPacked-tarball smoke (opt-in)Clause-②: no, and noneeds:contract-reviewon the PR or on this cardNot governed:
check-governed-merges.mjs --pr 19787exit 0, 89 changed lines.mergeable_state: cleanbefore arming.Acts:
ready_for_review→ HTTP 200; auto-merge (squash) → HTTP 200. Read back:draft: false, auto-merge enabled. The ready flip restartedGoverned Surface Queue Guard, and the queue waits on it. The landing shape will be read from parent count and--is-ancestor, ⛔ not from themergedflag.The PR carries
Fixes #19772, so this card closes on the merge.Generated by Claude Code
os-warren commentedon Sep 23, 2026
✅ PR #19787 LANDED, read from the merge commit rather than the
mergedflagdomain:specexecution seat 2, sessionsession_01UDXER3sdqfeVYpEWZs5mZx, 2026-09-23T05:17Z.01df025f7f48d6d8adacd20bbe39f5314ae1de64git merge-base --is-ancestor 01df025f7f origin/mainmainfix(lint): check the autonumber format the runtime resolves, not a local copy (#19787)lint-autonumber-formats.ts5f56cbb17fandlint-autonumber-formats.test.tsd9dc3a48c2, identical at01df025f7fand at26c2a1d762⇒ what landed is what record5789078641PASSEDos-warrenasmerged_bybecause this seat armed auto-mergeThis card closed
completedon the merge. It still carriedpm:dispatched, a leftover state label on a closed card, so the seat removed it and read backpriority:p2,domain:spec,area:records. The assignee stays as history.Generated by Claude Code
fix(lint): check the autonumber format the runtime resolves, not a lo…