ts1261-filename-casing

Identify both casing spellings in the TS1261 message, choose the one matching your imports, then rename the file with a two-step git mv through a temporary name. Re-run your compile command to confirm the error is gone.

On case-insensitive filesystems like macOS and Windows, `git mv a.ts A.ts` often no-ops or fails because both paths resolve to the same file. A two-step move through a temporary name forces git and the filesystem to register the change.

Linux filesystems are typically case-sensitive, so case-only renames work directly and TS1261 casing conflicts are rare. The two-step rename workflow is primarily needed on macOS and Windows default filesystems.

Re-run your compile command (for example npm run compile) and check that TS1261 no longer appears. Also run `git ls-files` on the directory and grep for the basename to confirm a single entry whose casing matches your imports.

Use `git rm --cached` only to remove a stale wrong-cased index entry, but you still must place the content on disk under the correct casing. The two-step git mv updates both the index and working tree in one workflow, avoiding a detached delete step.