Classify findings #5, #6, and #7 as protocol-stub false positives

[Copilot]

Reviewed the reported code quality findings and confirmed they do not indicate executable no-op logic. All three findings point to intentional typing.Protocol method stubs, so no source changes were needed.

• What was reviewed

  • bowtie/_commands.py
    • Command.to_request
    • Command.from_response
  • bowtie/_core.py
    • _MakeValidator.__call__

• Why these findings are false positives

  • The flagged lines are ... bodies inside Protocol method declarations.
  • In this context, ... is the standard stub form used to define an interface contract without implementation.

• Code pattern involved

  class Command(Protocol[R]):
      def to_request(self, validate: Callable[..., None]) -> dict[str, Any]:
          ...

• Result

  • No functional changes proposed.
  • Findings build(deps-dev): bump @types/react-dom from 18.2.11 to 18.2.13 in /frontend #5, build(deps-dev): bump @typescript-eslint/parser from 6.7.4 to 6.7.5 in /frontend #6, and build(deps): bump com.fasterxml.jackson:jackson-bom from 2.15.2 to 2.15.3 in /implementations/java-openapiprocessor #7 should be treated as analyzer false positives rather than remediated in code.