Update readme and json files

[mcpat-it]

Hi,

first of all, I really like your wrapper. I have some questions and suggestions.

Update the readme for installing your template to
dotnet new -i Aeroverra.StreamDeck.Template
and update (at least for VS 2026) is
dotnet new update

During packing I got some errors:

1. Fontsize must be a number "FontSize": 16
2. Name should be equal to Category
3. UUID must be in the manifest and appsettings: "UUID": "com.your.plugin.name",

Enabling DRM

And one question, acc. Elgato from January 19, 2026, new plugins will be required to be DRM compatible, and have a minimum Stream Deck version of 6.9 or higher, and manifest SDK version of 3 or higher. From February 19, 2026, this will also apply to new plugin version updates.
Plugins created with Stream Deck CLI 1.6 or higher have DRM enabled as default

Update to @elgato/streamdeck v2 or higher (Node.js plugins only). Learn more.
In your manifest, update SDKVersion to be 3.
In your manifest, update Software.MinimumVersion to be "6.9" or higher.

So the question is, would it be possible with your wrapper to enable DRM (I am just at the beginning in coding my plugin, therefore I didn't upload it until now, because they write following procedure for testing DRM:

To prepare and access a DRM protected version of your plugin:

1. Log in to Maker Console.
2. Upload your plugin, with "Publish after review" unselected.
3. Navigate to your product's page in Maker Console.
4. Select the "Versions" tab.
5. Select the new version of your plugin.
6. Download the DRM protected version.

Thank you,
Patrick

[Aeroverra]

Thank you for the feedback.

Weird though I thought I updated the templates but maybe I forgot to publish the numbers fix.

As for DRM im caught a bit off guard because when I was doing my update rounds a month or two ago I didn't see anything about this being required. Seems very short notice. It appears they are trying to appeal to a larger corporate audience sadly.

From what I can tell it should work although poentially there could be an issue if outputting to a log file maybe. I will test it with my NestControl plugin and see if it breaks at all.