[Hoggormino]

Summary

A tag whose type code is not in the profile table gets a zeroed profile: kind Unknown, 0x0, Mono. NFC scan, targets.txt and web_job.txt all create such targets. Because only Segment tags were excluded, these targets were offered Set Text, Set Image and WiFi Plugins. Set Text on a 0x0 job reaches malloc(0), which official and Momentum firmware treat as a fatal error.

• Set Text, Set Image and WiFi Plugins are offered only for dot-matrix profiles found in the table. Every one of the 28 dot-matrix entries, including type 1626, keeps them.
• Show Tag Info says the type is not in the profile table and which actions are hidden, instead of "Size: 0x0" and "Color: Mono".
• A 0x0 text job is refused before either sized text path allocates.
• Manual barcode entry with all 16 slots used shows "Target List Full". It used to open Target Actions with selected_target -1, where Show Tag Info and LED Test index targets[-1].
• Widget buttons call back on press, short press and release, so the "Unsupported Tag" Back button went back twice. It now acts on the short press only.

Independent of #56 and #54; merges cleanly with both.

Verification

• Builds with zero warnings against release SDK 1.4.3 (API 87.1) and dev SDK 7f0b6e1c (API 88.2).
• A host check of the old and new graphics predicate over the whole profile table: only unknown profiles change.
• New strings measured against the firmware's u8g2 fonts; all fit.
• Hardware (Flipper Zero, Momentum mntm-012, API 87.1): entering a barcode whose type code is not in the profile table shows "Unsupported Tag", and one press of the on-screen Back button returns to Targeted Payloads. Before this change the same press went back twice, landing on the main menu.

🤖 Generated with Claude Code