Align public GitHub content with current evidence

[berginj]

What changed

• reconciles public status and test evidence with the exact green main run at 211d246 (1,267 passed, 32 skipped, 0 failed)
• rewrites the linked installation, launcher, quick-start, FAQ, build, and release guides around the actual no-installer release state
• removes stale rolling-shutter, universal camera-placement, unsupported accuracy, storage, update, and security-bypass guidance
• adds public support and security policies and hardens issue/PR templates for privacy-safe evidence
• replaces the hard-coded release publisher with explicit tag/artifact/notes/checksum inputs and overwrite refusal
• marks superseded and historical camera/troubleshooting pages so they cannot compete with current status
• corrects wrong repository links and obsolete launcher commands

Why

The public repository mixed current evidence-first v2 status with older v1.x installation, webcam, setup, and release instructions. Some pages linked to Claude Code issues, claimed an installer that is not attached to v2.0.0, advised bypassing Windows security controls, or stated universal calibration geometry that has not been physically validated.

GitHub settings already aligned

• private vulnerability reporting enabled
• empty Wiki disabled; repository Markdown remains canonical

Validation

• all local links resolve across 98 active Markdown files
• no known wrong-repository or master branch links remain
• all three issue-template YAML files parse
• release-helper PowerShell syntax parses
• release helper has no hard-coded release identity
• Flake8 passes repository-wide with zero findings
• file-length and schema-mirror gates pass
• git diff --check passes

Evidence boundary

This change updates public claims; it does not claim physical speed/location validation, known-good hardware, or a released v2 installer.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ccc4b955d7

ℹ️ 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]

Verify installer version before publishing

Because this uploads whatever -InstallerPath points to after only checking that its checksum file matches, a release operator can pass -Tag v2.1.0 with a stale PitchTracker-Setup-v2.0.0-stereo.exe and the matching .sha256, and the helper will publish the old installer under the new tag. Since this script is now the documented release publication path, reject installer/checksum filenames or embedded metadata whose version does not match $Tag before calling gh release create.

Useful? React with 👍 / 👎.