Files

T

check / check (push) Successful in 4m50s

Details

Reformat the existing Markdown with prettier (closes #7 )

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

2026-10-06 06:31:14 +00:00

2.0 KiB

Raw Blame History

Workflow

branch (from main)
do the work in Next Step
move Next Step to the top of Completed Steps
move the top item of Future Steps into Next Step
commit (TODO.md changes in the same commit as the work)
merge to main if the branch is not protected, otherwise open a PR
push

Status

pre-1.0

Next Step

Add the canonical .golangci.yml, move the lint phase to golangci-lint v2.14.0 in the same commit, and fix the findings it surfaces (#6).

Completed Steps

2026-10-06: Formatted Markdown with prettier: script/fmt writes and script/fmt-check checks every Markdown file; prettier pinned in package.json and yarn.lock, installed by script/bootstrap with a pinned node and yarn; existing Markdown reformatted.
2026-10-05: Brought the repo up to the standard layout: canonical .gitignore, .dockerignore and .editorconfig; lint and test phases in the Dockerfile, built by script/lint and script/test; canonical script/cibuild, script/docker and CI workflow; no linter installed on the host; re-vendored REPO_POLICIES.md.
2026-07-07 Adopted scripts-to-rule-them-all: script/ entrypoints, Makefile shims, README Entrypoints section
2026-06-28: Fixed errcheck lint failures; added compilation smoke test; tidied go.mod.
2026-06-28: Added repo scaffolding: README, LICENSE, Makefile, Dockerfile, REPO_POLICIES.md, and Gitea CI.
2026-02-12: Fixed SQLite database locking by removing parallel processing; fixed Linux build via golang.org/x/sys/unix Fadvise.
2026-02-12: Optimized file copy for large databases; moved temp directory to NVMe scratch storage.
2026-02-11: Added date range support.
2026-02-09: Initial implementation: single-day extraction, specific-date targeting, faster pruning of throwaway database copies.

Future Steps

Expand tests beyond the compilation smoke test: unit tests for the extraction, verification, and atomic-publish paths.
Cut a first SemVer release once compliance and test coverage land.