Kjell Tore Guttormsen 44e5e39f67 test(llm-security): v8 Phase 5 step 3 - invert the unvendored-commons test ... Vendoring commons v0.1.0 under scanners/commons/ falsified the premise of `degrades gracefully when commons has not been vendored yet`: it asserted the default DEFAULT_COMMONS_ROOT did not exist. It was the only red test after the subtree add (2072/2073). The graceful-empty contract it guarded is covered twice over by the missing-artifact and invalid-JSON cases, which drive the same code path through an explicit commonsRoot. So the replacement asserts the direction that is now uncovered and matters more: a non-zero record count through the real default root, no override. That is the positive load-assertion Phase 5 step 4 requires. Every other gate we have treats a commons load failure as indistinguishable from a legitimately empty table, so a total loss of the vendored corpus would leave the suite green. Proven red-capable by moving scanners/commons aside: the assertion fires by name, not as an incidental TypeError elsewhere. Suite 2073/2073.		2026-08-10 20:52:04 +02:00
..
e2e	test(llm-security): cover TRG/SIG/AST in e2e pipeline + SIG miner/hacktool/rot13 families (#58,#59)	2026-07-18 10:46:19 +02:00
fixtures	feat(llm-security)!: v8 Phase 3 complete - riskScoreV1, posture heuristic, docs	2026-08-09 10:25:03 +02:00
golden	fix(llm-security): v8.x-A - close <script> recall hole, add whole-table ReDoS gate	2026-08-10 14:53:29 +02:00
helpers	test(llm-security): add JetBrains fixture tree + build helper	2026-04-18 10:49:49 +02:00
hooks	feat(llm-security)!: v8 Phase 3 step 1 - remove the deprecated mode env-vars	2026-08-09 10:17:47 +02:00
lib	test(llm-security): v8 Phase 5 step 3 - invert the unvendored-commons test	2026-08-10 20:52:04 +02:00
scanners	feat(llm-security)!: v8 Phase 3 complete - riskScoreV1, posture heuristic, docs	2026-08-09 10:25:03 +02:00