feat(audit): item-counting grammar to config (#6855 phase 1, harness-gated)#6915
feat(audit): item-counting grammar to config (#6855 phase 1, harness-gated)#6915chubes4 wants to merge 1 commit into
Conversation
…rness-gated (#6855 phase 1)
Homeboy Results —
|
Held as draft — root cause of the harness fidelity gap FOUNDThird attempt. The fidelity-upgraded harness (#6914) passes all 3 tests (matches_snapshot, skips_test_paths, deterministic) AND structural parity passes (24 tests). Yet CI Audit fails identically to #6896/#6906: Root cause: the harness exercises the WRONG audit entry point
These are DIFFERENT code paths. The actionable fix (prerequisite for #6855)The runtime audit regression harness must call This is the real fidelity gap (deeper than the fixture-content gap fixed in #6914). I'll redirect to upgrading the harness to use the CLI workflow entry point. Migration itself is correct in isolation (parity + fixture harness pass); held pending the workflow-path harness. |
Third attempt at #6855 Phase 1, gated by the fidelity-upgraded runtime audit harness (#6914) which now exercises test-path skipping AND the agnostic detector — the two behaviors #6896/#6906 broke. Extracts structural.rs item counting into config-driven LanguageGrammar; enum Language/symbol_graph/is_empty untouched. All 3 audit_runtime_regression harness tests + structural parity pass with unchanged findings.