[no-release] docs(handover): #144 merged, jarvis on 2026.8.5, next up #132

[simons-plugins]

Docs only — no code, no version bump (2026.8.5 is untagged, so version-check
passes; a docs PR should not mint a version nobody installs).

The handover header still described an open PR and a 2026.8.4 jarvis. It now
records three things the merge itself does not:

• Two merges are unreleased. fix(export): restore endpoints at startup so the bridge is never online-and-empty (#141) [no-release] #142 and [no-release] feat(menu): group Plugins ▸ Matter into five sections (#134) #144 both went in under
  [no-release], so the latest release is still v2026.7.23 and the only 2026.8
  artefact is the hand-cut v2026.8.0 pre-release. Whoever cuts the next real
  release ships Bridge serves an EMPTY aggregator after restart — Apple resets rooms on every reboot #141's endpoint restore and Group the two Install/update menu items — they are 11 apart and easily confused #134's menu together — worth
  knowing before writing the release notes.
• The separators were confirmed to RENDER, in the Indigo client, on jarvis.
  No test can assert that: the suite pins the file's shape, not what Indigo
  draws. If a future Indigo release stops honouring an empty <MenuItem/>, the
  suite stays green and the menu silently flattens — the symptom is a blank
  clickable row where a divider used to be. That is now written down.
• The deploy method, because it was only safe under a precondition: two
  files over SSH plus a restart, after checksum-comparing the install against
  the branch and finding no hot-patches.

NEXT UP is now #132 (the Rebuild Endpoint Map warning overstates what the action
does), then #131.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 14 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e55bef36-db31-4d12-8457-6e1d2e44cd2d

📥 Commits

Reviewing files that changed from the base of the PR and between 08d64dc and 76cb30a.

📒 Files selected for processing (1)

• docs/HANDOVER.md

---

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