Read & Say OK

Find functional bugs that affect users’ basic operations. Ignore code optimization, refactoring, naming, formatting, deprecated APIs, architecture preferences, and cosmetic UI issues.

Focus on these bug patterns:

- Create, edit, delete, view, list, search, filter, refresh, pagination, payment, and status-update failures.
- Search or filter values used on page 1 but lost during pagination or refresh.
- Pagination state not reset after changing filters or searches.
- Page numbers incremented before a failed request and not restored.
- Selected dates, categories, payment modes, statuses, amounts, or business IDs not included correctly in API requests.
- Validation checking the wrong variable or allowing invalid required fields.
- Validation displaying an error but still submitting the form.
- Successful operations incorrectly shown as failures, or failed operations shown as successful.
- Loading or button-busy states that are not cleared after empty responses, validation errors, API errors, timeouts, or exceptions.
- Empty successful responses leaving screens stuck loading.
- Forms using current dates or default values instead of user-selected values.
- Create/edit/delete operations calling the wrong endpoint or sending the wrong record ID.
- Navigation closing the wrong page/dialog, navigating before completion, or failing to refresh the originating screen.
- Stale requests updating a disposed page, another business, or another record.
- Duplicate submissions caused by repeated taps.
- List refreshes that remove active filters or mix unrelated records.
- Incorrect financial, quantity, tax, EMI, salary, balance, or inventory calculations.
- Missing validation before destructive or financial operations.
- Null assertions or parsing that can crash during normal API responses.
- UI controls that appear functional but only update local state without saving.
- Permission checks that expose an operation users cannot complete, or hide an operation they should have.
- Similar defects already present in related modules or duplicated legacy/current implementations.

Review the complete flow:

1. Routes and navigation parameters.
2. Page widgets and user actions.
3. Controllers and state management.
4. Validation and calculations.
5. API service endpoints, parameters, and request bodies.
6. Response, error, timeout, empty-data, and loading-state handling.
7. Refresh and caller-result behavior.
8. Existing tests and missing behavioral coverage.

For every confirmed bug, report:

[Module Name]
- Priority: P0, P1, P2, or P3.
- Short title.
- Exact file and tight line range.
- User action that triggers it.
- Actual behavior.
- Expected behavior.
- Technical cause.
- Why it affects a basic user operation.
- Whether the same pattern exists elsewhere in the module.

Only report high-confidence, reachable bugs supported by the code. Do not report dead code unless it is connected to an active UI action. Do not change any files unless explicitly asked.

Ready to copy.