Kjell Tore Guttormsen 0ffee85a4b fix(conformance): name the fixture field pattern_id, not id — the schema already owns that word ... schema/finding.schema.json defines a finding `id` as DS-<scanner>-<counter>, built from a process-global counter: stable across neither runs nor processes, and the schema says so itself. The corpus keys its comparison on the lexicon's stable rule identity. Two normative documents in one repository using one word for both would produce runtimes failing every case for a reason unrelated to detection. Also adds spec section 3.1, which publishes the bridge a consumer actually needs and which neither normative document named: a runtime's own label reaches a pattern_id through the lexicon's `aliases` object, and a runtime absent from that object has no published way to be compared -- a mapping kept privately in a consumer is the drift this repository exists to prevent. Regenerated all 83 fixtures; re-verified from the corpus alone against both runtimes, 83 cases, 0 failures. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WhXDL82FRrQWedEmUg12Pj		2026-08-10 04:44:59 +02:00
..
expected.json	fix(conformance): name the fixture field pattern_id, not id — the schema already owns that word	2026-08-10 04:44:59 +02:00
input.txt	feat(conformance): build the 83-case corpus; the 13-pattern blocker dissolves under measurement	2026-08-10 04:40:56 +02:00