TenantAtlas/specs/332-product-process-flow-system-v1/tasks.md
Ahmed Darrazi a7897fa064
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 3m49s
Add product process flow for restore create
2026-05-26 02:03:14 +02:00

2.5 KiB

Tasks: Spec 332 - Product Process Flow System v1

Input: specs/332-product-process-flow-system-v1/spec.md, specs/332-product-process-flow-system-v1/plan.md

Reconciliation

  • Keep only one Spec 332 directory in the repo: specs/332-product-process-flow-system-v1.
  • Document that Spec 332 was reconciled from the narrower restore-run-preview-productization path into the intended Product Process Flow scope.

Phase 1: Product Process Flow pattern

  • Reuse existing restore safety, preview integrity, execution readiness, and backup quality state as the Product Process Flow source of truth.
  • Add the shared Step 1 full-flow presentation for Restore Run Create.
  • Add the shared compact later-step safety status presentation.

Phase 2: Restore Run wizard contract

  • Step 1 renders Restore Safety decision card.
  • Step 1 renders backup selector plus backup quality summary.
  • Step 1 renders the full vertical Restore safety gates flow.
  • Step 1 renders Restore Proof aside with diagnostics collapsed.
  • Step 2+ render compact Restore Safety Status instead of the full gate flow by default.
  • Step 2 hides mapping details by default and only reveals an explicit Resolve target mappings resolver when opened.
  • Step 2 resolver shows progress copy and blocks Next until required mappings are resolved.
  • Step 2 group mapping picker uses task-specific cache-empty guidance and source-group context instead of generic directory-cache empty copy.
  • Step 3 blocks Next when validation blockers exist.
  • Step 4 remains decision-first and reflects actual gate state.
  • Step 5 remains high-friction before execution.
  • No false recovery-proof claims appear before execution/post-run evidence exists.

Phase 3: Tests + formatting

  • Add/update feature tests for:
    • only one Spec 332 directory exists
    • Step 1 full Product Process Flow
    • Step 1 usable source gate truthfulness
    • Step 2 compact safety status
    • Step 2 explicit resolver mode and blocked progression
    • Step 2 empty group-picker productized empty state
    • Step 3 blocked progression
    • Step 4 truthful preview copy
    • Restore Proof persistence
    • diagnostics collapsed
    • no false recovery-proof claims
  • Add/update browser smoke for Step 1, Step 2 default, Step 2 resolver, Step 2 empty picker, Step 3 blocked, and Step 4 preview.
  • Run targeted Spec 332 and Restore Run create wizard tests.
  • Run browser smoke.
  • Run pint --dirty.
  • Run git diff --check.