v0.1.7

Added

• Shared vault-resolution flow for auth and request handling, plus regression coverage for first-use index creation when switching into an unindexed top-level vault.
• Focused frontend regression coverage for settings persistence so client-preference rerenders no longer wipe unsaved notification fields.

Changed

• Collapsed the runtime model back to one configured vault root with optional top-level folder switching, removing the old per-user-root vault layout.
• Simplified auth toward a single-account deployment model, including setup wording, session/runtime terminology, and settings flow.
• Separated /api/meta runtime-vault state from current session-vault state so server config and active request scope are exposed distinctly.
• Startup indexing and notification polling now stay lazy around the configured root instead of eagerly creating index state on boot.
• Split large frontend UI surfaces out of frontend/app.ts into dedicated modules for session UI, settings, help, palettes, history/trash, page tree operations, client preferences, and inline editors.

Fixed

• User notification settings now persist correctly when saving from the settings dialog, including ntfy topic/token fields.
• Rendered table editing now matches the visual table metrics more closely, uses a softer active-cell fill, and supports consistent Enter/Escape finish and cancel shortcuts.
• Rendered table navigation no longer exposes raw markdown as part of the upward movement workaround attempts; table editing stays behind the dedicated table editor UI.