Type the ledger through drizzle - #21
Merged
Merged
Conversation
…e schema. Keep the v14 SQL ladder for existing databases; drop the hand-written row/report types that just restated what the queries already return. Co-authored-by: Cursor <cursoragent@cursor.com>
Octember
added a commit
that referenced
this pull request
Aug 14, 2026
The concurrent ledger rewrite absorbed a stale partial copy of this branch; this is the reconciliation: main's idiom (drizzle orm, typed one/many, guard helpers, pedantic oxlint), the branch's final reviewed semantics — provenance- gated recentIdenticalPost (+already-landed sentinel), failCards, absolute slack paths, v15 terminal-report triggers, §8.6 recent tier + decay, per-identity workspaces, message-ref task_confirm, dead code kept dead (no guests, no distillation/ambient chains). agent-tools pinned 0.5.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Octember
added a commit
that referenced
this pull request
Aug 14, 2026
The concurrent ledger rewrite absorbed a stale partial copy of this branch; this is the reconciliation: main's idiom (drizzle orm, typed one/many, guard helpers, pedantic oxlint), the branch's final reviewed semantics — provenance- gated recentIdenticalPost (+already-landed sentinel), failCards, absolute slack paths, v15 terminal-report triggers, §8.6 recent tier + decay, per-identity workspaces, message-ref task_confirm, dead code kept dead (no guests, no distillation/ambient chains). agent-tools pinned 0.5.1. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
src/ledger/schema.tsas the query-time contract (JSON columns typed, enums derived from the tables).schema.sql) is unchanged, so existing ledgers and the v1→14 migration test still apply. FTS5 / triggers stay custom SQL.RewindReport,TimerRow,AuditRecord, status/budget wrappers, etc.) that just restated what the schema or the function already returns.Test plan
bun run typecheckbun run lintbun test(413 pass)Made with Cursor