Setup saves its four config values (visibility, docs_target, oracle_backend, scan_deep) all together or not at all, so when one of them was deferred with 'decide later' and another is answered, neither is written: the answer reaches the setup answers record but never .abcd/config.json. A full ahoy install does this today, and the new ahoy install --only-waiting inherits it, so an answer a person gives after an update can silently not take effect.

Setup saves its four config values (visibility, docs_target, oracle_backend, scan_deep) all together or not at all, so when one of them was deferred with 'decide later' and another is answered, neither is written: the answer reaches the setup answers record but never .abcd/config.json. A full ahoy install does this today, and the new ahoy install --only-waiting inherits it, so an answer a person gives after an update can silently not take effect.

Grounds

• pursued: an answer given beside a deferred value reaches .abcd/config.json in both install modes; a deferred value appearing in the file, or an answered one missing from it, would show it wrong