demo: Add benchmark-react with normalization and ref-stability scenar…

…ios (#3783)

* demo: Add benchmark-react with normalization and ref-stability scenarios

- Browser benchmark comparing @data-client/react (Playwright, customSmallerIsBetter).
- Scenarios: mount, update entity/author, ref-stability (item/author ref counts).
- Hot-path (CI) vs with-network (local): simulated delay for overfetch comparison.
- CI workflow runs hot-path only; reports to rhysd/github-action-benchmark.

Made-with: Cursor

* more of the plan

* More scenarios

* more scenarios

* add react compiler option

* bugbot: dead code

* No throttling

* yarn lock

* bugbot + fix test data client correctness

* fair comparisons

* ts 6

* bugbot

* update website types

* improve ci

* internal: Bench runs concurrently

* better abstractions

* CRUD

* virtualize

* create adds to list; larger high end case

* No seeding

fix yarn lock

* fix test conditions to be more accurate

* dynamic accuracy

* fix bench measurements

* remove unneeded bench

* fix measurement by eliminating paint timings from measurement

* increase scale, remove redundant

* bench name updates

* more realistic data

* MutationObserver timeout silently fails without signaling completion

* Make sorted mount consistent

* fix sorted-view-update-entity for some frameworks

* change reporting

* move scenario

* Init scenarios capture wrong react-commit-update measurement

* Upgrade benchmark baseline from dual list to triple list

Made-with: Cursor

* bugbot

* server sim

* Make author component more expensive

* network sim flag; new scenario

* bugbot

* DRY

* Potential fix for code scanning alert no. 83: DOM text reinterpreted as HTML

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* delete dead code

* movewith docs

* review

* switch to github data

---------

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

demo: Add benchmark-react with normalization and ref-stability scenar…

…ios (#3783)

* demo: Add benchmark-react with normalization and ref-stability scenarios

- Browser benchmark comparing @data-client/react (Playwright, customSmallerIsBetter).
- Scenarios: mount, update entity/author, ref-stability (item/author ref counts).
- Hot-path (CI) vs with-network (local): simulated delay for overfetch comparison.
- CI workflow runs hot-path only; reports to rhysd/github-action-benchmark.

Made-with: Cursor

* more of the plan

* More scenarios

* more scenarios

* add react compiler option

* bugbot: dead code

* No throttling

* yarn lock

* bugbot + fix test data client correctness

* fair comparisons

* ts 6

* bugbot

* update website types

* improve ci

* internal: Bench runs concurrently

* better abstractions

* CRUD

* virtualize

* create adds to list; larger high end case

* No seeding

fix yarn lock

* fix test conditions to be more accurate

* dynamic accuracy

* fix bench measurements

* remove unneeded bench

* fix measurement by eliminating paint timings from measurement

* increase scale, remove redundant

* bench name updates

* more realistic data

* MutationObserver timeout silently fails without signaling completion

* Make sorted mount consistent

* fix sorted-view-update-entity for some frameworks

* change reporting

* move scenario

* Init scenarios capture wrong react-commit-update measurement

* Upgrade benchmark baseline from dual list to triple list

Made-with: Cursor

* bugbot

* server sim

* Make author component more expensive

* network sim flag; new scenario

* bugbot

* DRY

* Potential fix for code scanning alert no. 83: DOM text reinterpreted as HTML

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* delete dead code

* movewith docs

* review

* switch to github data

---------

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor

internal(fix): GitHub releases not created on publish (#3779)

The `if: steps.changesets.outputs.published == 'true'` condition was
never satisfied because changesets/action cannot detect publications
from the custom `yarn workspaces foreach ... npm publish` command.

Revert to self-scanning approach that checks each package's version
against existing GitHub releases (idempotent on every push).

Made-with: Cursor