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
23 lines
668 B
JSON
23 lines
668 B
JSON
{
|
|
"$comment": "Generated from a differential measurement, not written by hand. Normative semantics: spec/conformance-corpus.md. Measurement header and per-runtime provenance: conformance/manifest.json.",
|
|
"case_id": "markdown__link-anchor-injection",
|
|
"input": {
|
|
"file": "input.txt",
|
|
"bytes": 37,
|
|
"sha256": "d20d46e5d09712e0c8f7445b8546ff84489c892665e085ad3a97b1b6926202a8"
|
|
},
|
|
"scope": [
|
|
"lexicon/injection-lexicon.json"
|
|
],
|
|
"match": "exact-within-scope",
|
|
"findings": [
|
|
{
|
|
"pattern_id": "markdown:link-anchor-injection"
|
|
}
|
|
],
|
|
"observed_out_of_scope": {
|
|
"llm_ingestion_guard": [
|
|
"active:markdown-link"
|
|
]
|
|
}
|
|
}
|