Release v0.100.0 · cbundy/dev-system

New

The factory commands have fabriek names - Every factory command in the base image is now fabriek-<x> (for example fabriek-issue-read, fabriek-event, fabriek-merge), and every setting can be given as FABRIEK_<X>. The old callum-flow-<x> commands stay as aliases with the same output and exit codes, and the old CALLUM_FLOW_<X> settings still work; FABRIEK_<X> wins when both are set. The old names are kept for 10 minor releases. (#1362)
The shared plugin is now fabriek - The callum-flow plugin is renamed fabriek, and its skills name the fabriek-* commands. The marketplace keeps a callum-flow entry with the same content for 10 minor releases, so repos that enable callum-flow@callum keep working. The image now installs fabriek@callum by default, replaces an old callum-flow install with it, and falls back to callum-flow@callum when a repo pins a release older than the rename. dev-doctor warns when both names are installed or enabled. (#1363)
The loop calls the fabriek commands - The factory loop, its companions and the HUD now run the fabriek-* commands, falling back to the old callum-flow-* names on an image older than 2.79.0. (#1364)

Plugin: run npx callum-dev update, commit the .claude/settings.json it produces, then restart the container or run dev-init --plugins. A repo can switch callum-flow@callum to fabriek@callum in its .claude/settings.json; enable only one of the two. A loop workspace on the orchestrator-loop template picks up the plugin only after that template is pushed at this release (coder/push.sh orchestrator-loop).
Base image: rebuild or re-pull the dev container to get image 2.79.0, which brings the fabriek-* commands, the FABRIEK_<X> settings and the plugin twin handling.

Technical changes