editlisted

# Estimator — Edit / Delete History Records Edit field(s) of existing records, or delete records, in `history.csv` by Jira key. Inserting new records is NOT supported (use `/add` or `/sync` to add records). ## 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'` ## Step 1 — Preflight Resolve `<DATA_DIR>`. If `<DATA_DIR>/history.csv` does not exist, tell the user to run `/sync` first to build the dataset, and stop. ## Step 2 — Resolve the key(s) Take one or more keys from the user's message/argument (space- or comma-separated) and uppercase them. Expand bare numbers via `config.json` `project_keys`: one cached key → prefix (`7777` → `ABC-7777`); several → ask which project; none cached → ask for the project key. If no key can be determined, prompt the user. ## Step 3 — Determine the operation Infer **edit** vs **delete** from the user's wording ("delete/remove …" → delete; "edit/change/fix/update …" → edit). If unclear, ask which. ## Step 4 — Load current records, report missing Look up the keys with the find script to fetch current values: `python3 "<PLUGIN_ROOT>/skills/find/scripts/find_records.py" "<DATA_DIR>/history.csv" KEY [KEY ...]` (or `python …`, or `py -3 …`, or `node "<PLUGIN_ROOT>/skills/find/scripts/find_records.mjs" …` — same ladder). Report any keys in the result's `missing` list and proceed with the fo