docs: correct Windows CI record, add release-gating note (C1/C2, I6)

- I6: README claimed Windows CI status as "Unconfirmed". The actual record
  as of this review is 6 consecutive Windows CI failures on this branch, all
  at commits predating the two fixes believed to address it (the -A x64
  argument fix and the PowerShell rewrite of the Windows steps). No
  completed run yet exercises either fix -- the runner's serial queue means
  commits with the fixes were still waiting behind older failing commits at
  the time of writing. Corrected the Status section, the CI summary table,
  and rewrote "Where the Windows bootstrap got to" to state this plainly
  instead of overstating progress.

- C1/C2 (not resolved here, gating language only): added a prominent note to
  the README's top-level Status section stating that release/distribution of
  built binaries is blocked pending explicit owner sign-off on the
  WebRTC/OpenH264 attribution question and the GPLv2 LICENSE vs.
  Apache-2.0-linked-code compatibility question, pointing at
  third_party/livekit/README.md where the details already live. Checked
  .gitea/workflows/build.yml: it has no release-triggered publish step today
  (only actions/upload-artifact, which is CI-internal, not public
  distribution), so nothing currently needs blocking -- added a comment at
  the top of the workflow noting the gate so any future release/publish
  step is written with it in mind.

Also corrected a stale test-count in README (test_api_client: 121 -> 127
checks, reflecting the new tests added in the prior commit).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RL8abRmgFXkVASHkkqiJbE

.gitea/workflows/build.yml

@@ -9,6 +9,15 @@ name: Build
 # bootstrap (buildspec.json + cmake/common/buildspec_common.cmake), which
 # downloads the pinned obs-deps bundle and obs-studio source and builds just
 # `libobs`. That step is the slow one: several minutes on a cold runner.
+#
+# RELEASE GATE: this workflow only builds, tests, and uploads CI-internal
+# workflow artifacts (actions/upload-artifact, below) -- it does not create a
+# Gitea Release, push a tag-triggered publish, or otherwise distribute
+# binaries publicly, and it must not start doing so without explicit owner
+# sign-off on the WebRTC/OpenH264 attribution and GPLv2/Apache-2.0
+# license-compatibility questions tracked in third_party/livekit/README.md
+# and the README's top-level Status section. If a real release/publish step
+# is ever added here, it must carry that same gate.
 
 on:
   push: