Use mutations for manual access checks

[Lakes41]

Difficulty: Hard

Type: Refactor

Summary

Change the access check flow from query-driven execution to mutation-driven execution. Manual user-triggered checks should behave like actions, not passive cached queries.

Current Behaviour

app/access-check.tsx stores checkParams in local state and calls checkAccess with either the real params or an empty fallback object. The underlying hook uses useQuery and relies on enabled to avoid running with empty values.

Expected Behaviour

Access checks should run only when the user submits the form, expose clear pending and result states, and avoid stale query results when inputs change.

Suggested Implementation

Replace the access check query wrapper with a useMutation-based hook. Reset the previous result when input changes after a completed check. Keep form validation separate from the network action.

Files or Areas Likely Affected

• src/features/access/useAccessCheck.ts
• app/access-check.tsx
• src/components/AccessStatusCard.tsx
• tests/

Acceptance Criteria

• Access checks run only after the user presses the check button
• Previous results are cleared or marked stale when inputs change
• Loading and error states come from mutation state
• Failed checks do not leave stale success results visible
• Tests cover success, failure, loading, and input-change reset behaviour
• The implementation remains compatible with future QR-code input

Additional Notes

This issue should complement, not duplicate, the existing form validation issue.

[YfengJ]

I would like to apply for this issue.

If assigned, my plan is to convert the manual access-check flow from query-triggered state to a focused useMutation hook, keep form validation separate from the network action, clear the previous result when inputs change after a completed check, and update app/access-check.tsx so checks only run on submit. I would keep the scope limited to the access-check path and validate with the project tests/lint plus a focused check of pending, success, error, and input-change reset states.

[David-patrick-chuks]

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.
My PR will be submitted in under 10hours.