content-factory/tasks/023-workflow-template-binding-and-demo-readiness.md

Task 023: Workflow Template Binding And Demo Readiness

Development description: Bind Admin-managed workflow templates into the demo product flow so article/site configuration references an active workflow template and the final demo checklist proves workflow management is not an isolated Admin CRUD surface.

Implementation Details

• Backend binding:
  • Add active workflow template reference to target site configuration or article creation input, following the existing product model.
  • Validate that article creation cannot reference archived or missing workflow templates.
  • Preserve existing article workflow status behavior while exposing the configured workflow template snapshot in article detail.
  • Store the workflow template version/snapshot used by each article so later template edits do not rewrite historical article context.
• Frontend binding:
  • Article creation/site configuration shows the selected active workflow template.
  • Article detail shows the configured workflow template and stage summary in the workflow/history area.
• Demo readiness:
  • Update demo seed data with at least one active workflow template.
  • Update demo checklist/protocol to include Admin workflow creation/editing and article creation using the active workflow.
  • Keep the existing end-to-end publishing path working.

Public Interface

• Admin can configure which active workflow template is used by a site or article.
• Editor can see which workflow template governs an article.
• Demo reviewers can prove the Admin workflow builder affects the article flow.

Acceptance Criteria

• TDD pre-requirement: before implementation, write one failing public API test showing article creation stores the active workflow template snapshot; proceed one behavior at a time and record evidence in Result.
• Seed data includes an active workflow template with stages matching the demo pipeline.
• Article creation records the workflow template id, version, and stage summary snapshot.
• Article creation rejects archived/missing workflow template references.
• Article detail exposes workflow template summary to the frontend.
• Site configuration or article creation UI allows selecting an active workflow template.
• Existing end-to-end demo publishing smoke still passes.
• Final demo readiness protocol includes manual steps for Admin workflow create/edit/reorder/activate and Editor article flow using that workflow.

Verification

• Run backend article creation workflow-template binding tests.
• Run existing end-to-end demo stack smoke test.
• Run frontend model tests for the selected workflow template display.
• Run final manual demo checklist and record the protocol.

Result

• Status: Not started.
• TDD plan:
• Red evidence:
• Green evidence:
• Refactor notes:
• Verification output: