Observation-class finding, filed unassigned while re-transcribing the ObjectOS quickstart boot samples against @objectstack/cli 17.3.0 (objectstack-ai/objectos#141, PR objectstack-ai/objectos#264). No action requested — routing and grading are the triage seat's.
What a clean boot prints
Booting @objectstack/cli@17.3.0 — both os start on an empty kernel and pnpm dev on a fresh os init -t app scaffold — emits 5 [sql-driver] warning blocks, naming only the platform's own system tables:
[sql-driver] while creating table "sys_metadata_commit": declared field 'id' asks for storage
the platform's own 'id' column does not provide — maxLength: 64 (the column is 255). The
platform emits id/created_at/updated_at itself, so THOSE attributes are not applied; ...
{
table: 'sys_metadata_commit',
field: 'id',
phase: 'create',
undelivered: [ 'maxLength' ]
}
Two distinct tables are involved — sys_metadata_commit and sys_http_delivery — across phase: 'create' and phase: 'alter'.
Why this looks like residue rather than the intended steady state
The warning itself is working as designed: it is the diagnostic that #12015 was filed for, since a declared id used to be discarded silently. The finding is not the warning — it is that the platform's own shipped declarations are what trip it, on a first boot, with nothing user-authored involved.
That is the same class #12131 cleared for 45 system objects declaring id as text. These two are a narrower sibling residue: the attribute is maxLength: 64 rather than a type, so they survived that sweep. The remedy the warning itself recommends — "Drop the storage attribute(s) named above" — appears to be exactly right here, since nothing can honour a maxLength on a column the platform emits itself.
Measured, not recalled
Captured on a pty from a pristine home, with a 17.2.0 control booted from an exact-pinned scaffold:
|
17.2.0 |
17.3.0 |
[sql-driver] warning lines, os start |
338 |
5 |
[sql-driver] warning lines, pnpm dev |
356 |
5 |
So this is being actively worked down and is nearly finished — 338 to 5 in one minor release. This card is about the remainder, and is filed precisely because a count that small is the one most likely to be left as permanent background noise.
Why it is worth a card at all
A first-run quickstart is the highest-leverage first impression the platform has, and the reader cannot tell a warning about the platform's internals from one about their own code. It also has a documentation cost that is already being paid: the quickstart's two declaration sentences now have to name these warnings among the output they omit (objectstack-ai/objectos#264), and declaring noise is not the same as the noise being correct.
Related: #12015 (added this diagnostic), #12131 (cleared the 45-object text residue), objectstack-ai/objectos#141, objectstack-ai/objectos#264.
Observation-class finding, filed unassigned while re-transcribing the ObjectOS quickstart boot samples against
@objectstack/cli17.3.0 (objectstack-ai/objectos#141, PR objectstack-ai/objectos#264). No action requested — routing and grading are the triage seat's.What a clean boot prints
Booting
@objectstack/cli@17.3.0— bothos starton an empty kernel andpnpm devon a freshos init -t appscaffold — emits 5[sql-driver]warning blocks, naming only the platform's own system tables:Two distinct tables are involved —
sys_metadata_commitandsys_http_delivery— acrossphase: 'create'andphase: 'alter'.Why this looks like residue rather than the intended steady state
The warning itself is working as designed: it is the diagnostic that #12015 was filed for, since a declared
idused to be discarded silently. The finding is not the warning — it is that the platform's own shipped declarations are what trip it, on a first boot, with nothing user-authored involved.That is the same class #12131 cleared for 45 system objects declaring
idastext. These two are a narrower sibling residue: the attribute ismaxLength: 64rather than a type, so they survived that sweep. The remedy the warning itself recommends — "Drop the storage attribute(s) named above" — appears to be exactly right here, since nothing can honour amaxLengthon a column the platform emits itself.Measured, not recalled
Captured on a pty from a pristine home, with a 17.2.0 control booted from an exact-pinned scaffold:
[sql-driver]warning lines,os start[sql-driver]warning lines,pnpm devSo this is being actively worked down and is nearly finished — 338 to 5 in one minor release. This card is about the remainder, and is filed precisely because a count that small is the one most likely to be left as permanent background noise.
Why it is worth a card at all
A first-run quickstart is the highest-leverage first impression the platform has, and the reader cannot tell a warning about the platform's internals from one about their own code. It also has a documentation cost that is already being paid: the quickstart's two declaration sentences now have to name these warnings among the output they omit (objectstack-ai/objectos#264), and declaring noise is not the same as the noise being correct.
Related: #12015 (added this diagnostic), #12131 (cleared the 45-object
textresidue), objectstack-ai/objectos#141, objectstack-ai/objectos#264.