v1.6.0

[1.6.0] — 2026-08-12

Search-index correctness and ranking (docs/plans/search-index.md). Schema: 21 —
migration V21 rebuilds nodes_fts.

Fixed

• B80 — 29% of the account was missing from the search index. node_is_indexable_tx
  required a null-parent ancestor, which only the My Files root has, so every node under a
  device folder was dropped from nodes_fts on its first upsert after the v16 backfill
  (2,705 of 9,252 nodes on the account this was diagnosed against). The rule now matches the
  backfill, migration V21 replays it, nodes under a trashed folder stay out, and the walk is
  depth-capped.
• B81 — the prompt labelled every Drive hit "My files", including device folders; pin
  rows also took is_dir from Pin::recursive.
• B82 — a parent_uid cycle hung the daemon on any short search: the recursive CTEs in
  path_of and the pin walk use UNION ALL, which does not deduplicate. path_of is now
  depth-capped at 256 and returns the truncated path.

Changed

• Local search ranking: whole-query prefix matches get their own lane (newest first) ahead
  of trigram rank, which on a home directory full of dependency trees was burying the
  obvious answer — 73% of the 500 best-ranked candidates for "test" came from one Go module
  cache. The single-character lane, which recovers a typo that destroys every trigram, stays
  behind it.