fix: align root write context schema metadata - #276
Merged
Joncallim merged 11 commits intoJul 27, 2026
Merged
Conversation
test: run root privilege mutations in upgrade proof
test: use root owner for grant option mutation
test: bind root grantor to mutation session
test: close root reconciler grant options
test: close root reconciler column privileges
Joncallim
marked this pull request as ready for review
July 27, 2026 21:07
Joncallim
merged commit Jul 27, 2026
99ca55b
into
codex/pr198-ordinary-app-trigger-inputs
2 of 3 checks passed
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.
Scope
Aligns the protected write-context table’s physical PostgreSQL metadata with its Drizzle declaration.
pg_catalog.clock_timestamp()forentered_at; Drizzle now expresses the same wall-clock default rather thannow()/ transaction-start time.Compatibility
Migration 0027 is unshipped in this stack, so the corrected DDL applies directly on fresh and populated upgrade paths; no applied-database constraint rename is needed. No constraints are dropped or rebuilt.
Validation
clock_timestamp()defaultnpm test -- --run __tests__/project-root-reconciliation.test.ts(21 passed)npm test(1,630 passed, 19 skipped)npx eslint --max-warnings=0 db/schema.ts __tests__/project-root-reconciliation.test.tsnpx tsc --noEmitnpm run buildgit diff --check