Repair Unicode Filename, Path & Normalization Bugs

The likely issue is a contract mismatch around Unicode filenames, normalization forms, case folding, combining characters, path comparison, archive/object keys, cross-platform filesystem behavior, duplicate identity, display-versus-storage representation, and migration safety. I would first define the invariant: Filename identity must use an explicit canonical comparison contract while preserving the original display name; visually equivalent or canonically equivalent names must not silently become different authorization or storage identities. Then I would trace the smallest owning boundary, apply or propose a bounded repair/review step, and add deterministic normal, boundary, failure and replay tests. The workflow preserves existing authorization, privacy, security policy, public interfaces, user-visible behavior, and documented operational ownership. If repository/workspace files are available, findings can be mapped to exact paths and focused local validation; with partial evidence, the result stays an explicit diagnosis/evidence map with assumptions and no invented execution claims.