0.2.0
Observations from the first real use of 0.1.0, gathered on the ragnar test instance, plus the suggestions accepted on 2026-09-05. Every issue carries one exclusive tier/* label.
Tier 1 — critical, in suggested order. The smoke test first, because everything after it rewrites the interface: #36. Then the shell: #8 icons → #9 theme switch → #10 header and account menu. The account model, before more accounts exist: #1 username → #2 full name → #3 verified emails. The settings area that the rest hangs from: #22, then #27 two-factor. The workflow change, before more data accumulates: #25 Listings. And #32 backup and restore, because nobody should run 0.2.0 without a way back.
Tier 2 — next. Administration and sign-in: #24 server settings, #6 native OIDC. The roots of every integration: #11 connections → #4 notifications and SMTP, #12 the API and tokens, #14 interviews. Daily use: #20 tables, #30 gone quiet, #39 industries, #7 avatars, #26 password meter, #33 account deletion, #29 search, #31 CSV import. The extensions, whose API already exists: #17 then #18. And #37, the release workflow, so that 0.2.0 ships as an image.
Tier 3 — later. The plugins, each behind its root in tier 2: #5 Apprise, #13 stores → #15 Paperless, #16 DAV, #34 IMAP, #19 MCP, #38 plugin installation. And the polish: #28 document kinds, #21 logos, #35 board drag and drop, #23 hide the Dashboard link.
Dependencies are registered as blocked-by relations; the roots are #8, #11, #12, #14, #22, #24 and #25.
