[Iteration 017][Verification] Run revision-loop and audit-trail acceptance

[beagle1903]

Outcome

Verify the complete Iteration 017 contract on the merged implementation and record durable acceptance evidence.

Canonical contract: Iteration 017
Parent: #22
Blocked by: all implementation and presentation work items under this parent.

Scope

• Profile, evidence, screening-policy, construction-policy, explanation-only, mixed, and close-without-revision decisions.
• Successful side-effect reuse, explicit retry, ambiguous-attempt fail-closed behavior, and adapter call counts.
• Revision/audit JSON round trips and tamper cases.
• Expiry preview/prune, exact-thread deletion, restore failure after deletion, and in-memory discard.
• Dashboard revision history and safety boundary.
• Durable evidence in the canonical iteration record.

Acceptance criteria

• Every feedback class reaches only its contracted restart boundary and invalidation set.
• Completed side effects are not replayed; ambiguous attempts stop before adapter invocation.
• Lineage and source snapshot identities survive checkpoint restore and fail closed on tampering.
• Retention/deletion behavior matches the accepted lifecycle contract.
• Full repository gates and representative local UI verification pass.
• No credentials, network market-data call, provider request, trade, or external financial write is required unless separately approved.
• The iteration record contains tested commit, commands/results, UTC timestamp, environment, scenarios, limitations, PR/CI links, and acceptance outcomes.

Verification

Run the standard gates and the iteration-specific acceptance matrix against the merged baseline.