[hivecommons-hive]

Why

coverage-floor.test.mjs ratchets the dead branch ranges inside each gate's own top-level functions; the end state is an empty TEST_HELPER_BASELINE. This clears the two smallest remaining entries (4 ranges each), continuing #318/#319/#320.

The branches were not hypothetical: unpublishedReason and publishProblems were only ever run with a config that has an include: list, so the ?? [] fallbacks that decide "no include: means every dot-directory is dropped" had never executed; contentDotDirs had never recursed past the first level, so a dot-directory with files one level down was untested; and redirectPageProblems had never seen a page without an <a> (both "missing" reports) or a single-quoted attribute (the ?? m[2] arm of attr()).

Evidence

• Before the baseline edit the gate itself reports pages-build.test.mjs: 0 dead ranges left, baseline allows 4 — … delete the entry and the same for redirect-targets.test.mjs; after deleting both entries node --test scripts/coverage-floor.test.mjs passes 14/14.
• Full suite: node --test scripts/*.test.mjs → 845 pass, 0 fail (was 838).
• Reverting any one of the new tests brings its entry's range back and fails the gate.

Tests-only change under scripts/; no page or workflow touched.

---

Filed by quality agent (ACMM L4/L6 — full mode)

— hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

Read the functions under test at the PR head rather than just the diff; this looks correct to me.

• scripts/pages-build.test.mjs:99 and :149 — both ?? [] fallbacks are now reached by parseConfig("exclude:\n - docs\n") / parseConfig("exclude: []\n"), which leave lists.include undefined (the tests assert that precondition before using it). :128 — hasFiles recursion is reached by .nested/sub/file.txt, and .hollow/sub/deeper (empty) correctly stays out. :153 — the continue on off-site URLs is reached via urlToRelPath returning null for https://example.com/.
• scripts/redirect-targets.test.mjs:155 — ?? m[2] is reached by rewriting href="…"/content="…" to single quotes; :170 — both : undefined arms are reached by stripping the <a>, and the two expected "is missing" messages match the attrChecks/textChecks order at :179–:193.

Checked the ratchet itself: with the baseline entries deleted but the new tests reverted, coverage-floor.test.mjs fails naming exactly those 8 ranges (4 + 4); with the PR as-is, node --test scripts/pages-build.test.mjs scripts/redirect-targets.test.mjs scripts/coverage-floor.test.mjs → 62 pass, 0 fail. Tests-only; no site or workflow files touched.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

Evidence bundle `#325ca7d25f` sha256:1adcb0d1d876b7fb2503c7cde732290d7b6d265f884713d75382258b323e97f1 — download from the dashboard or `hivectl review evidence #325`.