Rename 'Recovery Checkpoints' to 'Backups' across Excel add-in
Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Replace jargony 'Recovery Checkpoints' terminology with plain-language 'Backups' (and 'Pi edits') throughout all user-facing strings in the codebase, and ship it to main.
- +0Prompt · +0'Recovery checkpoints' language is hard for non-technical users. Should we call it Time Machine or Backups?
- +0mAgent did · +0mSearched codebase for all 'checkpoint' references to scope the rename across UI, tools, and docs.
- +0mAgent did · +0mRecommended 'Backups' over 'Time Machine' (trademark/confusion risk) and drafted a clearer subtitle for the overlay dialog.
- +1mPrompt · +1mWhat happens if a human edits in between AI edits? Also let's call it Pi's edits.
- +1mAgent did · +1mTraced snapshot capture logic in recovery-log.ts and write-cells.ts to explain how human edits interleaved with Pi edits are preserved in backups.
- +3mAgent did · +3mRenamed 'Recovery Checkpoints' to 'Backups' and adjusted 'Pi edit' language across overlays.ts, pi-sidebar.ts, init.ts, workbook-history.ts, recovery-metadata.ts, system-prompt.ts, CSS, DECISIONS.md, docs, and tests (roughly 16 files).
- +7mAgent did · +7mRan lint, typecheck, and build; found unrelated pre-existing test module-resolution errors, then did a final grep audit and caught two more leaked 'checkpoint' strings in session.ts and format-cells.ts.
- +10mPrompt · +10mGreat, push to main please.
- +10mFail · +10mCommit and push failed: local branch was based on a feature branch, not main, and cherry-picking onto main produced conflicts in docs/upcoming.md, DECISIONS.md, and format-cells.ts.
- +10mAgent did · +10mResolved the three merge conflicts by keeping upstream content updates while reapplying the backups/Pi-edits rename, reran checks, and pushed the cherry-picked commit to main (16 files changed).
- +11mOutcome · +11mRename shipped to main as commit a02421d: 16 files changed, 73 insertions/73 deletions, lint/typecheck/build all passing.
Next time I'd tell the agent up front to check I'm on the right branch before it commits, since the push-to-main step turned into an unplanned rebase/cherry-pick conflict resolution. The actual terminology work went smoothly once I gave clear direction ('Backups' + 'Pi's edits'), and asking about the human-edit-interleaving behavior early saved us from shipping confusing semantics. The final grep audit before pushing was the correction that mattered most — it caught two leaked strings that would have shipped otherwise.