feat(enakgame): spin as an EnakGame game; remove the old game flow

EnakGame phase 10 of docs/tasks-enakgame.md (EG-1001 to EG-1003).

Spin (EG-1001)
- PROBABILITY entries take an optional label (a wheel segment). The customer game
  list shows a PROBABILITY game's prizes (entry, label, amount, never weights), and
  completing returns the drawn prize, so the client can draw the wheel and stop it
  on the server's draw.
- docs/enakgame-spin.md: the admin steps to set up spin per organization (no
  seeder) and the customer app flow. An HTTP test plays it end to end.

Old game flow removed (EG-1002)
- Routes POST /customer/spin, GET /customer/games, GET /customer/ferris-wheel, and
  admin /marketing/games, /marketing/game-prizes, /marketing/rewards, with their
  handlers, services, processors, repositories, validators, models, contracts,
  mappers and tests (GamePlayProcessor, SpinGameService, rewards, ...). This also
  closes RFC §15 findings 1 and 2 (double charge, spinning another org's game).
- Tables games, game_prizes, game_plays and rewards stay for ledger history.
  entities.StringSlice moves to its own file; the omset tracker (unrouted) keeps
  game_id but no longer embeds the old game response.

games.is_active dropped (EG-1003)
- Migration 000115; nothing reads metadata.coin_cost any more.

The EnakPoint integration docs now point at /customer/enakgame. The Postgres tests
were not run: no test database here. Migration 000115 has not been run anywhere.
The customer app must stop calling the removed endpoints before this is deployed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/mobile-customer-enakpoint.md

@@ -116,7 +116,7 @@ Endpoint **tukar** dan **transfer** wajib header `Idempotency-Key` (string unik,
 | Tukar EnakCoin | `GET …/exchange/preview`, `POST /customer/wallet/exchange` | Ya |
 | Transfer | `GET …/transfer/recipient`, `POST /customer/wallet/transfer` | Ya |
 | PIN (buat, ganti, lupa) | `/customer/pin/*` | – |
-| Game | `POST /customer/spin` | – |
+| Game | `GET /customer/enakgame/games`, `POST /customer/enakgame/sessions`, `POST …/sessions/:id/complete` | – |
 | (latar belakang) registrasi push | `PUT` / `DELETE /customer/devices` | – |
 
 ---
@@ -524,22 +524,20 @@ Penerima mendapat push `WALLET_TRANSFER_IN`.
 
 ## 8. Game (memakai EnakCoin)
 
-`POST /api/v1/customer/spin` dengan `{ "spin_id": "<id game>" }`. Tanpa PIN.
+`POST /api/v1/customer/spin`, `GET /customer/games`, dan `GET /customer/ferris-wheel`
+sudah dihapus. Semua game, termasuk spin, dimainkan lewat EnakGame. Tanpa PIN.
 
-```json
-{
-  "game_play": { "id": "…", "game_id": "…", "coins_used": 1, "created_at": "…" },
-  "prize_won": { "id": "…", "name": "Voucher 10rb" },
-  "coins_remaining": 7
-}
-```
+1. `GET /api/v1/customer/enakgame/games`: daftar game dengan `entry_cost` (EnakCoin per
+   main). Tampilkan biaya sebelum main, dan nonaktifkan tombol bila `coin_balance`
+   kurang. Spin punya `prizes` untuk menggambar roda.
+2. `POST /api/v1/customer/enakgame/sessions` dengan `{ "game_id": "…" }` dan header
+   `Idempotency-Key` (satu key per tap; retry memakai key yang sama). Response berisi
+   `session_id` dan `coin_balance` setelah dipotong.
+3. `POST /api/v1/customer/enakgame/sessions/:id/complete` dengan hasil main (`score`
+   atau `outcome`; spin cukup `{}`). Server yang menentukan hadiah: perbarui saldo dari
+   `coin_balance`, tampilkan `reward_total`, dan untuk spin hentikan roda di `prize.entry`.
 
-- Setiap game punya biaya sendiri: `metadata.coin_cost` pada data game dari
-  `GET /api/v1/customer/games` (atau `GET /customer/ferris-wheel`), default 1 bila kosong.
-  Tampilkan biaya sebelum main, dan nonaktifkan tombol bila `coin_balance` kurang.
-- `304`: EnakCoin kurang, game nonaktif, atau hadiah baru saja habis. Tidak ada
-  EnakCoin yang terpotong; tampilkan pesan dan biarkan customer mencoba lagi.
-- Setelah main, perbarui saldo EnakCoin dari `coins_remaining`.
+Rincian spin ada di [`enakgame-spin.md`](./enakgame-spin.md).
 
 ---