add-benchmark

A protocol-agnostic benchmark adapter requires a thinnest wrapper approach, making the benchmark accessible to any agent without coupling to specific protocols. It enforces reusing existing harness assets to avoid duplication and ensure consistency.

The best way to update a benchmark adapter is to apply a thin, protocol-agnostic wrapper and validate the changes with representative smoke tests. This explicit smoke-test validation guarantees compatibility and correct behavior before finishing the update process.

You validate a benchmark adapter by running explicit smoke-test validation with representative test cases. This ensures the adapter maintains reliability and correct behavior by verifying the protocol-agnostic contract before the adapter is finalized.

No, you do not need to build custom scoring logic. The benchmark adapter workflow enforces reusing external harness assets and scoring wherever possible to avoid duplication and maintain consistency across the repository.

You should use a thinnest wrapper approach whenever adding or updating a benchmark adapter to ensure it remains protocol-agnostic. This design maintains a minimal wrapper, allowing any Exgentic agent to access the benchmark without unnecessary implementation overhead.