From 970730394ee84a66e84aaacd2ebea8a33ba3d33b Mon Sep 17 00:00:00 2001 From: Trenton Holmes <797416+stumpylog@users.noreply.github.com> Date: Mon, 17 Aug 2026 21:12:59 -0700 Subject: [PATCH] docs: drop *_id field-removal note from usage.md These prefixes were never documented public API (undocumented internal fields the old KNOWN_FIELDS happened to accept), so their removal isn't a user-facing regression worth calling out in usage.md. The behavior is still covered by test_acceptance.py's TestUnregisteredIdFieldFoldsToLiteralText. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01RVj8NFy821G3YhNf68PF6X --- docs/usage.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/usage.md b/docs/usage.md index ed6b7e64d..832ad1f1a 100644 --- a/docs/usage.md +++ b/docs/usage.md @@ -915,14 +915,6 @@ original_filename:invoice.pdf - `original_filename` matches the filename of the document as originally consumed. -Older, undocumented `*_id` field prefixes (`tag_id`, `owner_id`, `viewer_id`, -`correspondent_id`, `document_type_id`, `storage_path_id`, `type_id`, and -`path_id`) are no longer recognized advanced-search fields. A query using one -of them (e.g. `tag_id:5`) does not error; it silently falls back to a literal -text search for that string, which will almost never match real document -content. Use the corresponding named field (`tag`, `correspondent`, -`document_type`, etc.) instead. - Matching inexact words: ```