content-factory/tasks/019-end-to-end-demo-stack.md

Task 019: End-To-End Demo Stack

Development description: Assemble and verify a complete demo-ready Docker Compose product path from article brief to Git-backed publish commit using deterministic runner/research/review fixtures and a local demo Next content repository.

Implementation Details

• Add demo fixtures:
  • Seed target site.
  • Demo Admin and Editor users.
  • Fake Codex runner outputs for questions, plan, sections, SEO, language, assets.
  • Fake research search/fetch corpus.
  • Local bare Git repository or mounted demo Next content repository as publish target.
• Add end-to-end test path:
  • Start stack.
  • Create article.
  • Generate/submit boundary answers.
  • Generate/approve plan.
  • Run research.
  • Verify evidence matrix.
  • Run production jobs.
  • Assemble draft.
  • Review assets, SEO, and language.
  • Final approve.
  • Dry run.
  • Create publish commit.
• Add demo documentation:
  • Setup.
  • Login/role selection.
  • Happy path.
  • Failure demo path.
  • How to inspect object storage, database state, and Git commit.

Public Interface

• A reviewer can run one command, open the frontend, and complete the pipeline without external credentials.
• The final demo produces a real Git commit in the configured demo repository.

Acceptance Criteria

• TDD pre-requirement: before implementation, write one failing end-to-end smoke test for the shortest happy path through public UI/API boundaries; add failure-path checks one behavior at a time and record evidence in Result.
• docker compose up --build starts the complete demo stack.
• Demo requires no real Codex, search, WHOIS, cloud S3, or GitHub credentials.
• Editor can complete the happy path from article brief to PUBLISH_COMMIT_CREATED.
• Final commit contains Markdown/MDX, frontmatter, and referenced assets according to site config.
• Object storage contains research source-section artifacts and manifests.
• Workflow timeline shows all major actions.
• Demo includes at least one visible failure/retry scenario.
• README/demo guide is accurate and enough for a new developer to run the product.

Verification

• Run the full end-to-end smoke suite.
• Run docker compose up --build from a clean checkout.
• Manually execute the documented demo path.
• Inspect final Git commit, object storage artifacts, and workflow history.

Result

• Status: Pending execution.
• TDD plan: To be filled during execution.
• Red evidence: To be filled during execution.
• Green evidence: To be filled during execution.
• Refactor notes: To be filled during execution.
• Verification output: To be filled during execution.