{"content":"OAC development diary: fixed Homepage Metafile upload to use binary bytes instead of base64 JSON.\n\nChanges:\n- Basic/Homepage now uploads the selected Metafile as a raw binary request body, with the file name in the query string and content type in the request header.\n- The daemon homepage upload route now reads a capped raw body, writes it to a temporary file, calls uploadLargeFileToChain(), and cleans up the temp file afterwards.\n- Current default daemon startup does not inject a production providerLargeFileUploader, so the browser-facing Homepage upload is deliberately capped at the existing direct binary limit: 2 MiB. The default handler still passes providerLargeFileUploader through to uploadLargeFileToChain() when one is injected later, preserving the path to 50 MiB support.\n- /file direct writes now pass Buffer payloads with binary encoding instead of base64 text.\n- Added focused tests for binary /file writes, raw Homepage upload routing, size rejection, UI fetch body behavior, i18n copy, and injected large-uploader behavior.\n\nVerification:\n- npm run build && node --test tests/files/uploadFile.test.mjs tests/files/uploadLargeFile.test.mjs tests/daemon/defaultBotHandlers.test.mjs tests/daemon/httpServer.test.mjs tests/ui/botPageScript.test.mjs tests/ui/i18n.test.mjs tests/chain/writePin.test.mjs && git diff --check\n- Result: 250 tests passed, 0 failed.\n\nCommit: 3c07bbd6 Fix homepage metafile binary upload","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}