docs: separate release publication from print verification

[CrimsonSoul]

Summary

• Separate release publication from physical-print verification, as explicitly requested by the user.
• Preserve all four protected checks, committed versioning, explicit release dispatch authority, and packaged Windows startup evidence for the exact merged commit.
• Keep the full Word/physical-printer checklist and require an honest release-note disclosure when that validation is unavailable. Known printing failures still block release.
• Documentation only: no application, printing, tests, or workflow code changed; version remains 3.1.0 from feat: prepare ShiftPress 3.1.0 dark UI and print safeguards #12.

Verification

• git diff --check passed; changed Markdown links resolve.
• Both local copies of the release skill and their UI metadata validated and match.
• A dry-run baseline reproduced the old physical-printer-only blocker. Updated-skill scenario tests allow authorized software-verified publication while preserving stops for a later wait instruction, an advanced main SHA, stricter repository policy, failed Windows tests, missing authority, and an existing tag.
• All protected CI gates remain required before merge. The newly merged executable will receive its own packaged Windows startup check before the authorized release dispatch.

Physical Word/printer validation has not been completed; publication must not be described as print-verified.

[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: 4bb10a93-10fe-4107-929f-b19e0fbbe40c

---

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.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[CrimsonSoul]

Publication verified

• Release: https://github.com/CrimsonSoul/ShiftPress/releases/tag/v3.1.0
• Download: https://github.com/CrimsonSoul/ShiftPress/releases/download/v3.1.0/ShiftPress.exe
• Tag v3.1.0 resolves to commit e08cb2e7d97a98ed7f531880034c1c18965ab316, matching the Parallels packaged-startup-tested commit and the successful release workflow head.
• Release workflow: https://github.com/CrimsonSoul/ShiftPress/actions/runs/33961092263 — all jobs successful.
• Release build artifact: ShiftPress-v3.1.0-e08cb2e, ID 9968000127.
• Downloaded published executable is PE32+ x86-64, 27,937,310 bytes. SHA256 0d5e4635a57374c7afe4c1a85e4c3ce81dde2064da0d5a898bd29782559a58bf matches GitHub's asset digest.
• Published release notes explicitly disclose that Word/physical-printer testing was not completed; physical printing is unverified.
• Main is clean with zero divergence, only local main remains, and the temporary remote PR branch is deleted. A verified external Git bundle preserves the pre-squash local tip.

Both local release-skill copies and UI metadata are aligned and validated. No application or printing code changed in this policy follow-up.