## 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
.dbconfig fk off
CREATE TABLE main.[t1](a, b, c);
-- sqrt({v})

INSERT INTO t1 VALUES(if(json_patch(CAST(0.0 AS CHARINT), 0.0), 1, 1),'aaa','bbb');
INSERT INTO t1 SELECT * FROM t1;
INSERT INTO t1 VALUES(2,'ccc','ddd');
SELECT DISTINCT a AS x, b||c AS y FROM t1 WHERE NOT NOT (y IN ('aaabbb','xxx')) ;
SELECT DISTINCT a AS x, b||c AS y FROM t1 WHERE +y='aaabbb';
CREATE VIRTUAL TABLE t0 USING fts4("x", "y", "z");
CREATE TABLE T (
  a FLOAT,
  b TEXT,
  c REAL
);
INSERT INTO T VALUES ('a','b',5.0), ('a','c',5.0), ('b','d',-8.25);
SELECT a,b,c,
RANK() OVER (PARTITION BY a ORDER BY c DESC) AS d FROM T;
DROP TABLE t0;
CREATE TEMPORARY  VIEW IF NOT EXISTS v_t1_6630 AS SELECT c FROM t1;
ANALYZE;
UPDATE t1 SET a = '' WHERE 1 RETURNING *;
ANALYZE;
SELECT TOTAL(c) FROM T;
ALTER TABLE t1 RENAME TO t1_r682;
VACUUM;
CREATE  VIEW IF NOT EXISTS v_T_9629 AS SELECT c FROM T;
ALTER TABLE T RENAME TO T_r2076;
ALTER TABLE T DROP COLUMN c;
UPDATE T SET b = b + 1 WHERE rowid = 1 RETURNING *;
SELECT LAST_VALUE(b) OVER (PARTITION BY b ORDER BY b ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW EXCLUDE TIES) FROM T;
```

## 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
```

