Track shipped features, product direction, and meaningful platform changes.

Changed

• Added Cloudflare R2 support for normalized cover uploads.
• Added app-side R2 safety caps for total stored bytes, daily upload bytes, and daily upload count.

Why it matters

• New covers should stay visible in production instead of disappearing when Vercel local upload paths are unavailable.
• Stored covers are compressed before upload, keeping media usage small for early testing.

Changed

• Added cover recovery jobs and candidate storage for missing, broken, fallback, and low-confidence covers.
• Extended extension Quick Save with source-page evidence, poster candidates, rendered image capture, and screenshot fallback.

Why it matters

• Saved entries should keep their covers even when remote sites block hotlinking or later change image URLs.
• Users can see where a cover came from and how much storage it uses.

Changed

• Refactored entry progress quick actions around shared client save logic and focused mutation rules.
• Split the entry layout studio into smaller layout, board, selection, sizing, persistence, and save-scope modules.

Why it matters

• Chapter and status updates should feel more consistent because quick actions no longer rely on full-page redirects.
• Layout customization is safer to use because personal, library-default, restore-default, and built-in-template behavior are more clearly separated.

Changed

• Connected the live product to lore-keep.com as the main public domain.
• Kept the updated sign-in and registration surfaces aligned with the current product visual language.

Why it matters

• Users can now share and revisit a stable branded domain instead of relying on a temporary deployment URL.
• Account access feels more trustworthy and less jarring because the auth surfaces now match the current product shell.

Changed

• Added public library pages with explicit public-vs-owner/member behavior and a cleaner bridge back into editable library views.
• Added followed-library foundations including follow/unfollow actions, notifications, and activity tracking for public library changes.

Why it matters

• Users can browse public libraries and then move back into their own library flow without getting lost in mismatched page designs.
• Following and notifications make public libraries more useful over time instead of acting like one-off read-only pages.

Changed

• Registration now sends a verification email instead of signing the user in immediately.
• Unverified accounts are blocked from production sign-in until the email link is used.

Why it matters

• New accounts now need one email-confirmation step before they can log in.
• Forgot-password links arrive through a real production sender instead of only existing as dev output.

Changed

• Deployed the web app to Vercel Hobby and connected it to a Neon production database.
• Applied the full Prisma migration history to production so the live app has the real schema instead of an empty database shell.

Why it matters

• Private beta testing can now happen against a real hosted environment instead of only localhost.
• The live app is less fragile during first deploys and fresh-environment setup.

Changed

• Added a first-class post type for upcoming roadmap entries.
• Extended the in-app updates editor so content editors can create and manage upcoming posts.

Why it matters

• Users can distinguish between what already shipped and what is planned next.
• Editors can communicate roadmap work directly instead of relying only on status labels inside feedback.

Changed

• Added one-time recovery codes for encrypted libraries.
• Added a guided recovery page for replacing a lost library password.

Why it matters

• Users have a safer path back into encrypted libraries after losing a library password.
• Encrypted libraries are now more practical for everyday use because mistakes are less catastrophic.

Changed

• Added password reset request and confirmation routes inside the app.
• Added one-time password reset tokens with expiry and replay protection.

Why it matters

• Users can recover account access without manual intervention.
• Resetting a password no longer leaves older signed-in sessions active.

Changed

• Added a dedicated documentation page with product-focused guidance.
• Added structured documentation sections covering accounts, libraries, field structure, security, updates, and feedback.

Why it matters

• New users have a clearer path to understanding the product before creating content or submitting feedback.
• Core workflows are easier to learn without trial and error.

Changed

• Added a dedicated MediaAsset model for uploaded and external media.
• Added cover media support on entries with proper foreign-key relationships.

Why it matters

• Libraries can present books, manga, and other collection items with clearer visual identity.
• Entries are easier to scan because covers and titles are now first-class data instead of improvised fields.

Changed

• Added explicit library encryption modes so standard and zero-knowledge protection are modeled separately.
• Added browser-side zero-knowledge key material with dedicated verifier and wrapped-key storage.

Why it matters

• Users can protect their most sensitive libraries with a stronger privacy model than the original encrypted-library foundation.
• Returning to protected libraries feels more practical because unlock state can persist for a limited session instead of forcing constant re-entry.

Changed

• Stacked members and fields into a cleaner top-to-bottom layout.
• Replaced the cramped field-builder grid with a guided field-creation form and field cards.

Why it matters

• Users can shape a library without fighting the layout.
• The field builder is easier to understand for non-technical users.

Changed

• Added persistent auth rate limiting for login, registration, and reset flows.
• Added one-time password reset tokens with expiry and active-session revocation after reset.

Why it matters

• Accounts are harder to brute-force or abuse through repeated failed attempts.
• Password recovery is now available without weakening session security.

Changed

• Added a public feedback board with bug reports, feature requests, and improvement requests.
• Added per-issue pages with clear process steps, status history, and official updates.

Why it matters

• Users can see what has been reported, what is planned, and what has already been addressed.
• Feature requests and bug reports now stay visible and traceable instead of disappearing into private support channels.

Changed

• Added a public updates feed with dedicated post pages.
• Added an in-app updates editor with role-based access for content editing.

Why it matters

• Users can follow real product progress in one place instead of relying on scattered explanations.
• Editors can publish major changes directly inside the app without touching source files.

Changed

• Added encrypted library setup flow with separate password confirmation.
• Generated recovery codes and one-time recovery-code screen after creation.

Why it matters

• Sensitive libraries now have a real setup path instead of a placeholder encrypted flag.
• Recovery handling is clearer for users who need to protect access without relying only on their main account session.

Changed

• Implemented registration, login, logout, hashed passwords, and hashed session tokens.
• Created a shared authenticated navbar and account menu.

Why it matters

• The app now feels like a real product instead of a dev scaffold.
• Users can sign in and return to the dashboard without mixing auth forms into the homepage.

Changed

• Split SQL trace and audit log into separate internal tools.
• Added developer, moderator, owner, and log-cleaner system-role flows.

Why it matters

• Moderation and developer access are no longer mixed together.
• Operational debugging is easier without exposing dangerous tooling to broader roles.

Changed

• Added dashboard library creation and library detail pages.
• Made library cards clickable and connected them to per-library views.

Why it matters

• The app now has a real content structure instead of only auth and admin tooling.
• Users can shape their own library schema before entries are added.