itd-2609221017023290 ac-2 promises a walkthrough that offers the three homes with the keychain recommended in the prose above the choice; its press release says abcd asks the person once per service where the secret should live, and spc-2609221017544877 scope 2 says the CLI asks on the terminal and the plugin page asks through the host's question tool. Delivered, the CLI's abcd ahoy credential <name> explains and lists the homes with a setup command for each and writes nothing, and the choice is a --home flag on a second invocation (internal/surface/cli/ahoy_credential.go newAhoyCredentialCommand); the CLI never asks. Only the plugin page asks, through the host's question tool (commands/ahoy.md, the credential section). A non-interactive CLI is consistent with every other abcd verb and with the value arriving on stdin only, so this may be the right shape, but the spec and the press release say otherwise and no recorded decision says the CLI's ask was dropped. Either the record says the CLI takes the home as a flag, or the walkthrough asks. Fidelity audit verdict: ac-2 MET_WITH_CONCERNS.

itd-2609221017023290 ac-2 promises a walkthrough that offers the three homes with the keychain recommended in the prose above the choice; its press release says abcd asks the person once per service where the secret should live, and spc-2609221017544877 scope 2 says the CLI asks on the terminal and the plugin page asks through the host's question tool. Delivered, the CLI's abcd ahoy credential <name> explains and lists the homes with a setup command for each and writes nothing, and the choice is a --home flag on a second invocation (internal/surface/cli/ahoy_credential.go newAhoyCredentialCommand); the CLI never asks. Only the plugin page asks, through the host's question tool (commands/ahoy.md, the credential section). A non-interactive CLI is consistent with every other abcd verb and with the value arriving on stdin only, so this may be the right shape, but the spec and the press release say otherwise and no recorded decision says the CLI's ask was dropped. Either the record says the CLI takes the home as a flag, or the walkthrough asks. Fidelity audit verdict: ac-2 MET_WITH_CONCERNS.

Remedy grounds (2026-09-29)

• Why: the two answers CA9 lists; the ruling is unanswered and none is picked, but both keep a flag route and the value off the command line.
• Sources (consulted 2026-09-29): the Command Line Interface Guidelines say to prompt only when stdin is an interactive terminal, never to require a prompt, and never to take secrets through flags (https://clig.dev/); gh auth login prompts interactively by default and takes a token on stdin with --with-token for scripts (https://cli.github.com/manual/gh_auth_login). Either answer fits that practice so long as --home stays.
• Rejected: a prompt with no flag route, which would break every non-interactive caller.