## Summary
<!--Explain briefly what goes wrong and explain why you believe this is a bug and not the intended behavior of SQLite (if it is not a crash).-->**No review yet**

## Minimized query

```sql
SAVEPOINT sp5387;
.clone
SAVEPOINT sp7623;
PRAGMA vdbe_listing = NO;
PRAGMA short_column_names = ON;
PRAGMA trusted_schema = YES;
.fullschema --indent 4
CREATE TABLE T (
  a INTEGER,
  b TEXT,
  c REAL
);
INSERT INTO T VALUES (jsonb_patch(if(0, 1, 0, 1), 1),'a',1.25), (2,'b',-3.5), (3,'c',0.0);
SELECT * FROM T WHERE NOT NOT (c < 2.0) ORDER BY c;
PRAGMA writable_schema = FALSE;
CREATE  VIEW IF NOT EXISTS v_T_2769 AS SELECT c FROM T;
ROLLBACK TO sp7623;
RELEASE sp7623;
INSERT INTO T DEFAULT VALUES;
VACUUM;
VACUUM main;
CREATE UNIQUE  INDEX IF NOT EXISTS idx_T_6640 ON T(a);
ALTER TABLE T RENAME TO T_r6569;
CREATE  VIEW IF NOT EXISTS v_T_4751 AS SELECT c FROM T;
SELECT NTILE(0) OVER (PARTITION BY a ORDER BY a RANGE BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING EXCLUDE NO OTHERS) FROM T;
INSERT INTO T VALUES ('x', NULL, 1) ON CONFLICT(a) DO UPDATE SET a = excluded.a, b = excluded.b, c = excluded.c;
SELECT * FROM T;
CREATE TRIGGER IF NOT EXISTS trg_T_9509 AFTER UPDATE OF c ON T FOR EACH ROW BEGIN SELECT RAISE(IGNORE); END;
SELECT LAG(c, 2) OVER (ORDER BY c) FROM T;
ROLLBACK TRANSACTION TO SAVEPOINT sp5387;
RELEASE SAVEPOINT sp5387;
```

## Actual output

```sql
3.39.0 2022-05-10 23:28:12 764b71267e0b31ff7eaf2a0def7526a1a02dce4d5b456dea060d97ed342ealt1
```

## Expectation

```sql
3.51.1 2025-11-28 17:28:25 281fc0e9afc38674b9b0991943b9e9d1e64c6cbdb133d35f6f5c87ff6af38a88 (64-bit)
```

## Flag

```
-version
```