Post-v0.6.0 spot-check of the three 2026-05-04 architecture-review specs (per CLAUDE.md rule #4) confirms: - CLI restructure: shipped as Plan B Cycles 1+2 (b9bd152,3dd1e1b,3759f6a,e69b347). Last gap (read-side refresh_groups_cache callers) closed ind717f0d. Done-criteria all met. - Security polish: shipped as Stream A Cycle 1 (89090a8) plus follow-ups for start.sh fourth window (0c9387f) and recovery_qr.rs docs (229e483). All four phases done. - Extension restructure: genuinely outstanding. vault.ts is 1037 LOC (criterion ~200); the five-module split has not happened; setup.ts still imports relicario-wasm directly; shared/state.ts still has any-typed StateHost; SW router helpers still duplicated; CLI parity gap (relicario status) still open. Effort estimate: L. Removes the incorrect "subcommand reorganization, interactive TUI mode" descriptor — the original CLI restructure spec is about file structure, not TUI or renames. The TUI descriptor was a roadmap mis-paraphrase, not a real outstanding item. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
40 lines
2.8 KiB
Markdown
40 lines
2.8 KiB
Markdown
# Relicario Roadmap
|
||
|
||
> Living document — update alongside `STATUS.md` when milestones shift.
|
||
> "Up next" items have specs; "Medium-term" items may have specs; "Long-term" items are direction, not committed scope.
|
||
|
||
## Shipped
|
||
|
||
| Version | Highlights |
|
||
|---|---|
|
||
| v0.6.0 *(2026-05-30)* | Security audit fixes; device authentication; backup/restore + LastPass import; fullscreen UX Phases 1+2A+2B; v0.5.1 Streams A/B/C (3-column vault layout + bottom-sheet picker + toast system; left-nav settings; Recovery QR end-to-end + setup wizard Style C); 1C-γ (attachments + Document type + device registration + trash + field history); Plan B multi-stream refactor (commands/ split, prompt_or_flag, core/WASM seam); vault-tab management surfaces revamp (settings synced/local split, devices fingerprint, trash purge countdown, field-history polish, item-history-index, `#history/<id>` routing); doc-structure redesign (rename to DESIGN/CRYPTO/docs/FORMATS, scope headers + Next: footers); GPL-3.0-or-later license |
|
||
| v0.2.0 | Typed-item rewrite (Plans 1A/1B/1C-α/β₁/β₂) |
|
||
|
||
See `CHANGELOG.md` for tagged-release detail and `STATUS.md` for the per-train commit list.
|
||
|
||
## Up next
|
||
|
||
Per the 2026-05-30 post-v0.6.0 audit: of the three 2026-05-04 architecture-review specs, two are already shipped (CLI restructure = Plan B Cycles 1+2; security polish = Stream A Cycle 1). Only the third is genuinely outstanding:
|
||
|
||
- **Extension restructure** — `vault.ts` split (5 modules), setup.ts SW-abstraction routing, type-checked `shared/state.ts`, SW router-helper dedup, `relicario status` parity, plus P2 cleanups (inactivity timer / gitHost-on-expiry / debounced detector). Effort: **L (multi-day to multi-week)**.
|
||
Spec: `docs/superpowers/specs/2026-05-04-extension-restructure-design.md`
|
||
Plan: not yet written — that's the next concrete move.
|
||
|
||
## Medium-term
|
||
|
||
- **Phase 4: command palette** — ⌘K global search + action dispatch across the vault tab (no spec yet)
|
||
|
||
## Long-term / backlog
|
||
|
||
- **Relay server** — encrypted WebSocket relay for multi-device sync without a shared git server
|
||
Spec: `docs/superpowers/specs/2026-05-02-relay-server-design.md`
|
||
Plan: `docs/superpowers/plans/2026-05-02-relay-server.md` (`c0921b1`)
|
||
Code skeleton: `crates/relicario-server/` exists but only houses the pre-receive hook today; the relay binary would either extend or replace it.
|
||
- **Mobile** — Rust core compiles to ARM; JNI wrapper for Android, Swift wrapper for iOS
|
||
|
||
## Non-goals (explicitly deferred or cancelled)
|
||
|
||
- **Reference-image rotation** — changing the image factor without re-embedding. Back-burner, not cancelled.
|
||
- **Per-entry subkeys** — no real-world benefit at family-vault scale; see design rationale in `docs/CRYPTO.md`.
|
||
- **libgit2 / gitoxide** — shell-out to `git` is intentional; see `crates/relicario-cli/ARCHITECTURE.md`.
|