[Enhancement]: Document EIP-55 checksum requirement for Atlas SVR solver_getSolverOperationResult query API

What would you like us to improve?

The Atlas SVR searcher onboarding page documents a query API for tracing solver operation results:

• Page: https://docs.chain.link/data-feeds/svr-feeds/searcher-onboarding-atlas#tracing-solver-operation-results
• Endpoint: https://solver-query-api-fra.fastlane-labs.xyz/
• Method: solver_getSolverOperationResult

In practice, addresses passed to this API (e.g. solverOperationFrom) must be in EIP-55 checksum format. If you pass an all-lowercase or otherwise non-checksummed address, the lookup will silently fail and the API returns:

"solver operation not found"

even when the solver operation was actually received and processed. This error is also the same one returned when the operation arrives too late, which makes it very confusing to debug — solvers can spend significant time investigating timing/auction issues that don't actually exist.

The docs should:

Add a callout in the Tracing Solver Operation Results section stating that all addresses must be EIP-55 checksummed, with a link to https://eips.ethereum.org/EIPS/eip-55.

Add a new bullet to Common Mistakes titled something like "Querying the API without an EIP-55 checksummed address" explaining that this produces a misleading "solver operation not found" response.

How important it is?

Medium-high importance for any team integrating with Atlas SVR as a searcher. The failure mode is silent and the error message points searchers in the wrong direction (toward auction timing or signature issues rather than address formatting), so this can cost meaningful integration time. The fix is a small documentation change with no code impact.