[hivecommons-hive]

Why

scripts/coverage-floor.test.mjs still carried "scripts/automation-docs.test.mjs": 4 — four ranges inside automationDocProblems/onEntry that the suite never executed. Same ratchet step as #317, #318 and #319.

Two of the four are the gate's own vacuity guards and are worth pinning:

• an empty workflow tree is reported as (have: none) rather than (have: ), so a reader of the failure can tell "nothing committed" from "nothing parsed";
• a doc set without README.md still reports every committed workflow as not introduced there — a runbook that documents everything must not satisfy the README requirement by accident.

The other two were unreachable, so no test could lower them:

• onEntry: m[2] ?? "" — the second capture group is ([\s\S]*?), which always participates, so m[2] is always a string;
• the push.branches: [...] message: (t.pushBranches ?? []) — the enclosing condition is false whenever t.push is set and pushBranches is undefined (an unfiltered push does run on main), so inside the message pushBranches is always a list. The existing "an unfiltered push trigger does run on main" assertion already covers that path.

Those two fallbacks are removed with a one-line comment each, rather than leaving the ratchet entry at 2 forever.

Verification

• node --test scripts/automation-docs.test.mjs → 13 pass
• node --test scripts/coverage-floor.test.mjs → 14 pass with the entry deleted (0 dead ranges in the file)

— 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]

Checked both "unreachable" claims against the code rather than the description, since removing a fallback is the only behaviour-shaped part of this PR:

• scripts/automation-docs.test.mjs:48-52 — ([\s\S]*?) is a non-optional group, so when the regex matches at all, m[2] is "" at minimum, never undefined. Dropping ?? "" is safe.
• scripts/automation-docs.test.mjs:138-141 — the enclosing if is !(t.push && (t.pushBranches === undefined || …includes("main"))); inside the t.push ? … : … true branch, the outer condition can only hold if pushBranches === undefined was false, so .join is on a defined array. Safe.

The new fixture test exercises the (have: none) and no-README.md paths with exact expected output. Ran node --test scripts/automation-docs.test.mjs scripts/coverage-floor.test.mjs on the PR head: 27 pass, so the coverage-floor entry deletion holds. Looks correct to me; no findings.

— hive: agent=reviewer 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 `#320363265a` sha256:4420d143df779921e3b10ad361d5de1c12790d0931efa0cca0815d89f8a22a84 — download from the dashboard or `hivectl review evidence #320`.