andreagrandi / andreagrandi/draftomen

Update replay, audit, and backtest for multi-card picks

Aperta
#262 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
draftomen enhancement size: L
Lingua principale
Python
Stelle
0
Fork
0
Merge medio
1h 18m
PR unite (30g)
197

Descrizione

## Problem

Replay, audit, and backtest records store one chosen card and use Quick Draft 14/42 arithmetic. Pick-Two would lose one selected card, misstate progress, and make singular actual-versus-recommended comparisons ambiguous.

## Proposed change

Carry draft format and selected-card collections through replay output, audit records, and backtest reconstruction. Define recommendation-following semantics for one-card and two-card logical picks without adding pair-optimization.

## Acceptance Criteria

- [ ] Replay output identifies the draft format and includes every card selected at each coordinate.
- [ ] Audit records preserve multi-card choices without changing coordinate identity.
- [ ] Backtest reconstructs logical picks and pool growth without equating pick count to card count.
- [ ] Recommendation-following semantics are deterministic for one-card and two-card picks.
- [ ] Existing Quick Draft golden output is intentionally migrated and remains deterministic.
- [ ] Focused replay/audit/backtest tests and the changelog cover every format.

## Scope notes

No scoring-model changes, UI work, or historical-data pipeline changes.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Locate the replay, audit, and backtest record and reconstruction code, then inspect the existing Quick Draft golden-output and focused tests to trace how a single selected card is represented. Update the formats and deterministic recommendation-following behavior for one-card and two-card picks, preserving coordinate identity and pool growth; done means every acceptance criterion is covered by focused tests and the changelog.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
python
Ambito
backend, testing
Tipo di issue
Funzionalità
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Attiva
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.