chore(docs): upgrade Blume to 1.1.0

[SutuSebastian]

Summary

• Bump apps/docs from Blume 1.0.4 → 1.1.0 (lockfile + clear .blume caches validated).
• Wire native search.popular from existing CURATED_POPULAR (custom Search/404 kept).
• Add post-build docs:audit to CI; skip Blume 1.1.0 basePath canonical false-positives and oversized typedoc Lit API HTML.

Test plan

• bun run docs:validate -- --strict
• bun run docs:check -- --isolated
• bun run docs:build (after docs:api / packages built)
• bun run docs:audit (exits 0 with documented skips)
• Smoke: no dist/**/_home/** routes; sitemap/llms.txt under /layers; changelog + _headers present

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2e0e80f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 18 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7a788318-dd88-451e-bf6f-e41432840c29

📥 Commits

Reviewing files that changed from the base of the PR and between 9d804c2 and 2e0e80f.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• .agents/lessons.md
• .github/workflows/ci.yml
• apps/docs/blume.config.ts
• apps/docs/package.json
• apps/docs/pages/index.astro
• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch blume/1.1.0

---

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.}