fix(state): declare apns_registration_tombstones STRICT#108850
Merged
Conversation
The canonical SQLite schema requires every OpenClaw-owned table to be STRICT (src/infra/sqlite-strict.ts). apns_registration_tombstones (added in #108543) was declared without STRICT, so gateway startup migration throws "Canonical SQLite schema contains non-STRICT tables" and every gateway-boot test fails. Match the sibling apns_registrations table.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Main is broken: gateway startup migration throws
Canonical SQLite schema contains non-STRICT tables: apns_registration_tombstones, failing every gateway-boot test across the node/contract/QA-smoke shards.Why This Change Was Made
src/infra/sqlite-strict.tsrequires every OpenClaw-owned canonical table to be declaredSTRICT(no allowlist).apns_registration_tombstones, added in #108543, was declared withoutSTRICTwhile its siblingapns_registrations(andnode_host_config, etc.) areSTRICT. This regenerates the canonical schema with) STRICT;.User Impact
Unblocks CI for all open PRs and restores clean gateway startup. No behavior change beyond the table now enforcing STRICT column typing, consistent with every other canonical table.
Evidence
src/state/openclaw-state-schema.sql+ regeneratedopenclaw-state-schema.generated.tsnow declare the tableSTRICT.node scripts/run-vitest.mjs src/infra/sqlite-strict.test.ts→ 14/14 passed.node scripts/generate-kysely-types.mjs --verifyclean (generated matches source).