mattogodoy/nametag

createNtfyEndpointSchema in lib/validations.ts is now a @deprecated alias kept solely so that existing tests resolve. The creation route validates with createEndpointSchema, the discriminated union that also accepts webhooks. The two are structurally equivalent today, because the union contains exactly that object, so nothing is actually untested. But tests/lib/validations.test.ts exercises a schema that no production code path uses, which is the kind of divergence that quietly stops meaning anything the moment the union changes. Point those tests at createEndpointSchema and delete the alias. While there, note that createEndpointSchema itself has no direct unit tests in that file, so the union's discriminant behaviour is only covered indirectly through the route tests. Found during review of #449.

Two areas of the UI have translations that were written without a native speaker and would benefit from review. Notification destinations (added in #435) 22 new keys under settings.notifications.* in all ten locale files. Lower confidence on ru-RU, ja-JP and zh-CN. The important pair is endpointTestBlocked and endpointTestDns. These deliberately convey different things: endpointTestBlocked is permanent: the URL was refused and the user must change it. endpointTestDns is transient: the hostname did not resolve, the URL may be fine, try again. A translation that renders both as a generic "could not connect" silently undoes that distinction for those users, and no automated check can detect it: the locale parity test only compares key trees, not meaning. A self-hoster whose resolver hiccupped would be told to change a URL that was correct. Specific wording to look at: ru-RU: "не удалось определить" for DNS resolution is weaker than the conventional "разрешит