Frontend: Worker task, pre-submit feedback, submission, and revision surface

[Abiorh001]

Parent: #29
Depends on: #50, #31, #36, #38

Why

Workers need a UI for assigned tasks, guide context, submission packets, evidence, pre-submit checker feedback, and revision replay. This is central to the Workstream pilot loop.

Roadmap Source

• docs/product_first_user_flows.md Flows 3 and 6
• docs/operations_operator_workflow.md Worker Submission and Revision Workflow
• docs/operations_revision_replay.md
• docs/decision_0011_submission_artifact_policy_drives_pre_submit.md frontend/demo wording boundary

Scope

• Worker task detail view.
• Submission packet form: summary, artifacts, evidence, package hash, worker attestation.
• Pre-submit checker feedback view using worker-safe messages.
• Submission version/history view.
• Needs-revision view showing prior findings and required fixes.
• Revision replay form with evidence per finding.

Acceptance Criteria

• Blocking pre-submit failures are displayed as pre-submit feedback, not review decisions.
• Worker cannot submit when backend marks packet ineligible.
• Worker sees only safe messages; internal task_setup_blocked details stay hidden.
• Revision replay requires each high/medium finding to be addressed when backend support exists.
• Tests/demo evidence cover clean submit, blocked pre-submit, and revision flow.

Contributor Fit

Major frontend/pilot issue with high demo-day value.