[publish-mahdar-ar] move محضر اجتماع to live blog (auto-publish workflow no-op'd)

[Smetools]

PR #98 merged the محضر اجتماع draft but publish-blog-draft.yml logged "Nothing to commit" — the post never reached app/content/blog/, so the live URL would 404.

Cause: the "Find draft files" step runs git diff base.sha..head.sha but only fetches head.sha into its shallow checkout. base.sha is absent → diff errors → || true → zero drafts → publish skipped.

This PR: ran the canonical scripts/publish-draft.mjs → published file added, draft removed (rename R095). lang: ar / dir: rtl carried through for RTL.

Follow-up (separate): fix the workflow (fetch-depth: 0 or fetch base.sha) so future blog-draft merges auto-publish. Until then merges need this manual step.

Live on merge: https://knowcap.ai/blog/namuthaj-mahdar-ijtimaa-ar
🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
knowcap-landing	Building	Preview, Comment	Jun 28, 2026 2:46pm

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 10 minutes and 20 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 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c1e2bd75-2c55-46e7-99e8-c3218f20896c

📥 Commits

Reviewing files that changed from the base of the PR and between 4bc846e and 58eb75f.

📒 Files selected for processing (1)

• app/content/blog/namuthaj-mahdar-ijtimaa-ar.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hassan/publish-mahdar-ar

---

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