Extraction behavior seems a bit off

[eagr]

From the HTTP/3 spec.

If the certificate is not acceptable with regard to the new origin
for any reason, the connection MUST NOT be reused and a new
connection SHOULD be established for the new origin.

There are two keywords of different requirement levels, and it results in a single entry of spec requirement.

[[spec]]
level = "MUST"
quote = '''
If the certificate is not acceptable with regard to the new origin
for any reason, the connection MUST NOT be reused and a new
connection SHOULD be established for the new origin.
'''

---

Each code of the format 0x1f * N + 0x21 for non-negative integer
values of N (that is, 0x21, 0x40, ..., through 0x3ffffffffffffffe)
MUST NOT be assigned by IANA and MUST NOT appear in the listing of
assigned values.

This one contains two keywords of the same requirement level, yet it results in two entries of spec requirements. A bit surprising.

[[spec]]
level = "MUST"
quote = '''
Each code of the format 0x1f * N + 0x21 for non-negative integer
values of N (that is, 0x21, 0x40, ..., through 0x3ffffffffffffffe)
MUST NOT be assigned by IANA and MUST NOT appear in the listing of
assigned values.
'''

[[spec]]
level = "MUST"
quote = '''
Each code of the format 0x1f * N + 0x21 for non-negative integer
values of N (that is, 0x21, 0x40, ..., through 0x3ffffffffffffffe)
MUST NOT be assigned by IANA and MUST NOT appear in the listing of
assigned values.
'''

[camshaft]

For the first one, the extract logic isn't sophisticated enough to split on conjunctions. So, instead, if multiple requirements are specified in a single sentence then it takes the highest level.

For the second one that seems like a bug.

[eagr]

Yeah, the first one was kinda expected. And based on the assumption of which, the second just seemed off.