[engine-failure] PROJ-379-predicting-molecular-excitation-waveleng @ tasks: RuntimeError

Automated report (spec 023 / FR-016) — an unexpected engine failure occurred while processing **PROJ-379-predicting-molecular-excitation-waveleng** at stage `tasks`.

```
RuntimeError: LLMReviewer[ordering]: review frontmatter has neither `verdict:` nor `concerns:`/`action_items:` — a contentless/truncated review MUST NOT count as acceptance (false-convergence guard). First 200 chars: '```yaml\n---\nreviewer_name: ordering\nreviewer_kind: llm\nstage: tasked\nartifact_path: projects/PROJ-379-predicting-molecular-excitation-waveleng/specs/001-predicting-molecular-excitation-waveleng/tasks.'
```

The project remains schedulable; it will retry on its normal cadence and recover once the underlying defect is fixed. Closing this issue does not require any project-state change.

Start with the `tasks` stage for project `PROJ-379-predicting-molecular-excitation-waveleng` and inspect the `LLMReviewer[ordering]` review artifact under `projects/PROJ-379-predicting-molecular-excitation-waveleng/specs/001-predicting-molecular-excitation-waveleng/tasks.`. Use the RuntimeError and truncated YAML excerpt to reproduce the failure; done means a contentless or truncated review is handled without being counted as acceptance and the normal retry can recover.

Written by the indexing model from the issue text.