docs(tables): finish the v2 cutover's documentation trail

Regenerate the two artifacts the `ncontains` commit left stale: the tool
metadata bundle and the generated Table integration page both still published
the operator list without it, so `bun run tool-metadata:check` failed at HEAD.

Point the remaining docs previews at `table_v2`. `BLOCK_DISPLAY_WORKFLOWS`
already moved, but the two hand-written table example workflows and the
OutputBundle on the workflows guide still named the v1 type, so every table
example in the docs described the block the toolbar no longer yields. They
render identically today only because both types share an icon-map entry.

The workflows guide told readers the log shows "the filter and sort it sent";
v2 sends `order`.

Document the `sunset` step in the three skills that describe the v1 -> v2
cutover. All three stopped at `(Legacy)` + `hideFromToolbar`, but
`check-block-registry` fails a legacy block with no `replacedBy`, and the
amber badge and its click-to-upgrade action read from that field - following
the procedure verbatim produced a build failure. Also record the ordering
constraint this cutover hit: the v1 `sunset` edit and the v2 `preview` removal
must land together, since the check rejects a `replacedBy` that is still
preview.

Left alone: the academy video previews still show v1 labels. They mirror
recorded footage, so correcting the label without a re-record would only make
the still disagree with the video it claims to depict.

Author: mzxchandra

.agents/skills/add-block-preview/SKILL.md

@@ -41,7 +41,7 @@ A revealed block that is not globally GA (`enabled !== true`, or env-revealed) r
    - GA via config (code cleanup pending): `{ "enabled": true }` — suffix disappears everywhere within ~30s (AppConfig TTL) + client refetch.
 
    Same runbook as `feature-flags`: edit the hosted document, `aws appconfig start-deployment` with the `sim-<env>-fast` strategy (see the infra README).
-5. **GA cleanup:** delete `preview: true` from the block (now visible to self-hosters on their next upgrade), add its `BlockMeta` + regen docs, and drop the AppConfig entry. For a v2 upgrade, this is also when v1 gets `hideFromToolbar: true` (the superseded-version paradigm).
+5. **GA cleanup:** delete `preview: true` from the block (now visible to self-hosters on their next upgrade), add its `BlockMeta` + regen docs, and drop the AppConfig entry. For a v2 upgrade, this is also when v1 gets `hideFromToolbar: true` **and** `sunset: { status: 'legacy', replacedBy: '<v2-type>' }` (the superseded-version paradigm). Both edits must land in the **same commit** as the `preview: true` removal — `check-block-registry` fails a sunset block whose `replacedBy` is still `preview`, so splitting them breaks the build in between. Also move the block's `BLOCK_DISPLAY_WORKFLOWS` entry (`apps/docs/components/workflow-preview/block-display-workflows.ts`) to the new type, or `BlockPreview` silently renders nothing on the docs page.
 
 ## Kill switch (shipped blocks)
 

.agents/skills/add-block/SKILL.md

@@ -695,6 +695,10 @@ export const ServiceBlock: BlockConfig = {
   type: 'service',
   name: 'Service (Legacy)',
   hideFromToolbar: true,  // Hide from toolbar
+  // Required: drives the amber legacy badge and its click-to-upgrade action.
+  // `check-block-registry` fails a legacy block with no `replacedBy`, one whose
+  // target does not exist, or one whose target is itself sunset or still `preview`.
+  sunset: { status: 'legacy', replacedBy: 'service_v2' },
   // ... rest of config
 }
 

.agents/skills/add-integration/SKILL.md

@@ -598,7 +598,10 @@ If creating V2 versions (API-aligned outputs):
 
 1. **V2 Tools** - Add `_v2` suffix, version `2.0.0`, flat outputs
 2. **V2 Block** - Add `_v2` type, use `createVersionedToolSelector`
-3. **V1 Block** - Add `(Legacy)` to name, set `hideFromToolbar: true`
+3. **V1 Block** - Add `(Legacy)` to name, set `hideFromToolbar: true`, and add
+   `sunset: { status: 'legacy', replacedBy: '{service}_v2' }` — `check-block-registry`
+   fails a legacy block with no `replacedBy`, and the amber legacy badge plus its
+   click-to-upgrade action read from that field
 4. **Registry** - Register both versions
 
 ```typescript

apps/docs/components/workflow-preview/examples.ts

@@ -139,7 +139,7 @@ export const TABLE_ENRICH_WORKFLOW: PreviewWorkflow = {
     {
       id: 'table1',
       name: 'Table 1',
-      type: 'table',
+      type: 'table_v2',
       bgColor: '#10B981',
       position: { x: 0, y: 0 },
       hideTargetHandle: true,
@@ -162,7 +162,7 @@ export const TABLE_ENRICH_WORKFLOW: PreviewWorkflow = {
     {
       id: 'table2',
       name: 'Table 2',
-      type: 'table',
+      type: 'table_v2',
       bgColor: '#10B981',
       position: { x: 660, y: 0 },
       rows: [
@@ -1644,7 +1644,7 @@ export const TABLE_ROUNDTRIP_WORKFLOW: PreviewWorkflow = {
     {
       id: 'query',
       name: 'Table',
-      type: 'table',
+      type: 'table_v2',
       bgColor: '#10B981',
       position: { x: 0, y: 0 },
       hideTargetHandle: true,
@@ -1664,7 +1664,7 @@ export const TABLE_ROUNDTRIP_WORKFLOW: PreviewWorkflow = {
     {
       id: 'update',
       name: 'Table',
-      type: 'table',
+      type: 'table_v2',
       bgColor: '#10B981',
       position: { x: 680, y: 0 },
       rows: [

apps/docs/content/docs/integrations/table.mdx

@@ -204,7 +204,7 @@ Delete multiple rows that match filter criteria. Use with caution - supports opt
 
 ### Query Rows
 
-Query rows with a typed predicate filter and cursor pagination. A single filter can be a plain condition: `\{"field":"wins","op":"gte","value":10\}`. Use `all` (AND) or `any` (OR) groups for multiple or nested conditions. Operators: eq, ne, gt, gte, lt, lte, in, nin, like, ilike, nlike, nilike, contains, startsWith, endsWith, isNull, isNotNull, isEmpty, isNotEmpty. Order is a sort spec, e.g. `[\{"field":"wins","direction":"desc"\}]`. Omit limit to return the entire result — the query fails if it exceeds the 5MB budget (narrow with a filter or set a limit). With a limit, a page can end early at the byte budget: a non-null nextCursor means more rows exist — pass it back as cursor to continue; never infer completion from page size.
+Query rows with a typed predicate filter and cursor pagination. A single filter can be a plain condition: `\{"field":"wins","op":"gte","value":10\}`. Use `all` (AND) or `any` (OR) groups for multiple or nested conditions. Operators: eq, ne, gt, gte, lt, lte, in, nin, like, ilike, nlike, nilike, contains, ncontains, startsWith, endsWith, isNull, isNotNull, isEmpty, isNotEmpty. Order is a sort spec, e.g. `[\{"field":"wins","direction":"desc"\}]`. Omit limit to return the entire result — the query fails if it exceeds the 5MB budget (narrow with a filter or set a limit). With a limit, a page can end early at the byte budget: a non-null nextCursor means more rows exist — pass it back as cursor to continue; never infer completion from page size.
 
 #### Input
 

apps/docs/content/docs/tables/using-in-workflows.mdx

@@ -43,7 +43,7 @@ Later blocks read these by name: `<table1.rows>` is the array, `<table1.rowCount
 
 <OutputBundle
   blockName="table1"
-  blockType="table"
+  blockType="table_v2"
   blockColor="#10B981"
   duration="84ms"
   values={[
@@ -138,7 +138,7 @@ After the run, the table holds the enriched rows. The next run queries them agai
 
 ## Inspecting reads and writes
 
-Every Table block's input and output is recorded in [logs](/logs-debugging). For a Query block, the log shows the filter and sort it sent and the rows it received. For an Update or Insert, it shows the row data written and the count affected. When a write does nothing or a query comes back empty, the log is where you check the filter and the data shape before looking anywhere else.
+Every Table block's input and output is recorded in [logs](/logs-debugging). For a Query block, the log shows the filter and order it sent and the rows it received. For an Update or Insert, it shows the row data written and the count affected. When a write does nothing or a query comes back empty, the log is where you check the filter and the data shape before looking anywhere else.
 
 ## Next