mirror of
https://github.com/PR0M3TH3AN/SeedPass.git
synced 2026-10-28 08:22:03 +00:00
The README had zero mentions of the TypeScript implementation -- on the branch proposing to make it the main line, a reader (including PR #989's reviewers) would find only the Python product. A bridge section near the top now says what the rebuild is, its status (under independent review; do not put irreplaceable secrets in it yet), and where the migration guide, the vault/identity spec, and the cutover plan live. Deliberately a bridge, not a rewrite: everything below it still accurately describes the Python version, which is what install.sh installs today. Advertising the TS implementation as the product before its review lands would be docs describing an aspirational state -- the exact failure mode this branch has been stamping out. The 14 Python-era planning docs most likely to mislead (tui_v2/v3, index0/atlas, semantic) carry a one-line legacy banner so a reader can tell a historical record from a living document. The full TS-first rewrite -- README, landing page, docs triage, CI scoping, dependabot config -- is specced as a merge-day checklist under the cutover item in TODO.md, so main never advertises a stale product in either direction. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tkj4rzKBA3uhfgk7kqjsb8
3.5 KiB
3.5 KiB
TUI v2 Parity Backlog
Legacy (Python implementation). This document describes the Python version, which retires to
legacy/after the TypeScript cutover (PR #989). The TypeScript interactive mode follows the classic v1 menus; TUI v2/v3, index0/atlas, and semantic search were not ported. Kept as historical record.
Status: Active tracking on beta (updated 2026-03-01).
This document captures parity learnings and the remaining implementation queue for Textual TUI v2 versus legacy interactive TUI.
Linked plans:
docs/tui_v2_plan.mddocs/tui_v2_parity_checklist.mddocs/tui_v2_cutover_decision.mddocs/tui_v2_ui_refresh_plan.mddocs/semantic_vector_index_plan.md(cross-interface semantic retrieval roadmap)
What We Learned
- Core shell workflows are stable in TUI v2:
- list/search/filter/detail
- archive/restore
- document edit save/cancel
- graph links + relation filtering + neighbor traversal
- retry/error-recovery flows
- Security-sensitive parity has improved:
- reveal/QR for
password,totp,seed,managed_account,ssh,pgp,nostr - high-risk confirm gates (
reveal confirm,qr private confirm) - secret-mode clipboard-aware reveal behavior
- Scale validation now exists for KB-like workloads:
- core sort/tag/search + high-degree graph link stress
- TUI large-index navigation stress
- Remaining parity is mostly feature-surface breadth, not stability:
- add-entry creation flows in v2
- legacy retrieve/action micro-workflows
- dedicated 2FA board
- settings/profile/nostr operational menus
Active Build Queue
Phase A: Add Entry in TUI v2
- Add password creation flow
- Add TOTP creation flow
- Add key/value creation flow
- Add document creation flow
- Add SSH/PGP/Nostr/Seed/Managed Account creation flows
- Add validation and post-create focus/selection behavior
Phase B: Retrieve/Action Parity
- Add note from selected entry
- Add custom field / hidden field actions
- Edit tags action parity
- Field-level edit parity for non-document kinds
- Document export action
- Nostr QR submenu parity (public/private explicit flows)
Phase C: 2FA Board Parity
- Dedicated 2FA list board view
- rolling code refresh + remaining timer UI
- secret-mode clipboard behavior in board view
- deterministic/imported split parity and display semantics
Phase D: Settings/Profile/Nostr Parity
- profile switch/add/remove/list/rename
- secret mode / quick unlock / offline toggles
- inactivity timeout + KDF settings
- relay view/add/remove/reset + sync controls
- checksum verify/generate, import/export db, export totp, parent seed backup/reveal
Phase E: Release/CI Closure
- Add CI smoke step for
seedpass tui2 --check - Extend docs/help parity after each feature landing
- Keep
legacyfallback path until parity checklist has no high-severity gaps
Release note:
- CI now runs a dedicated
tui2 --checksmoke gate viascripts/tui2_check_smoke.sh(invoked byscripts/run_ci_tests.sh) and in Poetry workflow (tests.yml). - Legacy fallback command/flag paths remain available (
seedpass legacy,seedpass --legacy-tui, andtui2fallback toggle) while cutover hardening continues.
Execution Notes
- Implement in small vertical slices and check boxes as each slice lands with tests.
- Each parity slice must include:
- command/keybind discoverability,
- service-layer coverage,
- Textual interaction tests.