docs: close the pre-release gaps — changelog coverage, watches config, section order

[mabry1985]

Release prep for the 25 commits on main since v0.105.2.

Changelog

[Unreleased] had two separate ### Fixed sections, which would have rolled into a malformed release section. Merged them and reordered to Keep a Changelog's Added / Changed / Fixed.

Four user-facing changes were missing entirely:

Missing	Section
watch tools gated behind watches.enabled, default off (#2099)	Changed
PR review read code at the default branch, not the PR head (#2100)	Fixed
shell/fs policy + Work folders moved onto the Filesystem group (#2084)	Added
PWA theme-color painted the status bar with the brand accent (#2083)	Fixed

The watch entry calls out explicitly that existing configs relying on those tools must now set watches.enabled: true — it's a silent capability removal otherwise.

ADRs and CI-internal commits are deliberately not listed: this repo cites ADRs inline in the entry they belong to (see the 0.105.0 section) rather than as standalone lines.

Docs

watches.enabled shipped with no documentation outside a commented block in the example config — while simultaneously flipping the tools to default-off. That's the combination most likely to read as "the watch tools disappeared."

• docs/reference/configuration.md gains a ## watches section (there wasn't one at all).
• docs/guides/watches.md gains a "Turn it on first" section, since the guide otherwise opens by teaching a feature you can no longer use.

Both state the three things the flag deliberately does not do, because they're what bites when toggling it on a running agent:

1. It's tool-availability only — stored watches are never deleted, and the background poller keeps running and firing on_met.
2. goal.enabled must also be true; the tools ride inside the goal tool group, so watches.enabled: true alone binds nothing.
3. It defaults off as of Enhancement: Put watches behind a feature flag #2020 — agents upgrading from ≤0.105.2 must opt in.

Wording verified against graph/config.py:460-467 and the example config so the three don't drift apart.

Not included

The four open PRs (#1995, #1999, #2001, #2007) are all drafts that explicitly ask for your review — "needs your eyes before merge", "for local testing before merge (as requested)", "decision record in progress". Two also have conflicts. They're parked deliberately, so I left them out of the release rather than sweeping them in.

Testing

ruff clean · 3899 Python tests · docs nav regenerated + its sync test passing · changelog.py check passes.

🤖 Generated with Claude Code

[protoreview]

QA panel review — PASS

code-review · head 7da77d6a57b7 · formal

[review-synthesizer completed: workflow code-review:report]

The change carries negligible risk as no defects were identified by the review panel or the verification pass. There are no items to fix, and there was no disagreement among the finders. Verification confirmed the absence of findings.

[]

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 53 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: ASSERTIVE

Plan: Pro

Run ID: c937cc98-35a1-4273-abd8-c471c555ba13

📥 Commits

Reviewing files that changed from the base of the PR and between c9e9c47 and 7da77d6.

⛔ Files ignored due to path filters (1)

• CHANGELOG.md is excluded by !*.md

📒 Files selected for processing (2)

• docs/guides/watches.md
• docs/reference/configuration.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/pre-release-changelog-and-watches

---

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