fix(rlm): configure UTF-8 for frozen Windows CLI

[zeegin]

Summary

• configure UTF-8 stdout and stderr in frozen Windows Python entrypoints before importing the upstream RLM CLI
• add captured root/build/update/info help contracts, including literal Cyrillic output, and record the Windows-only packaging policy in provenance
• advance the immutable RLM packaging identity to v1.33.0-build.2 and add a pre-merge real Windows frozen smoke job

The upstream source remains v1.33.0 at commit 3e6920cd015a61af4ba7aa1a5f1fedd8bc935549. Its frozen lock, licenses, and empty patch set are unchanged. This PR does not publish a release or change a consumer lock.

TDD evidence

RED reproduced both generated Windows entrypoints failing before main with UnicodeEncodeError under captured ASCII stdio, and showed that the producer executed only top-level help rather than nested build/update/info help.

GREEN proves both MCP and index launchers emit UTF-8 on stdout and stderr before upstream import; non-Windows stub bytes remain unchanged; missing Cyrillic output fails the producer smoke contract.

Verification

• 39 unit tests
• Python byte compilation
• actionlint
• pinned source and license validation for all manifests
• fresh Darwin native RLM build with root/build/update/info help smoke and literal Cyrillic assertion
• independent code review: no Critical or Important findings

Merge gate: the new Windows frozen smoke job must show Cyrillic index build help and exit 0 before this PR is considered ready to merge.