docs(plans): encryption-migrations follow-ups working doc#407
docs(plans): encryption-migrations follow-ups working doc#407
Conversation
Working notes accumulated while building #357 (the `stash encrypt` command group + `@cipherstash/migrate`) and the post-#395 init/handoff work that led into it. Persisted here so context compaction across agent sessions doesn't lose them, and so the next person picking up any of these threads has the *why* alongside the *what*. Categorised by area: skills coverage; wizard alignment; CLI/library follow-ups including known bugs and ergonomic enhancements; setup/detection improvements; public docs; the suite repo; smaller opportunistic items; and an agent-ergonomics section capturing patterns the 2026-05-04 spike's agent-cost feedback flagged as avoidable waste. Notable items worth pulling out: - §3.7 deploy-ordering safeguards for the migrate-existing-column flow (self-guarding generated SQL + opt-in event trigger + skill emphasis + optional pre-deploy verify command). - §3.8 known bug: `encrypt cutover` only emits a `cut_over` event for the column named on the CLI, but `rename_encrypted_columns()` promotes the whole pending config in one go. Fix walks the just- promoted config and emits per-column events. - §3.12 `stash db doctor` / `--verbose` status — compresses the partial-state diagnostic spiral from ~6 SQL probes to one command, and pairs with `stash db uninstall` for a supported teardown path. - §1.4 skill restructuring for agent token economy — three options for cutting the 600-line front-load. The doc is intentionally a working artefact, not user-facing documentation. Items get pulled out into PRs as they're addressed.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
Lands the working follow-ups doc accumulated while building #357 + the post-#395 init/handoff work that led into it. Notes have been living locally as
docs/plans/encryption-migrations-followups.md; landing them in-repo so the next person picking up any thread has the why alongside the what, and so context compaction across agent sessions doesn't lose them.Not user-facing — items get pulled out into PRs as they're addressed.
Worth flagging
A few items where the next move is clearer than the others:
encrypt cutoveronly emits acut_overevent for the column named on the CLI, butrename_encrypted_columns()promotes the whole pending config in one go. Walks the just-promoted config and emits per-column events.stash db doctor/db status --verbose— compresses the partial-state diagnostic spiral from ~6 SQL probes to one command, pairs withstash db uninstallfor a supported teardown.Test plan