feat: add Week 2 claim-check blog post with interactive React components

[Bueller87]

What changed?

New blog post: Bypass the 2 MB Limit Without Shrinking Your Workflow — Week 2 of the DataConverter series (blog/2026-06-10-claim-check-pattern/). MDX post with four embedded React components:

Component	Section	Purpose
PayloadFlowDemo	How it works	Animated encode/decode particle flow; large dot shrinks at Blob Store before a tiny ref travels to History
SizeChart	Threshold tuning	Scroll-triggered bar chart — inline vs claim-check payload sizes across five examples
BlobStoreTabs	Blob store options	Tabs for Local FS / S3 / GCS / Azure with Go + Java init snippets
FootgunCards	Common production pitfalls	Five expandable cards (UUID keys, TTL mismatch, outage, prefix schema, credentials) with cause + fix

Why?

Continues the DataConverter series (Week 1: #352). The claim-check pattern and its production gotchas aren't covered in the concept doc. This post fills that gap with enough depth for engineers to implement it safely.

How did you verify it?

• Ran production preview (npm run preview:github-pages -- --serve)
• Checked dark mode and light mode on affected pages

Potential risks

• New MDX post with React components. No changes to existing docs, config, or sidebar
• No new internal or external links beyond existing sample repo URLs already used in the series

Related changes

• Week 1 post: docs(blog): Your Workflow History Is Storing More Than You Think #352
• DataConverter concept doc: /docs/concepts/data-converter

[gitar-bot]

Code Review ✅ Approved

Adds a comprehensive blog post on the claim-check pattern featuring four interactive React components for explaining payload handling and production pitfalls. No issues found.

Rules ✅ All requirements met

Repository Rules

✅ Markdown Frontmatter Completeness: The blog post contains valid YAML frontmatter with all required keys (title, description, keywords, date, authors, tags) correctly populated.

✅ PR Description Quality Standards: The PR description includes all required sections with substantive content, follows the template guidance, and explicitly addresses production preview and dark/light mode verification for the included non-text (MDX/React) changes.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}