v1.13.6

Added

• Telemetry uploads are now durable. The dashboard upload was fire-and-forget
  with no retry and an ignored HTTP status, so a transient failure or a process exit
  mid-flight silently dropped a row that was recorded locally. Each report.json row
  now carries an upload-tracking flag: a confirmed 2xx — or a permanent 4xx
  rejection that retrying can't fix — settles the row, while a transient failure
  (5xx / 429 / network) leaves it pending. On startup the server resends any
  still-pending row. Rows written before this change are left untouched (never
  resent), so there is no mass re-upload of history. Rows the dashboard would
  reject — chiefly an honest negative saving where a focused view costs more than
  the bare relevant-code baseline (TokensWithTool > TokensWithoutTool) — are
  skipped client-side and settled locally rather than sent for a guaranteed 400.

Fixed

• NOT FOUND rows no longer log a bogus 0% saving. A focus miss returns a
  small members outline (plus the partial/inherited hint), not the whole file,
  yet telemetry logged whole-file → whole-file (0% saved). It now logs
  whole-file → actual response, crediting the real saving versus the model
  reading the whole file to discover the member isn't there. Applies to the
  NOT FOUND paths of focus_method, focus_multiple_methods, focus_type,
  and focus_callers.