fix(autonumber): single owner = persistent driver sequence (#1603)

[xuyushun441-sys]

Summary

Closes the #1603 "persistent autonumber sequence" gap by making autonumber generation single-owner.

Today autonumber values are generated in two places:

• the SQL driver's persistent, atomic _objectstack_sequences table (getNextSequenceValue / fillAutoNumberFields), and
• a non-persistent in-memory counter in the ObjectQL engine (applyAutonumbers).

Because the engine pre-fills the field before calling the driver, the driver always sees a value already set and skips (fillAutoNumberFields line ~618). So the persistent sequence is effectively dead code, and a multi-instance / post-restart deployment can mint duplicate numbers from the in-memory counter.

Changes

@objectstack/spec

• DriverCapabilities gains an optional autonumber flag — "driver natively generates persistent autonumber/sequence values".

@objectstack/driver-sql

• Advertises supports.autonumber = true.
• bulkCreate() now fills autonumber fields too — previously only create() / upsert() did, so bulk inserts skipped the sequence.
• Field parsing honors either the spec-canonical autonumberFormat key or the format shorthand (both appear in metadata). This prevents a format-loss regression now that the driver path is the live one.

@objectstack/objectql

• When the driver advertises native autonumber support, the engine no longer pre-fills — it defers entirely to the persistent driver sequence (single source of truth). For drivers without native support (memory, mongodb) the in-memory fallback is unchanged.
• The fallback also reads either autonumberFormat or format.
• Record-validation exempts autonumber from the required check — the value is runtime-owned and assigned after validation, so a required record number is never rejected as "missing".

No metadata changes required. Existing data is respected — the driver bootstraps each sequence from the current max numeric tail on first use (scanMaxNumericTail).

Testing

• driver-sql (140 pass): new tests for bulkCreate autonumber fill, the autonumberFormat key, and the supports.autonumber capability — plus the existing per-tenant / bootstrap / concurrency / global-sequence suite.
• objectql (526 pass): new engine-autonumber-defer.test.ts (native driver → engine does NOT pre-fill and never scans; non-native driver → engine fallback fills) and record-validator.test.ts (required autonumber missing → no error; required non-autonumber missing → error).
• Both packages build type-clean.

Risk

This activates a previously-dormant-but-fully-tested driver path. The driver's autoNumberFields map is already populated in production via syncSchema → initObjects, so generation does not silently stop. The format-key harmonization removes the one regression vector (metadata declaring autonumberFormat).

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Building	Preview, Comment	Jun 6, 2026 7:59am