Seal machine-generated ops review bindings

[areshand]

Summary

• make ops review-bind persist an exact machine-generated request/goal/runbook binding artifact
• have the supervisor validate reviewer ownership and seal that artifact beside the reviewer verdict
• verify the sealed artifact during execution instead of asking the model to reproduce cryptographic hashes
• keep legacy text-marker verification only for evidence already sealed by older running sessions
• simplify the reviewer prompt to verdict and reasoning only

Architecture

This preserves AD-005 and AD-006: Markdown remains human-readable procedure, the reviewer performs semantic goal/runbook review, and deterministic binding remains supervisor-mediated mechanism rather than prompt policy. No operation-specific or provider-specific behavior is added.

Validation

Not run in this side conversation.