Add E2E test coverage for core mobile flows

[Emoji-dot]

Description

Linked Issue

Closes #

Type of Change

• 🐛 Bug fix (screen or component)
• ✨ New feature / screen
• 🎨 UI/UX improvement
• 📝 Documentation update
• 🔧 Chore / refactor / dependency update
• 🧪 Tests only

Changes Made

Screenshots / Recordings

iOS	Android

Test Evidence

pnpm test:run output:

Checklist

• I have read CONTRIBUTING.md
• This PR is linked to an open issue
• pnpm typecheck passes
• pnpm lint passes
• pnpm test:run passes — all tests green
• UI changes include a screenshot or screen recording
• New screens handle loading, empty, and error states
• NativeWind (Tailwind) classes used — no StyleSheet.create for new UI without justification
• No native modules added that break Expo Go compatibility (without prior discussion)
• No secrets, keys, or wallet credentials included
• .env.example updated if new environment variables were added
• Accessibility: interactive elements are keyboard-navigable and have accessibility labels

Additional Notes

Required Deliverables:
✅ E2E tests cover onboarding to profile navigation

Created:
01-onboarding-to-profile.yaml
✅ E2E tests cover manual wallet entry

Created:
02-wallet-entry.yaml
✅ E2E tests cover guild list and guild detail navigation

Created:
03-guild-navigation.yaml
✅ E2E tests cover access check success path

Created:
04-access-check-success.yaml
✅ E2E tests cover access check failure path

Created:
05-access-check-failure.yaml
✅ E2E tests cover reset app state

Created:
06-reset-app-state.yaml
✅ README documents how to run the E2E suite locally

Updated: README.md with complete E2E testing section
close #23

[Lakes41]

@Emoji-dot Thats pretty good
Do resolve conflicts

[Emoji-dot]

Done sir/ma