Add a Maestro E2E test for cold-start deep linking

[Lakes41]

Difficulty: Intermediate
Type: test

Background
The README explicitly documents "Cold Start Support" — deep links working when the app isn't already running, launching and navigating to the correct screen — and the existing Maestro E2E suite already covers onboarding, wallet entry, guild navigation, and access-check flows.

Problem
The listed E2E coverage doesn't mention a cold-start deep-link scenario specifically, meaning this documented behavior isn't currently protected by an automated test and could regress silently.

Expected outcome
A new Maestro flow under .maestro/ force-stops the app, launches it via a guild-detail deep link (and, separately, an access-check deep link), and asserts the app lands on the correct screen with the correct data pre-filled.

Suggested implementation

• Add a new .maestro/0X-cold-start-deep-link.yaml flow using Maestro's stopApp/launchApp with a deep-link argument to simulate a true cold start.
• Cover both supported link types (guild detail and access check) as separate test cases or steps.
• Assert the resulting screen shows the expected guild/resource identifiers from the link.
• Update .maestro/README.md to document the new flow per existing conventions.

Acceptance criteria

• New flow(s) added covering cold-start guild-detail and access-check deep links
• Test correctly force-stops the app before launching via the link (true cold start, not warm)
• .maestro/README.md updated
• Flow passes locally via maestro test .maestro/

Likely affected files/directories

• .maestro/ (new flow)
• .maestro/README.md

[EngrEOOnoja]

I'd like to take this on. I'll add a new Maestro flow that force-stops the app and launches it via both deep-link types (guild detail and access check), asserting the app lands on the correct screen with the right data prefilled, and update .maestro/README.md to document the new flow per existing conventions

[grantfox-oss]

🦊 GrantFox — @EngrEOOnoja has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #239)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[EngrEOOnoja]

I'd like to take this on. I'll add a new Maestro flow that force-stops the app and launches it via both deep-link types (guild detail and access check), asserting the app lands on the correct screen with the right data pre-filled, and update .maestro/README.md to document the new flow per existing conventions.