relytcloud

Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch). MUST consult when: deciding a version number, cutting a release, creating a version tag, opening a release/patch branch, or backporting a bug fix.

Code style, include order, docs update rules, and submodule policy. MUST consult when: writing or modifying C/C++ files (include order matters), adding/removing/changing ducklake.* SQL functions or procedures (keep their inline comments in pg_ducklake--*.sql current), editing third_party/ code, or reviewing code for style.

Commit message conventions (Conventional Commits). Consult before every git commit.

Dev environment setup: build tools, PostgreSQL, submodules, worktrees. Always import on EnterWorktree/ExitWorktree.

Bump pg_ducklake (and optionally DuckDB) to a new version. Updates all pinned commits and version constants across the repo.

Build pg_duckpipe and all dependencies (PostgreSQL, pg_ducklake) from source into deps/

Set up a running PostgreSQL instance with pg_duckdb, pg_ducklake, and pg_duckpipe extensions loaded