alexion
0cbfe43ae0
Add the design record for distributing gitea-axi as a Nix flake: a package, a development shell, and a checks output, plus the continuous integration changes that come with it. ADR 0018 records the wrapper's deference to the operator's own `git` and `tea` — the reverse of the hermetic instinct, chosen because `tea` refreshes OAuth tokens in place and so must not have two versions mutating one credential store. Also records the `tea`-is-still-a-runtime-dependency gotcha, which ADR 0002's title obscures.
1.5 KiB
spec, blocked-by
| spec | blocked-by | ||
|---|---|---|---|
| nix-flake-packaging |
|
What to build
After it installs, the Nix build drives the wrapped binary it just produced through the shared installed-binary tier, pointing that tier at the installed path rather than letting it pack and install.
This guards a class of failure the fast tier structurally cannot reach.
The compiler does not set the executable bit that npm would otherwise set from the manifest's bin entry at install time.
And the setup command resolves the bundled Agent Skill relative to its own module location, which makes the relative arrangement of the built output and the bundled Skill load-bearing — an arrangement that only exists once installed.
The check reuses the seam from the parameterized tier; it does not introduce a second, weaker set of assertions in shell script, and it does not re-run the fast tier, which would not exercise the installed layout at all.
Acceptance criteria
- The Nix build drives the installed binary through the shared installed-binary tier after installation.
- A binary installed without its executable bit fails the build.
- A bundled Agent Skill installed at the wrong location relative to the built output fails the build.
- The post-install phase adds no assertions of its own beyond pointing the shared tier at the installed binary.
nix buildstill succeeds end to end on a clean checkout.