2 lexicon definitions are silently truncated by unquoted commas in YAML flow mappings

[kreneskyp]

Found by the refreshed FR-035 manifest schema (agent-ix/spec-artifacts-iso#15), which is the first thing to ever validate this manifest's lexicon: block. Same class as agent-ix/spec-objects-architecture#7.

Problem

lexicon entries are authored as YAML flow mappings with unquoted scalars. A comma inside the definition splits the mapping:

lexicon:
  secret: {definition: a confidential value (key, password) kept out of code}

parses as {definition: "a confidential value (key", "password) kept out of code": None}. The stored definition is the fragment a confidential value (key — an unbalanced parenthesis. LexiconTermDef is not deny_unknown_fields, so quire-rs accepts it silently.

The 2 affected terms

Term	Stored definition	Lost text
secret	a confidential value (key	password) kept out of code
audit	(truncated)	tamper-evident event trail

secret is the more pointed one: a security module's definition of "secret" currently reads as a truncated fragment.

Fix

Quote the scalars (or use block mappings). Not done by the finder: lexicon vocabulary changes are sweep-and-report, so the restored wording needs sign-off.

Sibling findings: spec-objects-architecture (8 terms, #7), spec-objects-operational (3 terms).