docs(rfc): record RFC0041.5 deferral closed — matrix + typed sums landed

[jensholdgaard]

Summary

Closes the loop on RFC 0041's last open criterion: v0.6.0 shipped typed columns, and both plugin repositories completed the RFC0041.5 matrix the same day (ourios-perses-plugin#9, ourios-grafana-datasource#4) — declared-minimum 0.5.0 alongside latest, wire-level typed sums with null-stays-null, leg-aware RFC0002.21 severity expectations. New §9.3 verification record; banner updated. Also notes #664 (found while validating the release against the envykube consumer).

mdbook build clean; docs-only.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Qtny6z6cA74xPZa4qRhk4F

Summary by CodeRabbit

• Documentation
  • Updated RFC 0041 acceptance and verification status to reflect completion of previously deferred data-source capabilities.
  • Documented v0.6.0 validation across supported image versions, including typed-column behavior and severity-floor differences.
  • Clarified the status of the Grafana data-source follow-up and recorded a related consumer issue observed during testing.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 52 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 Plus

Run ID: a4fbcdbf-bb1c-4367-89f3-59ccb9cfcde8

📥 Commits

Reviewing files that changed from the base of the PR and between b1c08bd and 5538a35.

📒 Files selected for processing (1)

• docs/rfcs/0041-dashboard-datasource-plugins.md

📝 Walkthrough

Walkthrough

RFC 0041’s status and verification text now records RFC0041.5 completion with v0.6.0, including typed-column validation, plugin compatibility results, severity-floor differences, and the related envykube incident.

Changes

RFC 0041 status and verification

Layer / File(s)	Summary
Acceptance status and completion record docs/rfcs/0041-dashboard-datasource-plugins.md	The RFC records RFC0041.5 completion with v0.6.0, updates its verification narrative, and documents the minimum/latest matrix, typed-column behavior, severity-floor expectations, and envykube incident.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• jensholdgaard/ourios#640: Drafted the same RFC document later updated here.
• jensholdgaard/ourios#643: Updated roadmap status for RFC 0041.
• jensholdgaard/ourios#661: Overlapped with RFC 0041 verification and v0.6.0 validation details.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The summary is solid, but the required Related and Checklist sections are missing, so it does not follow the repository template.	Add the Related section with RFC/issue links and complete the Checklist items from the template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	Clearly matches the RFC0041.5 documentation/status update and stays concise.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rfc0041-5-closed

---

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

[Copilot]

Pull request overview

Updates RFC 0041’s documentation to reflect that the previously recorded RFC0041.5 deferral has now been completed, and records the verification outcome for the v0.6.0 typed-columns release and associated plugin matrix coverage.

Changes:

• Updates the RFC header banner and verification narrative to reflect RFC0041.5 completion in v0.6.0.
• Revises §9.1 wording around the previously partial .5 criterion and adds a new §9.3 verification record for the deferral closure.
• Records an additional finding (#664) observed during release validation (noted as out of scope for the plugin work).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.