feat(dashboard): restore primitives grid, comparison table, API surface

[duyet]

Summary

PR #339 (shadcn redesign) rebuilt the landing page on the landing-page11 structure and dropped three content blocks that weren't preserved anywhere else. All three were recovered from ce9a1fa^:packages/dashboard/src/pages/index.astro (the pre-#339 tree) and restyled for the current shadcn token system rather than pasted back verbatim.

Closes #354

Where each block landed, and why

• Five-primitives grid (state, lease, claim, token, conversation) → landing page, new section right after the hero. This is core product identity, not supplementary content — the current feature grid had quietly stopped mentioning three of the five primitives (state, lease, claim never appear at all), even though they're still live in the API (see permissionScopes in docs.astro: state:read, state:write, lease:write, claim:write). Restyled with bg-card / border-border / hover:bg-muted to match the PR feat(dashboard): shadcn/ui redesign — landing page, dashboard spacing, chat components #339 system; kept --color-accent for the CTA link per the "accent is brand vermilion, not shadcn hover" rule.
• Memory-vs-AgentState comparison table → new /compare page. This is "why choose us" content that doesn't fit the trimmed shadcnblocks landing structure, but is valuable enough to deserve a permanent, linkable home rather than being buried. Linked from the header nav, footer "Product" list, and a callout in the new primitives section ("Why not just memory? → Compare").
• API-surface endpoint table → docs.astro, new "API surface" section in the Reference group (before Conversations). This is developer reference material, so it belongs in the docs where people already look for endpoint tables. Reuses the existing methodColor() helper and <ul>/<li> endpoint-list pattern already used by the Conversations/Analytics sections in that file, rather than reintroducing the old <table> markup — docs.astro wasn't touched by feat(dashboard): shadcn/ui redesign — landing page, dashboard spacing, chat components #339 and still uses the pre-shadcn token names (fg, edge, panel), so the new section matches that file's existing conventions instead of mixing token systems within one file.

Not in scope: the dropped 6th "Workers AI Durable Object" code-tab example mentioned in the issue as context — the issue's actual "Fix:" only calls out the three content blocks, and re-adding a 6th CodeTabs example is a separate, larger change (needs its own copy review). Flagging it here in case it should be a follow-up.

Test plan

• bunx biome check packages/dashboard/src/ — clean (pre-existing single-file-check false positives on MarketingLayout.astro/brand.astro confirmed present on main too, not introduced by this change)
• bunx astro check --minimumSeverity error — 0 errors across 201 files
• Manually reviewed recovered content maps 1:1 to the pre-feat(dashboard): shadcn/ui redesign — landing page, dashboard spacing, chat components #339 source, restyled (no copy/data dropped)

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[sourcery-ai]

Sorry @duyet, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Warning

Review limit reached

@duyet, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8fa67013-18c4-437e-9b6a-5ce7a75748e5

📥 Commits

Reviewing files that changed from the base of the PR and between 5e6abe4 and b2b417b.

📒 Files selected for processing (4)

• packages/dashboard/src/layouts/MarketingLayout.astro
• packages/dashboard/src/pages/compare.astro
• packages/dashboard/src/pages/docs.astro
• packages/dashboard/src/pages/index.astro

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/w13-landing-content

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}