Repository navigation
fix(driver-turso): converge remote date/json cells the pre-fix batch door stored unconverted - #19904
Conversation
…door stored unconverted A remote boot now rewrites a `date` stored as a full timestamp to the calendar day the driver already reads it as, and a json string stored bare (text that does not parse) to its JSON encoding. Both are exactly what the fixed write door stores for the same value, so no converted cell reads differently; the day filter now matches. Every json cell whose text parses (a stored `true` reading as 1, a string '42' reading as 42) is left as stored: its bytes collide with another writer's. Claude-Session: https://claude.ai/code/session_01TEhopqrWQYBycZzyJHpAZr Co-authored-by: Claude <noreply@anthropic.com>
github-actions
Bot
added
size/l
documentation
📓 Docs Drift CheckThis PR changes 1 package(s): 2 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:
What this run could not see
Coarse fallback — 6 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): Which tree this was computed onThis run read A worktree cut from an older # while this PR is open — GitHub drops the merge commit once it closes
git fetch origin e4e89671f9a482f80fc2f772a43627fdc62e005e && git checkout e4e89671f9a482f80fc2f772a43627fdc62e005e
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin d1ca8741dda9ff8f72d1a1d3cbef5c0fb3dc687e 257ac606073144ff8594440f459356f62d8a396b && git checkout -B drift-repro d1ca8741dda9ff8f72d1a1d3cbef5c0fb3dc687e && git merge --no-ff 257ac606073144ff8594440f459356f62d8a396b
node scripts/docs-audit/affected-docs.mjs --json d1ca8741dda9ff8f72d1a1d3cbef5c0fb3dc687e
|
Contract reviewServed-tier: Head = PR head; 4 files vs merge-base ① Derived judgments(a) Exact recoverability HOLDS for both rewritten classes.
(b) No converted cell reads differently: PINNED and HOLDS (the fixed driver's (c) Mechanics TRUE and PINNED: compare-and-set by rowid on the page's own text (1 change, then 0 on a stale retry; a racing write survives); paging by a rowid cursor, with resume needing no checkpoint; idempotence (second boot 0 (d) TWO FALSE SENTENCES:
(e) The disposition under the #12380 ruling CARRIES: the remote ambiguous class is the same on-disk byte collision for the same reason, and the PR body's quotations match ② Semver level
③ Boundary flags
Implemented-by: VERDICT: FAIL: ① (d) does not hold. The changeset sentence "No read of a Generated by Claude Code |
… fix; spell trim chars as escapes The changeset said no read of a `date` field ever returned the dropped time of day. Before the boot-door read fix (which ships in the same release) a boot-synced object read such a cell back exactly as stored, so every read claim now says what it is relative to. `JS_TRIM_CHARS` held twenty of its twenty-five characters as literal invisible characters although its docblock said escapes; all twenty-five are now `\uXXXX` escapes and the runtime string is byte-identical. The pre-filter's superset wording names its one miss: a date text with an embedded NUL after the day, which SQLite's length() undercounts. Claude-Session: https://claude.ai/code/session_01TEhopqrWQYBycZzyJHpAZr Co-authored-by: Claude <noreply@anthropic.com>
Contract reviewServed-tier: Narrow re-review of the patch round over record 5799532789 (head ① Derived judgments(a) The executable delta is the spelling of (b) The four rewritten changeset sentences are TRUE, each checked against (c) NUL exception reproduced on SQLite 3.51.2 ( (d) PR body: first line (e) CI at (f) Everything record 5799532789 judged true and the delta does not touch is CARRIED: exact recoverability of both classes, the no-read-change pin, compare-and-set, paging, idempotence and quietness, the #12380 disposition, the 14-case test file and the ② Semver level
③ Boundary flags
Implemented-by: VERDICT: PASS Generated by Claude Code |
⛔ merge queue 构建失败 — 先分诊，再决定要不要重排队列构建 35899547571 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集）， 失败的 job（日志抽取，best effort）：
跨 PR 相同签名（24h，按失败测试文件聚合）：
历史信号：
分诊清单：
Generated by Claude Code · merge-queue-triage workflow (#4859) |
Merge-queue ejection — new signature, not re-queued
Signature (queue build 35899547571,
Ledger reading: no Initial judgment: not this PR's regression.
What unblocks it: a human upgrade of the ledger (this file's timeout recorded as known flaky), or an instruction to re-queue once. In either case the seat re-arms auto-merge on the unchanged head Generated by Claude Code |
Re-queue on the maintainer's instruction — once, on the unchanged head
Whose instruction, verbatim, where: the maintainer ( Signature re-queued against (recorded in 5800424463): queue build 35899547571, Head: unchanged, Generated by Claude Code |
…ON nested past SQLite's depth limit is no longer quoted into a string (objectstack-ai#19972) Fixes objectstack-ai#19912 Clause-②: no ## What was wrong `SqlDriver.backfillCanonicalJsonEncoding` (the local SQLite `Field.json` storage backfill from objectstack-ai#12380) ran one statement per json column on every `syncSchema` / `initObjects` over an existing table: ```sql update ?? set ?? = json_quote(??) where typeof(??) = 'text' and json_valid(??) = 0 ``` SQLite's `json_valid()` answers 0 for JSON nested more than 1000 levels deep, while the driver reads such a cell with `JSON.parse` without trouble. So a deep array the current write door stored correctly was quoted into a JSON string on the next schema sync and read back as a string from then on. No error, no log line: a correct cell silently became a wrong one. ## The fix SQL now only pre-filters. The driver's codec decides. - **One rule, shared by both faces.** New `packages/drivers/driver-sql/src/unencoded-json-text.ts` exports `recoverUnencodedJsonText(stored)`: when `JSON.parse` accepts the text it returns `null` and the cell is left as stored; when `JSON.parse` rejects it, the cell is a legacy plain string and the function returns `JSON.stringify(stored)`, which is what the write path stores. It is exported from `@objectstack/driver-sql`, and the Turso remote residue backfill (`remote-codec-residue-backfill.ts`, from PR objectstack-ai#19904) now imports it. That remote change is an import plus one line in place of its inline copy, and the remote behaviour does not change. - **The local pass** (`convergeJsonColumn`) reads the `typeof(col) = 'text' and json_valid(col) = 0` candidates 500 at a time in `rowid` order, applies the rule to each, and rewrites only the cells the rule rejects. Each rewrite is a compare-and-set, `where rowid = ? and typeof(col) = 'text' and col = ?` bound to the text the decision read, so a value written concurrently is never overwritten. One transaction covers each page's writes. The pass walks every page, so a column still converges in a single sync, and memory stays bounded to one page. - **Idempotence holds.** A converted cell is outside the pre-filter. A withheld cell is re-read on every sync but never written. A re-run over a converged table changes zero rows, and that is pinned with `total_changes()`. - **Logging.** The failure posture is unchanged: `warn`, and the rows stay legacy. The warn now also reports how many rows the committed pages converted. Withheld cells get one `info` line per column. ## Measured before acting (the dispatch's H1 to H5) - **H1, confirmed** at `2c1011b`: the method and the statement are exactly as quoted above, guarded by `if (!this.isSqlite || !fields || fields.length === 0) return;` and `if (!tableExisted) return;`. - **H2, confirmed. It is a build-time constant, and every bundled build has 1000.** `json_valid` of an N-level array, measured on each bundled engine: | engine | SQLite | N=1000 | N=1001 | N=2000 | N=2001 | |---|---|---|---|---|---| | better-sqlite3 13.0.3 | 3.53.4 | 1 | 0 | 0 | 0 | | sql.js 1.14.1 | 3.49.1 | 1 | 0 | 0 | 0 | | `@libsql/client` 0.17.4 (local) | 3.45.1 | 1 | 0 | 0 | 0 | `JSON.parse` (Node v22.22.2) reads 1001, 1999, 2000 and 2001 levels. The bundled `sqlite3.c` defines `JSON_MAX_DEPTH 1000` unless `SQLITE_JSON_MAX_DEPTH` is set, and notes the limit "was 2000 prior to version 3.42.0". A Turso server build, or any custom or older build, can therefore differ. The fix does not depend on the value. - **H3, confirmed.** No override of the method exists outside `sql-driver.ts`. `SqliteWasmDriver` forces `isSqlite` and inherits `syncSchema` / `initObjects` unchanged. In local mode, `TursoDriver.syncSchema` goes to `super.syncSchema`, then `initObjects`, then `super.initObjects`; `initObjects` goes to `super`; `syncSchemasBatch` calls `super.syncSchema` once per schema. All three doors reach the backfill, and the Turso local face runs on better-sqlite3 (`toKnexConfig`). The Turso doors are pinned in a test. The wasm face was measured with a scratch probe but is not pinned (see Acceptance notes): through both `syncSchema` and `initObjects`, the 1001-level array read as an array after two backfills, and `bare` was converted. - **H4: the decision rule is shared, the paging machinery is not.** The remote pass runs over libsql `execute`/`batch` (`RemoteBackfillClient`), with a probe and a per-invocation budget. The local pass runs over knex. Sharing the walker would take more than an import swap on the remote side. The pre-filter SQL reads the same on both faces, but it only narrows the scan and never decides. - **H5, confirmed. The two are identical by construction.** The SQLite json arm of `formatOutput` is `JSON.parse(text)` inside a try/catch. The rule asks the same question, and a test pins the link through the driver: the backfill rewrites a cell exactly when the driver's read of that cell answers the stored text itself. **Preservation, byte for byte.** Stored and then read on better-sqlite3, `json_quote(col)` equals `JSON.stringify` of the text read back, for every non-surrogate BMP code point plus astral characters and an embedded NUL: 63,499 samples, 0 mismatches. Lone surrogates never reach disk; better-sqlite3 stores them as U+FFFD. The compare-and-set only writes when the stored bytes equal what was read, so every cell written is written with the bytes the retired statement produced. ## Tests New `packages/drivers/driver-sql/src/sql-driver-json-backfill-depth-limit.test.ts` (7 tests): 1. The card's reproduction: `bare`, a 1001-level array and `[1,2]`. Only `bare` is quoted, and the array still reads as an array after a **second** backfill. 2. Idempotence: `total_changes()` does not move over two re-runs, including with a withheld cell present. 3. Preservation: 11 legacy bare texts (empty, control characters, an embedded NUL, U+2028/2029, a leading U+FEFF, emoji and CJK) are each converted to the exact bytes `select json_quote(?)` gives, and each still reads as itself. 4. The rule is the read codec. The cases are 1000-, 1001- and 2001-level arrays, a 1001-level object, parseable and unparseable texts, `1e400` and an escaped lone surrogate. A cell is rewritten if and only if its pre-backfill read answers its own text, and no read moves. 5. Compare-and-set: a second connection writes the deep array into a candidate row between the page read and the write, and the write leaves it alone. 6. Paging: 1,100 rows, with deep cells at rows 0, 499, 500, 999 and 1099. All 1,095 legacy rows converge in one pass, and the log payloads report `rowsConverted: 1095` and `rowsWithheld: 5`. 7. A unit test of `recoverUnencodedJsonText`. New `packages/drivers/driver-turso/src/turso-local-json-backfill-depth-limit.test.ts` (3 tests) runs the dev's reproduction on `new TursoDriver({ url: ':memory:' })`, once through each local door: `syncSchema`, `initObjects` and `syncSchemasBatch`. Suites run at `74ff944`: - driver-sql: 181 files passed, 11 skipped; 2677 tests passed, 170 skipped. The skips are the live PG and MySQL cells; CI runs them in `Temporal Conformance`. - driver-turso: 60 files, 1334 tests passed. This includes the unchanged `turso-remote-codec-residue-backfill.test.ts`, run against the rebuilt driver-sql `dist`. - driver-sqlite-wasm: 29 files, 518 tests passed. - `tsc --noEmit` exit 0 for driver-sql and driver-turso. `--listFiles` shows each new test file inside its package's program. ## Reverse verification Both ablations went through `scripts/ablation-replace.mjs` (anchor hit 1 time, blob changed, and restore proven as blob == HEAD with an empty `git diff HEAD`) from the committed fix at `74ff944`. - **Ablation 1: the retired statement put back** in place of `convergeJsonColumn`. Afterwards driver-sql was rebuilt. `ablation-dist-preflight` found the marker `json_quote(??)` in `dist/index.js` and `dist/index.mjs`; before the mutation it was absent from both. - driver-sql file: **4 red, 3 green**. Red: the reproduction, the read-codec rule, paging, and compare-and-set. Compare-and-set is red because the old code never reads candidates, so the injection never fired (`expected +0 to be 1`); ablation 2 isolates it. Green: idempotence, preservation, and the unit test, which is the expected direction because the old statement is also idempotent and byte-identical on bare text. - Turso file: **3 of 3 red**, all with `expected false to be true` on `Array.isArray`. - Restore leg: rebuilt, the preflight with `--absent` found the marker in none of the 6 built files, and the tests went back to 7/7 and 3/3. - **Ablation 2: the compare-and-set predicate removed.** The update became `where rowid = ?`. **Exactly one test went red**, compare-and-set: `raced` was overwritten with `"bare"`. After the restore, the file is 7/7 green again. ## Gates `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` at `74ff944` derived 62 families: the dispatch's 56, plus `check:engine-double-contract`, `check:objectql-double-limit`, `check:query-options-erasure`, `check:type-check-coverage`, `check:type-check-debt` and `check:where-matcher`. Reconciled with `--ran` (exit codes recorded): **60 exit 0 and 2 NOT MEASURED** (both exit 3, a missing prerequisite). - `check:dual-build-cjs-loads` needs every workspace package's `dist`, and 78 published entry points have no `dist` here. As a narrowed probe: the CJS and ESM entries of driver-sql and driver-turso both load, and `recoverUnencodedJsonText` resolves from both driver-sql builds. - `check:type-check-debt` is missing the built type entries of 23 dependencies. The two packages this diff touches type-check clean (above). - `check:plugin-teardown-shape --self-test` first exited 3 on the shallow clone (its pinned fixture commit was unreachable). After fetching that one commit it passed, and `check:lean-entry-closure` passed after the `@objectstack/objectql` closure was built. - `check:driver-conformance` gave the same line before (`2c1011b`) and after (`74ff944`): `OK — 50 covered cell(s), 0 in the DEBT ledger, 0 exempt`. - `check:durability-log-level` exit 0: 36 durability-critical seams, all loud. - Narrowed lint, not the repo-wide `pnpm lint`: `eslint --no-inline-config --format json` over the 6 changed TS files gave 6 results, 0 errors and 0 warnings, at `74ff944`. Every one of the 6 falls under the `packages/**/*.{ts,tsx,mts,cts}` blocks of `eslint.config.mjs`, and the `.changeset` file is outside every lint glob. The config enables no type-aware linting (no `parserOptions.project`, no typed rules, as its own comment records), so this diff cannot move the verdict for an untouched file. ## Acceptance notes - **Behaviour on the wasm face, measured only.** sql.js reads text through a decoder that drops a leading U+FEFF, and its bind path truncates at an embedded NUL. Where the read differs from the stored bytes, the compare-and-set does not match, so the cell is not written and keeps reading as it did. The retired statement rewrote such cells, because `json_quote()` works on the stored bytes. For a BOM-prefixed JSON text, that would change this face's read from an array to a string. That last point is reasoned from the two measured reads; it was not run against the old code. The wasm face also used to run a zero-row `UPDATE` on every sync for every json column. Its dirty flag is set by statement kind, so the file-backed image was marked dirty each time. It now runs an `UPDATE` only when a candidate is rejected. A committed wasm pin would be a new file in `driver-sqlite-wasm`, which is outside this card's declared file surface, so none was added. - **Withheld cells cost a read on every sync.** A deep cell stays a pre-filter candidate forever, so it is read and parsed on each sync, with one `info` line per column. These cells are rare by shape. - **The json pre-filter has the same embedded-NUL exception as the date one.** `json_valid()` stops at a NUL, so a text that is valid JSON up to a NUL is never selected. That is the safe direction, and the local doc now says so. The remote module's header names only the date exception ("with one exception in the safe direction (the date bullet)"). This is a gap in the docs, not a defect. - **A cursor stall guard.** If a rowid comes back rounded (past 2^53) and the cursor stops advancing, the pass stops, leaving the rest of the column legacy, which reads the same. --- _Generated by [Claude Code](https://claude.ai/code/session_01Bvd69VPa6puiNzzPUroDBx)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
1 participant
Fixes #19868
Clause-②: no
What this changes
Every remote Turso schema door ends in
completeRemoteSchemaSync. It now runs a second backfill after the canonical temporal one. The new pass converges thedateandjsoncells that the pre-#19844syncSchemasBatchdoor stored withoutformatInput. It rewrites only the cells whose stored text already determines their value.Disposition of the residue the card's title names (seat decision, after the dev's report): a stored
truereading back as1, a string'42'reading back as42, and a string'true'reading back astruehave bytes identical to another writer's. That is the class the maintainer's ruling of 2026-08-26 on #12380 already settled for the local face (packages/drivers/driver-sql/CHANGELOG.md: "The class stops growing; it is not retroactively repaired.", "with that cost accepted explicitly"), for the same reason ("No migration can know which was written"). A new branch of a ruled class reuses that ruling with its reason, so it is the answer on the remote face too: this PR converges every exactly recoverable class, discloses the rest in its changeset, and closes the card. The first line was changed fromRefstoFixesby the seat accordingly.Recoverability, measured (A1/A2)
The pre-fix arm was run on the
libsqlSQLite double:RemoteTransport.syncSchemasBatchalone, thencreatewith no registration. The fixed driver then booted over the same database throughsyncSchemasBatch. The json column is TEXT affinity, so every scalar lands as TEXT andtypeofseparates nothing. The Turso-wire column comes from@libsql/client's hrana encoder, read innode_modules: a JS number is sent asfloat, and a boolean asinteger1n/0n. The double's better-sqlite3 binds a JS number (and the stub'strue→1) as REAL. Both shapes were measured into a TEXT column.'hello'hello(json_valid0)'hello'"hello"''json_valid0)''""true/false1.0/0.01/01/0true/false1.0is also a pre-fix number1.1is also a pre-fix string'1'and the fixed door's number10/1/420.0/1.0/42.00/1/42(correct)0/1/42'42.0'leaves the same bytes)'42'4242"42"42is what the fixed door stores for the number42'true'truetrue"true"trueis what the fixed door stores for the booleantruenullnullDate(UTC midnight)2025-07-28T00:00:00.000Z2025-07-282025-07-28Date= UTC+8 local midnight of 07-282025-07-27T16:00:00.000Z2025-07-272025-07-272025-07-27(see below)…Z/+08:00/-05:00/ zone-naive (space orT) / leading or trailing spaceYYYY-MM-DDYYYY-MM-DDOn the
datequestion in A2: a full timestamp maps to exactly one day under the codec.SqlDriver.toDateOnlytakes the LEADING day of a string (so2025-07-28T23:30:00-05:00is2025-07-28, not the UTC07-29) and the UTC day of aDate. ADatebuilt at local midnight east of UTC therefore already reads, and is already written by the fixed door, as the previous day. Measured withnew Date(2025, 6, 28)underTZ=Asia/Shanghai: stored2025-07-27T16:00:00.000Z, read2025-07-27, and the fixed door stores2025-07-27. The writer's zone is not in the cell, so the day the caller meant is not recoverable by any door. This PR writes the day the codec already answers and does not try to recover the caller's.The invariant the change keeps: it rewrites a cell only when the fixed READ already answers a determined value, and it writes the fixed WRITE door's form of that value. No converted cell reads differently afterwards; that is pinned. What changes is what a filter compares. Before the boot,
{ d: '2025-07-28' }matched only the bare-day row. After it, the filter also matches all 8 full-timestamp rows whose day is 07-28, and{ d: '2025-07-27' }matches the UTC+8 row, which it missed before.Landing site and design
packages/drivers/driver-turso/src/remote-codec-residue-backfill.ts(new): the pass.json_valid() = 0. For date, it is TEXT longer than 10 characters whose left-trimmed first 10 characters glob asYYYY-MM-DD; the trim uses the exactString.prototype.trimset, bound as an argument.JSON.parse/JSON.stringify, theformatOutput/formatInputjson arms. For date it isSqlDriver.toDateOnly.rowidcursor and reuses the temporal backfill'sbatchSizeandmaxBatchesdefaults, 500 × 20. It is resumable: a budget-stopped column is unmarked and resumes at the next sync. A second boot writes nothing.warn.SELECTper table, and all tables go out in one round-trip.turso-driver.ts:completeRemoteSchemaSynccallsbackfillRemoteCodecResidueQuietly()after the temporal backfill, which calls the privatebackfillRemoteCodecResidue(). Per-process marks live inremoteCodecResidueConverged. No public surface was added: the module is not exported fromindex.ts, and the method is private.json_valid()answers 0 at 1001 levels andJSON.parsereads it. It is withheld, because re-quoting it would turn an array into a string. The codec, not SQLite, decides.packages/drivers/driver-sqlis not touched. No helper was shared: the local face'sbackfillCanonicalJsonEncodingis a KnexUPDATE, and this pass needs a rowid walk plus a JS codec.A4: the local face
Measured through
TursoDriverlocal (:memory:)syncSchemasBatchandcreatewith the same inputs. Everydatelands as the 10-character day and every json scalar as its JSON encoding. The local door registers field types before any write, so it has no residue from this door, and nothing here runs locally. Full-timestampdaterows written beforeformatInputgained itsdatearm would be a different producer. They were not measured here (shallow history), and they are not fixed here.Tests
packages/drivers/driver-turso/src/turso-remote-codec-residue-backfill.test.ts, 14 cases, over real SQLite cells:$ltebare-day bound;null, a media column and deep JSON, all left byte-for-byte;UPDATEand one probe statement, and a second sync in-process issues no probe;toDateOnlyover a corpus that includes every trim character, andJS_TRIM_CHARSequals the engine's owntrimover the BMP;Package runs on
257ac60607(patch round 1; round 1 on4afdb8c170read the same counts):pnpm --filter @objectstack/driver-turso test:Test Files 59 passed (59)·Tests 1331 passed (1331).pnpm --filter @objectstack/driver-turso typecheck:tsc --noEmit, exit 0. The package tsconfig includessrc/**/*, so the new test file is compiled.Ablation (on
4afdb8c170; patch round 1 changed spelling and prose only, and the runtimeJS_TRIM_CHARSstring is byte-identical), run once throughscripts/ablation-replace.mjs, which deleted only the wiring lineawait this.backfillRemoteCodecResidueQuietly();. The anchor went 1 → 0, and the blob wenta686f4985bc4→ae43cfb30ecb. Four pins went red: the date rewrite and filter, the json re-encode, no-read-change (whose non-vacuity leg fails), and idempotence (the probe count).Tests 4 failed | 10 passed (14). The restore was proven: bloba686f4985bc4equals HEAD,git diff HEADis empty, andgit statusis clean. The source resolves through a relative import, so nodist/is involved.Gates
On
257ac60607(patch round 1):--commandsderived the same 61 commands (diff empty), and after a cached whole-package build all 61 exited 0 on the first pass;--ran:61 run, 0 NOT-MEASURED.pnpm check:nul-bytes,node scripts/check-issue-citations.mjsandnode scripts/check-changeset-no-major.mjs --base origin/main: exit 0.Round 1:
node scripts/pm/dispatch-gates.mjs --commandson4afdb8c170derived 61 commands, each run with its exit captured before any pipe. Three first exited 3 (PREREQUISITE NOT MET:dual-build-cjs-loads,lean-entry-closure,type-check-debt). After building the objectql closure and all packages (turbo run build --filter='./packages/*' --filter='./packages/*/*'), all three exited 0.--ran:61 derived famil(ies) accounted for — 61 run, 0 NOT-MEASURED. Also by hand:node scripts/check-issue-citations.mjs(the live verdict): exit 0.pnpm check:driver-conformance: exit 0.pnpm check:nul-bytes: exit 0.Acceptance notes
SqlDriver.backfillCanonicalJsonEncodingselectsjson_valid(??) = 0, so a json value nested past 1000 levels isjson_quoted into a string on the nextsyncSchema. Reproduced onTursoDriverlocal:memory:: before the re-sync,Array.isArray(row.j)istrue; after it,false(typeofstring), and the cell starts with a quote character.dateor json columns, once per process. Turso bills rows read.libsqldouble does not bind like the Turso wire: better-sqlite3 binds every JS number, and the stub'strue→1, as REAL, while hrana sends a boolean as INTEGER. The tests pin both shapes.resolveFileColumnsMoved, so an engine-supplied ADR-0104 resolver is never asked in remote mode. Whether a remote deployment can reach the moved state was not measured.Generated by Claude Code