docs(spec): state the pagination row bound as true before and after the per-kind limit retirement

The changeset, the form comment and the pin's docblock said
`pagination.pageSize` is a view's only row bound. The kanban, gallery and
timeline configs still declare a per-kind `limit` until its retirement
lands, so all three now say only that `pagination.pageSize` is the row
bound every view type carries. Wording only; no form entry, test logic,
bundle or translation moves.

Claude-Session: https://claude.ai/code/session_013RDBh5DqXd2xnLwvHLgLFr
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/19814-view-form-pagination-all-kinds.md

@@ -5,6 +5,6 @@
 
 The Studio view form (`viewForm`, served by `METADATA_FORM_REGISTRY.view`) now offers `pagination` for every view type, not only grids.
 
-`pagination.pageSize` is the one row bound a view carries; for a kanban, gallery or timeline view it is the only one. The form used to place `pagination` inside the grid-only `Table options` section (shown when `type` is `grid` or unset), so an author editing any other view type could not see or set it without editing the metadata by hand. It now has its own collapsed `Pagination` section with no visibility condition. `Table options` keeps `resizable`, `compactToolbar`, `rowHeight` and `selection`, still for grids only.
+`pagination.pageSize` is the row bound every view type carries. The form used to place `pagination` inside the grid-only `Table options` section (shown when `type` is `grid` or unset), so an author editing any other view type could not see or set it without editing the metadata by hand. It now has its own collapsed `Pagination` section with no visibility condition. `Table options` keeps `resizable`, `compactToolbar`, `rowHeight` and `selection`, still for grids only.
 
 No schema changed: every view type already accepted `pagination`. `@objectstack/platform-objects` ships the new section's label and description in its metadata-form translation bundles (en, zh-CN, ja-JP, es-ES).

packages/spec/src/ui/view-form-pagination.test.ts

@@ -6,9 +6,9 @@
  *
  * ## What is being pinned
  *
- * Maintainer ruling D on #19228: a view carries one row bound,
- * `pagination.pageSize`. For a kanban, gallery or timeline view it is the only
- * one. The form used to offer `pagination` only inside `table_options`
+ * `pagination.pageSize` is the row bound every view type carries; maintainer
+ * ruling D on #19228 makes it the direction for a view's row bound. The form
+ * used to offer `pagination` only inside `table_options`
  * (`visibleWhen: "data.type == 'grid' || data.type == null"`), so an author
  * editing any other view type could not see or set that bound short of editing
  * the metadata by hand. Two halves, both asserted:

packages/spec/src/ui/view.form.ts

@@ -61,10 +61,10 @@ export const viewForm = defineForm({
       ],
     },
     // `pagination` is NOT grid-only: every view type accepts it, and
-    // `pagination.pageSize` is the one row bound a view carries (maintainer
-    // ruling D on #19228) — for a kanban, gallery or timeline view the only
-    // one. Its own section with no `visibleWhen` puts it in front of every
-    // type; inside `table_options` a non-grid author could not reach it.
+    // `pagination.pageSize` is the row bound every view type carries (maintainer
+    // ruling D on #19228 makes it the direction for a view's row bound). Its own
+    // section with no `visibleWhen` puts it in front of every type; inside
+    // `table_options` a non-grid author could not reach it.
     {
       name: 'pagination',
       label: 'Pagination',