Make saved-deck event submission discoverability clearer in Phoenix

Source: Featurebase post 69ef1822c1bc08cddec3202d ("Additions to the decks feature") from Simeon N — https://cardeio.featurebase.app/p/additions-to-the-decks-feature

Problem Players who already maintain decks on their profiles cannot easily tell how to use those saved decks for a specific event. The current feedback is not asking for a deckbuilder from scratch; it is saying the saved-deck → event flow feels missing or too hidden.

Why this is likely a real gap

• Existing shipped work HYD2-4689 says players can select from saved decks when submitting to eligible events.
• New player feedback says: "It would be great to be able to assign decks we've added to our profiles to specific events. If that's actually possible, it isn't clear enough."
• That points to a discoverability / product-communication problem even if the underlying capability already exists.

Who has the problem Players using Phoenix / Player Networks who keep saved decks on their profile and register for events where deck submission is relevant.

Status quo / workaround Users have to guess where event-specific deck attachment happens, or assume they need to rebuild / re-enter the deck manually.

Requested outcome Make it obvious in the event flow when a player can submit / attach one of their saved decks to that event, and make the missing-state clearer when an event does not currently allow or require deck submission.

90/10 direction Clarify the event-detail entry point and copy around deck submission rather than inventing a new deck-management model.

Success criteria

• A player on an eligible event can clearly tell they can select from saved decks.
• The UI distinguishes "this event does not use deck submission" from "you have not submitted yet".
• A player can attach or update a saved deck for the event without guesswork.

Adjacent, not duplicate

• HYD2-4689 — shipped saved-deck submission capability
• SENG-70 — TO-facing deck-submission copy/behavior confusion
• HYD2-5548 / HYD2-6659 — event-published deck browsing IA, not the player submission/discoverability problem

Evidence

• Featurebase upvotes: 1
• Category: Player Networks