V1 Recovery R12 — Deliver Paper Feedback and the human Research Review loop

[tonywxx]

Part of #129.

Problem Statement

Feedback contracts are not a secure, visible path from realized OKX Paper evidence back to a human research decision.

Solution

Bind immutable feedback snapshots/reports to Host-derived User authority and expose review decisions that create new research attempts/bundles.

Acceptance Criteria

• Factor, Model, Strategy, and Execution feedback bind exact deployment, market, account, fills, horizon, and evidence lineage.
• Sample sufficiency and realized-horizon gates prevent premature conclusions.
• Research Review Required alerts and User decisions are visible, immutable, and User-authorized.
• A decision may create a new Attempt or Bundle but never retrains, switches, or hot-patches a running deployment automatically.

Out of Scope

Autonomous optimization, online learning, or cross-user review.

Planning Source

• docs/v1-completion-recovery-map.md
• docs/adr/0090-rebaseline-v1-to-okx-spot-end-to-end.md

Implementation must run in one independent $implement <issue> session. Complete every acceptance criterion, record exact verification in an English issue comment, and close only after all evidence passes.

[tonywxx]

This issue is retained as a future Paper Step 10 candidate under the fifteen-gate delivery sequence specified by #144.

It is not an executable frontier now. Its scope and current-head gaps must be revalidated when Gate 13 is explicitly User-authorized. Historical implementation and evidence remain useful, but do not grant Module Acceptance or Workflow Continuation Approval.