Week 12 - Aug 3-9, 2026¶
Focus: Direction 2 review and Direction 3 implementation
What I did¶
- Kept PR #911 in a focused three-commit structure for the numeric-setting feature, tests, and documentation. qlrd's first re-review gave the current change an informal LGTM.
- Opened Draft PR #922 for the
third audit-derived direction.
Load Mnemonicnow starts withQR Code,Words,From Storage, andOther Formats. - Kept the six specialist recovery formats in one flat
Other Formatsmenu, preserving their existing handlers and the two levels of Back navigation. - Checked the format-first menus on TZT, M5StickV, and Amigo, then completed physical TZT acceptance with touch and buttons.
- Checked all 11 translations against the M5StickV menu width after review raised a question about long labels.
Verification¶
- PR #922 passes 68 focused loader tests and the full 1,126-test suite with one expected failure and 97% coverage.
- Formatting, Pylint, translation validation, Vulture, the strict documentation build, and the MicroPython guardrail pass.
- The simulator sequences covered the common options, specialist formats, and both Back levels on TZT, M5StickV, and Amigo.
- Wrapping occurs in four M5StickV locales:
es-MX,ko-KR,pt-BR, andtr-TR. Every tested menu remains readable with all items and Back visible.
What I found¶
The format-first hierarchy shortens the common QR Code and Words routes. It makes specialist formats more explicit, but moves them one level deeper. This is why the PR remains a Draft for information-architecture review.
The translation check also exposed that the new Other Formats row was still
hard-coded in English. I restored the existing translation key, added a
Portuguese regression test, and refreshed the four wrapping-locale captures.
Things I noticed¶
- Translation stress needs to cover every available locale, not only the languages expected to produce the longest Latin labels.
- The M5StickV remains the useful constraint case for menu wrapping even when the same labels fit without wrapping on TZT and Amigo.
- A Draft PR gives maintainers a concrete design-review surface without expanding the work into new decoders, formats, or input methods.
Next week¶
- Follow maintainer review on PRs #911 and #922.
- Keep any PR #922 follow-up within its format-first menu scope.
- Complete the programme record through August 16 without mixing later implementation results into the original audit findings.