docs: refresh protected-main documentation fitness

[seonghobae]

Why

Protected main advanced materially beyond the prior documentation-fitness matrix. The old matrix still described the canonical documentation baseline, multilevel contracts, factor retention, item-bank lifecycle and other integrated work as open-PR-only or planned, which violated the repository's protected-main-vs-active-PR maturity discipline.

What

• separates documentation-family availability from capability maturity with finite explicit vocabularies;
• refreshes protected-main truth for integrated RAG request/provenance, post-pilot item-bank lifecycle, multilevel contracts, factor-retention evidence, paired rating-range evidence, fixed-anchor linking, documentation contracts, ADR-0013 governance, and now the merged observed-information/second-order Rust ownership slice refactor(inference): own observed information and second-order tests in Rust #758;
• keeps current JMLE optimizer work and fail-first parallel-analysis control/resource hardening explicitly active-PR rather than shipped;
• records active security/accessibility/caller lanes without promoting them to protected-main behavior;
• records remaining P0/P1 documentation-fitness gaps around API/version/fingerprint contracts, UML/ERD completeness, operability/recovery, security/data governance, release/rollback/provenance/licensing indexing, and root-authority consistency;
• adds focused regressions preventing the old open-PR-only documentation narrative and active-PR maturity promotion from returning.

Boundary

Documentation + documentation-contract regression only. No numerical formula, public runtime API, dependency, workflow authority, physical DB schema, release version, or provider/reviewer credential changes.

Current source head is documentation-only and remains Draft. Keep it Draft until exact-head documentation/full applicable CI and current-head review are green. Documentation completion is not product completion; active implementation lanes retain their own exact-head evidence and writer leases.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 11 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6c867a58-41a5-46d3-9ef1-488f43637c47

📥 Commits

Reviewing files that changed from the base of the PR and between 607e3f2 and dc5f70a.

📒 Files selected for processing (2)

• docs/documentation_coverage.md
• tests/test_documentation_coverage_fitness.py

---

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