[obaseyi2]

Fixes #892.

DuckDB and T-SQL treat a window frame as part of the preceding ORDER BY expression and break its bounds at AND.

Classify ROWS BETWEEN and RANGE BETWEEN as frame clauses in these dialects, plus GROUPS BETWEEN in DuckDB. Keep the bounds' AND inline; ordinary boolean AND formatting is unchanged.

SELECT
  sum(size) OVER (
    ORDER BY
      time_stamp
    ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW
  )
FROM
  some_events;

Regressions cover frame types, idempotence and tabular indentation. Both reported-layout tests failed before the fix.

Validation on the published head: 27 Jest suites passed (5,892 tests passed, 1 skipped, 63 snapshots); repository-wide formatting, lint, type checking and CJS/ESM/webpack builds passed.

Local tools were installed separately on Windows/Node 24 without lockfile changes; CI uses Node 22. Other dialects retain their current frame layout. Classification remains lexical, consistent with these dialects' existing clause handling.

[nene]

I assume this is AI generated. It's no good. I don't want to spend time explaining why, as you probably didn't spend much time in implementing this.