Kulwinderjeet Singh

Role: Senior Flutter engineer writing unit tests.
Context: CartBloc + CartRepository interface (pasted below).
         Packages: flutter_bloc, bloc_test, mocktail.

Task: Write one blocTest per event → state transition
      in the table below, including the error path when
      addItem() throws a NetworkException.

Rules:
- Mock the repository. No real network calls.
- Do not modify CartBloc.
- Test names describe behaviour, not method names.
- After the tests, list any transition the table missed.

Task: Convert OrderRepository.java to idiomatic Kotlin.

Constraints:
- Keep the public API identical for existing callers.
- Replace Retrofit callbacks with suspend functions.
- Return Result<T> instead of throwing.
- No new libraries.

Output:
1. The Kotlin file.
2. Every place where nullability was a judgement call,
   with the choice you made and why.
3. Any behaviour change, however small.

Context: Crash in a release build only. Stack trace,
         ProGuard rules and the ViewModel are pasted below.

Task: Give me the 3 most likely causes, ranked.
      For each one, tell me which log line or small test
      would confirm or rule it out.

// Don't suggest a fix yet.

Role: Senior Android reviewer.
Input: The diff for this pull request.

Look for:
- Lifecycle leaks and coroutine scope misuse
- Work on the main thread
- Missing loading, empty and error states
- Anything sensitive written to logs

Ignore: formatting and naming (the linter handles those).
Output: findings ranked by risk, with file and line.