0.32.0

Added

• zm meetings import reads zoom-searcher's .txt transcripts. YYYY-MM-DD_HHMM_topic.txt files with a header
  are imported: the header's title and start replace the file name's, its Zoom meeting ID becomes the series key
  (so the API's copy of the same meeting can join it once cli-core merges them), and its speakers become
  participants of that meeting only. A .txt and a .vtt with one name are one meeting; the .txt is read. A
  .txt not named like a transcript is skipped. The import result names the zone file times were read in
  (timezone), and zm meetings import --help shows the file names and that zone.
• Meeting search widens garbled words and reads the query language (cli-core 0.380.0): «риелтор» also finds
  «реелтора»; OR, (groups), -word, "phrases", "a b"~N, exact: and from:"Name". See
  search.

Changed — may break callers

• A search query is now syntax, and a date alone is a local day (cli-core 0.370.0 → 0.380.0, cli-base 0.49.0).
  :, (, ", - and AND/OR/NOT in zm search meetings mean query syntax; a query of punctuation alone
  is an error. --since-time 2026-10-01 starts at local midnight, not UTC midnight; write a time with Z for UTC.
  Search cursors from earlier versions are refused; search again.
• A transcript file name's time is read in this computer's zone unless files.timezone is set. It was read in
  UTC, so a 2026-10-21_1000_… file from Madrid was stored two hours late. A config that names a zone keeps it;
  saving another setting no longer writes UTC into files_timezone. Storage stays UTC.
• A Zoom time with no zone is read in this computer's zone, marked, and named in a warning. Zoom documents such a
  time as local. It was read in whatever zone the process had, without a word. Now it is read in the computer's IANA
  zone (UTC when daylight saving skips or repeats that hour), the meeting, participant or summary gets
  metadata.issues: ["time_without_zone"], and the command warns once on stderr: "N Zoom times had no zone; read in
  and marked time_without_zone". A malformed time is still refused. Recording times have no metadata, so
  they are counted in the warning only.
• zm recordings list ends "today" on the local day, not the UTC day. Without --until-time the list ended on
  the UTC date, so in Madrid between midnight and 02:00 it stopped at yesterday. It now takes today in the computer's
  zone, or in the new --timezone, and meta.timezone names it.
• Text output that shows a time ends with times in UTC. JSON, JSONL and MCP are unchanged: UTC, ending in Z.

Fixed

• A .txt transcript's time is read as the end of its recording. zoom-searcher named files and wrote Дата:
  from the Zoom portal's "created" time, which is when the recording ended. A .txt meeting now starts that time
  less its last line's offset and ends at it, so it lines up with the API's copy of the same meeting.