Distinct audit receipts across locked UI gateways

[aruintelligence]

Problem

In locked deployment mode, Agent UI component and governance-stream node receipts used the runtime's deterministic default audit ID. Separate live evaluations of the same input in the same timestamp window could have indistinguishable evidence. Caller-provided audit fields on later stream messages were also not explicitly rejected.

Change

• Give each locked Agent UI component and accepted governance-stream node a fresh server-generated audit stream UUID.
• Reject caller-selected audit IDs, including explicit nulls, throughout the locked gateway paths.
• Add validated trusted-host ID options for direct APIs while keeping fixed-input local replay deterministic.
• Update TypeScript declarations and locked-policy guidance.

Verification

The new gateway tests failed on the prior deterministic IDs / accepted node override. They now check distinct IDs and receipt hashes across repeated live requests, receipt verification, override rejection, and local replay behavior. Full Node tests, public contract, deployment surface, API stability, upgrade contract, and link checks pass.

An audit ID distinguishes records; it does not authenticate a caller or prove intent truthfulness.