Real per-chunk upload progress (web + native, 0.6.11)

[ehsan6sha]

Real per-chunk upload progress so apps can show a true percentage instead of a time-based estimate — on web + native (iOS/Android/Windows). Workspace 0.6.10 → 0.6.11.

SDK (fula-client)

The chunked upload paths now emit cumulative bytes the moment each content chunk's PUT lands (count-proportional: completed_chunks · total / N):

• Web/chunked: put_object_flat_with_progress.
• Native fresh: put_object_encrypted_resumable_with_cancel_and_progress.
• Native resume: resume_upload_with_cancel_and_progress — seeds the counter with the already-uploaded chunk count, so the bar continues mid-way and still reaches 100% even though only the remaining chunks are re-PUT.

The existing public put_object_encrypted_resumable_with_cancel / resume_upload_with_cancel keep their signatures (external test callers depend on them) — they're now thin wrappers delegating to the *_and_progress bodies with progress = None. Progress is an Option<Arc<dyn Fn(u64,u64)+Send+Sync>>; emitted from inside the spawned chunk tasks via a shared AtomicU64 so it reflects real concurrent completion order. No change to the upload/crypto data path — only added emit calls + new wrapper methods.

Flutter bridge (fula-flutter)

Progress is surfaced by polling an opaque handle, mirroring the proven CancelHandle / MasterHealthEvent pattern — not StreamSink (stream-handler codegen has never been exercised through the external publish pipeline; can't verify locally):

• ProgressHandle + create_progress_handle() + poll_progress() -> UploadProgress.
• put_flat_with_progress (web + native), put_flat_resumable_from_path_with_progress + resume_flat_upload_from_path_with_progress (native, take &CancelHandle + &ProgressHandle).

Apps poll poll_progress on a timer while the upload future runs. The handle's Arc lifecycle is the cleanup (no global registry, no leak on early-return/panic).

Tests

• chunk_put_progress.rs — web path reaches 100% (max == total).
• resumable_put_progress.rs — native fresh (max == total) + resume seed-correctness (max == total is reachable only when the counter is seeded; the partial manifest is produced by a real failed attempt, not hand-built — F1 BAO rejects synthetic manifests).
• upload_progress_real_server_e2e.rs — live-master E2E for both paths (3 MiB multi-chunk, asserts progress reaches 100% + byte-identical round-trip).
• Full fula-client --features test-fault-injection suite green (F1 nonce-reuse ordering, resumable_forest_persistence, v2 bridge tests unperturbed by the refactor).

Compile gates

cargo check green: fula-flutter native (the Send+Sync gate for the callback across the 16 spawned chunk tasks), fula-client wasm32, fula-flutter wasm32.

Consumer note (FxFiles)

SDK reports content 0 → total; cumulative hits total when the last chunk's PUT returns, before the index PUT + forest-flush tail — UIs should cap at <100% until their own completion signal (reuse the mobile clamp).

🤖 Generated with Claude Code