# GatherTradingData.xlsx Decision

## Option A: Track `GatherTradingData.xlsx`

Pros:

- Runner checkout always has the workbook.
- JSON regeneration never depends on Google Drive access.
- Manual recovery is simpler for operators.

Cons:

- Large binary file increases repo size and diff noise.
- Workbook changes become harder to review.
- The repository becomes dependent on spreadsheet artifacts that are not needed for normal runtime collection.

## Option B: Keep `GatherTradingData.xlsx` untracked

Pros:

- Repository stays smaller and cleaner.
- `GatherTradingData.json` remains the canonical runtime seed.
- Workflow can regenerate from local workbook or download it only when required.

Cons:

- If both seed files are missing, the workflow needs a download fallback or an operator intervention.
- Recovery depends on `.clasprc.json` or another source of truth.

## Recommendation

- Keep `GatherTradingData.xlsx` untracked.
- Track `GatherTradingData.json` in git.
- Preserve the workflow fallback path for regeneration and download.

