Land #226, #228, #235 and #239 together - #237
Merged
smaramwbc merged 12 commits intoAug 10, 2026
Merged
Conversation
Adds a detailed, reproducible benchmark writeup (scoreboard, methodology, run-it steps, scope, governance comparison, FAQ) run on mem0's own eval harness, plus the categorical chart palette and icon-only CodeCopyButton variant it needed.
Grounded product advisor + ops assistant use case: cited answers from retrieved evidence, citation validation against retrieved evidence, and ungrounded questions routed to a coverage-gap episode the content team resolves. - New GroundedShopAssistantPage with hero, why/how sections, ops console mockup, subjects table, API reference, and run instructions - Wires the route into App.tsx and seo-meta.ts - Registers the page in the use-case switcher/registry (use-case-pages.ts) - Adds the card to the UseCasesPage grid
Mem0 rewrote its OSS migration page on 2026-08-05 (mem0ai/mem0#6808), retitling the graph section from entity linking as the OSS successor to Platform-only graph memory, separate from entity matching. No code changed, only the label - but the page's claim was built on that label. - Table row (Graph / relationship memory): split OSS vs Platform behavior instead of naming entity linking as an OSS graph successor. - Footnote: replaced with claims checkable against deleted code, config surface, and response shape (graph_store config removed, relations field no longer returned, no graph payload in Platform responses) instead of Mem0's shifting terminology. Source: mem0ai/mem0 docs/migration/oss-v2-to-v3.mdx at 3f717e5.
Contributor
|
@jhuynh-devcups is attempting to deploy a commit to the Statewave Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… the closing CTA The "Diff the fork against upstream" button compared statewave-memory-benchmarks against itself. Extract UPSTREAM_DIFF_URL so it compares against mem0ai/memory-benchmarks, the repo it was forked from. Also brings the closing CTA in line with the site's cta-card treatment.
Each post now has its own on-brand banner + social card instead of sharing the site-wide default og-image.png — the original problem Kai-Uwe flagged (every post importing with the same generic image). - Adds headerImage (optional) alongside the existing image field in BlogPostFrontmatter — image feeds og:image/twitter:image/JSON-LD (already wired), headerImage is new: rendered inline inside the post's title card in BlogPostPage.tsx, which had no image slot before. - Images resized from the 2x/@retina source files (2-3.5MB each) down to their actual display size (1200x630 / 1600x640, ~500-650KB each) before committing, in line with the existing og-image.png's footprint. - public/images/blog/<slug>/{og,header}.png per post.
jhuynh-devcups
changed the title
jhuynh-devcups
changed the title
jhuynh-devcups
marked this pull request as ready for review
August 10, 2026 16:17
The reference build now lives at smaramwbc/statewave-grounded-shop-assistant (TypeScript). Link there instead of the original development location.
This was referenced Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lands four page and content PRs together, so they ship as one change instead of four sequential merges.
Merge this with a merge commit, not a squash. Every original commit is preserved with its own SHA, so a merge commit makes all four heads reachable from main and GitHub marks #226, #228, #235 and #239 as merged. A squash would create a new commit instead and leave the four showing as closed.
#228 does not build on its own - its
iconOnlyprop comes from #226's CodeCopyButton change - so the two can only land together or in that order.Conflicts between #226/#228 and #235 are already resolved here: the route and metadata additions in src/App.tsx and src/lib/seo-meta.ts keep both sides, with the two PAGE_META entries written out in full because they share a trailing property block; src/index.css takes #235's comment; and the two route tests in tests/routes.test.tsx are written as separate blocks because they share the same waitFor scaffolding. #239 needed no resolution.
Verified on this branch: typecheck, lint, and the production build pass, and the test suite is green at 324 passed.
Preview: https://statewave-web-git-fork-jhuynh-devcups-preview-4ab2f0-statewave.vercel.app
Pages:
/benchmarks,/use-cases/grounded-shop-assistant,/vs/mem0,/blog