The WebDriver BiDi spec recommends aligning modules with specifications, so that ownership is clear:
Other specifications may define their own WebDriver-BiDi modules that extend the protocol. Such modules must not have a name which contains a colon (:) character, nor must they define command names, event names, or property names that contain that character.
Authors of external specifications are encouraged to to add new modules rather than extending existing ones. Where it is desired to extend an existing module, it is preferred to integrate the extension directly into the specification containing the original module definition.
Client hints extending the "emulation" module violates this recommendation; I suggest unless there's a clear reason that this is necessary you either define a module called something like clientHints, or propose your extension for direct integration into WebDriver-BiDi (however note that the latter would likely be difficult since this specification is not on a standards track).
The WebDriver BiDi spec recommends aligning modules with specifications, so that ownership is clear:
Client hints extending the "emulation" module violates this recommendation; I suggest unless there's a clear reason that this is necessary you either define a module called something like
clientHints, or propose your extension for direct integration into WebDriver-BiDi (however note that the latter would likely be difficult since this specification is not on a standards track).