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.
|
||||
Reference in New Issue
Block a user