Repository navigation
v0.1.2
Documentation for adopting fleet-kit (#16, PR #18). No code changes.
- README: what fleet-kit is for and who uses it, a "What's verified" table of everything not yet run live, and the install model. You install the package and keep your configuration in a private repository of your own, never a fork. A fork of a public repository has to stay public.
docs/getting-started.md: the operator's path from start to finish:- prerequisites, linking to robot-council/cli's setup;
- install;
- the private configuration repository, and what must never go in it;
FLEET_KIT_CONFIG;seat-stage check, then--dry-run, then a first stage;seat-pace pace, thenread, then a scheduler;- updating.
docs/coordinators.md:- who does what;
- getting the verdict through the log or
on_change; - writing a pacing policy;
- what a restart does to seats and their tasks;
- an adoption checklist for a new organization.
- Stale text fixed: the Windows Task Scheduler template no longer says
readis unsupported on Windows. The scheduler examples andexamples/seats.tomlnow assume a Composer install and a private config repository.