open/llm-security-commons
1
0
Fork 0
Code Issues Releases 1 Activity

fix(spec): section 6 forbade a case the corpus ships, and the predicate under it was wrong too

Browse source 
The normative spec read "Such a payload MUST NOT be given a discriminated case
id" while manifest.json defined case_id_derivation.variant_suffix and
conformance/hybrid-xss__script-tag--src-no-close/ sat on disk under it. The
manifest was the correct party: the derivation was extended in corpus 0.3.0 and
the spec was never updated. No data moves here, only the text describing it.

The derivation block now carries the optional '--' suffix and the truncating
reverse, with the '--'-absence measurement stated as the reason the reverse
stays LEXICAL - re-measured at this commit rather than copied from 0.3.0's
numbers, and scoped to id spaces because '--' does occur inside pattern values.

The part that would have passed review while still being wrong: fixing only the
permission. Section 6 also reasoned that equal in-scope finding sets mean the
second case "cannot fail in any way the first does not" - and the shipped
variant falsifies exactly that. It expects the same single finding, same scope,
same match, and still gates what the base cannot, because the base input matches
the pattern under both its published and its superseded stricter form. The
discriminating signal is INSIDE the scope, in the form of the scoped rule. So
the MUST NOT is replaced by a predicate about failure surface rather than
finding sets, checked in both directions: it admits the shipped variant and
still excludes the omitted markdown-image payload, whose only distinguisher
lives in a table this repository does not publish.

manifest.json is untouched and stays at 0.5.0; no case directory moved. The
spec has no version of its own - "Through version 0.1.1" in section 4 is the
CORPUS version, verified against CHANGELOG [0.2.0] before acting, because the
session brief said otherwise. Section 6's stable-id and BREAKING sentences were
read, not edited.

Verified in scratchpad, never in the repo: the amended derivation transcribed
into a checker that reads all 94 cases back from disk, derives each pattern id,
round-trips it forward, and asserts the case expects it. All 94 reproduce.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M4xrxV3EXbSALqvB23kpeY
This commit is contained in:
Kjell Tore Guttormsen 2026-08-13 22:00:24 +02:00
commit cb784fea6f
3 changed files with 157 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

7
CLAUDE.md
View file

@ -86,6 +86,13 @@ Ingen. Data + prosa. Filformater: JSON (data + schema), Markdown (spec), rå tek
sann ved commiten `measurement` pinner. Retter du én av 83, står 82 målinger ved én commit
og én ved en annen, under en header som navngir én. Før avviket i manifestet med dato og
commit i stedet. Å re-pinne hele korpuset er en egen beslutning.
- **Like funn-sett betyr ikke lik feilflate.** Spørsmålet som avgjør om en variant-case skal
mintes er ikke om de to inputene gir ulike funn innenfor scope — det er om den andre
inputen kan FEILE, innenfor scope, under en endring i den scopede datafila som den første
ville bestå. Korpusets første variant forventer nøyaktig samme funn som base-casen og
gater likevel noe base-casen ikke ser: base-inputen matcher mønsteret både i publisert og
i tidligere, strengere form. En payload hvis skille ligger i en tabell vi ikke publiserer
består ikke terskelen og føres som navngitt utelatelse. Spec §6 bærer regelen.
### Id-rom: adoptert vs. navngitt