Location: cli/json.hpp (capabilities JSON, ~line 215)
Finding: The capabilities report's features array lists values like ldf, e2e, master, slave, virtual, mock. The spec defines features as protocol-specific capability strings, and defines no such strings for LIN. What's actually listed here are internal module/transport names — and virtual/mock duplicate what the separate transports field is meant to convey. Per the spec, unrecognized strings in this field are simply ignored by conformance tooling, so this isn't a hard conformance failure, but it does misrepresent what 'features' means for this binary.
Recommendation: Either drop the features field entirely (since LIN defines no standard feature strings), or clearly document these as vendor-specific extension values; in either case stop duplicating virtual between features and transports.
Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.
Location:
cli/json.hpp(capabilities JSON, ~line 215)Finding: The capabilities report's
featuresarray lists values likeldf,e2e,master,slave,virtual,mock. The spec definesfeaturesas protocol-specific capability strings, and defines no such strings for LIN. What's actually listed here are internal module/transport names — andvirtual/mockduplicate what the separatetransportsfield is meant to convey. Per the spec, unrecognized strings in this field are simply ignored by conformance tooling, so this isn't a hard conformance failure, but it does misrepresent what 'features' means for this binary.Recommendation: Either drop the
featuresfield entirely (since LIN defines no standard feature strings), or clearly document these as vendor-specific extension values; in either case stop duplicatingvirtualbetweenfeaturesandtransports.Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.