Add Microsoft Store packaging and privacy policy

[FaulMit]

Summary

• add a separate Microsoft Store MSIX packaging channel with the reserved Partner Center identity
• disable GitHub self-updates in Store builds and show Store-managed update status
• use the packaged Windows startup task while keeping HKCU startup for Installer and Portable builds
• add an English privacy policy covering local capture, logs, permissions, GitHub update checks, and Store updates
• link the privacy policy from the README and document future Store submissions

Why

Captail needs an upload-ready Microsoft Store package without changing the existing GitHub Installer and Portable distribution channels. The Store submission also requires a public privacy policy because Captail can process screen, system-audio, and microphone data locally.

Validation

• dotnet build Captail.sln -c Release --no-restore
• dotnet format Captail.sln --verify-no-changes --no-restore
• Store build completed with tools/BuildStorePackage.ps1 -Version 0.1.5
• MakeAppx pack and unpack validation passed
• generated identity matched faulmit.Captail, reserved publisher, version 0.1.5.0, and x64
• English and Russian localization dictionaries remained in parity

Notes

No MSIX or MSIXUPLOAD binaries are committed or attached to a GitHub Release. Microsoft Store remains responsible for signing and distributing the Store package.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4f308e210a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Load System.Drawing from the packaging host

When this documented script is run in Windows PowerShell 5.1—the built-in shell on the supported Windows versions—Add-Type -AssemblyName System.Drawing.Common cannot resolve the project's NuGet dependency, because it is neither a framework/GAC assembly nor loaded into the PowerShell process; the preceding single-file publish also bundles it rather than leaving a probeable DLL. The script therefore stops before generating any assets or MSIX. Load the framework System.Drawing assembly or explicitly load a known assembly path that works in the supported host.

Useful? React with 👍 / 👎.