andreagrandi / andreagrandi/draftomen

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

Ouverte
#262 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
draftomen enhancement size: L
Langage dominant
Python
Étoiles
0
Forks
0
Merge moyen
1 h 18 min
PR mergées (30 j)
197

Description

## 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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
backend, testing
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Active
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.