Guided memware setup walkthrough (release 0.2.5) - #6
Merged
Conversation
`memware setup` was a two-question backup-dest prompt. Broaden it into a guided one-time walkthrough aimed at both audiences that need it: a fresh install and an upgrade from a pre-backup (pre-0.2) version. It now: reports whether the store is empty; offers to index the transcripts already on disk (backfill) on a new install; helps pick a storage-agnostic backup destination; offers transcript mirroring; takes a first backup; and prints the operating guidance (automatic session-end backups, scheduling on an always-on machine, MEMWARE_NO_CAPTURE, and the wipe trap / restore-don't-rebackfill rule). `--yes` runs it non-interactively, and it stays safe on a closed stdin. A one-line stderr hint points anyone who has never configured backups at `memware setup` (from init/stats/backfill; silent from hooks and --json), and stops once setup has run or a destination is set — so pre-0.2 upgraders discover backups without any nagging afterward. Bumps to 0.2.5 (package + both plugin manifests, per the guard test) so the work machine can pick it up. README and docs/backup.md updated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NnaQwZUSDRbVUNh8fsdksD
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
You asked for a config walkthrough so net-new users and pre-2.0 → post-2.0 upgraders can set up backups (and the rest) without hunting through docs.
memware setupexisted but only asked two backup-dest questions, and nothing surfaced it — a pre-0.2 upgrade (which predates backups entirely) would never know to run it.What
memware setupis now a guided one-time walkthrough:MEMWARE_NO_CAPTUREfor sensitive sessions, and the wipe trap (restore --latest, never wipe-and-re-backfill).memware setup --yesruns it non-interactively; a closed stdin keeps every current value.Discovery
A one-line stderr hint points anyone who has never configured backups at
memware setup— shown frominit/stats/backfill, silent from hooks and in--jsonmode. It stops the moment setup has run or a destination is set, so pre-0.2 upgraders find backups once and are never nagged again.Tests
test_setup_yes_backfills_and_makes_first_backup— end-to-end--yes: indexes on-disk sessions, marks setup done, takes a snapshot, mirrors transcripts.test_setup_hint_shows_until_backups_configured— hint appears when unconfigured, never in--json, and disappears once a destination exists.Release
Bumps to 0.2.5 across the package and both plugin manifests (the drift-guard test from #5 enforces the manifest bump). Full suite, ruff, format, mypy green locally.
🤖 Generated with Claude Code