Prepare ms-private 0.0.1 release candidate

CONTRIBUTING.md

@@ -0,0 +1,11 @@
+# Contributing
+
+Use Windows PowerShell 5.1-compatible syntax. Keep the menu independent from system changes; core operations must be callable and testable without interactive input.
+
+Run `tests/Run-All.ps1` in both Windows PowerShell 5.1 and PowerShell 7. Do not use real app uninstallers or production registry writes in automated tests. Add a regression for a demonstrated failure path, including nonzero native exit codes and interrupted operations.
+
+Each new privacy control needs a primary source, edition/build scope, concrete impact, original-state capture and behavioral validation. A registry match is not proof that Windows enforces a policy. Do not add security exclusions, broad package-removal wildcards, arbitrary command-string execution, forced Edge removal or identifier spoofing.
+
+Keep personal reports, test captures, release binaries, local paths and credentials out of the repository. The reviewed privacy register and blog draft live under `docs`; generated intermediate data stays untracked.
+
+Before publishing a stable release, complete the live validation matrix, select a project license and record any signing/release provenance. A passing CI badge alone is insufficient.