FUI2017: Local token differs from its declared upstream source

Details

{
  "code": "FUI2017",
  "ruleId": "tokens/upstream-drift",
  "category": "Tokens",
  "defaultSeverity": "moderate",
  "lifecycle": "experimental",
  "fixAvailable": false,
  "evidenceRequired": true
}

Guidance

What it means

Fragments emitted FUI2017 from tokens/upstream-drift because the scanned source conflicts with an active tokens 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 authored governance configuration so tokens/upstream-drift reflects the intended contract. Do not hide the finding with a broad repository exclude; use a rule-specific exclude or a line-attached, reasoned suppression only when the exception is intentional.

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.