andreagrandi / andreagrandi/draftomen

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

Open
#262 0 comments 0 reactions 0 assignees View on GitHub
draftomen enhancement size: L
Dominant language
Python
Stars
0
Forks
0
Avg merge
1h 18m
Merged PRs (30d)
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.

Contributor guide

No contributing guide indexed for this repository

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.