Development record
commands/ahoy.md names the stray-hook gap id as harness.stray_hook.<Event>, but internal/core/ahoy/harness_strays.go appends .<n> for a second abcd hook on the same event. The page already tells the host to relay detail and fix_hint as they stand, so no action goes wrong; the id shape is simply incomplete. Deferred from the v0.13.1 cut to keep its content commit stable.
issueresolvednitpickiss-2610051540383966
commands/ahoy.md names the stray-hook gap id as harness.stray_hook.<Event>, but internal/core/ahoy/harness_strays.go appends .<n> for a second abcd hook on the same event. The page already tells the host to relay detail and fix_hint as they stand, so no action goes wrong; the id shape is simply incomplete. Deferred from the v0.13.1 cut to keep its content commit stable.
Grounds
- pursued: the ahoy page names both stray-hook id shapes the detector emits; TestAhoyPageNamesBothStrayHookIDShapes failing, or a page that omits the .<n> shape, would show it wrong
Frontmatter
| id | iss-2610051540383966 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-2610051540383966-the-stray-hook-gap-id-can-carry-a-number.md
open on GitHub ↗ · commit history ↗