docs: what the first live search turn left open

Two things the deploy did not settle: the turn was slow off a cold start and
that number is not yet trustworthy, and the personal boundary still has never
run on the box.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
kami
2026-08-02 02:46:05 +04:00
parent 587f1e6a07
commit 7079a240f7
+18
View File
@@ -260,6 +260,24 @@ Found live on 2026-08-01, not fixed. Everything else in that file was stale.
- **`safeKey` drops Cyrillic**, so Russian calendar events on one day collide.
Vikunja #443 with three fix options. It is a migration, not a patch.
## Open after the 02-08-2026 deploy
SearXNG runs on homesrv at `http://searxng:9563`, on `maven_default`, and the
rebuilt `mavend` wires it. "кто написал войну и мир?" now routes to query, takes
4 results off the search, and answers Толстой with the lookup opener. Two things
that turn left unsettled.
- **The turn was slow, and nobody knows yet whether that is real.** Route 7s,
search 1s, phrasing 15s. The p50 in `ROUTING-EVAL-31-07-2026.md` is 825ms. It
was the first turn after a cold start with the model still warming, so it
proves nothing either way. Re-run the same question warm before treating it as
a regression. Do not plan latency work off this number.
- **The personal boundary has never run live.** `queryPersonal` in
`cmd/mavend/actions_query.go` stops a question about him from reaching
SearXNG. The question above is not one, so only tests cover it. Ask something
about him on the deployed box and confirm from the log that no `voice: search`
line appears for it.
## Sequence
1. Failure taxonomy over the fixture.