docs(openapi): remove result envelope reintroduced in #31530

[andig]

As reported in #31530 (comment) by @StefanSchoof.

#31530 regenerated openapi.yaml from a base that predated #31989 and re-added the result: {...} response envelope. That envelope was removed from all HTTP handlers in #22299, and #31989 had already fixed the spec to match (fixes #31988, getLoadpointPlan example).

This re-applies the unwrap on the reusable *Result response schemas (NanoSecondsResult, NumberResult, IntegerResult, SocResult, PlanRatesResult, BooleanResult, NullResult, SuccessResult, BatteryModeResult) so the generated REST docs again show the real response shape, and regenerates mcp/openapi.json.

🤖 Generated with Claude Code

[sourcery-ai]

Hey - I've left some high level feedback:

• Since the envelope was reintroduced by regeneration, consider adding a guard in whatever tooling or script generates openapi.yaml/openapi.json to ensure *Result schemas remain unwrapped so this mismatch doesn’t recur.
• It may be worth scanning for any remaining result: {...} usages in reusable schemas or path responses beyond the listed *Result types, to ensure the spec is now fully aligned with the current handlers’ response shapes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since the envelope was reintroduced by regeneration, consider adding a guard in whatever tooling or script generates `openapi.yaml`/`openapi.json` to ensure `*Result` schemas remain unwrapped so this mismatch doesn’t recur.
- It may be worth scanning for any remaining `result: {...}` usages in reusable schemas or path responses beyond the listed `*Result` types, to ensure the spec is now fully aligned with the current handlers’ response shapes.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}