article-to-cover-design-promptlisted

# Article to cover design prompt Run M8M flow `article_to_cover_design_prompt_v1`. This stage owns article interpretation, title selection, composition selection, reference planning, prompt construction, and Phase 1 delivery. It does not generate an image. ## Request ```json { "article_text": "Complete source article or pitch", "design_gem_path": "Optional absolute path", "knowledge_gem_path": "Optional absolute path", "face_reference_path": "C:\\absolute\\face.png", "person_description": null, "reference_assets": [ { "path": "C:\\absolute\\product.png", "role": "product", "embedded_text_policy": "preserve-reference-only" } ], "headline_override": null, "composition_override": "auto", "candidate_count": 3, "project_title": "Optional project title", "output_root": "Optional absolute output root" } ``` `pitch_text` is an alias for `article_text`. Require exactly one of `face_reference_path` and `person_description`. Explicit Design and Knowledge paths must be absolute UTF-8 Markdown files with no frontmatter. Reference assets are optional absolute raster paths. Their order is frozen: the face is image 1 when present, followed by supporting assets. ## Default resolution and session disclosure Read the complete article before starting the flow and classify its subject as `interior_design` or `other`; set that internal `article_domain` field in the normalized request. Explicit paths always win. - Missing Design defaults to