Skip to content

[governor] 🐝 Hive Advisory Report #388

Open

Description

@hivecommons-hive

This issue collects advisory findings from Hive agents.

At lower ACMM levels, some agents work in advisory mode β€” they analyze code and post findings here but do not create issues or PRs. At higher levels, designated agents (e.g. quality) can open issues and PRs directly, while other agents remain advisory-only.

The governor posts periodic digest comments summarizing what advisory agents found.

Do not close this issue. It is a living document.

β€” hive: agent=governor

Activity

  1. hivecommons-hive commented on Nov 10, 2026

    @hivecommons-hive
    ContributorAuthor

    🐝 Advisory Digest β€” 2026-11-16 18:54 EST

    Automated code review findings from Hive agents. Each finding includes a file reference and suggested fix. This comment is updated periodically.

    Advice

    Frozen for governor mode QUIET until 2026-11-19 (next review in 3 day(s)). The list of recommendations is frozen; their numbers, items and links are recomputed on every digest.

    Counts quoted: governor actionable queue 2 PRs / 7 issues (what mode and cadence key on; excludes held, draft, in-review and human-gated items) β€” Overview chart 3 open PRs / 36 open issues (every open or held item across repo cards; the queue-health advice counts these).

    • Reduce the blocked PR queue β€” 2 of 3 open PRs (66%) are Blocked. 2 of 2 have merge conflicts β€” rebase or close the oldest. (signals: overview_open_prs=3, blocked=2, blocked_pct=66, failing_ci=0, merge_conflict=2, verdict_blocked=2, stale_blocked=0, oldest_blocked_days=35, top_repo=techdocs (2, 100%), top_author=iRaindrop (1, 50%))
      • First: techdocs#385 (merge conflict; verdict blocked: behind main β€” needs an update from the base branch; also an approving review is required by branch protection (0 given)), techdocs#406 (merge conflict; verdict blocked: behind main β€” needs an update from the base branch; also CI failing: DCO)
      • Full list: Blocked PRs (CSV), Blocked PRs in techdocs (CSV)
    • Clear the human gate on PRs β€” 1 of 3 open PRs (33%) wait on a human: 1 held, 0 labelled needs-human, 0 needs-decision β€” release, review, or close them. (signals: overview_open_prs=3, needs_human=1, held=1, needs_human_label=0, needs_decision=0)

    Bands named above (same rules as the Overview chart):

    • Blocked (PRs): blocked sweep verdict, merge conflicts, or failing CI β€” read the verdict, rebase, or fix the checks
    • Needs human (PRs): held, or labelled needs-human, stage/085-needs-decision, needs-decision, 2-discussing, blocked, stage/045-needs-decision, epic, needs-triage β€” a human must review, decide, or release the hold before automation continues

    Findings: 10

    πŸ’‘ Showing top 10 findings (by severity). 63 more exist. Set governor.advisory.show_all: true to see all.

    Severity Count
    🟠 high 10

    🟠 HIGH (10)

    • [onboarding] techdocs repo lacks local build/preview instructions (npm install, docus:start) README.md guide

      The cncf/techdocs repo (a Docusaurus site with npm scripts like docus:start, docus:build, check, test) has no documented procedure for a new contributor to install dependencies and preview the site locally. README.md and docs/index.md describe the site's content but never mention 'npm install' or any docus:* script. docs/repo-setup.md is guidance aimed at other CNCF projects' repos, not instructions for building this repo. CI workflows (.github/workflows/.yml) run npm scripts via a custom action but these are not surfaced to human contributors. Verified via grep: zero occurrences of 'npm install' or 'npm start' in README.md or docs/.md.

    • [coverage-gap] docusaurus.config.ts isProd-dependent url/editUrl branches had no unit coverage docusaurus.config.ts quality

      docusaurus.config.ts is excluded from the c8 coverage gate. Its three isProd-dependent fields (top-level url, docs preset editUrl, analyses plugin editUrl) had no unit assertion, and no end-to-end check asserts their values (Netlify deploy-preview only exercises the non-prod branch incidentally, without assertion; the prod branch never runs on PRs at all). Added lib/docusaurusConfigBuildContext.test.mts + test-only harness in PR test: cover isProd-dependent url/editUrl branches in docusaurus.config.tsΒ #413 (cncf/techdocs), tracked under issue [quality] npm run typecheck fails on main β€” merge race between #404 and #405Β #407's component cluster.

    • [coverage-gap] docusaurus.config.ts markdown.preprocessor: reference-style link (]:) branch untested docusaurus.config.ts quality

      markdown.preprocessor regex has two alternatives (inline '](' links and reference-style ']:' link definitions); only the inline branch was unit-tested. Manual mutation (deleting the ']:\s*' alternative at rev 418adeb) passed all existing tests, confirming the gap. No e2e/integration suite exists in this repo to provide alternate coverage, so Priority 1. Fixed in PR techdocs#410 (closes issue techdocs#409).

    • [coverage-gap] cncf/techdocs docusaurus.config.ts markdown.preprocessor regex-rewrite has zero test coverage (file path not found at analyzed commit β€” finding may be outdated) (reported 2Γ—) quality

      markdown.preprocessor (docusaurus.config.ts:44-50) runs a regex rewrite (strips .md from site-absolute /docs|analyses links) against the imported root README.md. Unit evidence: lib/**/*.test.mts (node --experimental-strip-types --test) has no test file for docusaurus.config.ts; function is untested. E2E evidence: no e2e/integration suite exists in this repo (checked for playwright/cypress dirs, none found; only format-check/link-check/spell-check CI). Covered by neither unit nor end-to-end tests -> Priority 1 ceiling, set to 2 (medium) given narrow impact (single README.md import path). Provenance: cncf/techdocs main@4b1f800, checked 2026-11-12. Root cause: logic is inlined in docusaurus.config.ts, which imports ./lib/getBuildContext and ./lib/remarkRewriteLinks without file extensions -- fine for docusaurus webpack bundler but unresolvable under this repo's own node --experimental-strip-types test runner (reproduced: ERR_MODULE_NOT_FOUND). Testing it directly therefore requires extracting the regex into its own lib/ module first, which is a production-code change outside quality agent scope (no production code / no refactors). Filed as issue-only; no PR possible without that extraction.

    • [coverage-gap] lib/remarkRewriteLinks/index.ts: 4 branches uncovered by unit tests (89.74% branch coverage) lib/remarkRewriteLinks/index.ts quality

      rewriteHref() in lib/remarkRewriteLinks/index.ts had 4 uncovered branches (c8 --reporter=text on node --experimental-strip-types --test 'lib/**/*.test.mts', local run against HEAD, 2026-11-11): (1) line 87, empty-path-after-split short-circuit (href consisting only of a query/fragment, e.g. '?x'); (2) line 99, the cross-plugin capture group 2 being undefined (a bare '../docs' with no sub-path); (3) line 112, the .mdx branch of the site-absolute strip-extension ternary; (4) line 140, file.path being undefined in the remark plugin wrapper. Repo has no end-to-end/integration suite (CI only runs format-check.yml, link-check.yml, spell-check.yml per [quality] npm run test:unit never runs in CI β€” unit tests have no CI signalΒ #390), so these branches were covered by neither unit nor end-to-end tests -> Priority 1.

    • [missing-workflow] cncf/techdocs: unit tests and c8 coverage gate (test:coverage) are never invoked by any CI workflow cncf/techdocs#415 quality

      format-check.yml/link-check.yml/spell-check.yml only run check:format, check:markdown, check:links, check:spelling. package.json 'check' aggregates only check:* scripts. No workflow calls npm run test:unit or npm run test:coverage, so the 52 existing unit tests and the 99/99/97/100 c8 coverage gate enforce nothing on PRs. Fix requires a .github/workflows/ change, which this agent's contributor-tier token cannot push; filed as issue only.

    • [missing-workflow] No CI workflow runs the unit test suite, typecheck, or coverage gate .github/workflows/ (reported 2Γ—) quality

      package.json defines test:unit (52 node:test specs under lib//*.test.mts and scripts//*.test.mjs, including scripts/typecheck.test.mjs which shells out to tsc), test:coverage (c8 wrapping test:unit with a 97-100% coverage gate), and typecheck, but .github/workflows only contains format-check.yml, link-check.yml, spell-check.yml, trigger-contribute-site-netlify.yml, and copilot-setup-steps.yml. None of them run npm run test:unit, npm run test:coverage, or npm run typecheck on pull_request. A regression in any of the 52 unit tests, a drop below the coverage thresholds, or a typecheck break (as happened with the TS5102/TS2339 regression PR test: fix typecheck regression from #404/#405 merge raceΒ #408 fixes) can merge to main without CI ever catching it.

    • [regression-risk] typecheck broken on cncf/techdocs main β€” test: cover docusaurus.config.ts markdown preprocessorΒ #404/test: fix broken typecheck script and add regression testΒ #405 merge race (fixed in PR test: fix typecheck regression from #404/#405 merge raceΒ #408) (file path not found at analyzed commit β€” finding may be outdated) quality

      PR test: cover docusaurus.config.ts markdown preprocessorΒ #404 and test: fix broken typecheck script and add regression testΒ #405 each passed npm run typecheck independently but merged ~2 min apart on cncf/techdocs main; combined, config.markdown.preprocessor destructures from a value typed DeepPartial|undefined once TS5102 no longer masked the error. Fixed with two assert.ok narrowing checks in the test file; filed as issue [quality] npm run typecheck fails on main β€” merge race between #404 and #405Β #407, fix in PR test: fix typecheck regression from #404/#405 merge raceΒ #408 (hold).

    • [test-gap] techdocs#415: npm test:coverage (99/99/97/100 gate) never invoked by any GitHub Actions workflow #415 scanner

      Confirmed independently: .github/workflows/format-check.yml, link-check.yml, and spell-check.yml run check:format/check:markdown/check:links/check:spelling respectively, but no workflow runs 'npm run test:unit' or 'npm run test:coverage' (c8 gate: --lines 99 --statements 99 --branches 97 --functions 100). package.json's aggregate 'check' script only picks up scripts matching check:*, excluding test:unit/test:coverage, so npm test (check && test:unit) is also never invoked in CI. A PR can merge a broken unit test or a coverage regression with all required checks green.

    • [test-gap] techdocs#390: confirmed β€” package.json test:unit script exists but no workflow invokes npm test/test:unit, only format/link/spell checks run in CI, so lib/*.test.mts regressions get green checks #390 scanner

      Verified independently: package.json defines test:unit (node --test over lib/**/*.test.mts) and a combined test script, but .github/workflows/ only contains copilot-setup-steps.yml, format-check.yml, link-check.yml, spell-check.yml, and trigger-contribute-site-netlify.yml β€” none run npm test or npm run test:unit. lib/remarkRewriteLinks/index.test.mts (and any new suites for lib/getBuildContext.ts etc.) can regress with all CI checks green.


    Analyzed at cncf/techdocs@92c2b9f1d987 (branch main) β€” the latest commit when this digest was generated. File references that no longer exist at this commit are flagged as outdated. Findings marked ⚠️ were computed at an older commit and have NOT been re-verified here.

    Updated 81 times Β· last 2026-11-16T23:54:16Z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions