UnENVerse 2026-09-10
No envv totp add/set. envv entry set X --totp … is the write path;
Handoff 28 — 2026-09-10
Phase 21 fixed, Phase 22 allocated and implemented (TOTP as a stored secret)
- **No
envv totp add/set.**envv entry set X --totp …is the write path; - a second verb for it would be two ways to write one field.
- **No
--dry-runpreview forenvv totp import.** The global--dry-runworks - (it is enforced inside
Access::save, so the parse and the report run and - nothing is written), which is most of the value. A dedicated preview that lists
- every planned action per entry would be better and is not there.
- No encrypted-export support for any source app, deliberately — see above.
- No import from a QR image. The app cannot decode one (no camera, no
- decoder), so
otpauth-migration://has to be pasted or saved to a file first. - No health-scan check for an unusable stored seed.
envv totp lsreports - one per row (
usable: falsewith the reason) and every write path validates, - so the only way in is an imported vault. Worth adding to
doctorin a later