andreagrandi / andreagrandi/draftomen

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

Offen
#262 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
draftomen enhancement size: L
Vorherrschende Sprache
Python
Sterne
0
Forks
0
Ø Merge
1 Std. 18 Min.
Gemergte PRs (30 T.)
197

Beschreibung

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

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python
Bereich
backend, testing
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.