Skip to content

[Web/PWA] Add Markdown export and deletion semantics #20

Description

@AlphaMao1

Parent

#11

What to build

Finish the first-version data lifecycle: users can export reading material as Markdown, delete books to reclaim storage, and trust that sync will not resurrect deleted rows. Direct Obsidian writing is out of scope; Markdown download is the supported bridge.

Acceptance criteria

  • A user can download Markdown containing book metadata, highlights, notes, and useful AI/memory references where appropriate.
  • The UI does not claim direct Obsidian vault writing.
  • Deleting a book removes the Supabase Storage EPUB object.
  • Deleting a book removes or invalidates local cached EPUB data.
  • Deleting a book removes RAG chunks/vectors/index records for that book.
  • Book-linked annotations and conversations are soft-deleted with deleted_at and hidden after sync.
  • Cross-book memories are retained unless the user explicitly confirms memory deletion.
  • A two-device smoke test proves deleted data is not resurrected.

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions