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(cayenne): a local cayenne_file_path moves the default metastore directory in versioned docs

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(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(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.

Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

docs(turso): indexes are supported under MVCC since v2.0.0