fix(runtime): require bridge materialization acknowledgment

[drewstone]

Failure reproduced

A stale HTTP bridge ignored agent_profile, echoed the current run-id and request-digest headers, returned IGNORED_PROFILE, and streamAgentTurn completed while reporting materialization known with matching authored and effective profile digests. The current receipt proves Runtime intended to send the profile; it does not prove the downstream agent used it.

Required behavior

• Require cli-bridge acknowledgment of the canonical effective profile digest and actual harness, provider, and model.
• Compare every acknowledged value against the exact AgentProfile and Runtime-selected execution before accepting output.
• Bind the acknowledgment to durable run identity and validate it on create, stream reconnect, read, resume, and terminal replay.
• Refuse old bridges, missing acknowledgments, and any mismatch before reporting successful execution.
• Keep raw observed-only adapters internal; public exact execution may not downgrade to intent-only evidence.

Completion proof

• The reproduced stale-bridge case fails closed.
• Matching current cli-bridge bytes complete and retain the acknowledgment in Runtime evidence.
• Digest, harness, provider, and model mismatch tests each fail.
• Resume/replay mismatch tests fail.
• Full Runtime tests and package checks pass.

[drewstone]

Use cli-bridge’s existing terminal profile_materialization receipt rather than defining another response object. Runtime must parse and compare the extended receipt; today bridgeExecutor only records its own intended materialization and ignores the bridge receipt.