Improve codes and description on data feed SVR page

src/content/data-feeds/llms-full.txt

@@ -5991,6 +5991,8 @@ func runSearcherGateway() {
 		}
 	}
 
+  subscribe()
+
 	// Main loop
 	for {
 		select {
@@ -6246,6 +6248,13 @@ FastLane provides a query API for solvers to trace what happened to their solver
 
 **URL:** `https://solver-query-api-fra.fastlane-labs.xyz/`
 
+<Aside type="caution" title="Use EIP-55 checksummed addresses">
+  All addresses passed to this API (e.g. `solverOperationFrom`) **must be in
+  [EIP-55](https://eips.ethereum.org/EIPS/eip-55) checksum format**. Lowercased or otherwise non-checksummed addresses
+  will not match the cached entry and the API will return `"solver operation not found"`, even if your solver operation
+  was actually submitted successfully.
+</Aside>
+
 **Example request:**
 
 ```json
@@ -6288,6 +6297,10 @@ This won't happen if you inherit from `SolverBase`.
 
 If the solver operation arrives after the auction duration has elapsed, it will not be included. The query API will communicate the error `"solver operation not found"`.
 
+**Querying the API without an EIP-55 checksummed address**
+
+If you query the [solver operation results API](#tracing-solver-operation-results) using an address (e.g. `solverOperationFrom`) that is not in [EIP-55](https://eips.ethereum.org/EIPS/eip-55) checksum format, the lookup will fail and the query API will return `"solver operation not found"` — even if your solver operation was actually received and processed. Always pass checksummed addresses when calling the query API.
+
 **Not enough bonded atlEth**
 
 Read the [bonding guide](#bond-bridged-eth-to-the-auction-contract) to learn how to bond atlETH. This error will be communicated in the query API response.

src/content/data-feeds/svr-feeds/searcher-onboarding-atlas.mdx

@@ -737,6 +737,8 @@ func runSearcherGateway() {
 		}
 	}
 
+  subscribe()
+
 	// Main loop
 	for {
 		select {
@@ -992,6 +994,13 @@ FastLane provides a query API for solvers to trace what happened to their solver
 
 **URL:** `https://solver-query-api-fra.fastlane-labs.xyz/`
 
+<Aside type="caution" title="Use EIP-55 checksummed addresses">
+  All addresses passed to this API (e.g. `solverOperationFrom`) **must be in
+  [EIP-55](https://eips.ethereum.org/EIPS/eip-55) checksum format**. Lowercased or otherwise non-checksummed addresses
+  will not match the cached entry and the API will return `"solver operation not found"`, even if your solver operation
+  was actually submitted successfully.
+</Aside>
+
 **Example request:**
 
 ```json
@@ -1034,6 +1043,10 @@ This won't happen if you inherit from `SolverBase`.
 
 If the solver operation arrives after the auction duration has elapsed, it will not be included. The query API will communicate the error `"solver operation not found"`.
 
+**Querying the API without an EIP-55 checksummed address**
+
+If you query the [solver operation results API](#tracing-solver-operation-results) using an address (e.g. `solverOperationFrom`) that is not in [EIP-55](https://eips.ethereum.org/EIPS/eip-55) checksum format, the lookup will fail and the query API will return `"solver operation not found"` — even if your solver operation was actually received and processed. Always pass checksummed addresses when calling the query API.
+
 **Not enough bonded atlEth**
 
 Read the [bonding guide](#bond-bridged-eth-to-the-auction-contract) to learn how to bond atlETH. This error will be communicated in the query API response.