feat(i18n): add Spanish medical knowledge locale

[Davidson3556]

Important

This is a stacked draft that depends on #103. Until #103 merges, GitHub will show the scaffold commits in this diff as well.

What does this change?

Adds a complete Spanish locale for the current educational dermatology knowledge surface:

• All 10 knowledge-base entries and their search keywords
• All four knowledge resources, including list metadata and full payload copy
• All three canonical clinical-safety disclaimers
• Accentless and compact search aliases such as asimetria, diametro, 6mm, evolucion, cancer de piel, and proteccion solar
• Focused tests for explicit loading, accented/unaccented search, localized resources, tool output, and disclaimer invariants

The translation covers current main. It intentionally excludes the four resources from closed PR #91 because those resources still await clinician approval and have not shipped.

Translation and review status

This translation is machine-assisted. It is not represented as native-speaker or professional translation.

Terminology was cross-checked against:

• American Cancer Society Spanish ABCDE guidance: https://www.cancer.org/es/cancer/tipos/cancer-de-piel-tipo-melanoma/deteccion-diagnostico-clasificacion-por-etapas/senales-y-sintomas.html
• MedlinePlus Spanish melanoma guidance: https://www.medlineplus.gov/spanish/ency/article/000850.htm

Before this can merge, it needs:

• Native Spanish review of all user-facing copy
• Maintainer review
• Explicit clinical-safety approval of every translated disclaimer

Related issue

Depends on #103
Fixes #22 after the reviews above are complete

Checklist

• npm run build passes
• No tools were added or removed
• No new tool input schemas
• Works in mock mode
• No secrets, real hostnames, account IDs, or personal data added
• No patient images added, including in tests
• Disclaimer translations preserve “educational only” and “not medical advice” meaning
• Full test suite passes: 119/119
• npm pack --dry-run includes locales/es/medical-kb.json

Does this change a tool's response shape?

No. This adds a locale asset and tests. English remains the runtime default; client-facing locale negotiation is tracked separately in #21.

[YauhenBichel]

Thank you for this, and I am sorry to be closing it — the work is not the problem.

MoleCare is a health product without clinical sign-off, so we hold a firm line: molecare-mcp never makes a clinical decision, and we do not ship medical wording that nobody here can vouch for. English text we already have has been through that thinking. A Spanish version needs someone who can read it as a clinician, in Spanish, and say it is right. We do not have that person today, and merging without them would quietly make the app a source of medical wording in a language we cannot check.

That is a limit on us, not on your work. The translation looks thorough, and the search aliases (asimetria, diametro, evolucion) show you thought about how people actually type.

Your branch stays where it is — nothing is deleted, and if a clinician joins who can review Spanish, this is the obvious place to start.

#103 is a different story: it moves the English text without changing a byte of it, so it needs no clinical review. I have reviewed it and I am happy with it.

Really, thank you for the care you put into this.