changedInput schema / properties / chunks_per_file / description
Previous value: -"Maximum number of sections to return per file\n(default 2). Set to 1 to get only the top-ranked section\nper file. Must be >= 1."New value: +"Maximum sections per note, at least 1; omit for the server\ndefault."
changedInput schema / properties / filters / description
Previous value: -"Filter by indexed frontmatter field values, e.g.\n{\"cluster\": \"craft\", \"tags\": \"pacing\"}. Only fields listed\nin indexed_frontmatter_fields (see 'stats') can be filtered.\nMultiple filters are ANDed. For list fields (e.g. tags),\nthis checks membership — {\"tags\": \"pacing\"} matches any\ndocument where \"pacing\" appears in the tags list. On an OKF\nbundle three keys carry OKF semantics: status (\"draft\"/\n\"stable\"/\"deprecated\"; \"stable\" also matches notes without\na status field), stale (\"true\"/\"false\" — stale_after\nreached), and trust_tier (\"unverified\"/\"machine-confirmed\"/\n\"human-reviewed\"); \"type\" filters normally, e.g.\n{\"type\": \"Playbook\", \"stale\": \"false\"}."New value: +"Frontmatter values to match, all of them, such as `{\"tags\": \"pacing\"}`;\nkeys come from indexed_frontmatter_fields in stats, and a list field\nmatches when it holds the value. On an OKF bundle, status (draft, stable\nor deprecated; stable includes notes with none), stale (`\"true\"` or\n`\"false\"`) and trust_tier (unverified, machine-confirmed or\nhuman-reviewed) filter too."
changedInput schema / properties / folder / description
Previous value: -"Restrict to documents under this folder path (e.g.\n\"Journal\"). Must match a value from 'list_folders'.\nUse folder=\"\" for root-level (top-level) documents only."New value: +"Only notes under this folder, a value from list_folders; `\"\"` for\ntop-level notes only."
changedInput schema / properties / limit / description
Previous value: -"Maximum results to return (default 10)."New value: +"Maximum notes to return (default 10)."
changedInput schema / properties / mode / description
Previous value: -"\"keyword\" uses FTS5/BM25 for exact terms. \"semantic\" uses\nvector similarity (requires embeddings). \"hybrid\" fuses both\nvia reciprocal rank fusion — best quality when available.\nOmit it (the default) to follow the vault's configured\nDEFAULT_SEARCH_MODE, which ships as \"auto\": hybrid where\nembeddings exist, keyword otherwise. Any configured default\ndegrades to \"keyword\" when it needs embeddings the vault\nlacks; an explicit \"semantic\"/\"hybrid\" still errors when\nunconfigured."New value: +"Omit for the best mode this vault serves. `\"keyword\"` suits exact terms,\noperators and filenames; `\"semantic\"` matches meaning only; `\"hybrid\"`\ncombines both. `\"semantic\"` and `\"hybrid\"` need semantic_search_available\nfrom stats."
changedInput schema / properties / query / description
Previous value: -"Natural language or keyword query string."New value: +"Words to match or a natural-language question."
changedInput schema / properties / snippet_words / description
Previous value: -"Width of the snippet window in words. Omit to use\nthe server default. Set to 0 to return full chunk content.\nUse read(path, section=heading) for full section recovery."New value: +"Snippet width in words; omit for the server default, 0 for\nwhole sections. read with section set to a result's heading returns that\nwhole section."