Update protondb-decky to v1.3.3

[bschelst]

Update protondb-decky to v1.3.3

Since version 1.2.0 on the decky plugin database, this are the changes:

Adding Compatibility Analysis button, all data from protondb, which:

• shows the details of the game , working status with confidence level, trend direction, freshness
• Reports — A 5-year report history chart showing good vs bad reports per month, plus the 20 most recent individual reports
• Versions — Proton version breakdown so you can see which version has the best results. The Steam Deck default is highlighted
• Settings — Launch options extracted from positive community reports. Tap Copy and paste directly into your game's launch options

Can be disabled in settings

Library Status Icons
Small status icons now appear on game covers in your library grid:

• Green = game should work
• Red = borked or not working
• Gray = unknown or not enough data

Can be disabled in settings

Trend Highlighting
The ProtonDB badge itself now shows trend borders. If recent reports show degraded behaviour, you'll see a red border. If things are improving, a green one.

Under the Hood

• Extensive caching to reduce API load and keep things fast on the Deck. Because of this you will see some delay in refreshing the badges if you have a huge library, but I don't think this should be a big issue, knowing that the API servers need to be able to handle all that load.
• Data validation throughout to prevent crashes if API data changes
• Background prefetching so your library icons are ready when you browse.
• Submit button changed to a compact icon to save space

Details tab	Reports tab
Versions tab	Settings tab
Library status icons	Store page overlay

---

Task Checklist

Developer

• I am the original author or an authorized maintainer of this plugin.
• I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.
• Generative AI was NOT used to write a majority of the code I am submitting.

Plugin

• I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
• I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

• No: I am using a custom backend other than Python.
• No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
• No: I am using a custom binary that has all of it's dependencies statically linked.

Community

• I have tested and left feedback on two other pull requests for new or updating plugins.
• I have commented links to my testing report in this PR.

Testing

• Tested by a third party on SteamOS Preview update channel.

[github-actions]

Issues Found

• Both testing boxes are present in your description. Please remove one of them per the Markdown comment above the testing section.

Next Steps

1. If we found any issues above, please edit your pull request description to resolve them and leave a comment saying you've done so.
2. For the quickest review, please see the Community section of the pull request template for how you can help other developers.
3. Once your description is correct, a maintainer will review your pull request as soon as possible.

Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️

[bschelst]

Example Plugin test reports:

#1029 (comment)
#922 (comment)
#946 (comment)

[Cliffback]

Gave this a test, and works great, however I think i noticed a bug. Not sure if it is related to this release, or if it was there from earlier. Looking at the changelog, I would guess not, but I'll just mention it here regardless.

There is two different scalings for the small size. Posted and issue in the plugin repo: bschelst/protondb-decky#4

[mdeguzis]

[x]  Generative AI was NOT used to write a majority of the code I am submitting.

Could you clarify the amount of usage here?

• bschelst/protondb-decky@d4212a6 is a massive single commit with boilerplate adds, structured multi-line descriptions that read a bit robotic when compared to other commits in history, and other A.I. patterns commonly used,
• The larger commits use mixed naming conventions, like getSetting vs setSetting, where Python is snake_case.
• Ignore .lean-ctx and remove dead library grid code: .lean-ctx is a context file used by Lean (an AI coding assistant, which used to be Cursor's context system), but the gitignore is just .le here so many just some confusion in reading this commit text vs the actual change

Otherwise change looks good.