FUI9009: Contract token source cannot be read
criticalWhy Fragments emitted FUI9009 and how to resolve contract/unreadable-token-source.
Details
{
"code": "FUI9009",
"ruleId": "contract/unreadable-token-source",
"category": "System",
"defaultSeverity": "critical",
"lifecycle": "experimental",
"fixAvailable": false,
"evidenceRequired": false
}Guidance
What it means
Fragments emitted FUI9009 from contract/unreadable-token-source because the scanned source conflicts with an active system contract rule. The finding location and evidence identify the exact authored input that was evaluated.
How to resolve it
Review the finding evidence, then change the source or the documented governance mechanism so contract/unreadable-token-source reflects the intended contract. Do not hide the finding with a broad repository exclude. When an exception is intentional, use a line-attached, reasoned suppression from the configuration reference.
Verify the change
Run npx @usefragments/cli check --changed --format agent, inspect the resulting evidence, and then run npx @usefragments/cli check --changed --ci. If the finding changes identity, review baseline churn instead of silently regenerating the baseline.
Intentional exception? Use a narrow, reasoned directive from the in-source suppression reference.