This index routes; the owning handbook leaves explain.
One row per file,
with the purpose taken from the file's own header line
and the grouping from the handbook leaf that owns the topic —
ownership by topic, navigation by place
(the rules).
Root of the documentation tree: handbook/.
| File | Purpose |
|---|
format.py | Format the source directory; driven by the Makefile's format-* targets. |
python_helpers.py | Shared file helpers for the Python scripts in this directory (imported by format.py). |
| File | Purpose |
|---|
rethrow.R | Generate R/rethrow-gen.R from R/cpp11.R: wrap each rapi_* binding to rethrow errors with call context; sourced by .Rprofile on repo load. |
| File | Purpose |
|---|
vendor-rfuns.sh | Vendor the rfuns extension: copy sources from a duckdb-rfuns checkout into src/ and commit with the upstream log, one commit per import. |
| File | Purpose |
|---|
flavor-package-name.R | Guard for the flavor rename. |
flavor.patch | — |
flavor.sh | Apply a package flavor: rewrite scripts/flavor.patch to the target name (say, duckdb.dev), apply it, and commit the rename; see BRANCHES.md. |
| File | Purpose |
|---|
install-duckdb-cli.sh | Download the standalone DuckDB CLI matching the vendored DuckDB sources under src/duckdb/. |
install-libduckdb.sh | Install the libduckdb prebuilt binary matching the vendored DuckDB sources under src/duckdb/. |
| File | Purpose |
|---|
warnings.sh | The compiler-warning gate: what each scope is held to, and the check itself. |
| File | Purpose |
|---|
each-shard.sh | Build one shard of an each-rcc plan: many commits, one job, one workspace. |
rcc-one.sh | Run the per-commit rcc gate against the working tree, once. |
| File | Purpose |
|---|
each-cost.py | Estimate how many unity objects a change invalidates. |
each-partition.py | Partition a commit range into contiguous, cost-balanced each-rcc shards. |
each-plan.sh | Plan the sharded per-commit rcc build for the checked-out branch. |
| File | Purpose |
|---|
rcc-decided.sh | Print the SHA of every commit the verdict store has decided, one per line. |
| File | Purpose |
|---|
rcc-consolidate.sh | Consolidate the orphan rcc2 branch: drop everything past the retention window, and squash the whole history to two commits. |
rcc-cutover.sh | One-shot: build the rcc2 verdict store from what the old rcc branch holds. |
rcc-lib.sh | Shared helpers for the verdict store on the orphan rcc2 branch. |
rcc-logs.sh | Collect rcc results and failure logs for commits the verdict store has no record for, and stage them for publication to the orphan rcc2 branch. |
rcc-publish.sh | Publish a staging directory to the verdict store on the orphan rcc2 branch. |
rcc-run-fields.jq | The subset of a GitHub workflow-run object that a record on the rcc2 branch carries, applied to gh api repos/{owner}/{repo}/actions/runs/<id>. |
rcc-store-test.sh | Check the invariants the verdict store rests on, offline, against a local bare repository -- optionally seeded from the real rcc branch. |
| File | Purpose |
|---|
VENDORING.md | DuckDB R Package Vendoring |
merge-version.sh | Git merge driver for DESCRIPTION. |
rconfigure.py | Regenerate the vendored build configuration from a DuckDB checkout: src/duckdb/, src/include/sources.mk, R/version.R, the Makevars files and the logos. |
setup-git.sh | Register repository-local git configuration that cannot live in versioned files. |
vendor-one.sh | Vendors DuckDB sources commit-by-commit from the upstream repository. |
vendor.sh | Vendors DuckDB sources from the upstream repository (manual vendoring). |
| File | Purpose |
|---|
r-universe-check.sh | Read-only: what did r-universe make of the refs this repository publishes? |
series-advance-test.sh | Check stage 5's carry of the base series' test-side fixes, offline, against a synthetic remote and clone built here -- no network, no fixtures on disk. |
series-advance.sh | The ref motion of the series loop, stages 3 and 5, for one series: fast-forward <S>-green over the all-green prefix, set <S>-build-base to the equivalent... |
series-check.sh | Read-only diagnosis for the series loop: what should a firing do? |
series-cutover.sh | Atomically replace a series with its forward counterpart. |
series-forward-build.sh | Populate <S>-fwd-build: replay every vendor commit of the old <S>-build onto HEAD, which must be the freshly flavored seed on current main (.claude/ski... |
series-glue.sh | Every R-side glue adaptation a series carries, in one read. |
series-port.sh | Bring a series' -dev branch level with main — stage 4 of the series loop (.claude/skills/series-loop.md). |
| File | Purpose |
|---|
snapshot-accept.sh | Rebuild a commit, run the suite, accept the named snapshots, re-run to confirm they hold. |