Trezor firmware

This commit removes an optional build feature called `storage_hw_key` and instead turns on hardware-derived storage key support automatically for one specific chip family (STM32U5) and never for the software emulator. It is a cleanup/refactoring change with no direct security fix or vulnerability visible in the diff.

This commit is a build-system cleanup for Trezor firmware. It removes repeated lists of hardware-model-specific feature flags from multiple Cargo.toml files and replaces them with a single shared list in a new target.toml file for each project. There is no change to the actual device code or security behavior—only how build features are organized.

This commit is a straightforward internal rename from 'target' to 'project' across build configuration files and the Rust xtask build helper. It does not change what the firmware does, how it behaves, or any security logic. It is purely a code-maintenance refactor.

This commit is a build-system cleanup. It removes separate 'emulator board' configuration files and instead makes the emulator reuse the real hardware board's settings, only swapping in a special emulator header and the Unix display/touch drivers. There is no user-facing change or security fix visible in the diff.

This commit adds new configuration files describing Trezor hardware models and build targets. It is a build-system feature with no user-facing behavior change and no apparent security relevance.

This is a build-system refactoring commit for Trezor firmware. It moves feature-resolution code into a new module and shifts hard-coded ELF section lists and signing-tool choices into TOML configuration files. There is no direct evidence of a security vulnerability being fixed; it is a code-cleanup and maintainability change.

This commit is a follow-up code cleanup that wraps more on-screen layout calls in Python 'with' blocks. It changes return-type annotations from LayoutObj to LayoutContext and makes several UI helper functions async. There is no direct evidence in the commit that it fixes an exploitable security bug; it appears to be a defensive refactoring to enforce layout scoping consistently.

This is a routine dependency update bumping the Python Mako templating library from version 1.3.10 to 1.3.12. The commit message says the change is meant to avoid false safety warnings, because Mako versions 1.3.11 and earlier have a known vulnerability in code that Trezor firmware does not actually use. Only the lock file (uv.lock) changed; no Trezor source code was modified.

This commit simply deletes an entire internal testing tool called automatic_battery_tester from the repository. It removes Python scripts, configuration files, documentation, and dependency lists used only for hardware battery testing in the lab. No firmware code that ships to users was changed, and nothing in the commit suggests a security fix or vulnerability.

This commit is a code cleanup that changes how user-interface layouts are managed in the Trezor firmware. It wraps more layout objects in explicit context managers (the `with ... as layout:` pattern) so their lifetimes are clearly scoped. There is no direct evidence in the commit that this fixes an exploitable security bug; it appears to be a follow-up refactoring for safer resource handling.

This commit is a code-quality fix in the Cardano app of the Trezor firmware. It removes direct access to the global translation object (TR) at the time the Python module is first loaded, and instead reads the translated strings only when they are actually needed. This avoids a potential startup-time crash or import-order problem if the translation system is not fully initialized when the module is imported. There is no direct evidence in the commit that this is an exploitable security vulnerability.

This is a tiny user-interface polish change for the Trezor hardware wallet. It changes one footer label from 'swipe up' to 'tap' on warning screens that have no header title. There is no security-relevant behavior change in the diff itself.