build-error-adapter

# Build Error Adapter Use this workflow to create new error adapters that fit Arcade TDK conventions. ## Official Reference Start here and align behavior with this doc: - [Arcade docs: Providing useful tool errors (Error adapters)](https://docs.arcade.dev/en/guides/create-tools/error-handling/useful-tool-errors#error-adapters) ## Quick Context - Adapter protocol: `arcade_tdk.error_adapters.base.ErrorAdapter` - Common error classes: - `arcade_tdk.errors.UpstreamError` — upstream responded with an HTTP status code - `arcade_tdk.errors.UpstreamRateLimitError` — 429 / quota-exhausted with `retry_after_ms` - `arcade_tdk.errors.NetworkTransportError` — no complete response was received (timeouts, connection/DNS/TLS failures, decoding errors, redirect exhaustion). `status_code` is always `None`; use one of the `NETWORK_TRANSPORT_RUNTIME_*` kinds: `_TIMEOUT`, `_UNREACHABLE`, `_UNMAPPED`. - `arcade_tdk.errors.FatalToolError` — unrecoverable tool-authoring bug or environment misconfiguration (invalid URL, unsupported protocol, bad headers, TLS trust failures). Never retried. - `arcade_tdk.errors.RetryableToolError` — transient tool-body failure with a hint for the LLM to retry. - `arcade_tdk.errors.ContextRequiredToolError` — needs human input before retry. ## Rules To Follow 1. Keep imports at top-level only (no inline imports), except optional dependency imports that must be lazy by design. 2. Adapter interface contract: - `slug` class a...