Location, confirmed at current HEAD. cli/CMakeLists.txt:1: add_executable(cpp-lin-cli main.cpp).
Finding. RELAY spec §13.2 "CLI binary names" mandates a lowercase <lang>-<proto> binary name
(e.g. go-lin, cpp-rcp, rust-someip) — i.e. this binary should build as cpp-lin, with no -cli
suffix. This is the same class of defect independently present in cpp-CAN's cpp-can-cli (filed there
as RELAY-TERM-03), found while skimming the audit's §3.1 CLI-binary-name matrix for further
individually-actionable naming defects beyond the six already-scoped RELAY-TERM findings. The sibling
cpp-RCP repo names its target correctly (add_executable(cpp-rcp cli/main.cpp) with an explicit
OUTPUT_NAME cpp-rcp), so there is an in-family precedent to follow.
Recommendation. Rename the CMake target (or set OUTPUT_NAME cpp-lin on the existing target) so
the built binary is named cpp-lin, matching §13.2 and the cpp-RCP precedent.
Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.
Location, confirmed at current HEAD.
cli/CMakeLists.txt:1:add_executable(cpp-lin-cli main.cpp).Finding. RELAY spec §13.2 "CLI binary names" mandates a lowercase
<lang>-<proto>binary name(e.g.
go-lin,cpp-rcp,rust-someip) — i.e. this binary should build ascpp-lin, with no-clisuffix. This is the same class of defect independently present in cpp-CAN's
cpp-can-cli(filed thereas RELAY-TERM-03), found while skimming the audit's §3.1 CLI-binary-name matrix for further
individually-actionable naming defects beyond the six already-scoped RELAY-TERM findings. The sibling
cpp-RCP repo names its target correctly (
add_executable(cpp-rcp cli/main.cpp)with an explicitOUTPUT_NAME cpp-rcp), so there is an in-family precedent to follow.Recommendation. Rename the CMake target (or set
OUTPUT_NAME cpp-linon the existing target) sothe built binary is named
cpp-lin, matching §13.2 and the cpp-RCP precedent.Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.