fix(editor): the x2t proxy must not fetch a document as if it were a URL

[chaxus]

Found while reviewing today's changes.

Guard 14 (#224) turns whatever the vendor passes into bytes before sending it to the x2t worker. For strings it fetched unconditionally. x2t_helper's own handleFileData does not — it sorts strings into DataURL / BlobURL / FileURL / HttpURL / URL and String, and that last case is not an error:

case 'String':
  resolve(new TextEncoder().encode(data));

So a document handed over as text — the empty-document template the offline patch uses (DOCY;v5;7372;…), or the latin1 DOCY form #113 was about — would have been requested as a relative URL instead of converted.

Fix

Strings that are not locations cross untouched, and the worker's own handleFileData decides, exactly as it did before conversion moved out of the frame. Same rule for media entries.

looksLikeUrl is exported for the unit test on purpose: it mirrors a classifier in vendor code that this proxy has to agree with, and getting it wrong turns a document into a request — pinning it directly is cheaper than reaching it through a conversion.

Re-ran the conversion-heavy specs (multi-sheet xlsx, CSV round trip, GBK CSV, PDF annotate + save, CJK PDF export, the offline seam): all green.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MKNHFQ1kek1cHeqhbH37Pk

[cloudflare-workers-and-pages]

Deploying document with    Cloudflare Pages

Latest commit:	20b4711
Status:	✅  Deploy successful!
Preview URL:	https://73b563f4.document-7hm.pages.dev
Branch Preview URL:	https://fix-x2t-proxy-string-input.document-7hm.pages.dev

View logs