feat: make edbs_meeting public with a board-meetings rewrite base

[pattonwebz]

Summary

• edbs_meeting now defaults to public => true with rewrite => ['slug' => 'board-meetings'] — a real single-page permalink, and the exact get_post_types(['public' => true]) check third-party plugins like ArchiveWP use to build their archivable-post-types list (GH#25 / PRO-1209), no longer requiring a site to opt in via edbs_cpt_args
• has_archive stays false — no generated archive listing; meetings are still meant to be browsed via the [edbs_boardscribe] shortcode's own REST-backed table
• edbs_cpt_args remains fully available to disable public/rewrite back to false, change the rewrite slug, or enable a real archive page
• Enables equalizedigital/boardscribe-pro#29's document-permalink nesting (a linked agenda/minutes document's URL nests under its meeting's slug) — that PR's DocumentCPT mirrors whatever this CPT's rewrite resolves to, so it was previously inert with today's paused default

Test plan

• composer lint, composer check-cs pass
• Updated BoardScribeCptTest: new defaults, the ArchiveWP-shaped regression check, and edbs_cpt_args filter coverage in all directions (disable public, enable archive, change the rewrite slug)
• composer test (PHPUnit) — not run in this environment
• Manual smoke test: visit a published meeting's permalink and confirm no fatal (theme's generic single template, since this CPT only supports title)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 11 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: CHILL

Plan: Pro

Run ID: c4d51360-d728-4ea1-96b1-70e2f6c18631

📥 Commits

Reviewing files that changed from the base of the PR and between 7a65082 and fe03213.

📒 Files selected for processing (3)

• CLAUDE.md
• includes/PostType/BoardScribeCPT.php
• tests/phpunit/BoardScribeCptTest.php

---

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