Release v0.1.3 — Reliability, recovery and Following · Tenyokj/devdevian

This release brings together the work from v0.1.1, v0.1.2 and v0.1.3, following the first public v0.1.0 release.

Reliability and recovery

Email-code password recovery with expiring, hashed codes, bounded attempts and revocation of previous sessions.
Explicit database migrations outside hosted request startup, reusable API initialization and readable failures with request references.
Active-screen loading, batched metadata reads, request deduplication and debounced search.
Persistent authentication/email budgets, upload reservations and storage limits.
Encrypted database/file backups with isolated restore verification, scheduled backup and health workflows, and sanitized server diagnostics.

Browser-local conversation drafts restore text, code, links, topic, technologies and audience after closing or reloading the form.
Topic and conversation subscriptions with in-app notifications, independent from bookmarks.
A personal Following feed with recent-activity ordering, search, topic/type filters and pagination.
Searchable subscription management, including safe removal of unavailable private conversations.
@Mention notifications in post and reply bodies, including newly added mentions in edits. Code and links do not send pings; duplicate alerts, self-mentions and inaccessible private content are excluded.
Reply permalinks reveal the correct nested pages, focus and highlight the target, and respect reduced-motion preferences.
Needs help keeps unresolved questions and code reviews visible even after they receive replies.

Dates now show the year, hours, minutes and timezone, including publication, edit, notification and moderation timestamps.
A compact forum footer links the running version, source repository, bug reporting and policies.
Responsive checks cover phone, tablet and desktop layouts.

68 tests passed against SQLite and the libSQL/S3 fixture configuration; Chromium acceptance checks cover real forms, subscriptions, mentions, nested pagination and responsive layouts.
The isolated local workload completed 210 requests at concurrency 10 with no errors. This is a regression check, not a production capacity guarantee.
No schema upgrade is needed from v0.1.2. Operators upgrading from v0.1.0 should back up their database and files, configure the required services and run the explicit migration. See deployment and backup/recovery.
Drafts stay on the current browser and attachments must be added again when reopening. Notifications are in-app; mentions consider the first ten distinct handles in a body. Backup automation requires operator-provided secrets.

Full comparison: v0.1.0...v0.1.3