chore: restore product scaffold to rollback baseline
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
# Chanora Adaptive Layout and Platform Guide
|
||||
|
||||
**Document status:** DV meeting baseline candidate
|
||||
**Date:** 2026-05-29
|
||||
|
||||
## 1. Layout Policy
|
||||
|
||||
Chanora prioritizes compact/mobile layout for MVP while preserving a path to medium and expanded layouts.
|
||||
|
||||
| Layout class | Current expectation |
|
||||
|---|---|
|
||||
| Compact | Primary supported layout for mobile and narrow windows |
|
||||
| Medium | Must preserve connection and voice control visibility; side navigation rail remains a P1 gap where not implemented |
|
||||
| Expanded | Persistent side panes are deferred beyond current candidate |
|
||||
|
||||
## 2. Platform Policy
|
||||
|
||||
| Platform concern | Required behavior |
|
||||
|---|---|
|
||||
| Safe areas/system bars | Critical controls remain reachable |
|
||||
| Android back | Back intent service mediates app behavior |
|
||||
| iOS gestures/haptics | Platform services handle iOS-specific behavior |
|
||||
| Desktop PTT | UI displays actual PTT capability level and fallback state |
|
||||
|
||||
## 3. DV Conclusion
|
||||
|
||||
Adaptive layout policy is documented. Medium/expanded hardening remains a tracked post-MVP/P1 gap where not implemented.
|
||||
@@ -0,0 +1,38 @@
|
||||
# Chanora Material 3 Component Catalog
|
||||
|
||||
**Document status:** DV meeting baseline candidate
|
||||
**Date:** 2026-05-29
|
||||
|
||||
## 1. Component Catalogue
|
||||
|
||||
| Component area | Source files | Purpose |
|
||||
|---|---|---|
|
||||
| Connect and bookmarks | `connect_widgets.dart`, `input_dialogs.dart` | Server input, bookmarks, connect actions |
|
||||
| Channel and client view | `snapshot_view.dart`, `client_info_sheet.dart`, `channel_spacer.dart` | Channel tree, clients, client details |
|
||||
| Chat | `chat_views.dart`, `bbcode_text.dart` | Channel text and BBCode rendering |
|
||||
| Voice controls | `voice_bar.dart`, `voice_compact.dart`, `voice_settings*.dart` | Mute, deaf, PTT, levels, processing controls |
|
||||
| Platform/permission indicators | `permission_state_banner.dart`, `ptt_capability_badge.dart`, `talk_power_warning.dart` | Platform readiness and safety warnings |
|
||||
| Diagnostics | `audio_debug_stats_panel.dart` and diagnostics surfaces in app shell | Runtime/debug evidence and export support |
|
||||
|
||||
## 2. Acceptance Criteria
|
||||
|
||||
| Component area | DV acceptance criterion |
|
||||
|---|---|
|
||||
| Connect and bookmarks | User can enter server details, save/reuse bookmarks, and receive user-safe errors |
|
||||
| Channel and client view | Channel tree and online clients remain visible after snapshot updates |
|
||||
| Chat | Channel text renders without corrupting Unicode or unsafe BBCode display |
|
||||
| Voice controls | Mute, deaf, PTT, metering, and processing controls expose current state clearly |
|
||||
| Platform/permission indicators | Permission and capability limitations are visible and not color-only |
|
||||
| Diagnostics | Diagnostic/debug surfaces do not expose unredacted secrets in release evidence |
|
||||
|
||||
## 3. Evidence Required Before Release
|
||||
|
||||
| Evidence | Purpose |
|
||||
|---|---|
|
||||
| Flutter widget test run | Confirms component behavior remains stable |
|
||||
| Accessibility review | Confirms critical states are not color-only and controls are reachable |
|
||||
| Candidate screenshots or demo notes | Supports DV review and release readiness |
|
||||
|
||||
## 4. DV Conclusion
|
||||
|
||||
The component catalog is sufficient for DV navigation. Final UI audit should attach screenshots or test evidence for each critical component.
|
||||
@@ -0,0 +1,21 @@
|
||||
# Chanora Material 3 Design Tokens
|
||||
|
||||
**Document status:** DV meeting baseline candidate
|
||||
**Date:** 2026-05-29
|
||||
|
||||
## 1. Source
|
||||
|
||||
Implementation token source is `apps/chanora_flutter/lib/design/chanora_tokens.dart`.
|
||||
|
||||
## 2. Token Areas
|
||||
|
||||
| Token area | Purpose |
|
||||
|---|---|
|
||||
| Color roles | Connection, voice, permission, diagnostic, warning, and neutral states |
|
||||
| Typography roles | App shell, status, channel/client lists, chat, settings, diagnostics |
|
||||
| Spacing roles | Compact/mobile layout, control grouping, list density |
|
||||
| Shape/elevation roles | Material 3 cards, sheets, banners, controls |
|
||||
|
||||
## 3. Verification
|
||||
|
||||
Token usage is verified through Flutter widget tests, visual review, and accessibility checks that critical state is not represented by color alone.
|
||||
@@ -0,0 +1,8 @@
|
||||
# Chanora Material 3 Guideline
|
||||
|
||||
**Document status:** DV path record
|
||||
**Canonical source:** `../material3-guideline.md`
|
||||
|
||||
The current Material 3 guideline lives at `docs/material3-guideline.md`. This file preserves the README-advertised path `docs/ui-ux/material3-guideline.md` for DV navigation.
|
||||
|
||||
Reviewers shall use `docs/material3-guideline.md` as the canonical UI/UX guideline until the migration moves it into `docs/ui-ux/`.
|
||||
Reference in New Issue
Block a user