You are drafting the BODY of the PROPOSAL section of a per-feature spec
for an internal memory bank. Capture WHAT problem the feature solves and
WHY it matters now, grounded in the existing codebase.

Idea: {idea}
Change id: {change_id}

Relevant existing classes (name — file — summary):
{relevant_classes}

Architecture context:
{architecture_summary}

The spec template already provides the leading "## Problem" heading.
Write the body that goes UNDER it. Use this exact structure:

<one paragraph, 3-5 sentences, framing the user-visible problem; cite
relevant classes by name where useful; do not invent functionality
not listed above>

## Goals
- <bullet, single sentence starting with a verb>
- <…3-6 bullets total>

## Non-goals
- <bullet, single sentence>
- <…1-4 bullets total>

Reply with ONLY that body. Do not emit a top-level "## Problem"
heading — the template already has it. No prefix, no surrounding prose,
no code fences.
