Fix APK privacy scan false positives

[Darkaxt]

Summary

• require a complete Windows path segment instead of treating any drive-prefix bytes as private
• preserve rejection of complete private paths embedded in binary assets
• add the immutable RC78 hotfix 3 release metadata and NONPARSER_REUSE attestation

Verification

• node --test tools/release/*.test.mjs (85/85)
• privacy validator passes the exact unsigned APK artifact from failed run 33260746313
• release evidence validates against RC77/schema 44 with Stage 7/8 closed
• failed run completed policy, evidence, web, Gradle/lint/build, and packaged Android gates; no release was created

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-29T15:52:18.765505Z	69088e0	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 69088e0beb

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

Match valid punctuation in Windows path segments

When an asset contains a Windows path whose first segment uses valid filename punctuation—for example, C:\Program Files (x86)\vendor\file—this character class stops at (, so the private-path scan accepts the asset. The same regression affects other valid characters and drive-root files such as C:\secret.txt; because this validator is the final privacy gate before release creation, those host paths could be published. Detect segment boundaries without restricting valid segment contents to this narrow allowlist.

Useful? React with 👍 / 👎.