fix: don't collect filtered reference warnings in sortByReference - #1763

Problem

When you combine a filter with outputReferences: outputReferencesFilter, Style Dictionary can still print "filtered out token references were found", even though the output has no references and every value is resolved (#1379). This happens when the filtered-out tokens reference other tokens (multiple levels of references). With only one token, the warning goes away.

Minimal repro:

tokens: {
  base:     { red: { value: '#f00' }, blue: { value: '#00f' } },
  mid:      { danger: { value: '{base.red}' }, info: { value: '{base.blue}' } },
  semantic: { error: { value: '{mid.danger}' }, notice: { value: '{mid.info}' } },
},
// file: filter: (t) => t.path[0] === 'semantic', options: { outputReferences: outputReferencesFilter }

The output is --semantic-error: #ff0000; --semantic-notice: #0000ff;, but the build still logs the warning for base.red / base.blue.

Cause

When outputReferences is set, formats sort tokens with sortByReference(tokens, { unfilteredTokens }). The sorter called getReferences(value, tokens, { unfilteredTokens, warnImmediately: false }), and that call adds a FilteredOutputReferences message for every reference missing from the filtered set. When two tokens reference other tokens but not each other, the sorter recurses into the referenced tokens (sorter(aRefs[0], bRefs[0])). Those tokens can be filtered out, so it also recorded their references (here base.red, base.blue). Those tokens are never output, so outputReferencesFilter never runs for them and can't remove the warnings.

Fix

Sorting only needs to resolve references. It doesn't need to report them. sortByReference now looks references up in unfilteredTokens ?? tokens directly, without the unfilteredTokens option, so it no longer adds filter warnings. Filtered references that really end up in the output are still reported by createPropertyFormatter. Without unfilteredTokens, behavior is unchanged.

One side effect: the verbose warning now lists references in output order. It used to list them in sort-comparison order (neutral.0 now comes before neutral.100), so I updated three snapshots for that. The set of references is the same.

Tests

• sortByReference.test.js: sorting with unfilteredTokens and multi-level references collects no filter warnings, and still sorts correctly through references that resolve to filtered-out tokens.
• __integration__/outputReferences.test.js: building the repro above with outputReferencesFilter logs no filtered-reference warning.
• The new tests fail without the fix (4 failing) and pass with it.
• npm run test:node: 998 passing, 4 pending. npm run lint (eslint, prettier, tsc) passes.
• Added a patch changeset.

AI disclosure: I used an AI coding assistant to investigate this issue and draft the fix and tests. I reproduced the bug and checked the change and test results locally.

Fixes #1379