WP-15: Deployment and Smoke Testing #80

Open
opened 2026-03-12 20:57:13 +00:00 by cal · 0 comments
Owner

Description

Deploy all Phase 1 changes to dev environment and execute full smoke test. No backfill needed — evolution starts fresh at Season 11. Cards get evolution_card_state records organically via pack opening hook (WP-10) or post-game callback (WP-13).

Repo: All three
Phase: 1d (Deployment)
Dependencies: All WPs (WP-01 through WP-14)
Complexity: M

Deployment Sequence

  1. Database (API server):

    • Run SQL migration (WP-04)
    • Seed evolution tracks with formulas + thresholds (WP-03)
    • Deploy API with new endpoints (WP-06, WP-07, WP-08, WP-10)
    • Verify endpoints respond correctly
  2. Bot deployment:

    • Deploy bot with /evo status (WP-11)
    • Deploy bot with tier badge (WP-12)
    • Deploy bot with post-game hook (WP-13)
    • Deploy bot with notifications (WP-14)

Smoke Test Checklist

  • GET /v2/evolution/tracks returns 3 tracks with formula and threshold fields
  • GET /v2/teams/{team_id}/evolutions returns states with current_value
  • GET /v2/evolution/cards/{card_id} returns correct state
  • /evo status in Discord shows paginated evolution progress
  • Card embed shows tier badge for cards with tier > 0
  • Play a game in dev environment
  • After game: player_season_stats updated with game's stats
  • After game: evolution_card_state.current_value increased
  • If formula value crosses threshold: current_tier advances + notification sent
  • Open a pack: new card gets evolution_card_state created
  • POST /v2/evolution/cards/{card_id}/evaluate force-recalculates correctly
  • Evolution processing failure does not break game completion
  • Evolution processing failure does not break pack opening

Plan reference: docs/prd-evolution/PHASE1_PROJECT_PLAN.md WP-15

## Description Deploy all Phase 1 changes to dev environment and execute full smoke test. No backfill needed — evolution starts fresh at Season 11. Cards get `evolution_card_state` records organically via pack opening hook (WP-10) or post-game callback (WP-13). **Repo:** All three **Phase:** 1d (Deployment) **Dependencies:** All WPs (WP-01 through WP-14) **Complexity:** M ## Deployment Sequence 1. **Database (API server):** - Run SQL migration (WP-04) - Seed evolution tracks with formulas + thresholds (WP-03) - Deploy API with new endpoints (WP-06, WP-07, WP-08, WP-10) - Verify endpoints respond correctly 2. **Bot deployment:** - Deploy bot with `/evo status` (WP-11) - Deploy bot with tier badge (WP-12) - Deploy bot with post-game hook (WP-13) - Deploy bot with notifications (WP-14) ## Smoke Test Checklist - [ ] `GET /v2/evolution/tracks` returns 3 tracks with formula and threshold fields - [ ] `GET /v2/teams/{team_id}/evolutions` returns states with `current_value` - [ ] `GET /v2/evolution/cards/{card_id}` returns correct state - [ ] `/evo status` in Discord shows paginated evolution progress - [ ] Card embed shows tier badge for cards with tier > 0 - [ ] Play a game in dev environment - [ ] After game: `player_season_stats` updated with game's stats - [ ] After game: `evolution_card_state.current_value` increased - [ ] If formula value crosses threshold: `current_tier` advances + notification sent - [ ] Open a pack: new card gets `evolution_card_state` created - [ ] `POST /v2/evolution/cards/{card_id}/evaluate` force-recalculates correctly - [ ] Evolution processing failure does not break game completion - [ ] Evolution processing failure does not break pack opening **Plan reference:** `docs/prd-evolution/PHASE1_PROJECT_PLAN.md` WP-15
cal added this to the Card Evolution Phase 1 milestone 2026-03-12 20:59:20 +00:00
cal added the
evolution
phase-1d
labels 2026-03-12 20:59:28 +00:00
Sign in to join this conversation.
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cal/paper-dynasty-database#80
No description provided.