[game-memory-mode] add Game Mode Optimizer

[sannidhyas]

When a game starts, voice typing and animated wallpapers can keep using desktop resources. Game Mode Optimizer temporarily stops active Voxtype and replaces live wallpapers with a static frame, then restores their previous state after the last game or manual/Gaming hold ends.

This community QS Bar plugin follows the existing Quick Settings Gaming switch without replacing its performance/DND behavior. It also provides an independent manual control and an optional argv-based launcher wrapper for Heroic and Steam. Launcher configurations are explicitly set by the user; the plugin never edits them. It uses Ryogami's owning API and only temporarily stops/starts voxtype.service, without changing enablement.

The helper starts on demand with no installation hooks or extra user unit, survives shell reloads during games, reconciles overlapping launches and dead owners, and restores/exits when unloaded with no remaining game. Private runtime writes stay in the plugin state directory. No networking, root access, compositor-specific API or NVIDIA dependency.

Validation:

• 12 controller tests passed, including prior-state restoration, user changes, overlapping holds, crash/new-boot recovery, invalid settings, rotation refusal, and failure rollback.
• Isolated fresh-install checks passed for startup, concurrent clients, crash restart, disabled automation and idle cleanup.
• Live desktop checks passed for overlapping wrappers, failed launches, helper SIGKILL/recovery, surviving game children and exact wallpaper/audio restoration.
• ryoku plugin validate: no blocking findings or warnings. tests/validate-catalogue.sh: passed. Staged security screen: no blocking findings and no findings in this plugin; existing catalogue warnings remain unchanged.
• On one tested NVIDIA desktop, these two actions reclaimed 1825 MiB of GPU memory. This is a measured benefit, not a promise of performance or a graphics-driver fix. An earlier Heroic/Control launch verified activation/exit restoration; sustained gameplay was not tested.

Limitations are documented: disable active wallpaper rotation first; Wallpaper Engine requires an explicit static image; Steam launch options are per game; independently regrouped game processes can escape group tracking. The README documents removal and the boundaries of source screening.

Community author/maintenance contact: @sannidhyas. MIT licensed. Contributor maintenance remains with the community author, not the Ryoku team.

Checklist:

• One plugin folder with manifest and real QS Bar screenshot.
• Registry entry with lastUpdated, official: false, upstream and content hashes.
• Tested live in Ryoku; existing bar/panel rendering checked and lifecycle checks passed.
• Catalogue validation passed.
• Original contribution licensed for redistribution.
• No direct user-configuration writes or privileged commands.