From 4d5f33b5830841ba72d6ebf648f71d7483d396e0 Mon Sep 17 00:00:00 2001
From: Trenton Holmes <797416+stumpylog@users.noreply.github.com>
Date: Mon, 15 Jun 2026 11:00:08 -0700
Subject: [PATCH] Tracks the tanvity update blocker

---
 .../specs/2026-06-15-search-query-translation-design.md   | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/superpowers/specs/2026-06-15-search-query-translation-design.md b/docs/superpowers/specs/2026-06-15-search-query-translation-design.md
index 00e34686f..17da750e2 100644
--- a/docs/superpowers/specs/2026-06-15-search-query-translation-design.md
+++ b/docs/superpowers/specs/2026-06-15-search-query-translation-design.md
@@ -77,6 +77,14 @@ aliasing, relative ranges, operator normalization, and the existing search tests
 validating the new pipeline). The old `_rewrite_*` regex helpers were left in place as
 delegation shims during the transition.
 
+Landed in 15 commits on `fix/search-query-translation` (`f1b92a493`..`816a078a4`):
+`_dates.py` extraction → partial-date helpers → scanner → comma resolution →
+scalar/range translation → field aliasing → relative ranges + operator normalization →
+`parse_user_query` wiring + delegation + tests. Key symbols in `_translate.py`:
+`scan`, `resolve_commas`, `translate_scalar`, `translate_range`, `translate_query`;
+constants `MULTI_VALUE_FIELDS`, `DATE_FIELDS`, `KNOWN_FIELDS`, `FIELD_ALIASES`,
+`NO_MATCH`, `OPEN_LO`, `OPEN_HI`.
+
 ## Phase 2 (pending — the thing being tracked)
 
 Replace the Phase-1 string workarounds with real `tantivy.Query` objects for date