defining it [the API] as a WebDriver BiDi module would allow adding events later (if needed) and it would allow WebDriver BiDi-only clients such as Puppeteer to expose the functionality for developers to write tests for their apps.
We do not need BiDi's bidirectional capabilities at the moment, but I don't think it would hurt to define a BiDi module in the future, just like the Permissions API does.
As discussed in https://github.com/w3c/compute-pressure/pull/284#issuecomment-2180990161:
We do not need BiDi's bidirectional capabilities at the moment, but I don't think it would hurt to define a BiDi module in the future, just like the Permissions API does.