Refresh HiveGrid Cloud reference snapshot

This commit is contained in:
david committed 2026-08-03 15:31:14 +02:00
1 parent 5e99e14772
commit 7f88026f79
5955 files changed
+1177325 -188362

No files matched your search

@@ -6,10 +6,8 @@
This document explains how test coverage is measured, gated, and reported in the
HiveGrid. Per-path thresholds are encoded as data in
`scripts/coverage-targets.json` and enforced by `scripts/verify-test-coverage.mjs`.
CI workflows run the gate on GitHub PRs and `push` to `main`, while the
Gitea coverage workflow currently runs on pull requests. Keep
`.github/workflows/coverage.yml`, `.gitea/workflows/coverage.yml`, and
this policy aligned when trigger coverage changes.
The Gitea coverage workflow runs the gate on relevant pull requests, pushes to
`main`, and manual dispatches. The local command uses the same targets.
## Why
@@ -83,8 +81,8 @@ latest ratchet already meets or exceeds for every critical-path row (see
3. Run `pnpm run verify:test-coverage` locally. The gate prints the actual
coverage; set the active gate at or slightly below that number so the
commit lands green.
4. Open a PR. The Coverage workflow will post a sticky comment showing the
new row in the per-path table.
4. Open a pull request. The Coverage workflow uploads a Markdown report showing
the new row in the per-path table.
## How to bump or lower a threshold
@@ -113,8 +111,8 @@ Bumps **down** (looser gate) — should be rare and reviewed:
- any target's actual `statements%` < `target.statements` **or**
actual `branches%` < `target.branches`
The GitHub workflow uploads `coverage/` as `coverage-report-<run_id>` even on
failure so contributors can drill into the HTML report.
The Gitea workflow uploads `coverage-gate/` and the rendered Markdown summary
as `coverage-report-<run_id>` even on failure.
## Type-only packages
@@ -128,15 +126,13 @@ sprint target, then cover their contract with `expectTypeOf` tests and
Task #76 is completed. Keep the gate useful as a no-regression control:
1. Confirm `docs/testing/coverage-sprint-backlog.md` still has no
critical-path or standard-tier positive-gap rows before release closeouts.
2. Keep each active `statements`/`branches` gate at or above the relevant
1. Keep each active `statements`/`branches` gate at or above the relevant
`sprintTarget`.
3. Treat `sprintTarget` fields as explicit release-floor annotations unless a
2. Treat `sprintTarget` fields as explicit release-floor annotations unless a
future cleanup removes them consistently from docs and gate data.
4. Run `pnpm run verify:test-coverage` after threshold changes — it must pass
3. Run `pnpm run verify:test-coverage` after threshold changes — it must pass
with the new gates.
5. Track additional Playwright/E2E coverage separately; it is not a blocker
4. Track additional Playwright/E2E coverage separately; it is not a blocker
for the completed per-module coverage gate.
## Out of scope (deferred to follow-up tasks)
@@ -147,12 +143,12 @@ Task #76 is completed. Keep the gate useful as a no-regression control:
but not delta. A future PR can add baseline-fetch + delta rendering similar
to bundle-budget.
- **E2E coverage via Playwright** (5 golden-path flows) — tracked separately.
- **Additional critical-path test writing** — see
`docs/testing/coverage-sprint-backlog.md` for the ordered backlog.
- **Additional critical-path test writing** — create a ticket with a measured gap from the current
`scripts/coverage-targets.json` contract.
## References
- Gate runner: `scripts/verify-test-coverage.mjs`
- Targets data: `scripts/coverage-targets.json`
- Summary/badge: `scripts/coverage-summary.mjs`
- CI: `.github/workflows/coverage.yml`, `.gitea/workflows/coverage.yml`
- CI: `.gitea/workflows/coverage.yml`