Add SocialNetwork-React experimental workload

suites-experimental/social-network/.gitignore

@@ -0,0 +1,19 @@
+node_modules
+
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+pnpm-debug.log*
+
+# dist-ssr / local
+dist-ssr
+*.local
+
+# Editor directories and files
+.vscode/*
+!.vscode/extensions.json
+.idea
+.DS_Store
+*.sw?

suites-experimental/social-network/README.md

@@ -0,0 +1,94 @@
+## Description
+
+Social feeds are among the most used pages on the web. A reader scrolls a long,
+virtualized list of rich stories, opens one to read its comments, types a reply,
+visits a profile and goes back, and searches, all on a page that also runs a
+lot of instrumentation: every callback is wrapped, every interaction is timed,
+and a steady stream of analytics events is batched, compressed and sent.
+
+This workload is an original, self-contained React 19 app built to reproduce
+that mix. It was modeled on the kind of work a large production feed does,
+measured from the outside with performance traces, and is **not** derived from
+any existing product's source code. It ships no third-party assets: all names,
+text and pictures are generated or written for it.
+
+## What are we testing
+
+-   React reconciliation of deep, many-component stories, mounting and
+    unmounting as a virtualized feed scrolls, with layout effects that measure
+    each unit. Stories, comment threads, the post dialog and the menus are sized
+    after a large production feed: a few hundred elements per story, and a
+    dialog that grows from about a thousand to about four thousand elements
+-   A normalized client cache fed by streamed, chunked responses with deferred
+    fragments. Components read it through fragments: each declares the fields
+    it renders and receives masked references for its children, every publish
+    re-reads the subscriptions that touched a changed record and keeps the
+    identity of unchanged data, and released queries are garbage collected
+-   A design-system layer: every box, text run, link, image and control is a
+    component that reads theme, logging surface and route from context, keeps
+    its own interaction state, and registers with interaction and
+    visual-completion trackers, so a page runs about two hooks per element
+-   A home page kept mounted inside `<Activity>` while the profile is shown, so
+    leaving it tears down its effects and returning reconnects them, re-checks
+    its cached data and restores its scroll position
+-   Component and event interception through the app's JSX runtime: every
+    component render is tracked and every event handler is wrapped, so an
+    interaction can be attributed to the component that rendered it
+-   ICU-style message formatting (plurals, selects, numbers) for every UI
+    string, at render time
+-   A typo-tolerant typeahead index over a large bootstrap payload: prefix
+    lookup over sorted terms, bounded edit distance, and ranking by rarity,
+    match quality and affinity
+-   A modal layer that makes the page underneath inert while it is open, and
+    comment drafts that outlive the dialog and show up in the feed
+-   Transitions for page navigation, and synchronous scroll-driven updates
+    (`flushSync`) for the feed window
+-   Forced layout from viewability checks (`getBoundingClientRect`,
+    `elementFromPoint`), auto-growing text areas and scroll-depth tracking
+-   Analytics work: error-guard wrappers, event enrichment, sampling, batching,
+    LZW compression and checksums, User Timing marks and feature-gate exposures
+-   Many small atomic CSS classes per element (Tailwind), masked SVG avatars
+    and generated SVG photos
+
+## How are we testing
+
+All content is generated deterministically at load time from fixed seeds (no
+`Math.random`, no `Date.now`). An in-page server answers each query with
+GraphQL-shaped JSON split into chunks, delivered one task apiece through a
+`MessageChannel`, so every iteration renders identical data without a network.
+
+The app fires a window event when the result of an interaction has committed
+(`feed-page-loaded`, `post-dialog-ready`, `search-results`, …), and the steps
+wait on those instead of on timers.
+
+-   `RefreshHomeFeed`: clicks Home while on the home page, which refetches the
+    stories tray, rails and badges, fetches a new ranking and remounts the feed.
+-   `LoadMoreStories`: reads down the feed one story at a time, loading the next
+    page whenever the end comes into range.
+-   `ExpandStoryTexts`: scrolls back to the top, expanding every truncated story.
+-   `OpenPostDialog`: opens a busy thread in the post dialog.
+-   `ExpandCommentReplies`: expands every reply thread on the first page,
+    following "more replies" until each thread is fully shown.
+-   `ChangeCommentOrder`: switches the comment order to "All comments".
+-   `LoadMoreComments`: scrolls the dialog to load more pages of comments.
+-   `TypeComment`: types a comment key by key, with a mention typeahead,
+    emoticon replacement and highlighting.
+-   `VisitOwnProfile`: closes the dialog, which saves the draft and hands the
+    feed back its focus and viewability, navigates to the viewer's profile and
+    scrolls through it, then returns to the home feed, which stays mounted while
+    hidden and comes back at its old position.
+-   `SearchTypeahead`: types a name into search; each key filters the local
+    index and asks the server.
+-   `OpenHeaderMenus`: opens and closes the menu, chats, notifications and
+    account popovers.
+
+## Developer Documentation
+
+The app was created with Vite + React 19 and Tailwind CSS. It can be previewed
+during development with `npm run dev`. To update the files run in the harness
+you have to run `npm run build`, which regenerates the committed `dist/`
+directory.
+
+The built workload can be loaded within the harness at e.g.
+`http://localhost:8080/?developerMode&suites=SocialNetwork-React`, or directly at
+`http://localhost:8080/suites-experimental/social-network/dist/index.html`.