docs(components): react-page scope comment says ObjectGrid, not the unregistered ObjectTable

The `kind:'react'` page header comment advertised two identifiers that do
not exist, so an author following it hit a wall either way:

  - `<ObjectTable>` -> ReferenceError, surfaced as the red "React page error"
    panel. `buildComponentScope` PascalCases each public non-container tag
    from the curated PUBLIC_BLOCKS contract, which carries `object-grid`
    (registered in plugin-grid) and no `object-table` at all, so the real
    injected identifier has always been `ObjectGrid`.
  - `<Block type="object-table" />` -> "Unknown component type", since
    nothing registers that type anywhere in the product.

`object-table` survives only in sdui-parser's synthetic compiler fixtures,
which build their own inline manifests and never touch the real registry.

Comment-only; no behavior change.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: os-zhuang

packages/components/src/renderers/layout/react-page.tsx

@@ -19,11 +19,11 @@
  *
  * Scope injected into the source:
  *   - `React`                — so authors can call hooks.
- *   - the PUBLIC data blocks — `<ObjectTable>`, `<ObjectForm>`, charts, metrics…
+ *   - the PUBLIC data blocks — `<ObjectGrid>`, `<ObjectForm>`, charts, metrics…
  *     each as a prop-driven wrapper that renders via SchemaRenderer. Layout is
  *     left to plain HTML + Tailwind (React's strength); only the data blocks
  *     that can't be expressed in HTML are injected.
- *   - `Block`                — escape hatch: `<Block type="object-table" .../>`.
+ *   - `Block`                — escape hatch: `<Block type="object-grid" .../>`.
  *   - `useAdapter`            — live data hook: query/create/update objects.
  *   - `data` / `variables`   — page data + local variables, for convenience.
  */