docs: correct data workflows, SQL and operations (#4534)

This PR is part of the documentation revamp. Once the full set of PRs is
merged, we’ll publish the combined site to staging for review before
updating docs.lancedb.com.

The curation, SQL and operations pages contain outdated claims and
examples that do not reliably work as written.

This corrects those pages against the reviewed SDK and local server
evidence, including prepared statements, background jobs, cleanup and
monitoring. Integration guides are grouped with their examples in #4533.

Function and Secret-object documentation stays unpublished until its
release. The two Function pages are listed in `.mintignore` and left out
of the navigation, and the sections about them on other pages are MDX
comments.

Stacked on #4533. Each MDX file has one PR owner. Rebase onto main after
#4533 is squash-merged.

Local assembly, Mint validation and link checks pass, and the assembled
site shows no Function or Secret-object content. A local release
rehearsal that uncomments the drafts and restores the navigation also
passes. Hold publication until this PR and lancedb/sophon#8688 are on
`main`.

docs/web/sql/dml/copy.mdx

@@ -6,7 +6,11 @@ icon: file-export
 keywords: ["copy", "export", "parquet", "sql"]
 ---
 
-<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
+<Warning>
+Recent deployment versions refuse `COPY` over the SQL endpoint with "COPY is not
+supported". On those, export a result by reading it through a Flight SQL client
+or an SDK and writing the files from your application.
+</Warning>
 
 ```sql
 COPY (SELECT id, title FROM documents) TO 's3://bucket/export/' STORED AS PARQUET

docs/web/sql/dml/delete.mdx

@@ -6,12 +6,16 @@ icon: trash
 keywords: ["delete", "sql"]
 ---
 
-<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
+<Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
 ```sql
-DELETE FROM documents WHERE created_at < '2025-01-01'
+DELETE FROM documents WHERE created_at < TIMESTAMP '2025-01-01 00:00:00'
 ```
 
+Compare a timestamp column with a typed literal, as above, or with
+`CAST('2025-01-01' AS TIMESTAMP)`. A bare string such as `'2025-01-01'` is
+rejected in a `DELETE` predicate, even though a `SELECT` accepts it.
+
 Deletion marks rows rather than erasing them, so the data remains recoverable
 for as long as the version holding it survives
 [retention](/maintenance/cleanup).

docs/web/sql/dml/insert.mdx

@@ -6,7 +6,7 @@ icon: plus
 keywords: ["insert", "insert into", "sql"]
 ---
 
-<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
+<Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
 ```sql
 INSERT INTO documents (id, title) VALUES (1, 'Merlin'), (2, 'Arthur')

docs/web/sql/dml/refresh.mdx

@@ -6,7 +6,7 @@ icon: arrows-rotate
 keywords: ["refresh column", "refresh materialized view", "backfill", "cascade"]
 ---
 
-<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
+<Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
 LanceDB extensions with no DataFusion equivalent. They are what makes
 [feature engineering](/feature-engineering) reachable from SQL: a column
@@ -52,33 +52,35 @@ REFRESH COLUMN embedding ON documents
 `num_workers` sets a count; the budget options size each worker. They are
 alternatives rather than a pair.
 
+{/*
+Draft for the Functions release.
+
 <Note>
 `error_policy` and `num_workers` are refused for a column filled by a registered
 [function](/management/function) with its own resource budget -- use the CPU,
 memory and GPU options there.
 </Note>
+*/}
 
 ## REFRESH MATERIALIZED VIEW {#refresh-materialized-view}
 
 ```sql
-REFRESH MATERIALIZED VIEW <name> [CASCADE] [WITH (<option> = <value>)]
+REFRESH MATERIALIZED VIEW <name>
 ```
 
 ```sql
 REFRESH MATERIALIZED VIEW chunks
-REFRESH MATERIALIZED VIEW chunks WITH (full = true)
 ```
 
-`full = true` asks for every row to be recomputed. Without it, whether a
-refresh rebuilds the whole view -- as every local SDK refresh does -- or
-reconciles only what changed in the source depends on the deployment's LanceDB
-Enterprise version and configuration.
+A refresh updates the view's stored result. Refresh views in dependency order,
+starting with their source views.
 
-<Warning>
-`CASCADE` asks for the views this one is built on to be refreshed first, in
-dependency order. Whether a deployment carries it out depends on its version;
-where it does not, refresh each view yourself, its sources first.
-</Warning>
+<Note>
+Some older server versions accepted `WITH (full = true)` and `CASCADE`.
+Those options are not accepted by the SQL implementation described here.
+Use the basic statement above; do not assume that the options accepted by a
+local SDK's `refresh()` method are also SQL options.
+</Note>
 
 ## Watching a refresh {#watching}
 

docs/web/sql/dml/update.mdx

@@ -6,7 +6,7 @@ icon: pen
 keywords: ["update", "sql"]
 ---
 
-<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
+<Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
 ```sql
 UPDATE documents SET title = upper(title) WHERE category = 'film'