Status: Active document in the current doc_updates package.
Note: Older dates inside a document may describe source authorship or earlier document history. This package revision date marks the current integrated update set.
The interface should feel calm, orderly, visually clear, and predictable. Established behavior should not shift casually between builds.
Documentation should explain behavior in human terms so readers understand what to expect before using the app.
2026-03-17 Full Integration Additions — UI Behavior, Labels, and Live/Export Parity
User-visible controls and labels must be localizable, centrally keyed, and documented in a language-agnostic way.
Live behavior should accurately preview composition intent so export does not surprise the user.
If the live UI shows QR, the export must include QR unless the user explicitly disables it.
Control labels, status text, and pills should be documented as keys or semantic identifiers rather than only English surface strings.
UI docs should warn future contributors that mixed-case filenames, hardcoded English labels, and undocumented control changes all create avoidable maintenance risk.