Chapter 13: tools, the helpers backstage

Nothing in this folder is part of the site. These are the things that help build it, run it on a laptop, and decide how it should behave. Three of them are small shell scripts with one job each; the last, eval/, is a whole program and gets the next chapter.

Aside. Why does a dev server need a script to report its own exits? Because wrangler's wrapper exits with status 0 when the runtime under it is killed (measured 2026-10-02), and pitchfork, which supervises it, only restarts something that failed. So wrangler-dev treats any exit nobody asked for as a failure, and pitchfork brings it back.

For the people who maintain it

Path	What
eval/	Picks the LLM, and checks the nine questions Jev is asked first. Chapter 14.
wrangler-dev	The Worker under `wrangler dev`, for pitchfork: it reports an exit nobody asked for as a failure, so pitchfork restarts it.
check-hosts	Curl checks of a running dev server's host handling (`apps/lmjtfy/src/host.rs`): `lmjtfy.fun` redirects every served repository to `code.lmjtfy.fun` with its path and query (redirect on) or serves it itself (off), and the code host has the code and nothing that asks Jev. Takes the mode as an argument. Needs a dev server per host and mode, because `wrangler dev` overwrites the Host header; the header says how.
devshell-root	Registers the owner's devshell as a nix garbage-collection root, so a collection does not make the next `nix develop` rebuild pitchfork. From `~/aifleet`.

← Previous: Chapter 12½, tree/src/ · Up: lmjtfy · Next: Chapter 14, eval/ →