Maintain the gfx1151 SDK locally using the official AMD archive. Use the TheRock patchelf pin and adapt LLVM auxiliary tools for pure Nix builds.
Verify SDK installation, HIP and rocBLAS GPU operations, and rebuild its consumers. Document the internal rc3 stamp and upstream migration findings.
nix-overlay-v09 keeps the completed migration evidence and the outstanding
ms-s1-max build gate; nix-overlay-y5r is tombstoned after the duplicate
codex-oauth-proxy work was superseded.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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).
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.
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.
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
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.
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.
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.
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.
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`.
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.
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.
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).