fix(operations): restack runner JSON integrity on current main

[seonghobae]

Draft successor to #330 on protected main 26de1c3ab69106900410f6ceb18420109bfd9f8f. Exact successor head c62e19eb31b52028b7ad8bd37b04effc3c13df79 is constructed directly on that base and changes only scripts/actions-runner-assignment-audit.mjs, test/actions-runner-assignment-cli.test.ts, and vitest.config.ts. The three protected target blobs were unchanged from #330's construction base immediately before the restack, so no intervening protected-main bytes are overwritten. The retained behavior rejects malformed UTF-8 and duplicate decoded JSON object names before runner-assignment evidence is parsed. This is read-only evidence hardening and does not prove runner assignment or operational acceptance. Keep Draft until fresh exact-head application CI, reviewer-ci, protected-base central Security Scan, configured 100% owned production statement/branch/function/line coverage with realistic tests, and zero valid unresolved findings are all terminal-passing. No predecessor evidence transfers. Supersedes #330 only after protected integration. Related: #30.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e2af205d-26b2-4c0c-95bc-502352ccc486

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Superseded by clean current-line successor #341, which retains the exact runner-assignment JSON byte-integrity and production coverage implementation. Closing this predecessor; its historical CI, scanner, and review evidence is not reused.