Marker Kind/Literal Contract Recheck

Verdict

MARKER_KIND_LITERAL_CONTRACT_NEEDS_FIX

The closed enum and per-kind literal validation are correctly implemented at single-marker unit level. Unknown, mismatched, and typo literals fail closed.

The required whole-document behavior is missing: no executable extractor enumerates markers, checks duplicate markers, validates fence balance/nesting/overlap, or produces marker records. The report states duplicate markers fail closed, but the SSOT code does not execute that rule.

T1 must implement and test the complete marker/extractor pipeline, including duplicate and ambiguity cases, in the runnable SSOT.