[Fix] Visual proof blocks capture when state requires simulation

[roomote-roomote]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Prevents the visual-proof orchestrator from adding blanket bans on source modifications, simulated payloads, or DOM/rendered-state setup to delegated proof briefs.
• Clarifies that application-source simulation remains caller-owned while the proof runner may consume the disclosed resulting state and other brief-authorized simulations.
• Adds focused regression coverage for both shared prompt layers and the removed prohibition.

Why this change was made

The shared policy already allowed transparent simulation, but dynamically authored proof briefs could still reintroduce the former blanket restriction. The prompt contract now requires scoped disclosure instead of categorical refusal.

Impact

Visual proof can use transparent simulation when genuine state is impractical, without weakening provenance, cleanup, anti-fabrication, or proof-limit requirements.

[roomote-community]

No code issues found. See task

_{Reviewed 9266db1}