UI Behavior

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.

UI Behavior Additions

• Controls and labels must be centrally keyed for localization.
• Filename display should come from real filename state, not a substituted date string.
• Fit Height, Fit Everything, header text toggle, and related panel controls should remain stable across daily builds and must be explicitly documented when behavior changes.
• Visible live state and exported output should not contradict each other.