# Task 012: Parallel Production Jobs

Development description: Implement parallel section scaffolding, FAQ, SEO brief, tone guide, table specs, diagram specs, and hero prompt jobs after the evidence matrix is ready.

## Implementation Details

- Backend orchestration creates independent jobs for:
  - One section scaffold per approved plan section.
  - Hero image prompt.
  - Diagram specifications.
  - Table specifications.
  - FAQ block.
  - SEO metadata.
  - Internal link suggestions.
  - Tone guide.
- Each section scaffold output includes:
  - `section_id`
  - `heading`
  - `draft_markdown`
  - `used_evidence_ids`
  - `unsupported_claims`
  - `suggested_visuals`
- Failed section jobs can be retried independently.
- No scaffold may silently introduce unsupported factual claims.
- Use fake runner fixtures for deterministic tests and demo.

## Public Interface

- Editor starts production after evidence matrix is ready.
- UI shows parallel job status per production artifact.
- Editor can retry failed section jobs individually.

## Acceptance Criteria

- [ ] TDD pre-requirement: before implementation, write one failing behavior test that starts production and creates one job per plan section; proceed one artifact behavior at a time and record evidence in `Result`.
- [ ] Production cannot start before evidence matrix is ready.
- [ ] One section scaffold job is created per approved plan section.
- [ ] Jobs run independently and can fail independently.
- [ ] Retrying one failed section does not rerun successful sections.
- [ ] Each scaffold lists used evidence IDs.
- [ ] Unsupported claims introduced during scaffolding are captured and shown.
- [ ] UI displays per-artifact job state.

## Verification

- Run orchestration tests with fake runner.
- Run retry behavior tests.
- Run Docker Compose smoke flow from evidence-ready to production artifacts ready.

## 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.