startImagesFlow method
Settings → Images: the images: config section (issue #395) — the
registry kill switch (images.registry: false reproduces today's
request shape byte-for-byte) and the per-request unique-image cap.
Writes go through the surgical validated-yaml upsert into the USER
config (the file bin/fah.dart boots the registry from), and every
successful write re-publishes the process-wide imageRegistryConfig
from the saved file — the request build consults that global, so the
change lands on the next request build without a restart (AC3/E3:
what's live is what's on disk). Loops until cancelled or done.
Implementation
Future<void> startImagesFlow() async {
for (;;) {
final picked = await _pickOption('images', _imagesMenuOptions());
if (picked == null || picked == 'done') return;
await _applyImagesPick(picked);
}
}