abcd ahoy install and abcd ahoy remote apply disagree on how a refused run exits: remote apply returns exit 1 when its result is refused or aborted (internal/surface/cli/cli.go, the applyCmd RunE, 'A change that did not happen exits non-zero'), while ahoy install renders every core refusal (the committed .abcd symlink hazard, the stale-binary guard, the retired docs.target refusal) with status refused and exits 0, so a script cannot tell an install that wrote nothing from one that landed. iss-2610020705158672 names the stale-binary case alone; this is the asymmetry across every install refusal and against the sibling verb.

abcd ahoy install and abcd ahoy remote apply disagree on how a refused run exits: remote apply returns exit 1 when its result is refused or aborted (internal/surface/cli/cli.go, the applyCmd RunE, 'A change that did not happen exits non-zero'), while ahoy install renders every core refusal (the committed .abcd symlink hazard, the stale-binary guard, the retired docs.target refusal) with status refused and exits 0, so a script cannot tell an install that wrote nothing from one that landed. iss-2610020705158672 names the stale-binary case alone; this is the asymmetry across every install refusal and against the sibling verb.

Grounds

• pursued: every refused ahoy install and refused remote apply exits 2 with its reason on stdout, and an aborted apply exits 1; a refusal exiting 0 or 1 from either verb would show it wrong