Check in versioned docs and remove generate-versions script (#1386) * Check in versioned docs and remove generate-versions script Transition from per-branch versioning to all versions checked in. Generated versioned docs from release branches 1.5 through 1.11. Removed generate-versions.sh and updated .gitignore. * Remove generate-versions script from build workflow Versioned docs are now checked in directly. Remove the script invocation from package.json build, drop the fetch-depth: 0 from CI (no longer needed), and update README to reflect the new process.

Improve documentation formatting for clarity and consistency (#1389) * Refine documentation across various sections for clarity and consistency - Updated descriptions in datasets, models, runtime, and views documentation to enhance readability and precision. - Improved explanations regarding retry mechanisms and refresh attempts in acceleration settings. - Clarified the purpose and functionality of the `WITH` clause in SQL documentation. - Enhanced troubleshooting guidance with detailed common issues and solutions for dataset loading, query performance, and AI chat results. - Revised use case descriptions for agentic apps, edge AI, federated MCP server, object-store AI engine, and more to improve clarity and impact. - Streamlined language throughout the documentation to ensure consistency and better user understanding. * Improve documentation formatting for clarity and consistency across multiple sections * Apply suggestion from @lukekim * Update documentation links for consistency and clarity across multiple sections

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.