feat: prepare ShiftPress 3.1.0 dark UI and print safeguards

[CrimsonSoul]

Summary

• Introduce dark-only Midnight and Rose themes with refined typography, consistent selection controls, themed Help and titlebars, content-aware window sizing, and a shared neutral printer icon.
• Preserve independent Night/Day scopes, manifest ordering, template lookup, and date patterns while blocking partial date-processing failures, keeping submitted jobs successful after cleanup errors, locking Reset/Setup during runs, and retaining failure reports on every exit.
• Add native Windows UI and backend regression tests, consolidate the project guides, and set the sole application version source to 3.1.0.

Verification

• Focused tests: 195 passed.
• Complete macOS suite: 316 passed, 10 skipped; Windows dependencies are mocked on macOS.
• Black, mypy, pylint (9.29/10), 83 script tests, and git diff checks passed.
• Parallels Windows suite: 324 passed, 2 skipped, including real Tk UI tests.
• Follow-up addresses hosted findings without altering printing: scaling-aware Help overflow fixture, focused Help behavior coverage, shared UI constants, and a behavior-preserving theme-loop simplification. All hosted gates must pass on the final revision.

Release boundary

This PR prepares the 3.1.0 release candidate; it does not establish physical-print verification. Word is not installed in the testing VM. Public release dispatch remains blocked until the merged executable completes the documented Microsoft Word and physical-printer smoke test. No scheduling or template naming rules were changed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
96.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 344dc5b3-8672-4179-b682-3e39da3b9f35

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[CrimsonSoul]

3.1.0 release-candidate evidence

• Merged commit: 1a2f5668046ce3fda223d9b1466c3eaa9a64dbd4.
• Required Build quality, Windows tests, SonarQube, and Snyk gates passed before merge; all four remain required by main protection. Post-merge Build and Security workflows also succeeded.
• Build run produced ShiftPress-v3.1.0-1a2f566.
• Downloaded executable is PE32+ Windows x86-64. SHA-256: 466163f2086113bd9570932e6e8860b61b627834f4a47cca99715bf3ec96baf5; the copied Windows file has the identical hash.
• On 2026-09-05, launched this packaged executable in Parallels Windows 11 with an isolated application-data profile. Confirmed the exact executable's visible ShiftPress window, displayed version 3.1.0, printer icon, dark main layout, startup survival, and clean exit code 0. Existing saved setup was not changed.
• Local main is clean and synchronized to origin/main. The temporary PR branch was deleted. Pre-squash local commits are preserved in an external verified Git bundle.

Release not dispatched

Word.Application is not registered in the VM. A physical HP printer is visible, but no documents were printed. The candidate still needs every Required run and State and safety check in the Windows print smoke checklist, with tester/date, Windows/Word versions, printer, and per-check results. Do not treat automated COM fakes or packaged startup as real printing evidence. No v3.1.0 tag or public release was created.

[CrimsonSoul]

Updated 3.1.0 release evidence

The user explicitly requested fixing the release skill's blanket physical-printer blocker and confirmed continuing publication. The two installed shiftpress-release skill copies are corrected and scenario-tested. #13 aligns the repository policy: packaged Windows startup remains mandatory, physical printing requires its own evidence and honest disclosure, and known printing failures still block release.

• Policy PR docs: separate release publication from print verification #13 merged as e08cb2e7d97a98ed7f531880034c1c18965ab316 after all four protected checks passed. Those same checks also passed on merged main.
• The only changes after feat: prepare ShiftPress 3.1.0 dark UI and print safeguards #12 are AGENTS.md, README.md, and docs/windows-smoke-test.md; application/printing code remains unchanged.
• Main Build: https://github.com/CrimsonSoul/ShiftPress/actions/runs/33960880310
• Artifact: ShiftPress-v3.1.0-e08cb2e, ID 9967927191.
• Downloaded/guest executable SHA256: 148afb30bcc4efff85ee783ba243f788e14e4c9a4eb96f551813d4b3ad4297ca.
• Packaged app launched on Windows 11 in Parallels under the interactive user with isolated APPDATA. Exact executable path matched the visible ShiftPress window; startup PASS, clean exit 0. Screenshot showed v3.1.0, the full layout without an initial scrollbar, dark titlebar, and updated printer icon.
• Word.Application is not registered in this VM. No physical print job was performed; physical printing remains unverified.
• Local main was clean and synchronized, committed version was 3.1.0, no tag/release existed, and remote main matched the startup-tested SHA immediately before the explicitly authorized dispatch.
• Release dispatch: https://github.com/CrimsonSoul/ShiftPress/actions/runs/33961092263 (head SHA matches the tested commit).

This supersedes the earlier blanket publication blocker; it does not supersede the physical-print validation limitation.