Evaluate an oracle adapter without recording it

Runs the adapter policy against the address at one pinned block and answers the verdict in the stored assessment's shape. Nothing is written: no registry row, no assessment; the adapter is recorded when a router installs it (the indexer's ConfigSet handler) or when the hourly router-history sweep finds it. Cross-adapter legs the registry does not know are evaluated inline at the same block, two levels deep, and reported in legs; Pyth reads carry a fresh Hermes update like the stored checks. The address must have bytecode on the chain (422 otherwise), one address is evaluated at most 6 times per minute (429 with Retry-After), a repeated request within 30 seconds answers the same evaluation, and the on-chain reads are given 12 seconds (504 when exceeded). Accepts a platform session or a API key holding assessments:evaluate; a curator session is never enough.

Needs the assessments chain capability; a chain without it answers 404 CHAIN_CAPABILITY_DISABLED.