Wiki: the manifests are YAML
Every page is YAML now: the root loadout.yaml, program files named by the file,
*.loadout.yaml sections for several programs, and machine and profile files that
name each program with install_with. Links to the live example point at the
dotfiles' new paths; the eject target is builtin.loadout.yaml.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Configs: observed and applied through chezmoi
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.0: repo layout, profiles, live links into .dotfiles
New Repo layout page. Writing your manifest, Home and A day with loadout
describe loadout.toml, groups and profiles, `file:` with values and the
built-in omarchy installers, and link into josemiguelo/.dotfiles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
the home screen, upgrade as a verb, and actionable oracles
Home: a design-stance bullet for "converging installs; upgrading is its
own verb" and the bare-`loadout` home screen after Install; the binary's
update is `self-upgrade` now.
A day: the morning starts on the home screen (rows, l/h/enter, the
capitals) before `status`; maintain opens on the last observed verdicts
and `run --pending` is the same rule; a new "Acting on it" section under
the weekly remotes — `loadout upgrade dnf brew` whole-mechanism (why no
single package, --all is only what this machine maps, the re-check
after), custom sources one item at a time within the pin's major,
read-only nvim-plugins, the remote table's tick boxes ([x] per mechanism
or per item, [–] for nothing movable) and the floating pane: question
first, one rule per step, esc kills, footer names the failure, rows
refresh underneath. Loop diagram gains the upgrade arrow.
Writing your manifest: the installers table gets its `upgrade` column;
`[outdated.*]` documents `upgrade = "... {item}"` (once per item, exit
code is the verdict, omit it for read-only rows); the oracle patterns
table gains the update column, loses the dead zsh-plugins link and stops
describing nvim-plugins as a clone walk (it asks Lazy). Version-floor fix
is `self-upgrade`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C28kxwCMTRUgMJB73zYeeX
teach the tool that exists: built-in installers first
Writing-Your-Manifest opened by hand-writing command/check/regex and built
up to "an installer declares a mechanism once — and by the way, some ship
with loadout". Since 0.8.0 that's backwards: §1 is now `via = ["dnf"]` in a
two-line repo, §2 leads with the eight built-ins and their oracles, and
declaring your own is the escape hatch it has become. The params section
uses the shipped dnf-copr/dnf-repo instead of telling people to build the
repo script loadout now provides.
Also: the blueprint table gains COPR and vendor-rpm-repo rows and stops
citing kitty as a repo-script example (it hasn't been one since the config
repo migrated); Home lists all eight built-ins; A-Day shows the boxed
status rows the tool actually draws now, and documents --all.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C28kxwCMTRUgMJB73zYeeX
installers ship with loadout
Home gains the stance bullet (mechanics in the tool, intent in the repo,
built-in is not detected); Writing-Your-Manifest §2 stops telling people
to write the installers table and shows `loadout installers` instead,
dropping the now-404 link to the live repo's deleted fragment; A-Day ties
built-ins to the min-tool-version floor.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C28kxwCMTRUgMJB73zYeeX
concepts, manifest guide, day-with-loadout