feat(preset): add a "Suggest new features" preset

[suleimansh]

Closes #1109. The last unchecked leaf under Agentic PM on the roadmap (#538).

Adds an autonomous "Suggest new features" preset: it studies what the product does today and proposes net-new features it should have, writing each as a ticket under tickets/ for the normal triage pipeline.

Why it is a new preset and not one we already have

The Agentic-PM cluster is dense, so I checked the overlap before building. It fills the one missing corner:

preset	direction	mode
Suggest new tickets	you type the line, agent expands it	interactive echo
Market research	outward (external market) → tickets	autonomous
Suggest tickets to work on	picks from existing tickets	gated on approval
Suggest new features	inward (this product) → new features as tickets	autonomous, generative

Autonomous rather than gated on purpose: a proposal is a reviewable ticket, so the human triages later instead of approving mid-run, which also keeps it usable on a schedule. Paramless — it scopes itself to the whole product.

The prompt (first draft — preset wording is yours to tune)

1. Study what this product does today: skim the README, the docs, and the main user-facing surfaces, plus the existing `tickets/`
2. Think like a product manager and propose net-new features the product should have next
   - Net-new capabilities a user would want, not bugs, refactors, or chores
   - Skip anything an existing ticket already covers, and anything already built
   - Favour features that fit the product's direction and are worth building
3. Write each proposed feature as a new ticket under `tickets/`, following the ticket format
4. Show a short summary of what you proposed via `showMarkdown()`

Recipe

The per-preset module pattern is gone — a preset is now one catalog row. So: new prompts/presets/suggest_new_features.md, one definePreset row + import + LAUNCHER_PRESETS entry in preset-catalog.ts, and the pinned name-list + PARAMLESS entries in preset-catalog.test.ts. The index/client re-exports and the launcher button all derive from the catalog — no edit. Not added to PRESET_STEMS (suggest-class presets do not materialize to .the-framework/presets/).

Verified

• framework 1243 tests, 1242 pass, 1 skipped, 0 fail; dashboard 420 pass; typecheck clean.
• rendered the preset from the built dist: paramless, in LAUNCHER_PRESETS, template renders verbatim.
• drove the real dashboard: /suggest-new-features "Suggest new features" shows in the / preset menu, positioned between "Suggest new tickets" and "Suggest tickets to work on" (screenshot in the commit history of my session).

[suleimansh]

A new preset added 'Suggest new features'
@brillout, still not tested, ping me if needed

[brillout]

Testing things is always good :) (I didn't test it)