Frontend: Project setup, guide, source snapshot, and policy activation flow

[Abiorh001]

Parent: #29
Depends on: #50, backend policy APIs #30

Why

Flow 1 requires admins/project managers to create projects, add guide material, run guide sufficiency, approve derived policy, compile pre-submit policy, and activate the project. There is no real frontend for this yet.

Roadmap Source

• docs/product_first_user_flows.md Flow 1
• docs/architecture_lockdown.md Project Guide Structure
• PR [codex] Implement submission artifact policy foundation #28 project setup APIs

Scope

• Project creation form.
• Guide creation/edit view.
• Guide source snapshot view showing immutable source refs and bundle hash.
• Sufficiency report status, blocking gaps, warning acknowledgement.
• Submission artifact policy review/approval view.
• Effective policy and pre-submit checker bundle summary.
• Activation readiness checklist.

Acceptance Criteria

• Project manager can complete the project activation setup path from UI when backend prerequisites exist.
• Blocking/warning states are visible and actionable.
• Unsafe hidden internals are not exposed to workers.
• UI surfaces immutable hashes/provenance clearly for operators.
• Tests or demo evidence cover happy path and blocked activation path.

Contributor Fit

Good product/frontend task after the frontend foundation and policy runtime APIs stabilize.