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>

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(embeddings): the chunk offset column is <column>_offset, not _offsets (#2170) Every page that documents bring-your-own chunked embeddings named the required offset column '<column_name>_offsets'. The runtime looks for '<column>_offset': offset_col! in runtime-search generates '{col}_offset', ChunkedSearchIndex ::chunking_offset_col formats the same, and base_col strips '_offset'. The consequence is silent. EmbeddingTable::base_table_has_embedding_column looks the column up by that exact name and, unlike the two neighbouring early-returns, logs nothing when it is missing - it just returns false, so the column is not treated as precomputed and Spice re-embeds it from scratch. A user who followed the docs pays for embeddings they already had and gets no diagnostic explaining why. The vector-search page already contradicted itself: its 'describe sales' example for the chunked case shows 'address_offset', matching the code, one section below the constraint that asked for '_offsets'. Swept all 11 doc sets and all three page types that carry the claim.

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(embeddings): the chunk offset column is <column>_offset, not _offsets (#2170) Every page that documents bring-your-own chunked embeddings named the required offset column '<column_name>_offsets'. The runtime looks for '<column>_offset': offset_col! in runtime-search generates '{col}_offset', ChunkedSearchIndex ::chunking_offset_col formats the same, and base_col strips '_offset'. The consequence is silent. EmbeddingTable::base_table_has_embedding_column looks the column up by that exact name and, unlike the two neighbouring early-returns, logs nothing when it is missing - it just returns false, so the column is not treated as precomputed and Spice re-embeds it from scratch. A user who followed the docs pays for embeddings they already had and gets no diagnostic explaining why. The vector-search page already contradicted itself: its 'describe sales' example for the chunked case shows 'address_offset', matching the code, one section below the constraint that asked for '_offsets'. Swept all 11 doc sets and all three page types that carry the claim.