Observation from the lane LA assessment (GHSA-4q78 reproduction): `ahoy install --yes` with missing config values still emitted an interactive value prompt ("visibility (private/public) []:") on stdout, then proceeded as partial when stdin was empty. `--yes` approves categories, not values, so the partial outcome may be by design, but a prompt landing on stdout under a non-interactive flag with no TTY is worth a look: a scripted install reads it as output, and the prompt is the one line in the run that is not a receipt. Not fixed in this run.

Observation from the lane LA assessment (GHSA-4q78 reproduction): ahoy install --yes with missing config values still emitted an interactive value prompt ("visibility (private/public) []:") on stdout, then proceeded as partial when stdin was empty. --yes approves categories, not values, so the partial outcome may be by design, but a prompt landing on stdout under a non-interactive flag with no TTY is worth a look: a scripted install reads it as output, and the prompt is the one line in the run that is not a receipt. Not fixed in this run.

Grounds

• pursued: an install --yes without a terminal asks its value questions on stderr only; shown wrong if the pinned test sees a value prompt on stdout