notes20261002

Overview ¶

Command notes20261002 writes the notes of 2026-10-02 into nova-config: the reason each route the first real sprint disabled was disabled, and why one machine is held, as the `note` of the row (pkg/config, migration 0015; docs/SPEC-CONFIG.md, "The note"). The reasons were recorded on nova-tools#5101 until the field existed; the numbers below are that issue's comments (ok / total over the day's work and reads), nothing re-measured.

The coordinator runs it once, after `nova-config migrate` has applied 0015 to the store, naming the machine that was held (the one whose reads ran kernel-bound at 1:46 PM), first as a dry run:

NOVA_PG_DSN=postgres://... NOVA_FRIEND=<actor> notes20261002 <machine> --dry-run
NOVA_PG_DSN=postgres://... NOVA_FRIEND=<actor> notes20261002 <machine>

It reads and writes through nova-config only: one `route set <name> --note` per disabled route and one `machine set <machine> --note`, each recorded in the row's history under the actor. A route that is not disabled when the program reaches it is skipped (a note that says why it is off must not sit on a route that is on), and a route that is no row is counted missing and the program ends 1; nothing is enabled, disabled or removed here. Run again, it writes the same notes again, one more history row each.

env: NOVA_CONFIG the binary (default nova-config); NOTES_AS the actor (default NOVA_FRIEND, which nova-config reads itself); NOTES_CONN extra flags for every call, split on white space, such as --pg <dsn> or --file <path> (default none: NOVA_PG_DSN names the store).