[hivecommons-hive]

Test Improvement

package.json's test:coverage script (c8 --reporter=text --reporter=lcov npm run test:unit, added in #397) reports coverage but never fails the build on regression: c8's defaults are 0% for branches/functions/statements and 90% for lines. #396 (closed via #397) deliberately deferred adding --check-coverage thresholds until the in-flight coverage PRs merged, to avoid landing the gate red.

lib/ is now 100% statements/branches/functions/lines (after #389/#392/#394/#401 merged). Only scripts/add-frontmatter.mjs remains below 100% branch coverage, tracked by the still-open #402. This PR sets thresholds at the currently achieved levels — --lines 99 --statements 99 --branches 97 --functions 100 — verified locally to pass today (exit 0) and to fail when tightened past actual coverage (exit 1, 'does not meet global threshold'). Once #402 merges, a follow-up can tighten this to c8's --100 shortcut.

Single-line change to an existing script; no production code, no .github/workflows/** files touched.

Related Issue

Part of #390 — #390's task-list sweep lists package.json among the not-yet-touched items; this PR addresses only that local-tooling portion. The remainder of #390 (adding .github/workflows/unit-test.yml so the unit suite actually runs in CI) still needs a human or an ISSUES_PRS_MERGE agent, since this lane's contributor-tier token cannot push workflow-file changes.

---

Filed by quality agent (hold-gated mode). Human review required.

— hive: agent=quality backend=copilot model=claude-opus-4-6 copilot=1.0.88

[hivecommons-hive]

Important

Held for human review by the hive's ACMM level gate.

This PR was opened by the "quality" agent while Hive policy required a human checkpoint for that agent. Agent PRs are held at ACMM L3–L5; an outreach PR that targets a repository this hive does not manage is held at every level because it publishes project-facing communication into someone else's project.

Hive will keep the hold label until a human removes it. Operators can make a deliberate one-off release during an ACMM level change with release_level_holds=true, but level changes never release this hold automatically.

[netlify]

✅ Deploy Preview for cncf-techdocs ready!

Name	Link
🔨 Latest commit	309aab5
🔍 Latest deploy log	https://app.netlify.com/projects/cncf-techdocs/deploys/6af652b72898f14bddf684b5
😎 Deploy Preview	https://deploy-preview-403--cncf-techdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hivecommons-hive]

309aab5

ℹ️ Sentinel notice — informational; author is trusted (hive agent), merge is not blocked

Hive flagged this PR (author @hivecommons-hive[bot], head 309aab59f78d) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

• sensitive_path — changes 1 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
  • package.json

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

[hivecommons-hive]

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

Reviewed by reviewer — no findings.

Reviewer notes

Verified this end-to-end and it looks correct to me.

• Ran npm ci && npm run test:coverage at head 309aab5: all 46 tests pass and the gate exits 0, with actual coverage 99.09% lines / 99.09% statements / 97.77% branches / 100% functions — above the thresholds set in package.json:39 (--lines 99 --statements 99 --branches 97 --functions 100).
• Confirmed the gate enforces: re-running with --branches 98 exits 1 with ERROR: Coverage for branches (97.77%) does not meet global threshold (98%). So this turns test:coverage from report-only into a real regression gate, exactly as the body claims.
• The only sub-100% file is scripts/add-frontmatter.mjs (90.9% branches, lines 95–97 uncovered), which matches the body's note that test: cover add-frontmatter.mjs main() catch block and empty-frontmatter branch #402 tracks it; once test: cover add-frontmatter.mjs main() catch block and empty-frontmatter branch #402 merges, tightening toward --100 is the natural follow-up.
• Scope is a single line in an existing npm script; no workflow or production code touched. Note the gate only runs where someone invokes test:coverage — CI enforcement still depends on the unit-test.yml workflow deferred in [quality] npm run test:unit never runs in CI — unit tests have no CI signal #390, as the body says.

No findings. A maintainer approval is all this needs.