[viceice]

Changes

Important

Sixth and last in the lib/modules/manager coverage stack, on top of #45954. This must merge after the rest of the stack — the new threshold only holds once those branches are in, so merging it early would fail CI on main.

Raises the branch coverage threshold from 98.71 to 99.14.

A full run on this branch reports:

	before the stack	on this branch
statements	100% (49240/49240)	100% (49249/49249)
branches	98.72% (25434/25765)	99.16% (25479/25696)
functions	100% (7333/7333)	100% (7333/7333)

Both numerator and denominator move: the new tests cover branches that were counted and missed, and the documented ignores remove branches that cannot be reached from the count entirely.

99.14 keeps the same rounding-down margin as the previous ratchet, which set 98.71 from an actual 98.7236% — floor to two decimals, then 0.01 of headroom. Statements, functions and lines are already pinned at 100 and stay there.

Two notes on the measurement:

• It was taken on this branch, so it accounts for the manager stack but not for test(datasource): close branch coverage gaps #45943, which closes the datasource gaps separately off main. If that merges too the real figure goes higher, so 99.14 stays conservative either way.
• Before this stack there was no headroom at all: the baseline floors to exactly 98.71, the threshold already in place.

Context

Please select one of the following:

• This closes an existing Issue, Closes: #
• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

• No — I did not use AI for this contribution.
• Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
• Yes — substantive assistance (AI-generated non‑trivial portions of code, tests, or documentation).
• Yes — other (please describe):

Claude Opus 5, via Claude Code: ran the coverage measurements, worked out the new threshold, and wrote this description.

Use of AI in replying to PR comments

Who answers review comments:

• @viceice will read and reply directly. Name the account.
• An agent will draft replies and @username will read them before they are posted. Name the account.
• Nobody has explicitly committed to replying.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests, but ran on a real repository, or
• Both unit tests + ran on a real repository

The change is a CI threshold; it was derived from full-suite coverage runs before and after the stack rather than from new tests.

🤖 Generated with Claude Code

[github-actions]

🎉 This PR is included in version 44.91.0 🎉

The release is available on:

• GitHub release
• 44.91.0

Your semantic-release bot 📦🚀