sneak/bsdaily
1
0
Fork 1
Code Issues 2 Pull Requests 2 Actions 3 Packages Projects Releases Wiki Activity

Reformat the existing Markdown with prettier (closes #7)
check / check (push) Successful in 4m50s
Details

Browse Source 
The output of make fmt after the previous commit: README.md and TODO.md
are rewrapped at 80 columns, and the TODO.md Workflow list uses -
markers. No wording changes. REPO_POLICIES.md was already formatted.

Model: opus-5-5
This commit is contained in:
clawbot
2026-10-06 06:31:14 +00:00
parent 47e48a2529
commit 8125d4aebf
2 changed files with 147 additions and 153 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+120 -126
View File
@@ -1,28 +1,26 @@
# bsdaily # bsdaily
[bsdaily](https://git.eeqj.de/sneak/bsdaily) is a command-line utility [bsdaily](https://git.eeqj.de/sneak/bsdaily) is a command-line utility written
written in [Go](https://golang.org) that carves a single day (or a range of in [Go](https://golang.org) that carves a single day (or a range of days) of
days) of [Bluesky](https://bsky.app) firehose data out of a large, [Bluesky](https://bsky.app) firehose data out of a large, continuously-growing
continuously-growing SQLite database and writes it out as a self-contained, SQLite database and writes it out as a self-contained,
[zstd](https://facebook.github.io/zstd/)-compressed SQL dump. The dumps are [zstd](https://facebook.github.io/zstd/)-compressed SQL dump. The dumps are
named by date (e.g. `2026-06-27.sql.zst`), organized into per-month named by date (e.g. `2026-06-27.sql.zst`), organized into per-month directories,
directories, and are designed to be published, archived, mirrored, and later and are designed to be published, archived, mirrored, and later re-merged back
re-merged back into a single database. into a single database.
The source database is read from a read-only [ZFS](https://openzfs.org) The source database is read from a read-only [ZFS](https://openzfs.org)
snapshot, so extraction never contends with the live firehose ingester that snapshot, so extraction never contends with the live firehose ingester that is
is writing to the original database. The tool is operationally writing to the original database. The tool is operationally conservative: it
conservative: it checks free disk space before starting, copies the snapshot checks free disk space before starting, copies the snapshot to fast scratch
to fast scratch storage, processes one day at a time to avoid SQLite lock storage, processes one day at a time to avoid SQLite lock contention, verifies
contention, verifies every compressed output before publishing it, and every compressed output before publishing it, and writes output atomically via a
writes output atomically via a temp-file-and-rename so a partial run never temp-file-and-rename so a partial run never leaves a corrupt `.sql.zst` behind.
leaves a corrupt `.sql.zst` behind.
This project was written by [@sneak](https://sneak.berlin) to produce a This project was written by [@sneak](https://sneak.berlin) to produce a daily,
daily, mergeable, publicly-mirrorable archive of the Bluesky firehose. It is mergeable, publicly-mirrorable archive of the Bluesky firehose. It is currently
currently a one-person effort. The current version is pre-1.0 and there has a one-person effort. The current version is pre-1.0 and there has not yet been a
not yet been a versioned release; [SemVer](https://semver.org) will be used versioned release; [SemVer](https://semver.org) will be used for releases.
for releases.
# Build Status # Build Status
@@ -33,15 +31,14 @@ branch must always be green.
Primary development happens on a privately-run Gitea instance at Primary development happens on a privately-run Gitea instance at
[https://git.eeqj.de/sneak/bsdaily](https://git.eeqj.de/sneak/bsdaily) and [https://git.eeqj.de/sneak/bsdaily](https://git.eeqj.de/sneak/bsdaily) and
issues are [tracked issues are [tracked there](https://git.eeqj.de/sneak/bsdaily/issues).
there](https://git.eeqj.de/sneak/bsdaily/issues).
Changes must always be formatted with `make fmt` (`go fmt` for Go, Changes must always be formatted with `make fmt` (`go fmt` for Go, prettier for
prettier for Markdown), syntactically Markdown), syntactically valid, and must pass the linting defined in the
valid, and must pass the linting defined in the repository (presently the repository (presently the `golangci-lint` defaults), which can be run with a
`golangci-lint` defaults), which can be run with a `make lint`. The `main` `make lint`. The `main` branch is protected and all changes must be made via
branch is protected and all changes must be made via [pull [pull requests](https://git.eeqj.de/sneak/bsdaily/pulls) and pass CI to be
requests](https://git.eeqj.de/sneak/bsdaily/pulls) and pass CI to be merged. merged.
See [`REPO_POLICIES.md`](REPO_POLICIES.md) for detailed coding standards, See [`REPO_POLICIES.md`](REPO_POLICIES.md) for detailed coding standards,
tooling requirements, and workflow conventions. tooling requirements, and workflow conventions.
@@ -51,58 +48,54 @@ tooling requirements, and workflow conventions.
This repository adheres to the This repository adheres to the
[Scripts to Rule Them All](https://github.com/github/scripts-to-rule-them-all) [Scripts to Rule Them All](https://github.com/github/scripts-to-rule-them-all)
standard: normalized scripts in `script/` are the entrypoints for the standard: normalized scripts in `script/` are the entrypoints for the
development workflow, and the Makefile targets are thin shims that call development workflow, and the Makefile targets are thin shims that call them. We
them. We provide: provide:
- `script/bootstrap` — install all development dependencies (go, Go - `script/bootstrap` — install all development dependencies (go, Go module
module download, a pinned node and yarn, and the prettier pinned in download, a pinned node and yarn, and the prettier pinned in `package.json`
`package.json` and `yarn.lock`); the linter is not installed on the host and `yarn.lock`); the linter is not installed on the host
- `script/setup` — make a fresh clone ready for development: runs - `script/setup` — make a fresh clone ready for development: runs
`script/bootstrap`, then `script/install-precommit` `script/bootstrap`, then `script/install-precommit`
- `script/projectname` — print the project name (used for the Docker - `script/projectname` — print the project name (used for the Docker image tags)
image tags) - `script/test` — build the Dockerfile's `test` phase, which runs the test suite
- `script/test` — build the Dockerfile's `test` phase, which runs the with `-race` (verbose rerun on failure)
test suite with `-race` (verbose rerun on failure)
- `script/lint` — build the Dockerfile's `lint` phase, which runs - `script/lint` — build the Dockerfile's `lint` phase, which runs
`golangci-lint run ./...` `golangci-lint run ./...`
- `script/fmt` — format the Go code with `go fmt` and every Markdown - `script/fmt` — format the Go code with `go fmt` and every Markdown file with
file with prettier (writes) prettier (writes)
- `script/fmt-check` — check the Go formatting with `gofmt` and the - `script/fmt-check` — check the Go formatting with `gofmt` and the Markdown
Markdown formatting with prettier (read-only) formatting with prettier (read-only)
- `script/check` — run `script/test`, `script/lint`, and - `script/check` — run `script/test`, `script/lint`, and `script/fmt-check`
`script/fmt-check` - `script/docker` — build the Docker image tagged via `script/projectname`; the
- `script/docker` — build the Docker image tagged via build runs the `lint` and `test` phases first
`script/projectname`; the build runs the `lint` and `test` phases - `script/cibuild` — CI entrypoint: runs `script/bootstrap` and `script/check`,
first then builds the Docker image tagged via `script/projectname`
- `script/cibuild` — CI entrypoint: runs `script/bootstrap` and - `script/precommit` — pre-commit gate: `go mod tidy` (must not change `go.mod`
`script/check`, then builds the Docker image tagged via or `go.sum`) and `go fmt`, then `script/check`
`script/projectname` - `script/install-precommit` — install the git pre-commit hook that runs
- `script/precommit` — pre-commit gate: `go mod tidy` (must not change `script/precommit`
`go.mod` or `go.sum`) and `go fmt`, then `script/check`
- `script/install-precommit` — install the git pre-commit hook that
runs `script/precommit`
Every Docker build in `script/` is uncached, so the `lint` and `test` Every Docker build in `script/` is uncached, so the `lint` and `test` phases
phases always run rather than being served from the build cache. always run rather than being served from the build cache.
# Problem Statement # Problem Statement
A Bluesky firehose ingester writes every observed post (and associated A Bluesky firehose ingester writes every observed post (and associated users,
users, hashtags, URLs, and media references) into a single ever-growing hashtags, URLs, and media references) into a single ever-growing SQLite
SQLite database, `firehose.db`. This database has several properties that database, `firehose.db`. This database has several properties that make it
make it awkward to publish or archive directly: awkward to publish or archive directly:
- It is **large and always growing**, so re-publishing the whole thing every - It is **large and always growing**, so re-publishing the whole thing every day
day is wasteful. is wasteful.
- It is **continuously written**, so reading from it directly risks lock - It is **continuously written**, so reading from it directly risks lock
contention with the live ingester and inconsistent reads. contention with the live ingester and inconsistent reads.
- It is **monolithic**, so there is no natural unit at which to mirror, - It is **monolithic**, so there is no natural unit at which to mirror, share,
share, or distribute "just yesterday's posts". or distribute "just yesterday's posts".
What is wanted instead is a stable, immutable, per-day artifact: a small What is wanted instead is a stable, immutable, per-day artifact: a small file
file containing exactly one calendar day of firehose data, cheap to publish, containing exactly one calendar day of firehose data, cheap to publish, cheap to
cheap to mirror, and trivially re-mergeable into a full database by anyone mirror, and trivially re-mergeable into a full database by anyone who collects a
who collects a set of them. set of them.
# Proposed Solution # Proposed Solution
@@ -112,81 +105,81 @@ A tool, `bsdaily`, that:
filesystem, so it reads from a consistent point-in-time copy that the live filesystem, so it reads from a consistent point-in-time copy that the live
ingester cannot be writing to; ingester cannot be writing to;
- copies the snapshot's database files to fast scratch storage; - copies the snapshot's database files to fast scratch storage;
- **extracts** a single day's `posts` (and all rows reachable from them) into - **extracts** a single day's `posts` (and all rows reachable from them) into a
a fresh, minimal per-day SQLite database; fresh, minimal per-day SQLite database;
- **dumps** that per-day database to SQL and pipes it through multithreaded - **dumps** that per-day database to SQL and pipes it through multithreaded zstd
zstd compression; compression;
- **verifies** the compressed output (zstd integrity check plus a sanity - **verifies** the compressed output (zstd integrity check plus a sanity check
check that the decompressed stream actually looks like SQL); that the decompressed stream actually looks like SQL);
- **publishes** the result atomically as - **publishes** the result atomically as
`DailiesBase/YYYY-MM/YYYY-MM-DD.sql.zst`. `DailiesBase/YYYY-MM/YYYY-MM-DD.sql.zst`.
Each daily dump is emitted with `INSERT` statements over the full schema Each daily dump is emitted with `INSERT` statements over the full schema
(including the deduplicated `users`, `hashtags`, and `urls` lookup tables), (including the deduplicated `users`, `hashtags`, and `urls` lookup tables), so
so any collection of daily dumps can be merged into a single database by any collection of daily dumps can be merged into a single database by rewriting
rewriting `INSERT INTO` to `INSERT OR IGNORE INTO` and replaying them in `INSERT INTO` to `INSERT OR IGNORE INTO` and replaying them in sequence. Two
sequence. Two helper scripts ([`merge_daily_dumps.sh`](merge_daily_dumps.sh) helper scripts ([`merge_daily_dumps.sh`](merge_daily_dumps.sh) and
and [`regenerate_auxiliary_tables.sql`](regenerate_auxiliary_tables.sql)) are [`regenerate_auxiliary_tables.sql`](regenerate_auxiliary_tables.sql)) are
included to do exactly this and to rebuild the aggregate statistics included to do exactly this and to rebuild the aggregate statistics
(`use_count`, `first_seen`, user `resolved_at`/`updated_at`) afterward. (`use_count`, `first_seen`, user `resolved_at`/`updated_at`) afterward.
# Design Goals # Design Goals
- **Never disturb the live ingester.** All reads come from a ZFS snapshot, - **Never disturb the live ingester.** All reads come from a ZFS snapshot, never
never the live database. the live database.
- **Crash-safe, idempotent runs.** Output is written to a temp file and - **Crash-safe, idempotent runs.** Output is written to a temp file and
atomically renamed; a day whose final output already exists is skipped, so atomically renamed; a day whose final output already exists is skipped, so
re-running a range is safe and resumable. re-running a range is safe and resumable.
- **Mergeable output.** Daily dumps re-combine losslessly into a full - **Mergeable output.** Daily dumps re-combine losslessly into a full database
database via `INSERT OR IGNORE`. via `INSERT OR IGNORE`.
- **Operationally cautious.** Free-space preflight checks on both scratch and - **Operationally cautious.** Free-space preflight checks on both scratch and
output filesystems; explicit verification of every artifact before it is output filesystems; explicit verification of every artifact before it is
published. published.
- **Fast where it's free.** Large snapshot copies use a 256MiB buffer, - **Fast where it's free.** Large snapshot copies use a 256MiB buffer,
pre-allocate the destination, and (on Linux) issue `posix_fadvise` pre-allocate the destination, and (on Linux) issue `posix_fadvise`
sequential/willneed hints; extraction uses aggressive, sequential/willneed hints; extraction uses aggressive, crash-unsafe-by-design
crash-unsafe-by-design SQLite pragmas because the working data lives only SQLite pragmas because the working data lives only in disposable scratch
in disposable scratch space. space.
# Non-Goals # Non-Goals
- **Real-time export.** `bsdaily` operates on daily snapshots; the freshest - **Real-time export.** `bsdaily` operates on daily snapshots; the freshest day
day it can produce is the snapshot date minus one. it can produce is the snapshot date minus one.
- **Schema ownership.** The schema is defined by the upstream firehose - **Schema ownership.** The schema is defined by the upstream firehose ingester;
ingester; [`schema.sql`](schema.sql) is included for reference only. [`schema.sql`](schema.sql) is included for reference only. `bsdaily` copies
`bsdaily` copies whatever table and index DDL it finds in the source. whatever table and index DDL it finds in the source.
- **Cross-platform deployment.** It is built and run on Linux (the - **Cross-platform deployment.** It is built and run on Linux (the free-space
free-space check and fadvise hints use `golang.org/x/sys/unix`; a non-Linux check and fadvise hints use `golang.org/x/sys/unix`; a non-Linux build
build compiles but is a no-op for the fadvise hints). The hard-coded paths compiles but is a no-op for the fadvise hints). The hard-coded paths assume
assume the production host's ZFS layout. the production host's ZFS layout.
# How It Works # How It Works
A single run proceeds as follows: A single run proceeds as follows:
1. **Find the snapshot.** Scan `SnapshotBase` for directories matching 1. **Find the snapshot.** Scan `SnapshotBase` for directories matching
`zfs-auto-snap_daily-YYYY-MM-DD-NNNN`, pick the most recent, and confirm `zfs-auto-snap_daily-YYYY-MM-DD-NNNN`, pick the most recent, and confirm it
it contains `firehose.db`. contains `firehose.db`.
2. **Determine target days.** Default to the snapshot date minus one day; 2. **Determine target days.** Default to the snapshot date minus one day; or use
or use `--date`, or every day in the inclusive `--from`/`--to` range. `--date`, or every day in the inclusive `--from`/`--to` range.
3. **Preflight disk space.** Require at least 500GiB free on the scratch 3. **Preflight disk space.** Require at least 500GiB free on the scratch
filesystem and 20GiB free on the output filesystem. filesystem and 20GiB free on the output filesystem.
4. **Copy the database to scratch.** Copy `firehose.db`, its `-wal`, and (if 4. **Copy the database to scratch.** Copy `firehose.db`, its `-wal`, and (if
present) its `-shm` from the snapshot into a fresh temp directory under present) its `-shm` from the snapshot into a fresh temp directory under
`TmpBase`. `TmpBase`.
5. **Per day**, processed strictly one at a time to avoid SQLite contention: 5. **Per day**, processed strictly one at a time to avoid SQLite contention:
- skip the day if its final output file already exists; - skip the day if its final output file already exists;
- `ATTACH` the copied source DB to a new empty per-day DB, recreate the - `ATTACH` the copied source DB to a new empty per-day DB, recreate the
table DDL, and `INSERT ... SELECT` the target day's `posts` plus all table DDL, and `INSERT ... SELECT` the target day's `posts` plus all rows
rows reachable from them (`posts_hashtags`, `posts_urls`, `hashtags`, reachable from them (`posts_hashtags`, `posts_urls`, `hashtags`, `urls`,
`urls`, `users`, and `media` if that table exists); `users`, and `media` if that table exists);
- abort the day cleanly if there are zero posts (`ErrNoPosts`), rather - abort the day cleanly if there are zero posts (`ErrNoPosts`), rather than
than emitting an empty dump; emitting an empty dump;
- recreate indexes, detach the source, and verify the inserted row count; - recreate indexes, detach the source, and verify the inserted row count;
- `sqlite3 .dump | zstdmt` into a hidden temp file; - `sqlite3 .dump | zstdmt` into a hidden temp file;
- run a zstd integrity check and confirm the decompressed head looks like - run a zstd integrity check and confirm the decompressed head looks like
SQL; SQL;
- atomically rename into place and delete the per-day scratch DB. - atomically rename into place and delete the per-day scratch DB.
6. **Clean up** the temp directory and log a processed/skipped/total summary. 6. **Clean up** the temp directory and log a processed/skipped/total summary.
# Usage # Usage
@@ -223,9 +216,9 @@ sqlite3 merged.db < regenerate_auxiliary_tables.sql
- **Go** (see [`go.mod`](go.mod) for the toolchain version) to build. - **Go** (see [`go.mod`](go.mod) for the toolchain version) to build.
- **Linux** for production use (ZFS snapshots, `statfs` free-space checks, - **Linux** for production use (ZFS snapshots, `statfs` free-space checks,
`posix_fadvise` hints). `posix_fadvise` hints).
- The **`sqlite3`** and **`zstdmt`** (multithreaded zstd) binaries on - The **`sqlite3`** and **`zstdmt`** (multithreaded zstd) binaries on `PATH`;
`PATH`; `zstdcat` is used for verification. SQLite reads/writes during `zstdcat` is used for verification. SQLite reads/writes during extraction use
extraction use the pure-Go [`modernc.org/sqlite`](https://pkg.go.dev/modernc.org/sqlite) the pure-Go [`modernc.org/sqlite`](https://pkg.go.dev/modernc.org/sqlite)
driver, so no cgo is required for that part. driver, so no cgo is required for that part.
# Configuration # Configuration
@@ -245,21 +238,21 @@ elsewhere.
# Data Model # Data Model
The firehose schema (reference copy in [`schema.sql`](schema.sql)) centers The firehose schema (reference copy in [`schema.sql`](schema.sql)) centers on a
on a `posts` table, with `users` keyed by DID and many-to-many junction `posts` table, with `users` keyed by DID and many-to-many junction tables
tables linking posts to deduplicated `hashtags` and `urls`. An optional linking posts to deduplicated `hashtags` and `urls`. An optional `media` table
`media` table tracks downloaded blobs by content hash. `bsdaily` does not tracks downloaded blobs by content hash. `bsdaily` does not own this schema; it
own this schema; it reflects whatever DDL exists in the source snapshot and reflects whatever DDL exists in the source snapshot and selects forward from
selects forward from `posts` along the foreign-key relationships to produce a `posts` along the foreign-key relationships to produce a referentially-complete
referentially-complete per-day slice. per-day slice.
# Use Cases # Use Cases
## Daily public archive ## Daily public archive
Publish one small, immutable file per day to static HTTP (or IPFS, or a Publish one small, immutable file per day to static HTTP (or IPFS, or a mirror
mirror network) so that anyone can fetch exactly the day(s) they want and network) so that anyone can fetch exactly the day(s) they want and re-merge them
re-merge them locally. locally.
## Backfilling a range ## Backfilling a range
@@ -269,16 +262,17 @@ safe to re-run.
## Reconstituting a full database ## Reconstituting a full database
Collect any set of daily dumps and merge them with `INSERT OR IGNORE` to Collect any set of daily dumps and merge them with `INSERT OR IGNORE` to rebuild
rebuild a complete, queryable SQLite database, then regenerate the aggregate a complete, queryable SQLite database, then regenerate the aggregate statistics
statistics tables. tables.
# See Also # See Also
## Links ## Links
- Repo: [https://git.eeqj.de/sneak/bsdaily](https://git.eeqj.de/sneak/bsdaily) - Repo: [https://git.eeqj.de/sneak/bsdaily](https://git.eeqj.de/sneak/bsdaily)
- Issues: [https://git.eeqj.de/sneak/bsdaily/issues](https://git.eeqj.de/sneak/bsdaily/issues) - Issues:
[https://git.eeqj.de/sneak/bsdaily/issues](https://git.eeqj.de/sneak/bsdaily/issues)
- Bluesky: [https://bsky.app](https://bsky.app) - Bluesky: [https://bsky.app](https://bsky.app)
- zstd: [https://facebook.github.io/zstd/](https://facebook.github.io/zstd/) - zstd: [https://facebook.github.io/zstd/](https://facebook.github.io/zstd/)
TODO.md
+27 -27
View File
@@ -1,12 +1,12 @@
# Workflow # Workflow
* branch (from `main`) - branch (from `main`)
* do the work in Next Step - do the work in Next Step
* move Next Step to the top of Completed Steps - move Next Step to the top of Completed Steps
* move the top item of Future Steps into Next Step - move the top item of Future Steps into Next Step
* commit (`TODO.md` changes in the same commit as the work) - commit (`TODO.md` changes in the same commit as the work)
* merge to `main` if the branch is not protected, otherwise open a PR - merge to `main` if the branch is not protected, otherwise open a PR
* push - push
# Status # Status
@@ -14,37 +14,37 @@ pre-1.0
# Next Step # Next Step
Add the canonical `.golangci.yml`, move the lint phase to golangci-lint Add the canonical `.golangci.yml`, move the lint phase to golangci-lint v2.14.0
v2.14.0 in the same commit, and fix the findings it surfaces in the same commit, and fix the findings it surfaces
(https://git.eeqj.de/sneak/bsdaily/issues/6). (https://git.eeqj.de/sneak/bsdaily/issues/6).
# Completed Steps # Completed Steps
- 2026-10-06: Formatted Markdown with prettier: `script/fmt` writes and - 2026-10-06: Formatted Markdown with prettier: `script/fmt` writes and
`script/fmt-check` checks every Markdown file; prettier pinned in `script/fmt-check` checks every Markdown file; prettier pinned in
`package.json` and `yarn.lock`, installed by `script/bootstrap` with a `package.json` and `yarn.lock`, installed by `script/bootstrap` with a pinned
pinned node and yarn; existing Markdown reformatted. node and yarn; existing Markdown reformatted.
- 2026-10-05: Brought the repo up to the standard layout: canonical - 2026-10-05: Brought the repo up to the standard layout: canonical
`.gitignore`, `.dockerignore` and `.editorconfig`; `lint` and `test` `.gitignore`, `.dockerignore` and `.editorconfig`; `lint` and `test` phases in
phases in the `Dockerfile`, built by `script/lint` and `script/test`; the `Dockerfile`, built by `script/lint` and `script/test`; canonical
canonical `script/cibuild`, `script/docker` and CI workflow; no linter `script/cibuild`, `script/docker` and CI workflow; no linter installed on the
installed on the host; re-vendored `REPO_POLICIES.md`. host; re-vendored `REPO_POLICIES.md`.
- 2026-07-07 Adopted scripts-to-rule-them-all: `script/` entrypoints, - 2026-07-07 Adopted scripts-to-rule-them-all: `script/` entrypoints, Makefile
Makefile shims, README Entrypoints section shims, README Entrypoints section
- 2026-06-28: Fixed errcheck lint failures; added compilation smoke test; - 2026-06-28: Fixed errcheck lint failures; added compilation smoke test; tidied
tidied go.mod. go.mod.
- 2026-06-28: Added repo scaffolding: README, LICENSE, Makefile, - 2026-06-28: Added repo scaffolding: README, LICENSE, Makefile, Dockerfile,
Dockerfile, REPO_POLICIES.md, and Gitea CI. REPO_POLICIES.md, and Gitea CI.
- 2026-02-12: Fixed SQLite database locking by removing parallel - 2026-02-12: Fixed SQLite database locking by removing parallel processing;
processing; fixed Linux build via golang.org/x/sys/unix Fadvise. fixed Linux build via golang.org/x/sys/unix Fadvise.
- 2026-02-12: Optimized file copy for large databases; moved temp - 2026-02-12: Optimized file copy for large databases; moved temp directory to
directory to NVMe scratch storage. NVMe scratch storage.
- 2026-02-11: Added date range support. - 2026-02-11: Added date range support.
- 2026-02-09: Initial implementation: single-day extraction, specific-date - 2026-02-09: Initial implementation: single-day extraction, specific-date
targeting, faster pruning of throwaway database copies. targeting, faster pruning of throwaway database copies.
# Future Steps # Future Steps
- Expand tests beyond the compilation smoke test: unit tests for the - Expand tests beyond the compilation smoke test: unit tests for the extraction,
extraction, verification, and atomic-publish paths. verification, and atomic-publish paths.
- Cut a first SemVer release once compliance and test coverage land. - Cut a first SemVer release once compliance and test coverage land.