Broader entity handling and sensitive-type escalation

Klyo Context Engine v0.5.0 broadens how it handles enterprise content across English, German, and French.

Multi-word organization names — hospitals, banks, clinics, agencies — are resolved as organizations rather than reading the trailing word as a person. Phone-shaped identifiers (SKUs, serials, order numbers, invoice numbers) are not treated as personal contact numbers when context makes the business intent clear. Example IBANs in documentation, product keys shaped like passport numbers, and tax IDs in business context are each handled separately from their personal-data counterparts.

For catastrophic-sensitivity content — API keys, credit cards, medical identifiers, genetic and biometric data — the engine now actively escalates classification to BLOCK when context confirms the candidate is real, in addition to its existing role of suppressing false positives.

Recall on real personal data stays at 100% across all test corpora. No action required.