When setup ends with no .abcd/config.json (the starter files declined, at a terminal or off one), it reports the README question under optional_skipped, and both routes its hint names fail: the summary's action says to run abcd ahoy install at a terminal without --yes and answer it, which is the run just made and does not ask it, or to pass --readme-parts, which storeReadmeParts refuses because .abcd/config.json does not exist yet; the text render's extra line says the same. The true route, creating the starter files first, is named only by the separate declined-starter-files entry.

When setup ends with no .abcd/config.json (the starter files declined, at a terminal or off one), it reports the README question under optional_skipped, and both routes its hint names fail: the summary's action says to run abcd ahoy install at a terminal without --yes and answer it, which is the run just made and does not ask it, or to pass --readme-parts, which storeReadmeParts refuses because .abcd/config.json does not exist yet; the text render's extra line says the same. The true route, creating the starter files first, is named only by the separate declined-starter-files entry.

Grounds

• pursued: a person whose run ends without the config is pointed at the one route that works; a run with no config whose summary or text render still names only the question or --readme-parts as the way to answer it would show it wrong