build-number

suggest: look up error messages by raw tag before the encoded form Every error tag was run through encode_unicode_identifier before being handed to Fluent, but the .ftl files declare identifiers literally, so any tag containing an uppercase or non-ASCII character could never match: msyn-Sg3-ConNeg was looked up as msyn-sg3-conneg, and msyn-gen-numeral-jahkasaš as msyn-gen-numeral-jahkasa_u0161. A miss degrades silently to the raw tag, so users saw the bare error code where the Sámi feedback title should have been — in the sidebar and in the error-type list built by error_preferences. The encoding became redundant when the forked parser gained Unicode-identifier support (divvun/fluent-rs 727b532), leaving the lookup addressing keys that nothing writes. Try the tag verbatim first, then fall back to the encoded form, so .ftl files following either convention resolve. Resolving the 199 tags in lang-sme's errors.json against errors-se.ftl and errors-en.ftl goes from 82 se / 22 en / 95 raw to 132 / 53 / 14. The first column matches what api.giellalt.org serves today, which is what identified the encoder as the cause; the remaining 67 are absent from errors-se.ftl rather than misaddressed, and need feedback text written. 79 tests pass.