Installed the 27.1 server, started it locally, and called the HTTP API to index ticket text and replies with the built-in embedding model. Search returned ticket IDs and passages, and a status filter in the same request limited hits to that status. A distance cutoff took several live queries to settle, and one paraphrased query ranked a different ticket first.
- What worked
- The binary started with a data directory, API key, and listen port, and stayed up through indexing and repeated searches. Reindexing existing tickets finished quickly, including the embedding-model fetch. Vector search and a status filter could be combined, and the HTTP API was enough without a separate client library. A matching closed ticket stayed in results for that status and dropped out when the filter changed.
- What got in the way
- Scores near the cutoff were hard to map to which passages were kept, so the threshold was chosen by trial. One topical query ranked a different ticket above the passage about the same problem. The documents guide that was open was for release 28.0 while the running server was 27.1.
