@lacrous/omnicloud 0.2.24 → 0.2.25

package/dist/index.d.cts

@@ -812,10 +812,12 @@ interface StorageStats {
  * COMMITTING the stored object is being turned into a file record by exactly one
  *            request, which holds this state as an exclusive claim
  * COMPLETED  Telegram object stored and file record committed; result is final
+ * UNKNOWN    the Telegram write may have stored the object but the outcome is not
+ *            known; it is resolved, never silently re-uploaded
  * FAILED     Telegram write definitively failed; the operation may be retried
  *            under a new id
  */
-type UploadOperationStatus = "PENDING" | "UPLOADING" | "COMMITTING" | "COMPLETED" | "FAILED";
+type UploadOperationStatus = "PENDING" | "UPLOADING" | "COMMITTING" | "UNKNOWN" | "COMPLETED" | "FAILED";
 
 /**
  * Repository interfaces. The application depends on these, not on a specific
@@ -1277,15 +1279,6 @@ interface FileUploadInput {
     onProgress?: (progress: TransferProgress) => void;
     signal?: AbortSignal;
 }
-/**
- * File metadata operations. Every method verifies ownership: records
- * belonging to other users are reported as missing.
- *
- * Reliability rules honored here:
- *  - metadata is written only after the storage upload succeeds;
- *  - permanent deletion removes the remote object before the metadata;
- *  - client-supplied ownership is never trusted (userId is server-derived).
- */
 declare class FileService {
     private readonly files;
     private readonly folders;

package/dist/index.d.ts

@@ -812,10 +812,12 @@ interface StorageStats {
  * COMMITTING the stored object is being turned into a file record by exactly one
  *            request, which holds this state as an exclusive claim
  * COMPLETED  Telegram object stored and file record committed; result is final
+ * UNKNOWN    the Telegram write may have stored the object but the outcome is not
+ *            known; it is resolved, never silently re-uploaded
  * FAILED     Telegram write definitively failed; the operation may be retried
  *            under a new id
  */
-type UploadOperationStatus = "PENDING" | "UPLOADING" | "COMMITTING" | "COMPLETED" | "FAILED";
+type UploadOperationStatus = "PENDING" | "UPLOADING" | "COMMITTING" | "UNKNOWN" | "COMPLETED" | "FAILED";
 
 /**
  * Repository interfaces. The application depends on these, not on a specific
@@ -1277,15 +1279,6 @@ interface FileUploadInput {
     onProgress?: (progress: TransferProgress) => void;
     signal?: AbortSignal;
 }
-/**
- * File metadata operations. Every method verifies ownership: records
- * belonging to other users are reported as missing.
- *
- * Reliability rules honored here:
- *  - metadata is written only after the storage upload succeeds;
- *  - permanent deletion removes the remote object before the metadata;
- *  - client-supplied ownership is never trusted (userId is server-derived).
- */
 declare class FileService {
     private readonly files;
     private readonly folders;

package/dist/index.js

@@ -1437,6 +1437,13 @@ function uploadRequestFingerprint(input) {
 }
 
 // ../core/src/services/file-service.ts
+function connectionCausedFailure(error) {
+  if (error instanceof TelegramConnectionError) return true;
+  if (error instanceof UploadFailedError) {
+    return error.details instanceof TelegramConnectionError;
+  }
+  return false;
+}
 var FileService = class {
   constructor(files, folders, engineFor, activity = noopActivityRecorder, operations = null, log = null) {
     this.files = files;
@@ -1513,8 +1520,9 @@ var FileService = class {
       await operations.update(op.id, { status: "COMPLETED", fileId: record.id });
       return record;
     } catch (error) {
+      const status = connectionCausedFailure(error) ? "UNKNOWN" : "FAILED";
       await operations.update(op.id, {
-        status: "FAILED",
+        status,
         error: error instanceof Error ? error.message.slice(0, 200) : "upload failed"
       });
       throw error;