[engine-failure] PROJ-281-the-impact-of-perceived-control-over-dig @ tasks: RuntimeError

Automated report (spec 023 / FR-016) — an unexpected engine failure occurred while processing **PROJ-281-the-impact-of-perceived-control-over-dig** 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: tasks\nartifact_path: projects/PROJ-281-the-impact-of-perceived-control-over-dig/specs/001-the-impact-of-perceived-control-over-dig/tasks.m'
```

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 reported review artifact at projects/PROJ-281-the-impact-of-perceived-control-over-dig/specs/001-the-impact-of-perceived-control-over-dig/tasks.md and the tasks-stage output, then trace the validation path that raises RuntimeError. Done means a malformed or truncated review is treated as a failure rather than acceptance, while the normal retry can proceed.

Written by the indexing model from the issue text.