Repository navigation
SQLite ladder + delivery hardening, green from-empty E2E - #17
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
SQLite target needs no Docker or cloud: new nextjs-sqlite-vercel preset, scaffold branches (sqlite provider/file URL, no supabase client, no compose), provision records the target, provider-aware DB check (COUNT probes for sqlite). From-empty E2E green: all 19 checks pass. Delivery hardening: HANDOFF excluded from delivery commits, scaffold output committed so agents see the app, post-merge guard against silent loss, .gitignore covers .worktrees. Also fixed: compose YAML flattened by continuations; artifacts moved out of the repo. Tests: 242 lib + 42 integration. Docs: LOCAL-DATABASE.md.
This branch was successfully deployed
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.
Closes the local-database loop: a zero-dependency SQLite ladder plus delivery hardening, with a green from-empty E2E.
SQLite ladder (no Docker, no cloud)
nextjs-sqlite-vercelpreset (database: sqlite, no MCP requirement).provider = "sqlite"+file:./dev.db, no supabase client/lib, no compose file, local-first.env.sqlitetarget without touching Docker; verification's DB check is provider-aware (to_regclassfor Postgres, per-modelCOUNTprobes for SQLite —db executeprints no rows there).db push→ all 19 checks pass, includingdatabase reachable + schema appliedand E2E runtime. ~6 min.Delivery hardening (from real-run evidence)
HANDOFF_*.mdexcluded from delivery commits (it leaked into the deliverable, same class as.acc/).commit_scaffold_output, exactly the scaffold's file list): agent worktrees branch from the base branch, and uncommitted scaffold output was invisible to every agent — an agent literally reported "no package manifest exists in this worktree". History now readsempty → scaffold → agent → merge..gitignorenow covers.worktrees/.Also fixed on the way
render_compose_ymlused\-continuations that strip indentation → flattened YAML with a duplicatevolumes:key, caught only by the live Docker test. Rewritten as a raw string + structural assertions.git statusclean.Gates
Rust 242 lib + 42 integration (3 real-agent tests ignored), Web 341, tsc/lint clean.
Still pending
Live container boot (Docker engine was down; self-skipping live test + exact commands in LOCAL-DATABASE.md) and the cloud-migration proof (
EXTERNAL-VERIFICATION.md).