fix: Resolve PinNote/PInNote case-collision causing phantom modified files

[steverobertsuk]

What was happening (plain English)

Some users would clone the repository and immediately see several files marked as “changed,” even though they had not edited anything.

This happened because the repository accidentally contained two folder names that look almost the same:

• PinNote
• PInNote

On Windows (and some Mac setups), those names are treated as the same folder because the file system ignores uppercase/lowercase differences. Git, however, treats them as different paths. That mismatch makes Git think files are constantly modified.

Why this was confusing

• "Discard changes" did not fix it.
• "Stash" did not fix it.
• Re-cloning did not fix it.
• It looked like a local user issue, but it was actually a repository naming conflict.

What this PR changes

This PR removes the duplicate case-variant folder and keeps a single canonical PinNote path.

Result

After this change:

• Fresh clones no longer show false file modifications.
• Git status is clean for users who made no edits.
• Normal workflows (stash, discard, pull, commit) behave as expected.

User impact

This is a cleanup/fix PR. It does not introduce new features.
The main benefit is reliability and reduced confusion for contributors, especially on Windows.