Problem
Library keeps entries and @string definitions in separate key namespaces, but the test suite currently exercises strict duplicate handling only for entries. That leaves two related contracts implicit:
- duplicate
@string keys must fail under the default strict policy; and
- an entry and an
@string definition may legitimately share the same key.
Without explicit coverage, a future change to duplicate detection could either admit duplicate string definitions or incorrectly treat different block types as conflicts.
Proposed coverage
Add focused library tests that verify strict duplicate rejection for String blocks and verify that entry and string keys remain independent namespaces. No production behavior needs to change.
Problem
Librarykeeps entries and@stringdefinitions in separate key namespaces, but the test suite currently exercises strict duplicate handling only for entries. That leaves two related contracts implicit:@stringkeys must fail under the default strict policy; and@stringdefinition may legitimately share the same key.Without explicit coverage, a future change to duplicate detection could either admit duplicate string definitions or incorrectly treat different block types as conflicts.
Proposed coverage
Add focused library tests that verify strict duplicate rejection for
Stringblocks and verify that entry and string keys remain independent namespaces. No production behavior needs to change.