Conversation
Bumps the development-dependencies group with 1 update: [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip). Updates `knip` from 6.3.0 to 6.3.1 - [Release notes](https://github.com/webpro-nl/knip/releases) - [Commits](https://github.com/webpro-nl/knip/commits/knip@6.3.1/packages/knip) --- updated-dependencies: - dependency-name: knip dependency-version: 6.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
🏷️ Automatic Labeling SummaryThis PR has been automatically labeled based on the files changed and PR metadata. Applied Labels: dependencies,size-s,npm Label Categories
For more information, see |
🔍 Lighthouse Performance Audit
📥 Download full Lighthouse report Budget Compliance: Performance budgets enforced via |
|
@copilot fix issues in TypeScript & JavaScript Testing / Unit Tests (Vitest) (pull_request) |
- analysis-quality-validation: allow ≥1 dok_id for single-document synthesis files - analysis-reader: fix test to expect subdirectory preference (matches code behavior) Agent-Logs-Url: https://github.com/Hack23/riksdagsmonitor/sessions/bca6fa0f-684a-4987-82d3-b0f3062ee528 Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
🔍 Lighthouse Performance Audit
📥 Download full Lighthouse report Budget Compliance: Performance budgets enforced via |
Fixed in 5532a13. Two test failures were caused by new analysis content (2026-04-08) with only 1 document:
All 4060 tests pass. |
Two Vitest failures on CI unrelated to the knip bump — caused by new single-document analysis content (2026-04-08) exposing stale test assumptions.
analysis-quality-validation.test.ts: dok_id density threshold was hard-coded to ≥2 for all strict-v2 synthesis files. Single-document analyses legitimately cite only 1 dok_id. Now scales minimum usingextractDocumentsAnalyzedCount():analysis-reader.test.ts: Test asserted root-level file precedence, butreadAnalysisFile()intentionally prefers subdirectory files (AI-generated) over root-level (script-generated). Fixed assertion to match actual behavior ('LOW'from subdirectory, not'HIGH'from root).