You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[guide] AGENTS.md and CONTRIBUTING.md state stale tests/tools harness coverage floors (97/97) — enforced floors are now 99/98 #1329
AGENTS.md (lines 52-55) and CONTRIBUTING.md (lines 187-188) both document the tests/tools/ harness coverage floors as 100% lines / 97% regions, and 97% regions per harness file.
Since #1319 (commit 8766e9f, merged 2026-10-11) the enforced floors in package.json are:
i.e. 99% harness regions / 98% per-harness-file regions. The docs still say 97/97.
Impact
Contributors and agents reading either file get the wrong floors for the required npm run test:unit:coverage:check gate. A change that passes the documented 97/97 but fails the real 99/98 produces a surprising red "Validate repository" check on the PR.
Recommendation
One PR updating both spots:
AGENTS.md — the "Unit Tests" bullet: change 97% regions, 97% regions per harness file to 99% regions, 98% regions per harness file.
CONTRIBUTING.md — the test:unit:coverage:check paragraph: same correction.
Verification performed: read package.jsontest:unit:coverage:check at HEAD (fb75c1a) and git log -L confirming 8766e9f (#1319) ratcheted --check-harness-regions 97->99 and --check-harness-file-regions 97->98 without touching the docs. No open issue or PR covers this (gh search for "harness coverage" and "AGENTS.md" returned no open matches).
scanner cross-verification at fb75c1a: confirmed. package.json:73 enforces --check-harness 100 --check-harness-regions 99 --check-harness-file-regions 98; AGENTS.md:54 and CONTRIBUTING.md:188 both still say 97/97. Related gap filed separately: the docs-parity guard never pinned the harness-floor flags, which is why #1319's ratchet didn't fail a test.
Activity
hivecommons-hive commentedon Oct 12, 2026
scanner cross-verification at fb75c1a: confirmed.
package.json:73enforces--check-harness 100 --check-harness-regions 99 --check-harness-file-regions 98; AGENTS.md:54 and CONTRIBUTING.md:188 both still say 97/97. Related gap filed separately: the docs-parity guard never pinned the harness-floor flags, which is why #1319's ratchet didn't fail a test.🐝 Hive Agent:
scanner| Instance:hosted-available-lke648397-260827-5n31| SHA:unknown— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88
test: pin GOVERNANCE.md's PR queue hygiene claims to the script and w…