[major] Retire .Core from the published package ID

[matt-edmondson]

Fixes #72

What changed

Keybinding.Core.csproj published as ktsu.Keybinding.Core. Because ktsu.Sdk derives the package ID from the project filename, an internal decision about whether the repo also ships an executable was leaking into the published ID.

• Renamed the project folder and file Keybinding.Core → Keybinding, so the derived package ID becomes ktsu.Keybinding.
• Updated the solution entry and the ProjectReference in both Keybinding.Test and Keybinding.Demo.
• Retargeted all 80 entries in CompatibilitySuppressions.xml, which address suppressions by assembly path (lib/<tfm>/ktsu.Keybinding.Core.dll → lib/<tfm>/ktsu.Keybinding.dll).
• Updated the NuGet badges and the project-reference sentence in README.md, and the tree diagram in CLAUDE.md.

Keybinding.Demo already matched the convention and needed no rename.

Verification

	Package produced	Tests	Demo build
main	ktsu.Keybinding.Core.1.0.54.nupkg	—	—
this branch	ktsu.Keybinding.1.0.54.nupkg	52/52 passed	0 errors

The CompatibilitySuppressions.xml retarget is load-bearing. Reverting just that file and re-packing surfaces 6 diagnostics that main suppresses:

Diagnostic	main	this branch	suppressions left stale
CP0014	—	—	5
CP0015	—	—	1
unmatched-suppression	2	2	3
CP0001 / CP0002 / CP0008 / CP0016	6 / 20 / 1 / 7	6 / 20 / 1 / 7	6 / 20 / 1 / 7

With the file retargeted, this branch's diagnostic signature is identical to main's.

Note that dotnet pack exits non-zero on main in this environment already — suppressed diagnostics resurface regardless of the rename. That is pre-existing and orthogonal; the point of the table is that the before/after signatures match exactly.

One open question, deliberately not decided here

Source namespaces still read ktsu.Keybinding.Core, ktsu.Keybinding.Core.Models, ktsu.Keybinding.Core.Contracts and so on. The issue's Convention paragraph says "assembly name and root namespace equal the package ID", which would make these ktsu.Keybinding.* — but its numbered Change list asks only for the folder, .csproj and solution entry.

Those differ in blast radius by a lot. Renaming the package alone breaks a consumer's PackageReference line; renaming the namespaces additionally breaks every using directive they have. I kept to the change list, so this PR is a package-ID break only and existing source keeps compiling. If the namespaces should move too, that is worth its own issue and is best landed in the same major.

Not in this PR

Step 3 of the issue — republishing ktsu.Keybinding.Core once as a deprecated meta-package depending on ktsu.Keybinding, so the 35 already-published versions get a working upgrade path rather than a dead ID — is a nuget.org publishing action rather than a source change. It still needs doing before or alongside the first ktsu.Keybinding release.

The commit is tagged [major] per the issue's "ship at the next major".

🤖 Generated with Claude Code

https://claude.ai/code/session_01KgqmLojZd3sn1M5mRN75ms

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate failed

Failed conditions
52.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud