logan 26251badda
CI / check (push) Skipped
CI / e2e (push) Skipped
CI / check (pull_request) Successful in 3m0s
CI / e2e (pull_request) Successful in 10m18s
ci(skill-check): scan the docs a contributor reads
The check asserts that every make target named in a doc exists, and its
scanned set was .pi/ plus CLAUDE.md.  Since #50, CONTRIBUTING.md is the
document a *human* goes to for a build command, and it names 21 targets
that nothing verified; README.md names none today and is in for the same
reason.  The script's own header sentence is the argument — a renamed
target sends a person off the same cliff it sends an agent off.

The file list is now one `docs` variable used twice, because the failure
message carried a second copy of it and a second list is a second thing
to forget.  The `[ -d .pi ]` guard went with it: gating the whole run on
.pi/ would make the human-facing half conditional on the agent-facing
one, and an empty list is the same "nothing to scan" exit without the
coupling.

The lefthook glob is that scanned set now rather than
{Makefile,.pi/**/*.md} — #220's smaller half, and it did not fire on
CLAUDE.md either, which the script had read for months.

Verified by planting a bad target rather than by reading the diff: both
matched forms in each of the four scanned surfaces, each naming the
right file; the same two plants pass on the pre-change script; unfenced
prose still does not match; and the hook fires on a staged
CONTRIBUTING.md under the new glob where the old one skipped it.  The
count is unchanged at 47 — the set is a union — so coverage is the only
thing that moved.

Closes #220
2026-08-28 03:38:28 -04:00
2026-08-14 14:01:02 -04:00

YellowJacket

Music how it was meant to bee.

YellowJacket plays the music you already own. Point it at your folders and it scans them, reads the tags and the cover art, and gives you a library you can browse, search, queue and tidy up — on your own machine, with no account, no streaming service and no telemetry.

It plays MP3, FLAC, OGG Vorbis and WAV, on Linux and Android, and builds from source on macOS.

The track list, with something playing

What it does

Plays your files. Play, pause, seek and volume with a mute toggle; a read-ahead buffer so seeking is instant rather than gappy; a queue you can add to, reorder and shuffle, with play-next; shuffle and repeat (off / all / one). It remembers the track, the position and the queue between sessions, and it answers your desktop's media keys — MPRIS on Linux, a media notification and lock-screen controls on Android.

Keeps the library tidy. It scans the folders you give it and rescans only what changed, so a big library costs its full scan once. It de-duplicates embedded cover art rather than storing the same image a hundred times, notices files that have gone away, and spots duplicate tracks. Browse by album, artist or genre, search across everything, mark favourites, and see what you have been playing.

Playlists, and playlists that write themselves. Drag tracks in and reorder them, or describe what you want — genre, play count, how long since you played it — and let a smart playlist keep itself up to date.

Explore and auto-tag, from the MusicBrainz catalog. Explore browses artists, releases and genres from the catalog rather than only from what you own, so an album page can tell you that you have nine of its twelve tracks. Auto-tag matches your files against MusicBrainz and fills in the metadata that is missing, with a review step before anything is written to disk. Lyrics search finds a track from a line you remember.

Explore needs its catalog, which is a one-off ~0.6 GB download from Settings → Search Index. It asks first on a metered connection, and everything else in the app works without it.

Install

Every download comes from the releases page.

Linux

Download yellowjacket-<version>-linux-amd64.tar.gz from the latest release and unpack it. It holds the binary, a .desktop entry and an icon.

On Arch, install it from the package registry instead and get updates with the rest of your system — the one-time key import and pacman.conf block are in packaging/arch/README.md:

sudo pacman -Sy yellowjacket

Android

Install the APK from the release page, or from the URL below, which always points at the newest build:

https://git.ljones.me/api/packages/yonlu/generic/yellowjacket-android/latest/yellowjacket.apk

That URL needs no credentials, so Obtainium can poll it directly and keep the app up to date. The build is arm64-v8a only, and docs/android-release.md says why.

macOS

Homebrew builds it from source on your own Mac — there is no prebuilt .app, because a signed macOS bundle needs a macOS machine to produce it and the release runner is a Linux container.

brew install shadow-puppet/yellowjacket/yellowjacket

See packaging/homebrew/README.md.

Windows

Not published. It cross-compiles cleanly, but no Windows build of this app has ever been run, and nothing here can exercise one — so shipping it would be a promise that cannot be kept. You can still build it yourself: see CONTRIBUTING.md.

Coming from a 1.x install?

Versions restarted at 0.0.1 when releases became automatic, which every package manager reads as a downgrade. It costs one reinstall, once — the details are with each channel: Homebrew, Android.

First run

  1. Launch YellowJacket.
  2. Add the folder your music lives in — the first-run wizard asks, and Settings → Libraries is where you add more later.
  3. Watch the scan finish. It reports progress, and you can browse while it runs.
  4. Queue something and press play.

Your library and settings stay on your machine:

Linux / macOS Windows
Config ~/.config/yellowjacket/ %LOCALAPPDATA%\yellowjacket\config
Library data ~/.local/share/yellowjacket/ %LOCALAPPDATA%\yellowjacket\data

Setting YJ_HOME moves both, which is how you keep a second library separate.

More screenshots

An album page knows what you own, and says so:

An album page, with two discs and the transport playing

The home page suggests somewhere to start rather than opening on a wall of everything:

The home page's shelves

Contributing, and the rest of the documentation

  • CONTRIBUTING.md — build it from source, run the tests, and how a change gets in.
  • CLAUDE.md — the deep reference: the architecture and the reasons behind the shape of it.
  • The issue tracker is what is wanted and what is being worked on; #73 is the roadmap.
  • Releases double as the changelog — every one is generated from the commits it contains.
S
Description
No description provided
Readme
15 MiB
v0.7.0
Latest
2026-08-26 16:03:22 +00:00
Languages
TypeScript 50.6%
Go 43.6%
Java 1.8%
JavaScript 1.5%
Shell 1.4%
Other 0.9%