exportlisted

# Estimator — Export Data Copy the stored dataset to a location the user chooses, for **backup** or **migration** (e.g. before a `/estimator:reset` or uninstall, or to move the dataset to another machine). Counterpart to the `import` skill. ## Data location Resolve `<DATA_DIR>` as the other skills do — the per-user data dir `~/.estimator`: - Bash: `DATA_DIR="$HOME/.estimator"` - PowerShell: `$DATA_DIR = Join-Path $env:USERPROFILE '.estimator'` Source files: `<DATA_DIR>/history.csv` and `<DATA_DIR>/config.json`. ## Step 1 — Preflight Resolve `<DATA_DIR>`. If `<DATA_DIR>/history.csv` does not exist, tell the user there is nothing to export (suggest `/sync` to build a dataset, or the `import` skill to load one) and stop. ## Step 2 — Determine the destination Use the destination path from the user's message if one was given; otherwise ask the user where to export to. Expand `~` and environment variables in the path. ## Step 3 — Pick the mode (from the path form) - Destination **ends in `.csv`** → **single-file mode**: copy *only* `history.csv` to that exact path (a named data backup, e.g. `~/backups/estimator-2026-06.csv`). - **Otherwise** → **directory mode**: treat the path as a directory and copy `history.csv` into it, keeping its name (any path without a `.csv` suffix is treated as a directory). **Ask the user whether to also include `config.json`** (the sync metadata — JQL, story-point field id, project keys); copy it only if they say yes. Create the direc