docs: Flutter architecture plan (ADRs 0017-0019) #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/flutter-architecture-plan"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Flutter Architecture Plan — ADRs 0017-0019
Planning documents for Phase 7 (Flutter app). No code yet — just architecture decisions before scaffolding.
ADR 0017: Technology Stack
ADR 0018: Clean Architecture (mirrors backend)
domain/— pure Dart entities + repository interfaces (no Flutter imports)data/— repository implementations, dio API client, freezed DTOspresentation/— widgets + Redux (state/actions/reducers/middleware)app/— composition root (store config, DI, theme)ADR 0019: Desktop-Native UX + "Gallery" Theme
#1A1A2E), warm coral-red primary (#E94560), amber-gold accent (#F5A623). Not generic Material 3.Summary
Summary
Coverage
DoujinManager.ApplicationCore - 84.8%
DoujinManager.Infrastructure - 91.6%
pshot
DoujinManager.RestAdapter - 84.2%
E5CB12CEAC5BBBEA65844E1C05F9ADA4DA38B848075C41304FC6A1ABF77__ValidationAttr
ibuteCache
DoujinManager.Server - 16.7%
🤖 Hermes automated review: no blocking issues found
Reviewed head
3b2359d2(basemain96c8532). This is a docs-only PR (+272/-0, 4 files) adding three planning ADRs for the Flutter app.Static security scan
Clean — markdown-only diff. No secrets, shell injection, eval/exec, SQL injection, or unsafe deserialization in added lines.
Structural / integrity checks
0017,0018,0019) added underdocs/adr/and linked indocs/adr/README.mdimplementation-phase section.Minor notes (non-blocking)
0018introduces an optionaluse_cases/layer indomain/and notes epics can call repos directly when orchestration is trivial. When scaffolding begins, consider documenting a concrete rule for when a use case is required vs. optional, to avoid inconsistency creeping in across features.0019defines compact touch targets ("smaller, mouse-optimized") but also targets Android tablets as secondary. Worth noting the minimum accessible touch size (e.g. 40–48dp) as a constraint when the Android target is worked on, so "compact" doesn't conflict with usability.Neither is a blocker for a planning-docs PR.
Verification
3b2359d2— forgejo-actions coverage comment #327 (06/29 16:11 UTC, line 83.6%, branch 49.4%);ci.ymlposts coverage only on successful build+test. Local build/test skipped per CI-evidence policy.Note: this is a PR conversation comment, not a formal Forgejo review approval — the current MCP integration cannot create inline review comments or approval states. I never merge PRs.
Automated daily review. I never merge PRs.