ahoy install's re-founding lineage prompt is a one-shot: under --yes/non-TTY it prints and silently takes the [y/N] default No, registers the root as new, and a second run reports already_up_to_date without re-asking — no verb links lineage after the fact, leaving two active index entries for the same project (old epoch 85573f…, new 488a0aa… after the attribution rewrite). Non-TTY identity prompts should refuse rather than default, and lineage should be linkable post-registration

ahoy install's re-founding lineage prompt is a one-shot: under --yes/non-TTY it prints and silently takes the [y/N] default No, registers the root as new, and a second run reports already_up_to_date without re-asking — no verb links lineage after the fact, leaving two active index entries for the same project (old epoch 85573f…, new 488a0aa… after the attribution rewrite). Non-TTY identity prompts should refuse rather than default, and lineage should be linkable post-registration

Remedy grounds (2026-09-29)

• The refusal-plus-flag shape follows the Command Line Interface Guidelines: only prompt when stdin is a TTY, and never require a prompt, always offering a flag for the same input (https://clig.dev/, checked 2026-09-29).
• The flag is common to both answers of ruling AV, so the remedy names it without choosing between refusing and linking afterwards.
• Rejected: keeping the silent No default, which is the behaviour the record reports.