v1.1.7

Dependency-maintenance release — no optimizer behavior changes from v1.1.6.

What changed since v1.1.6:

• Build-tool security bumps (fleet sweeps #4 and #5): setuptools 75.8.2 → 84.1.0 in the build system and dev set (through 83.0.0 for PYSEC-2026-34, then 84.1.0 for GHSA-xmj3-9gf7-h52w), the pywin32 pin aligned 310 → 312 to match the canonical pin list, and black 25.1.0 → 26.10.1 in the dev set (PYSEC-2026-2120/2121). Build and development tooling only — no runtime dependency changed.
• Dependency installs are hash-locked now (fleet policy adopted 2026-10-25): the runtime, development, and release sets each have a committed lock (NitroCore/requirements.lock.txt, requirements-dev.lock.txt, requirements-release.lock.txt), and every install path — CI, the release workflow, and the documented from-source routes — installs with --require-hashes. The release workflow's PyInstaller install, previously an inline pip install pyinstaller==6.11.1 with floating transitives, now goes through the release lock.
• A full functional bug hunt ran on this tree and found no defects to fix: full suite 195 passed, 1 skipped; --help, --self-check, and a headless --dry-run preview pass; the interface was built under a virtual display with all six tabs visited and every registered button confirmed wired to a real command.

Assets: NitroCoreOptimizer.exe, NitroCorePortable.zip, SHA256SUMS.txt. The release workflow's staged start proof (including the standard-user spawn check) ran and passed before publishing; no other hardware proof is claimed.

Full Changelog: v1.1.6...v1.1.7