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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RVj8NFy821G3YhNf68PF6X
This commit is contained in:
Trenton Holmes
2026-08-18 11:05:04 -07:00
co-authored by Claude Sonnet 5
parent 9f0e4c6d89
commit 970730394e
-8
View File
@@ -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:
```