Fjord DB 0.6.2

See CHANGELOG.md.

The binary

fjord is the tool. Linux x86_64, and it needs glibc 2.34 or newer
(Ubuntu 22.04, Debian 12, RHEL 9 and later):

curl -LO https://github.com/boxops-uk/fjord/releases/download/v0.6.2/fjord
chmod +x fjord
./fjord --help

The -x86_64-linux-musl builds are the same code linked statically, for an
older distro, Alpine, or a scratch container — no glibc floor. Both builds
allocate from the same allocator, but every number the project publishes is
measured on the one above, so take these only if it will not run.

Every file here carries SLSA provenance, and SHA256SUMS covers all of them:

gh attestation verify ./fjord --repo boxops-uk/fjord
sha256sum --check --ignore-missing SHA256SUMS

The schemas

fjord-schemas.tar.gz is schemas/ — every .sigla file this
repository ships. The binary embeds only the sample, so this is what
--schema wants for anything real:

curl -LO https://github.com/boxops-uk/fjord/releases/download/v0.6.2/fjord-schemas.tar.gz
mkdir -p schemas && tar -xzf fjord-schemas.tar.gz -C schemas
./fjord --schema-path schemas schema compose schemas/dotnet.sigla >dotnet.composed.sigla

Unpack the whole set rather than one file: an import is resolved against the
directory, and dotnet.sigla reaches five others.

The .NET indexer

Boxops.Fjord.Indexer.<version>.nupkg is a dotnet tool that walks a
real checkout with Buildalyzer and Roslyn and writes what
schemas/dotnet.sigla declares:

curl -LO https://github.com/boxops-uk/fjord/releases/download/v0.6.2/Boxops.Fjord.Indexer.0.6.2.nupkg
dotnet tool install -g Boxops.Fjord.Indexer --version 0.6.2 --add-source .
fjord-indexer --sln /path/to/Some.slnx --schema dotnet.composed.sigla --at /tmp/fjord.sock//code

A tool and not a binary, deliberately: it runs the design-time build out of
process, so it needs a .NET SDK present whatever shape it ships in — and any
machine that can index a .NET checkout already has one.

The book

fjord-docs-site.tar.gz is the design book as built at this tag — the
interactive site, with the engine compiled into the page, attested the same
way. Serve it from a root: every page in it is a file, and 404.html is
there for a path nothing knows about.