# Tasks — CLI-070: `--reset` documented in help and guarded by confirmation

Spec: `.agents/spec-docs/active/CLI-070-reset-flag-help-confirm.md`
Test Plan SSOT: the spec's TC table.

- [x] T1 (TC-01): `printHelp` lists `--reset` naming exactly what is deleted
      (`~/.robota/settings.json`) and the `--yes` skip (help-content test, flag-wiring
      guard family).
- [x] T2 (TC-02): non-TTY without `--yes` → refusal naming `--yes`, exit 1, settings file
      untouched.
- [x] T3 (TC-03): `--reset --yes` → deleted without prompt, exit 0.
- [x] T4 (TC-04): TTY prompt (injected confirm) — `n` → no deletion + exit 1; `y` →
      deletion + exit 0.
- [x] T5 (TC-05): no settings file present → reports nothing to delete, exit 0.
- [x] T6 (TC-06): CLI SPEC.md documents the flag + confirmation matrix
      (destructive-action contract).
- [x] T7: wrap-up — package test/typecheck/lint/build green; PR to develop (squash);
      backlog scenario evidence + move to completed/.

## Test Plan

Authoritative TC table: `.agents/spec-docs/active/CLI-070-reset-flag-help-confirm.md`
(## Test Plan). Summary: TC-01 printHelp content assertion; TC-02..TC-05 unit tests on
`runResetConfig` with temp HOME + injected confirm/TTY/yes; TC-06 SPEC.md diff review at
GATE-COMPLETE. User-execution scenarios: real binary `robota --help | grep reset`,
`robota --reset < /dev/null` (refusal), `robota --reset --yes` (deletion).
