Prepare 1.1.0: slugify() and hash()

[mohaelmrabet]

Two methods that were already being written by hand on top of tokenize() at call sites — which is how two callers end up with different answers for the same string.

slugify(string $text, string $separator = '-')

Joins the tokens tokenize() already produces, so a slug can never disagree with the rest of the package about where a word ends. Text that normalizes to nothing yields an empty string.

It is not an ASCII slugger. Non-Latin input stays in its own script, folded but not transliterated — the same distinction the README already draws against cocur/slugify, so that table gained a row rather than being contradicted:

$normalizer->slugify("L'adresse email de l'utilisateur"); // "l-adresse-email-de-l-utilisateur"
$normalizer->slugify('Météo à Rabat', '_');               // "meteo_a_rabat"

hash(string $text, string $algo = 'sha256')

Digests the slug. Two strings this package considers equivalent — casing, typographic apostrophes, collapsed spacing, trailing punctuation — always produce the same digest, which is what makes it usable as a deduplication or lookup key:

$normalizer->hash("L'adresse email") === $normalizer->hash('L’ADRESSE   email.'); // true

Documented as a fingerprint and not a secret: unsalted and deterministic by design, never a password hash. An unsalted digest invites the wrong reading, so both the PHPDoc and the README say so plainly.

Scope

No behaviour changed. normalize(), tokenize() and analyze() are untouched, and both additions are pure functions of normalize() — nothing folds text a second way.

52 tests green, PHPStan clean at max level.

Release

Prepares v1.1.0 (additive, minor). CHANGELOG.md is written for it; tag after merge.

[mohaelmrabet]

Fermée sans merge : le package n'est pas un générateur de slug.

Cette frontière est déjà écrite dans son README — il produit une clé de comparaison dans le script d'origine, et renvoie à cocur/slugify pour un slug d'URL. Joindre les tokens qu'il produit est l'affaire de son consommateur, qui le fait déjà.

L'origine de la demande, ADR-0042 §4 côté Concio, a été corrigée en conséquence.