[codex] Refactor content loading and post metadata normalization

[big-mon]

Summary

• Add a shared content index/source layer for posts and notes in apps/astro-blog/src/lib/content.ts.
• Reuse the indexed slug -> source map for getPostBySlug() and getNoteBySlug() instead of scanning all Markdown files again.
• Reuse note index sources when rendering all notes, keeping pagination/filter helpers separate from source loading.
• Centralize post metadata normalization in packages/content-processor/src/processor.ts so processMarkdown() and extractMetadata() share the same date, tag, cover image, draft, and reading-time handling.

Impact

This keeps existing URLs and rendering behavior intact while reducing repeated source work and keeping post metadata interpretation consistent between list metadata and detail rendering.

Closes #201
Closes #202

Validation

• pnpm type-check
• pnpm --filter astro-blog build
• pnpm --filter @estrivault/content-processor build
• git diff --find-renames -- content/blog

[coderabbitai]

Warning

Review limit reached

@big-mon, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 48 minutes and 48 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 928fad55-3ce0-47d0-bd31-11fb82cd76bd

📥 Commits

Reviewing files that changed from the base of the PR and between c29c385 and f8b6dd3.

📒 Files selected for processing (2)

• apps/astro-blog/src/lib/content.ts
• packages/content-processor/src/processor.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/issue-201-content-loader

---

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 and usage tips.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	estrilda	f8b6dd3	Commit Preview URL Branch Preview URL	Jun 22 2026, 07:30 PM

[big-mon]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: f8b6dd3f55

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".