docs(task_history): the acceleration refresh task is acceleration_refresh Eighteen deployment guides (and their 2.0.x-2.3.x snapshots) told readers to correlate object reads and accelerator spans with a task named accelerated_table_refresh. No release has ever recorded that name: the refresh span is declared as "acceleration_refresh" in the accelerated-table refresh task, and the task column is the span name unless a task_override label is present. The name a reader pastes into a task_history query has to match exactly, so a fabricated one returns no rows. cli/reference/trace.md already carried the correct name on these same snapshots.

docs(github): the connector has its own concurrency limiter, not the shared HTTP rate control (#2161) * docs(github): the connector has its own concurrency limiter, not the shared HTTP rate control The GitHub connector's `max_concurrent_requests` row was copy-pasted from the shared HTTP rate-control description used by the HTTP/HTTPS and GraphQL connectors. GitHub does not participate in that family: it declares its own `ParameterSpec::runtime("max_concurrent_requests")`, and connector-github does not even depend on the data-http-rate-control crate. - `runtime.params.http_max_concurrent_requests` is never read by GitHub. - Concurrency limiting is never disabled: a semaphore is always installed, at the connector default of 10 when nothing is configured. - The fallback chain is runtime.source_rate_control.github_concurrent_connections_limit, then the deprecated runtime.params.github_max_concurrent_connections, then 10. - The scope is the authentication context (token / GitHub App installation), not the upstream origin. Also corrects reference/spicepod/runtime.md, which listed GitHub as an HTTP-rate-control consumer and omitted Databricks, which is one. * docs(github): name Databricks alongside HTTP/HTTPS and GraphQL in the shared rate-control family Copilot review: connector-databricks also calls http_rate_control::resolve_config_for_component and declares max_concurrent_requests / requests_per_second_limit / requests_per_minute_limit / rate_control_jitter_{min,max}, so omitting it from the cross-reference was inconsistent with the reference/spicepod/runtime.md list this same PR corrects. --------- Co-authored-by: claudespice <claudespice@users.noreply.github.com>