Commit Graph

150 Commits

Author SHA1 Message Date
alex 85bd7421de feat(llm): package upstream inference engines
Centralize engine pins, compiler wrappers and NPU packages.
Use upstream Kyojin v1.8.10 and drop the Thunderbolt dependency.

Offline evaluation passed; workstation builds remain pending.

Bead: nix-overlay-v09
2026-11-12 20:36:52 +03:00
Marmel Coder 47829fe9a6 chore(beads): record completed codex-oauth-proxy implementation
CI / check (push) Has been cancelled
2026-11-12 17:09:55 +03:00
Marmel Coder 48a19c55b8 feat: export and document codex-oauth-proxy user service 2026-11-12 16:59:24 +03:00
Marmel Coder 8c6897e66d feat: add codex-oauth-proxy Home Manager service module 2026-11-12 16:49:26 +03:00
Marmel Coder 4d08fafddc feat(codex-oauth-proxy): package private-state user service 2026-11-12 16:40:15 +03:00
Marmel Coder dface8eb87 chore: ignore isolated worktrees 2026-11-12 16:32:01 +03:00
alex 76e8f4c691 chore(beads): sync issue state
CI / check (push) Has been cancelled
Export the pending codex-oauth-proxy service issue (nix-overlay-y5r) and the closed gpt-6.1-terra fix (nix-overlay-yf4).
2026-11-12 15:47:57 +03:00
alex 0feb16a0c0 fix(codex-oauth-proxy): support gpt-6.1-terra
1.1.1 omits the model from normalizeModel's allowlist, so requests for gpt-6.1-terra are rewritten to gpt-5.5. ChatGPT accounts are not entitled to gpt-5.5, so the request fails with model_not_found.

Add the model to the allowlist, allowed reasoning efforts, and default effort. Covered by the transform tests.
2026-11-12 15:47:53 +03:00
alex fb08077db9 chore(gitignore): ignore .marmel scratch directory
CI / check (push) Has been cancelled
Marmel leaves research notes and build/eval logs under .marmel/, which
are local-only like the other tool scratch already ignored here.
2026-11-12 12:00:08 +03:00
alex b485ced2d3 chore(serena): sync project.yml with current config template
Serena rewrote its project config: new language-server IDs in the
comment list plus included_apis, excluded_apis and agent_interface keys.
All new keys keep their empty defaults, so no setting changes.
2026-11-12 11:55:27 +03:00
alex 48a7d227f2 docs(agents): trim stale guidance and forbid unrequested edits
Remove content that no longer matches the workflow: package templates
already covered by the "Adding a New Package" steps, per-package notes,
the duplicated beads command reference, and the mandatory git push steps.
Drop the sequentialthinking MCP requirement and add a rule that AGENTS.md
changes need an explicit user request.
2026-11-12 11:55:16 +03:00
Marmel Coder 78c46e970c chore(beads): retarget pending publish to main 2026-11-12 10:49:08 +03:00
Marmel Coder 5cf40846ca chore(beads): track pending publish for codex-oauth-proxy 2026-11-12 04:15:37 +03:00
Marmel Coder c56869655c chore(beads): close codex-oauth-proxy packaging task 2026-11-12 02:04:27 +03:00
Marmel Coder 55f6a0b7ed feat(codex-oauth-proxy): add 1.1.1 Codex OAuth proxy package
Packages dvcrn/codex-oauth-proxy, which exposes a ChatGPT Codex account through OpenAI-compatible APIs, as a buildGoModule derivation. Builds only cmd/codex-oauth-proxy because the worker package is js/wasm code, and passes -buildvcs=false because the Nix source has no .git. Upstream Go tests run offline, so doCheck is enabled.
2026-11-12 02:04:06 +03:00
alex 19774c73f3 fix(codex-api-proxy): propagate sys.path to daemon child
CI / check (push) Has been cancelled
2026-11-09 22:22:25 +03:00
alex 5f0e9076e9 chore(beads): close codex-api-proxy packaging task
CI / check (push) Has been cancelled
2026-11-09 22:08:16 +03:00
alex 9ffe8b006f feat(codex-api-proxy): add 0.1.6 local Codex API proxy 2026-11-09 22:08:09 +03:00
alex 589936cd8d feat(marmel): add arbitrary HTTP headers patch
CI / check (push) Has been cancelled
Apply upstream 56d0b1f so top-level, specialist, validator and MCP request headers can be configured. nix build .#marmel passes with the patch.
2026-11-09 10:03:47 +03:00
alex 44e6d90a77 feat(magg): add magg 1.3.0 MCP aggregator package
CI / check (push) Has been cancelled
Add magg, an MCP aggregator / meta-MCP server, to the overlay. It is a
Python package on the hatchling backend, built with
python3Packages.buildPythonApplication from the v1.3.0 source tarball,
so no upstream release artifacts are fetched. Ships both console
scripts declared upstream: magg (the aggregator CLI/server) and mbro
(the MCP browser). License is AGPL-3.0-or-later.

The install check runs the upstream pytest suite with
-m "not integration", because the integration-marked tests need a live
server. A forced nix build .#magg --rebuild passes with 329 passed,
3 skipped, 3 deselected, 0 failed, and both binaries smoke-test clean.

Also adds the README and AGENTS.md package rows, the upstream and build
research notes, and the verification report in docs/magg_build_report.md.
2026-11-08 12:48:30 +03:00
alex e569243ae4 chore(marmel): bump to afcc1dc (main), give checks a usable TMPDIR
CI / check (push) Has been cancelled
Track upstream main at afcc1dc971ae4acd59b157f031d4bdbc9d52a7d0
(2026-11-07), 22 commits past the de3e99c8 pin. Upstream still ships no
tags or releases and Cargo.toml still reads version 1.0.0, so the dated
0-unstable-* string stays. cargoHash moves on its own: the new
crates/zim-search workspace member grew Cargo.lock from 399 to 621
entries, and cargo vendor hashes the whole workspace.

The real packaging work is the TMPDIR override appended to preCheck.
Upstream's new harness::fs::path_tests scratch-root helper puts its
scratch dirs under <cwd>/target/ and first asserts that root lies
outside std::env::temp_dir(). The build sandbox exports TMPDIR=/build,
which is an ancestor of the unpacked source at /build/source, so that
premise check tripped and all 8 path-security tests failed with
"scoped root /build/source/target/marmel-path-tests-N sits inside the
temp allow-list entry /build". Pointing TMPDIR at
/tmp/marmel-check-tmp, outside $NIX_BUILD_TOP, restores upstream's
premise, so all 8 tests keep running for real instead of being filtered
out of cargoTestFlags. Build-time only; the installed binary is
untouched.

Two derivation comments carried stale facts and are corrected:

- meta.license claimed the repository shipped no LICENSE file and that
  Cargo.toml had no license field. Upstream c98179d023 (Na1w/marmel#40)
  added a root LICENSE file and declared license = "MIT" in Cargo.toml,
  so the comment now records that MIT is asserted in the README,
  Cargo.toml and LICENSE alike; lib.licenses.mit was already the right
  value.
- the cargoTestFlags comment quoted "the lib suite passes at 1055
  tests". Roughly 500 test fns landed since (TUI, fs-path, PTY and
  dispatch-integrity suites), so the figure is dropped rather than
  refreshed: nothing checks it and it rots on every bump.

Also adds the two research notes behind the bump under docs/: the
de3e99c8..afcc1dc9 upstream delta audit and the update-tooling findings.

Verified: clean nix build .#marmel including the serialised test suite
(--test-threads=1) — 2146 passed, 0 failed.
2026-11-07 16:54:02 +03:00
alex 1edac7a69d feat(agnix): ship agnix-lsp and agnix-mcp with the CLI
CI / check (push) Has been cancelled
Editors and MCP clients need the language server and the MCP server, and
upstream's release job builds all three crates in one cargo invocation.
Build -p agnix-cli -p agnix-lsp -p agnix-mcp in the same derivation so the
workspace compiles once. Closes nix-overlay-ocf.
2026-11-03 15:33:28 +03:00
alex 9c39cff0b0 feat(agnix): add agnix 0.60.3 built from source
CI / check (push) Has been cancelled
Add the agnix agent-config linter to the overlay. Built with
rustPlatform.buildRustPackage from the v0.60.3 source tarball
(cargoBuildFlags -p agnix-cli), so no upstream pre-built release
binaries are fetched. Closes nix-overlay-wfv.
2026-11-03 15:14:49 +03:00
alex 43199e5b8b feat(pdfcraft): add PdfCraft 0.18.0 built from source
CI / check (push) Has been cancelled
Packages the storytold/pdfcraft Cargo workspace at tag v0.18.0: the pdfcraft
desktop app and pdfcraft-cli, with the desktop entry, AppStream metadata,
icons, licences and the two CC-BY-SA OCR models the app reads from
share/pdfcraft/models. No upstream binaries are downloaded.

Two deviations from upstream's build instructions:

- The three [patch.crates-io] entries upstream's own Cargo.lock records as
  [[patch.unused]] (egui_demo_lib, egui_inspection, egui_system_font_provider)
  have no package in nixpkgs' partial vendor tree to resolve against, so cargo
  aborts. postPatch drops them; they are unused, and cargo drops the matching
  lock entries itself, so the build runs without --locked.

- nixos-unstable's rustc 1.98.1 and 1.99.0 reject every AVX-VNNI intrinsic
  ("intrinsic signature mismatch for llvm.x86.avx512.vpdpbusd/vpwssd"), and
  rten-gemm, pic-scale and zlib-rs all use one. The package therefore builds
  against a new nixpkgs-rust195 input (nixos-26.05, rustc 1.95.0), the same
  pattern as nixpkgs-torch211. Follow-up: nix-overlay-g4w.

Also adds a Home Manager module (programs.pdfcraft) to
homeManagerModules.default, and documents both in the README.
2026-11-03 13:48:55 +03:00
alex d05ca58ee6 chore(kyojin): bump 1.7.1 -> 1.8.5
CI / check (push) Has been cancelled
Upstream 1.8.4/1.8.5 are iGPU decode and returning-session speedups with no
packaging change: setup.py still reads EXL3_ROCM_DEV_INCLUDE/EXL3_HIP_DEFINES,
the pyproject runtime deps are unchanged, and tools/{glm,mimo,qwen}/serve.py
are still the serve entry points. Only the pin and source hash move.

Verified on gfx1151: nix build .#kyojin, importing exllamav3_ext against the
pinned ROCm torch 2.11, kyojin-serve-qwen --help, and nix build
.#kyojin.tests.jit.
2026-11-02 16:16:00 +03:00
alex 4b9f1ed865 chore(agents): drop caveman mode and conventional-commit skill refs
CI / check (push) Has been cancelled
The agent instructions told agents to run two skills that are no longer
part of the workflow:

- remove the "Communication: Caveman Mode" section, so replies are no
  longer required to be compressed through the caveman skill
- replace the `conventional-commit` skill instruction with a plain
  requirement to follow Conventional Commits concisely
2026-11-02 02:05:18 +03:00
alex 7056685370 feat(memdoor): add memdoor 1.769.0
CI / check (push) Has been cancelled
Add guregodevo/memdoor, a Go coding/automation agent, built from source:

- the binary embeds the React UI through web/embed.go (`//go:embed
  all:dist`), and upstream gitignores web/dist, so the bundle is built
  with buildNpmPackage and copied into web/dist before the Go build
- CGO stays off: the SQLite driver is modernc.org/sqlite, so FTS5 needs
  no C flags and the binary is static
- upstream's whole Go suite runs (buildGoModule would trim checks to
  subPackages, where cmd/cli has no tests); it needs git on PATH and
  separate scratch dirs for HOME and the Go temp root, because one test
  writes ~/.memdoor and ProjectRoot walks up looking for that marker

Track the package in beads as nix-overlay-yxj.
2026-11-02 01:53:57 +03:00
alex 89b2f8a725 chore(awgen): bump 0.3.1 -> 0.3.2
CI / check (push) Has been cancelled
Upstream tagged v0.3.2 (5f97208) in alex/awgen. The fix prices allowed-IP
progress per progress instead of per whole route list; dependencies are
unchanged. cargoHash still moves because the crate version line in
Cargo.lock feeds the vendor staging hash.

Verified: nix build .#awgen is green, and result/bin/awgen --version
prints 0.3.2 (upstream now sets the crate version from the tag, so the
stale "prints 0.1.0" caveat from the 0.3 bump no longer applies).
2026-10-26 09:00:01 +03:00
alex 559994a66f chore(awgen): bump 0.3 -> 0.3.1
CI / check (push) Has been cancelled
Upstream tagged v0.3.1; refresh src and cargo hashes (dependencies
changed between the two tags). Verified with nix build .#awgen and
result/bin/awgen --version.
2026-10-25 17:36:56 +03:00
alex 387edce283 chore(awgen): bump 0.2 -> 0.3
CI / check (push) Has been cancelled
Upstream tagged v0.3 (3d10c5f) in alex/awgen. The dependency set is
unchanged, so cargoHash stays the same; only the source hash needed a
recompute for the new tag.

Verified: nix build .#awgen is green, cargo checkPhase reports 29 passed
/ 0 failed, and the resulting binary runs. Upstream Cargo.toml still
declares 0.1.0, so `awgen --version` prints 0.1.0 while the derivation
version (taken from the tag) is 0.3.
2026-10-25 17:06:26 +03:00
alex 6b2e9d3de6 chore(beads): close package update task
CI / check (push) Has been cancelled
Record the completed package bumps and the freetoken 0.2.0 blocker.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
2026-10-24 14:10:49 +03:00
alex e2f24b0876 chore(packages): bump pins to current upstream releases
- awg-tool 0.4.0 -> 0.5.0
- awgen 0.1 -> 0.2
- codeaf 0.7.1 -> 0.8.2
- ds4 -> ee7e840 (2026-10-21)
- freebuff 0.2.19 -> 0.2.34
- graphify 0.9.77 -> 0.9.95 (add pyyaml dependency)
- hipengine 0.6.1 -> 0.8.3
- kubernetes-mcp-server 0.0.67 -> 0.0.69 (build with go_1_27)
- kyojin 1.3 -> 1.7.1 (drop obsolete setup.py/pyproject patches, ship
  gr_mix_hip from the package, add ninja runtime dependency)
- marmel -> de3e99c (2026-10-23)
- omniroute 3.8.50 -> 3.8.52
- open-code-review 1.12.12 -> 1.13.3 (build with go_1_27)
- pilotdeck 2026.10.17 -> 2026.10.20
- radar 1.16.2 -> 1.18.0
- traycer 1.4.2 -> 1.5.1

Verified: nix build passes for every bumped package; kyojin.tests.jit
compiles all five JIT kernels.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
2026-10-24 14:09:34 +03:00
alex fc00731a45 chore(llama-cpp): remove package
Drop the llama-cpp derivation and its README entry.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
2026-10-24 14:09:11 +03:00
alex 722d608491 chore(beads): migrate issue tracking from bd to br
CI / check (push) Has been cancelled
Agents were told to run bd commands that beads_rust does not have (bd prime,
bd remember, bd dolt push, bd tag, bd note, bd children), and bd's git hooks
were still active, so bd could re-export its stale dolt state over br's
JSONL on commit.

- Rewrite AGENTS.md, docs/agents/issue-tracker.md, docs/agents/triage-labels.md
  and the .serena memories around br's real CLI surface
- Replace bd's generated AGENTS.md block with br's (br agents --add)
- Point the .claude session hooks at `br robot-docs guide`
- Remove bd git hooks and unset core.hooksPath; br installs no hooks
- Ignore br runtime files (local SQLite DB, recovery and merge artifacts)
- Rewrite .beads/README.md, config.yaml and metadata.json for br

Issue: nix-overlay-6pp
2026-10-21 18:47:16 +03:00
alex eefef7cce2 feat(awgen): add AmneziaWG configuration generator package
CI / check (push) Has been cancelled
Package alex/awgen (offline, stateless Rust CLI for AmneziaWG configs) from
the upstream Gitea repository. Source is fetched with fetchFromGitea and
pinned to the v0.1 tag; the cargo dependency hash is pinned as well.

Also list the package in the README package table and project tree.
2026-10-20 21:55:24 +03:00
alex 5310b47924 feat(pilotdeck): build Electron desktop app from source
CI / check (push) Has been cancelled
Replace the prebuilt .deb web-only package with the real Electron
application built from upstream v2026.10.17:

- compile apps/desktop main process (tsc) and launch it with
  nixpkgs electron_42 in app-dir mode; upstream env overrides
  (PILOTDECK_DESKTOP_RUNTIME_ROOT, PILOTDECK_DESKTOP_NODE) select the
  staged runtime and bundled Node.js
- replicate the upstream runtime staging (build-runtime.mjs): prod-only
  hoisted node_modules from the dedicated runtime lockfile via a second
  fetchPnpmDeps, dist/skills/ui tree, source-import rewrite, pinned Cua
  driver, upstream runtime verification probes
- share electron-updater into the app by expanding pnpm virtual store
  scopes of its dependency closure
- wrap bin/pilotdeck (desktop, --no-sandbox, ozone hint auto) and keep
  bin/pilotdeck-server (headless web server) on the same runtime
- add pilotdeck.desktop entry, hicolor icon, startupWMClass

Verified: nix build passes, app launches under Xvfb reaching
"PilotDeck Web UI ready" with the window mapped as WM_CLASS
pilotdeck-desktop; headless server answers on :3001.
2026-10-20 00:13:31 +03:00
alex a46a2bb967 fix(pilotdeck): build from source
CI / check (push) Has been cancelled
Replace the prebuilt Debian package with the documented source build. Build the web UI and gateway with pnpm, stage the pinned Cua driver, and start the web UI from the wrapper.
2026-10-19 21:52:37 +03:00
alex fd74633e8d feat: add PilotDeck package
CI / check (push) Has been cancelled
Package the upstream Linux Electron release for x86_64 and aarch64 as
pilotdeck. The Debian payload includes the bundled Node.js runtime and web
UI; the wrapper adds the Electron runtime libraries to LD_LIBRARY_PATH and
installs a desktop entry.

README lists the new package.
2026-10-19 21:07:13 +03:00
alex adbed5f3c0 chore(marmel): bump to b08923ea (main), drop obsolete patches
CI / check (push) Has been cancelled
Upstream fixed both reasons for the local patches, so neither is needed:

- 62cb75634c6e (#16) reports a missing TLS trust store instead of
  panicking through reqwest::Client::default(); the env-cleared test
  child now stays reachable without SSL_CERT_FILE, which is what
  session-boot-trust-store.patch existed to work around.
- b08923eaef60 (#17) adds /nix/store and /gnu/store to
  BUILTIN_READONLY_PATHS; the checkPhase rebuild confirms the store rule
  works on a Nix host: test_internal_sandbox_cross_directory_rename and
  test_internal_sandbox_extra_readonly_paths_never_grant_write run for
  real, no SKIP line is printed, and only the /etc/resolv.conf DNS test
  stays filtered. Lib suite: 1055 passed, 1 filtered; all integration
  suites green.

passthru.updateScript now passes the bare attribute name: nix-update
rejects ".#marmel" with AttributePathError, so the documented bump path
was broken. Verify with `nix-update --flake marmel --use-update-script`.
2026-10-19 09:52:45 +03:00
alex f12ce65f34 chore(beads): export marmel 981b35b bump task and stale 8wl state
CI / check (push) Has been cancelled
Export carries the new nix-overlay-51o (closed) plus a stale
in_progress state for nix-overlay-8wl that the tracked JSONL never
picked up when the issue was actually closed.
2026-10-18 14:53:48 +03:00
alex cb3f338e57 chore(marmel): bump to 981b35b (main)
CI / check (push) Has been cancelled
Track upstream main at 981b35b0d356e56de429ab4198e427ccfbe7d85f
(2026-10-17). Cargo.lock is unchanged between the two revisions, so
cargoHash stays; src hash regenerated by nix-update. Version string
follows nix-update's 0-unstable-* dated scheme now.

Both downstream patches still apply and upstream issues stay open
(Na1w/marmel#14, #13, fix PR #16 unmerged), so nix-overlay-pnb and
nix-overlay-nn2 remain blocked. Lib suite now passes at 1030 tests
with the same single DNS sandbox filter; comment updated.
2026-10-18 14:51:58 +03:00
alex 5a032f4182 chore(beads): link marmel trust-store follow-up to upstream issue
CI / check (push) Has been cancelled
nix-overlay-nn2 now points at Na1w/marmel#13, the upstream report filed for
the reqwest unwrap_or_default() panic on a missing CA trust store. The bead
stays open until upstream propagates the error, at which point
packages/marmel/session-boot-trust-store.patch can be dropped.

Export also carries the DB changes that were never exported before (9 issues
missing from the tracked JSONL).
2026-10-16 16:30:43 +03:00
alex 51dd95c19c fix(marmel): allow /nix/store in the Landlock sandbox
The upstream ruleset allow-lists FHS paths only (/usr, /bin, /lib, /opt,
/etc, /var), and every executable here resolves below the store: /bin/sh
is a symlink into /nix/store/<hash>-bash-5.3p9/bin/sh. Landlock matches
the resolved target rather than the symlinked view, so the harness
re-entry (`marmel --internal-sandbox-exec`) cannot exec the shell and
every shell tool call comes back as "Failed to exec shell in sandbox:
Permission denied (os error 13)" with exit 1. The sandbox is on by
default, so the only workaround on a Nix host is MARMEL_DISABLE_SANDBOX=1,
which drops the protection altogether.

The patch adds "/nix/store" to the read-only+execute list, guarded by
exists() like its neighbours. Store paths are world-readable by design,
so the added reach is nothing a local user did not already have. Checked
against the built binary: sandboxed exec works, git runs, workspace
writes work, ~/.ssh and /root stay blocked.

Tested: nix build .#marmel passes, lib suite 966 passed / 0 failed with
one filter. test_internal_sandbox_cross_directory_rename no longer needs
a skip and passes; test_internal_sandbox_exec_dev_null_and_dns stays
skipped for its own reason, the no-network build sandbox has no
/etc/resolv.conf. Temporary downstream fix, drop it once upstream takes
the store path (nix-overlay-5ml).
2026-10-16 16:19:18 +03:00
alex 892f30e82a fix(marmel): bump to 3f238ff, give e2e child a trust store
CI / check (push) Has been cancelled
Track main at 3f238ff (per-role reasoning_effort, #12), 21 commits past
d6627d7 ("1.0.0 (#6)"). cargoHash is unchanged: Cargo.lock is identical
across that range, so the vendored tree is byte-for-byte the same.

The new tests/test_session_boot.rs spawns the real binary with
env_clear(), which drops SSL_CERT_FILE. rustls-native-certs is then left
with a fixed list of /etc paths to probe, none of which exist in the Nix
sandbox, so the child dies in reqwest::Client::new() and four exit-code
assertions observe the panic's 101. The patch forwards the runner's
SSL_CERT_FILE to the child and leaves every assertion intact.

The underlying defect is upstream's rather than Nix's:
src/llm/client.rs builds its client with unwrap_or_default() on a
Result<Client, reqwest::Error>, and reqwest's Client::default() is
Client::new(), which repeats the same build and .expect()s it. The
fallback can therefore never recover; it turns a reportable "no CA
certificates" error into a panic. Reproduced on a stock busybox image
with no /etc/ssl at all, so it hits any minimal container, not just
sandboxed builds.

Tested: 1251 tests pass across 31 targets, 0 failures.
2026-10-16 14:32:15 +03:00
alex 0813f55762 fix(kyojin): Isolate JIT and runtime toolchains
CI / check (push) Has been cancelled
Allow a pinned JIT SDK without rebuilding PyTorch or the extension.
Keep runtime device bitcode unchanged: exporting TheRock bitcode into
the serving process crashes CLR 7.2 on a basic tensor operation.

Disable unsupported expandable segments and check all five HIP kernel
modules, with an optional GPU matmul and module-loading regression test.
2026-10-08 17:17:56 +03:00
alex 4c24610aae fix(kyojin): serve wrappers get a C compiler, hipcc and the JIT sources
CI / check (push) Has been cancelled
env.sh assumes a distro box: a system cc for Triton's runtime C builds, a hipcc
for the JIT HIP kernels and the repo root on PYTHONPATH. The wrappers now export
all three (, ,  for the amdgcn bitcode,
PYTHONPATH=${src}/gr for gr_mix_hip).

The wheel ships only the files pyproject lists, so the .hip kernel sources, the
qsa_proof marker gating the QSA prefill kernel, the dense-GEMM tuning seed and
gr/ never reached site-packages: kernels fell back to Triton and every start
re-tuned dense GEMM for 7 minutes.

Verified on the Strix Halo box: server READY, start-up 713 s -> 103 s, warm-up
418 s -> 4 s, 584-token prompt served over /v1/chat/completions with no
'unavailable' fallbacks.
2026-10-08 15:57:52 +03:00
alex e061d3c170 feat(kyojin): add Kyojin ExLlamaV3 engine for AMD Strix Halo
CI / check (push) Has been cancelled
Kyojin (Yamz-Labs/kyojin) is a fork of ExLlamaV3 that runs 100 GB-class
EXL3 MoE packs on one 128 GB Ryzen AI Max box. It ships a torch C++
extension that torch's cpp_extension cross-compiles to HIP, and upstream
supports gfx1151 only, so the kernels are built for gfx1151 alone and
the package is marked Linux-only. Pinned to the v1.3 release.

The extension must be compiled against a ROCm build of torch. The flake's
nixos-unstable carries torch 2.13, whose ROCm build fails in nixpkgs (the
CK SDPA configure step runs a script through /bin/bash) and has no binary
on the cache, so the build would compile PyTorch from source and die.
python3Packages.torchWithRocm from the already pinned nixpkgs-torch211
input gives torch 2.11 with ROCm 7.2.2, gfx1151 in its target list and a
cached binary, so default.nix builds through that input the way freetoken
does.

nixpkgs splits the single devel tree the AMD wheels ship, so two
symlinkJoins stand in for it: one as ROCM_HOME (hipcc, headers, amdgcn
bitcode) and one handed to setup.py as EXL3_ROCM_DEV_INCLUDE, which wants
hipsparse/, rocsparse/, rocrand/, thrust/ and pybind11 (nixpkgs torch no
longer exports pybind11 headers). hipsolver is in there because torch's
own HIPContextLight.h includes it.

setup.py gets one patch in postPatch. It imports exllamav3 to reach
build_config, that runs the package __init__, which imports ext.py, which
JIT-compiles the entire extension whenever no precompiled exllamav3_ext is
importable, meaning every wheel build, into a $HOME the sandbox does not
grant. Registering a stub package keeps the two leaf modules importable
without that detour.

doCheck = false: tests/ drives a real gfx1151 GPU and the published
packs. Inference on a card is not verified here, this builder has no
/dev/kfd, so the wheel-only LD_PRELOAD workaround for torch's bundled HSA
runtime is untested. It should not be needed, the store torch links the
store rocm-runtime.

Verified with nix build .#kyojin at v1.3: exllamav3_ext loads, torch
reports hip 7.2.53211, the closure holds one torch (ROCm), and
kyojin-serve-qwen plus kyojin-serve-glm print their usage.

Refs nix-overlay-du9
2026-10-07 16:14:09 +03:00
alex ff1fecc0ed fix(codeaf): build furrow from source and hand it over in CODEAF_FURROW
CI / check (push) Has been cancelled
The package used to fetch the Agent-Field/furrow release asset and stage it for
go:embed, which is what `make build` does. Those bytes are a stock glibc build
that no Nix phase ever touched, so the copy codeaf writes out to
~/.codeaf/bin/furrow-0.1.0 cannot start here: NixOS answers "Could not start
dynamically linked executable" and names stub-ld. Every furrow verb the package
offers was dead with it.

Staging a rebuilt furrow was not an option. Upstream's fetcher hashes what it
stages against internal/furrowbin/pin.json and refuses anything else, and
patching the downloaded asset changes its hash. So this stages nothing, and
./furrow.nix builds the pinned version from source instead. The wrapped codeaf
passes it through CODEAF_FURROW, which internal/furrow reads before it looks at
the embedded copy, so the go binary carries no furrow at all (63 MB, was 67 MB)
and nothing unpatched is written to the state root.

furrow is Rust, not Go, and rusqlite bundles sqlite, hence the build time. Its
test suite wants a filesystem that supports user.* xattrs; the sandbox /tmp is
tmpfs and answers EOPNOTSUPP, which takes out the fixture of all 54 cli tests at
tests/cli.rs:48 and one lib test with it. The unit tests run, minus that one.

Verified with nix build .#codeaf: `codeaf --version` reports 0.7.1, the wrapper
sets CODEAF_FURROW to the store furrow, that furrow prints `furrow 0.1.0`
against store glibc, and it sits in the codeaf output's references so a gc
cannot pull it out from under the wrapper. Not verified on darwin, no builder.

Refs nix-overlay-bju
2026-10-07 11:33:48 +03:00
alex c08c444a39 fix(marmel): skip the two Landlock sandbox-exec tests
CI / check (push) Has been cancelled
The lib suite failed in the Nix sandbox:

    harness::sandbox::tests::test_internal_sandbox_exec_dev_null_and_dns
    harness::sandbox::tests::test_internal_sandbox_cross_directory_rename
    Failed to exec shell in sandbox: Permission denied (os error 13)

apply_landlock_linux() allow-lists FHS paths only, and Landlock matches
inodes rather than symlinked views, so nothing under /nix/store can be
executed once the ruleset is applied; /bin/sh here is a store path. The
build sandbox also drops the /usr, /lib, /run and /var rules, since those
paths do not exist there, and has no /etc/resolv.conf without network, so
neither test can pass however the package is written. 342 of 344 tests run,
all green.

The same denial applies at runtime: every shell tool call goes through
marmel --internal-sandbox-exec and fails on NixOS. Tracked as
nix-overlay-5ml. Upstream main still carries the FHS-only list.
2026-10-06 22:31:40 +03:00
alex 03337bc545 feat(codeaf): add CodeAF coding agent package
CI / check (push) Has been cancelled
CodeAF (Agent-Field/CodeAF) is a Go coding harness that ships one binary.
Pinned to v0.7.1; the flake's nixpkgs already carries go 1.26.7 and go.mod
asks for 1.26.5, so no extra nixpkgs input is needed.

Two things about this build are not obvious from the derivation:

- `make build` runs two host-side steps before compiling: `go generate
  ./internal/manual` packs the built-in manual into the pages.pack.gz and
  chat.pack.gz that the codeaf_packed_manual tag embeds, and
  internal/furrowbin/cmd/fetch stages the pinned Agent-Field/furrow release
  into internal/furrowbin/cache for go:embed. Both are run in preBuild with
  GOOS/GOARCH unset, the way the Makefile does it, so a cross build does not
  try to run a target binary on the build machine. buildGoModule runs preBuild
  in the vendoring derivation as well, before vendor/ exists and before the
  dependencies are in reach, so the two steps are gated on vendor/.
- The furrow step gets its bytes from fetchurl and `-from`, the offline road
  upstream documents. The fetcher still checks the sha256 in
  internal/furrowbin/pin.json, so the hashes here duplicate a pin that is
  already in the source; drop the furrow entirely and codeaf still builds and
  falls back to looking for the binary on PATH.

Tests are off: the upstream suite is a make/CI matrix with network and timing
assumptions, not a `go test ./...` that fits buildGoModule.

Verified with nix build .#codeaf, `codeaf --version` reporting 0.7.1 and
`codeaf manual` listing the packed manual pages.

Refs nix-overlay-m5y
2026-10-06 21:45:16 +03:00