docs: correct stable row ID migration and storage

[lance-gatefixer]

Summary

• document how existing datasets migrate to stable row IDs and the index/concurrency constraints
• clarify that current writers always emit row ID and version sequences inline
• mark external version-sequence fields as unsupported and reserved while retaining the supported external row-ID read contract

Root cause

The format documentation and protobuf comments still described pre-implementation plans: they said existing datasets could not migrate and presented a 200 KB inline/external threshold as active writer behavior. Migration has since shipped, but writers still emit every sequence inline and readers cannot load external version sequences.

Validation

• protoc --proto_path=../protos --descriptor_set_out=/dev/null ../protos/table.proto
• uv run mkdocs build (completed with pre-existing missing-link warnings outside this change)
• git diff --check

Fixes #8851

[github-actions]

Important

Format specification vote

This PR modifies the Lance format specification, so it requires 3 binding +1 votes from PMC members (excluding the proposer) and a minimum 72-hour voting period, weekends excluded, before it can merge. Vote by approving this PR (+1) or requesting changes (−1, a veto). See the voting process.

Status: ❌ Blocked — 0 of 3 required approvals

Approvals (this commit)	none (0/3)
Vetoes	none
Voting period	ends Wed 2026-09-02 19:20 UTC (12:20 PDT)

_{Updated automatically by the format-spec vote gate, which re-checks every 15 minutes — just voted? Re-check now (press Run workflow; leave the input blank to re-check every open format PR). A PMC member may apply the format-waived label to waive the vote for a trivial edit (typo, wording, formatting).}

[lance-gatefixer]

Blocked: the current head cannot pass format-spec-vote until the required PMC approval process is satisfied.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1; the live format-spec-vote status reports 0/3 PMC approvals on this commit, while Actions run 33204888739 and its evaluator job completed successfully. I fetched both branches, verified ancestry, inspected the current-head status and logs, and found no terminal build or test failure or attributable code defect to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot pass format-spec-vote until the required PMC approval process is satisfied.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1; the live format-spec-vote status reports 0/3 PMC approvals on this commit, while current-head Actions run 33205470285 and its evaluator job completed successfully. I fetched both branches, verified ancestry, inspected all current-head checks and the evaluator logs, and found no terminal build or test failure or attributable code defect to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head is held by an unrelated Windows runner failure and the required format-spec approval gate.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1. Python windows job 98963312295 failed only test_torch_index_with_nans[Legacy] because PyTorch Inductor received PermissionError reopening a generated runner-temp file; the same test passed on Windows for the exact base in job 98918373866, and this branch changes only Markdown and protobuf comments. Separately, format-spec-vote reports 0/3 PMC approvals on this commit. I fetched both branches, verified ancestry, compared the current-head and exact-base logs, and found no attributable code defect to repair. The smallest next actions are to rerun the failed Windows job on a clean hosted runner and obtain the required three binding +1 PMC approvals after the voting period; practical alternatives are rerunning the full Python workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

[lance-gatefixer]

Blocked: the current head remains held by an unrelated Windows hosted-runner failure and the required format-spec approval gate.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1. Python windows job 98963312295 failed only test_torch_index_with_nans[Legacy] because PyTorch Inductor received PermissionError reopening a generated runner-temp file; exact-base Windows job 98918373866 passed that test and all 1,364 tests, while this branch changes only Markdown and protobuf comments. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, and evaluator run 33209947118 completed successfully. I fetched both branches, verified ancestry, compared the current-head and exact-base logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next actions are to rerun the failed Windows job on a clean hosted runner and obtain three binding +1 PMC approvals after the voting period; practical alternatives are rerunning the full Python workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33216656108 and reports 0/3 PMC approvals on this commit; its evaluator job 99001687932 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33217104161 and reports 0/3 PMC approvals on this commit; its evaluator job 99003082863 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33218990261 and reports 0/3 PMC approvals on this commit; its evaluator job 99008845859 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33219934264 and reports 0/3 PMC approvals on this commit; its evaluator job 99011652281 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33220685156 and reports 0/3 PMC approvals on this commit; its evaluator job 99013887195 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33221480344 and reports 0/3 PMC approvals on this commit; its evaluator job 99016231702 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33222441276 and reports 0/3 PMC approvals on this commit; its evaluator job 99019148730 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: PR #8852 at current head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by a non-attributable flaky macOS HNSW test and the required format-spec approval gate.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Rust mac-build (stable) job 99450847267 failed test_distance_range_prefilter_dispatch::case_1_prefetch with row IDs [] instead of [0]; exact-base macOS job 99450575155 passed the identical case and all 8,658 tests, and the base and repair heads have the identical HNSW source blob. The focused test failed once locally and passed on an immediate rerun, providing direct nondeterminism evidence. Format-vote run 33380610296 and evaluator job 99451898412 completed successfully but report PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, reproduced the alternating focused-test outcome, validated protobuf parsing, Rust formatting, diff checks, and the documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job on a clean hosted runner and obtain three binding PMC approvals after the voting period. Practical alternatives are rerunning the complete Rust workflow and, if this documentation correction qualifies under repository policy, having a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at current head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by a non-attributable flaky macOS HNSW test and the required format-spec approval gate.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Rust mac-build (stable) job 99450847267 failed test_distance_range_prefilter_dispatch::case_1_prefetch with row IDs [] instead of [0]; exact-base macOS job 99450575155 passed all 8,658 tests, the base and repair heads have identical HNSW source blob 005c09893f0a7199b3d5df4dbb0879f2f5edf69a, and repeated focused runs at this head have both passed and failed. Format-vote run 33380610296 and evaluator job 99451898412 completed successfully but report PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, reproduced the nondeterministic focused-test outcome, validated protobuf descriptor generation, Rust formatting, diff checks, and the documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job on a clean hosted runner and obtain three binding PMC approvals after the voting period. Practical alternatives are rerunning the complete Rust workflow and, if this documentation correction qualifies under repository policy, having a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at current head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by a non-attributable flaky macOS HNSW test and the required format-spec approval gate.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Rust mac-build (stable) job 99450847267 failed test_distance_range_prefilter_dispatch::case_1_prefetch with row IDs [] instead of [0]; exact-base macOS job 99450575155 passed all 8,658 tests, the base and repair heads have identical HNSW source blob 005c09893f0a7199b3d5df4dbb0879f2f5edf69a, and repeated focused runs at this head have both passed and failed. Format-vote run 33382904013 and evaluator job 99459025064 completed successfully but report PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, reproduced the nondeterministic focused-test outcome, validated protobuf descriptor generation, Rust formatting, diff checks, and the documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job on a clean hosted runner and obtain three binding PMC approvals after the voting period. Practical alternatives are rerunning the complete Rust workflow and, if this documentation correction qualifies under repository policy, having a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at current head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by a non-attributable flaky macOS HNSW test and the required format-spec approval gate.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Rust mac-build (stable) job 99450847267 failed test_distance_range_prefilter_dispatch::case_1_prefetch with row IDs [] instead of [0]; exact-base macOS job 99450575155 passed all 8,658 tests, the base and repair heads have identical HNSW source blob 005c09893f0a7199b3d5df4dbb0879f2f5edf69a, and repeated focused runs at this head have both passed and failed. Format-vote run 33383911206 and evaluator job 99462117096 completed successfully but report PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, reproduced the nondeterministic focused-test outcome, validated protobuf descriptor generation, Rust formatting, diff checks, and the documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job on a clean hosted runner and obtain three binding PMC approvals after the voting period. Practical alternatives are rerunning the complete Rust workflow and, if this documentation correction qualifies under repository policy, having a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at current head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by an inherited flaky macOS HNSW test and the required format-spec approval gate.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains the current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. The current-head mac-build (stable) job 99450847267 fails only test_distance_range_prefilter_dispatch::case_1_prefetch with [] instead of [0]; exact-base macOS job 99450575155 passed that test and all 8,658 tests, the relevant source blob is identical on base and repair, and repeated focused current-head runs alternate between passing and the same failure. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, while evaluator run 33385064077 job 99465740721 succeeded. I fetched both refs, verified ancestry and PR identity, inspected current-head and exact-base logs, reran the scoped diff, protobuf, formatting, and documentation validations, and pushed normally; no attributable defect remains in the two-file documentation/protobuf repair. The smallest next actions are to rerun the failed macOS job and obtain three eligible PMC approvals after the required voting period; practical alternatives are to rerun the full Rust workflow and, if this correction qualifies as trivial, have a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by the current macOS Rust failure and the format-spec vote requirement.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Current-head mac-build (stable) job 99450847267 fails only test_distance_range_prefilter_dispatch::case_1_prefetch with [] instead of [0]; exact-base macOS job 99450575155 passed all 8,658 tests, the implicated HNSW source blob is identical on base and repair, and the repair diff contains only the two documentation/protobuf files. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, although evaluator run 33387324564 job 99472778018 succeeded.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, validated the scoped diff, protobuf descriptor generation, Rust formatting, and documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job and obtain three eligible PMC approvals after the required voting period. Practical alternatives are to rerun the complete Rust workflow and, if repository policy permits for this correction, have a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by the current macOS Rust failure and the format-spec vote requirement.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Current-head mac-build (stable) job 99450847267 fails only test_distance_range_prefilter_dispatch::case_1_prefetch with [] instead of [0]; exact-base macOS job 99450575155 passed all 8,658 tests, the implicated HNSW source blob is identical on base and repair, and the repair diff contains only the two documentation/protobuf files. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, although evaluator run 33388513482 job 99476488830 succeeded.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, validated the scoped diff, protobuf descriptor generation, Rust formatting, and documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job and obtain three eligible PMC approvals after the required voting period. Practical alternatives are to rerun the complete Rust workflow and, if repository policy permits for this correction, have a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 remains blocked by the current macOS Rust failure and the format-spec vote requirement.

Remote head 709e1d06dcbf09e4562c5c594cec13ccdad10a95 contains current main tip f39a275ccd22d9c1a4d6a95346d0c0cb50d45ade. Current-head mac-build (stable) job 99450847267 fails only test_distance_range_prefilter_dispatch::case_1_prefetch with [] instead of [0]; exact-base macOS job 99450575155 passed all 8,658 tests, the implicated HNSW source blob is identical on base and repair, and the repair diff contains only the two documentation/protobuf files. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, although evaluator run 33389855210 job 99480734545 succeeded.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current-head and exact-base logs, validated the scoped diff, protobuf descriptor generation, Rust formatting, and documentation build, and pushed normally; no attributable repository defect remains. The smallest next actions are to rerun the failed macOS job and obtain three eligible PMC approvals after the required voting period. Practical alternatives are to rerun the complete Rust workflow and, if repository policy permits for this correction, have a PMC member apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every current-head build and test Check, including mac-build (stable), succeeds; the sole failing status is format-spec-vote. Evaluator run 33394783938 job 99496599044 completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current status and evaluator log, validated the scoped diff, protobuf descriptor generation, Rust formatting, and documentation build, and pushed normally; no attributable repository defect remains. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every current-head build and test Check, including mac-build (stable), succeeds; the sole failing status is format-spec-vote. Evaluator run 33396881671 job 99503393312 completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current status and evaluator log, and validated the scoped diff; no attributable repository defect remains. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every current-head build and test Check, including mac-build (stable), succeeds; the sole failing status is format-spec-vote. Evaluator run 33398793952 job 99509726366 completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current status and evaluator log, and validated the scoped diff; no attributable repository defect remains. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every current-head build and test Check, including mac-build (stable), succeeds; the sole failing status is format-spec-vote. Evaluator run 33400308333 job 99514728636 completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current status and evaluator log, and validated the scoped diff; no attributable repository defect remains. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every current-head build and test Check, including mac-build (stable), succeeds; the sole failing status is format-spec-vote. Evaluator run 33402576063 job 99522224149 completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the current status and evaluator log, and validated the scoped diff; no attributable repository defect remains. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every executable current-head Check succeeds; the sole failing status is format-spec-vote. Evaluator run 33404572454, job 99528826426, completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the live checks and evaluator log, and validated the scoped diff with git diff --check; no attributable repository defect remains to repair. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head babd27da521f454bd7339d1f2b22230b45369bfb remains blocked solely by the required format-spec vote approval gate.

Remote head babd27da521f454bd7339d1f2b22230b45369bfb contains current main tip 987adde0d611ada5e5d8176264bf61b388600963. Every executable current-head Check succeeds; the sole failing status is format-spec-vote. Evaluator run 33406108503, job 99533977454, completed successfully and its log reports PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and exact Ready-PR identity, inspected the live checks and evaluator log, and validated the scoped diff with git diff --check; no attributable repository defect remains to repair. The smallest action is for three eligible PMC members to approve this exact commit after the required voting period. If repository policy permits for this correction, a practical alternative is for a PMC member to apply format-waived.

[lance-gatefixer]

Blocked: PR #8852 at remote head 457e5ebcde6abe6bae61ae73bf12cf1a9655dd62 remains blocked solely by the required format-spec-vote approval gate.

Remote head 457e5ebcde6abe6bae61ae73bf12cf1a9655dd62 contains the current main tip a6016f1f6f5e3ecd8f91e4b3c3a13b643f2d4470. The live format-spec-vote status from Actions run 33410326212 reports 0/3 PMC approvals on this commit; its evaluator job 99547998622 completed successfully, and all 30 other current-head checks pass. I fetched both branches, verified ancestry and PR identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable repository failure remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatefixer]

Blocked: PR #8852 at remote head 457e5ebcde6abe6bae61ae73bf12cf1a9655dd62 remains blocked solely by the required format-spec-vote approval gate.

Remote head 457e5ebcde6abe6bae61ae73bf12cf1a9655dd62 contains the current main tip a6016f1f6f5e3ecd8f91e4b3c3a13b643f2d4470. The live format-spec-vote status from Actions run 33411806551 reports 0/3 PMC approvals on this commit; its evaluator job 99552920738 completed successfully, and all 30 other current-head checks pass. I fetched both branches, verified ancestry and PR identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable repository failure remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

[lance-gatekeeper]

✅ Gate recommendation: approve.

The merge from main leaves the pull-request patch unchanged. The new base widens floating-point accumulators used by vector normalization; it changes vector values only and leaves row identifiers, index metadata and commit rebasing, and row/version-sequence serialization untouched. The previously verified migration, index-quiescence, and inline/external storage guidance therefore remains accurate.