Development record

scanner lanHostRe and deviceHostRe keep the trailing ASCII word boundary the iss-307 sweep dropped from ipv4Re and macRe, so a LAN or device hostname abutting an underscore or alnum suffix is silently missed

issuewontfixminoriss-358

Evidence

internal/adapter/scanner/network.go:100 (lanHostRe) and :110 (deviceHostRe) end in \b; the alternation requires a literal suffix (local|lan, -macbook etc.), so RE2 cannot shorten to a boundary and a _/alnum-adjacent hostname drops the whole match. Verified through ScanText -> Redact: my_printer.local and bob-macbook.local_backup (LAN half) produce 0 findings; bare forms produce 1.
Prior art boundary: iss-307 (hunt A) drops the trailing \b from ipv4Re/macRe only; the two hostname patterns are the residual of that sweep.
Refuter verdict: CONFIRMED substantive for the class. Fix verified against a whole-tree sweep: findings byte-identical before/after apart from the new catches, go test ./... green. That verification was insufficient — the sweep ran over a tree containing no .local_/.lan_ snake_case selector, so it could not see the false-positive class the pre-merge review then proved (stream.local_addr and kin rewritten by irreversible Stage-1 redaction); a clean sweep over one tree is evidence about that tree, not about the input space.
Re-minted from the round-2 id that collided with a parallel hunt's mint (the collision class this ledger's own iss-344 records).

Frontmatter

id	iss-358
type	issue
lifecycle	wontfix
severity	minor

.abcd/work/issues/wontfix/iss-358-scanner-lanhostre-and-devicehostre-keep.md
open on GitHub ↗ · commit history ↗

mentions3

dcn-26082000000000022026-08-20 — bughunt round 2 (branch bughunt-b/round-2): captured the round-2 records (iss-346..iss-357, with the two colliding ids re-minted as iss-358/iss-359), fixed
iss-307scanner network ipv4Re and macRe rely on a trailing ASCII word boundary, silently missing a hard_fail address whose only sin is an adjacent word char
iss-344Parallel hunts capture the same defect twice: iss-306 (hunt A round 1, landed late) and iss-339 (hunt B round 2) record the identical githubRemoteRe case-sensitivity bug, minted independently on unmerged branches invisible to each other. Collision-proof ids (itd-114) do not solve this class — it is the semantic sibling of the id collision, sharing the root cause that parallel minters cannot see each other's unmerged mints. Candidate rungs: a capture-time similarity check (itd-84's validator rung), hunt briefings that read open PRs' ledgers, or a shared mint registry as a side effect of itd-114's forge-backed option