2 Commits

Include renames

Author	SHA1	Message	Date
asepharyana	24dfb1c6b1	fix: fail-fast guard TELEGRAM_CHUNK_SIZE_BYTES <= 19MB (Telegram getFile limit 20MB) ... Chunk parts > 19MB are stored to Telegram but getFile cannot resolve files over 20MB ('Bad Request: file is too big'), making every part undownloadable (prod bug 2026-08-01: 48MB chunk -> download 500). - src/env.ts: reject TELEGRAM_CHUNK_SIZE_BYTES > 19922944 at startup (log error + throw), default changed 20MB -> 19MB - src/shared/utils/validation.ts: TELEGRAM_CHUNK_SIZE_MAX_BYTES constant; asSafeChunkSize now enforces the max at runtime (covers S3 multipart parts too) - test/env.test.ts: unit tests + subprocess fail-fast tests (48MB rejected, 19MB accepted) - test/helpers/setup-env.ts: pin safe chunk size so a stale .env can't break the suite - .env.example + CLAUDE.md: document the 20MB getFile limit	2026-08-01 13:06:42 +07:00
Claude	ad917f6675	refactor: dedup dead code, shared utils, conditional headers helper ... - Extract shared utils: asSafeChunkSize (validation.ts), S3 detection (s3-detection.ts) - Remove dead _handleMaybeS3Root from index.ts and routes/index.ts - Remove dead _asArray from file-controller.ts - Consolidate maybeCompressChunk into shared compress.ts - Extract checkConditionalHeaders helper, remove ~120 lines dupe in s3-controller - Remove 500+ lines dead code from s3-object.ts (unused use cases + helpers) - Delegate upload-file.ts chunked path to ChunkedStorage, remove dupe - Fix broken dynamic import in file-controller.ts → proper DI - Fix test/files.test.ts import path and mocks [skip ci]	2026-07-29 16:39:52 +07:00