Files
nicholasDxy 595d685e39 wps: handle JSON parse failures with concrete recovery steps
Issue auto-fyi #168: sheets_info surfaced the raw underlying error
'Expecting value: line 1 column 1 (char 0)' to the agent. The error
text is the Python json parser's complaint about an empty/non-JSON
input — completely opaque to anyone who hasn't traced it. The agent
saw it and had no recovery path.

Root cause: when the upstream Kdocs API returns an empty body, an
HTML error page, or a redirect, the CLI tries to json-decode the
response and the parser fails at byte 0. This is consistent with
upstream auth/permission/file-not-found responses rather than a CLI
bug.

Added a row to the 错误速查 table mapping this error shape to an
ordered recovery checklist:
  1) kdocs-cli auth status — confirm token is still valid (some token
     failure modes don't trigger the 400006 path)
  2) re-verify file_id via drive search / wps file_info
  3) confirm the current account has read access (open in browser)
  4) 3-5s retry once for transient network blips; report to user
     if still failing

Bump version 2.4.12 -> 2.4.13.

Co-authored-by: Starchild <noreply@iamstarchild.com>
2026-05-27 13:01:17 +00:00
..