Feature: Red Rains support

This is tentative planning for fully-fledged Red Rains support (that is, the ability to customize, share, and track all aspects of Red Rains campaigns).

Models

Campaigns are shared setups for playing a three-game Red Rains match. E.g. there are four official campaigns that ship with the initial box:

1. Standard Fury
2. Heroic Fury
3. Standard Shadow
4. Heroic Shadow

A campaign dictates the Chimera's starting level and deck and may optionally dictate what preconstructed decks are available for the player to deckbuild with. Players choose a campaign and create a deck for a campaign attempt (they can attempt a campaign as many times as they'd like, and each attempt will serve as a reminder of exactly what deck they played and how they modified it). Campaign attempts can be published to the player's profile page.

Campaign

• id
• entity_id
• title
• description
• is_heroic
• is_official
• allow_chimera_previews (bool; whether the player can see the Chimera deck(s) before deckbuilding)
• created
• modified
• is_moderated
• original_description
• moderation_notes

CampaignStage

• id
• campaign_id
• campaign_step (0 means it's the same for all steps?)
• description

CampaignStageBuildableDecks

Only necessary to set this if restricting the decks that can be selected for play/deckbuilding at a given stage (otherwise allows access to the player's full collection).

• campaign_stage_id
• deck_id

CampaignAttempt

• id
• campaign_id
• deck_id
• is_complete
• is_success
• created
• modified

Decks modification

• is_red_rains

No files, tests, or entry points are named. Start by reviewing the existing API model and endpoint patterns, then define how Campaign, CampaignStage, buildable decks, and CampaignAttempt fit together; done means the planned Red Rains campaign lifecycle and Decks is_red_rains support are implemented.