FUI9006: Rule exclude matched no scanned file

What it means

You scoped a rule off a path with an exclude glob, and the scan consumed it — but no scanned file matched the pattern. The exclude reads as active policy while exempting nothing, which is the same "declared but not armed" failure Fragments names elsewhere. The usual cause is a path that moved or was deleted after the exclude was written; the next is a glob written against a directory the scan does not cover at all (check app.include / components).

The diagnostic is verdict-neutral: it warns on stderr and never fails the run on its own.

How to resolve it

Correct the glob to a path this scan covers, or remove it. ** crosses path separators and * stops at one, and globs are matched against repo-relative paths:

govern: {
  styles: [
    {
      kind: "style.rawColors.forbid",
      except: ["transparent"],
      prefer: "token",
      severity: "warn",
      exclude: [{ glob: "src/legacy/vendor/**", reason: "vendor drop, tracked in DS-611" }],
    },
  ],
}

If the path is gone because the debt was paid, deleting the exclude is the correct fix — that is the outcome the reason field exists to make legible. See the configuration reference for both authoring forms and how excluded findings are reported.

Verify the change

Run npx @usefragments/cli check and confirm no FUI9006 warning remains. If the exclude is meant to be live, confirm the exemption now appears in the run's ignored accounting — check --format json lists each excluded finding with its glob and reason under ignored.