chore(release): version packages

[frahlg]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

ftw@2.5.0

Minor Changes

• 4082a64: The EV modal's Start button becomes "Charge now → target": the manual
  hold charges at the slider's amps and releases itself once the car's
  estimated state of charge reaches the schedule's target (80 % when no
  schedule is set), falling straight back to planned dispatch — pressing
  Start no longer overrides the planner for the rest of the session. The
  release target survives restarts with the hold, holds without a target
  keep the old pin-until-Stop-or-unplug contract, and
  POST /api/loadpoints/{id}/manual_hold accepts the new
  release_at_soc_pct field.
• 3d99dd8: The EV modal now says why the charger is or is not charging, and when it
  will: the next planned charge window from the active plan ("Charging
  planned 02:15–06:30, ~18 kWh"), an explicit "waiting for tomorrow's
  prices — PV surplus only until then" state when grid-funded planning is
  deferred past the published price horizon, "charger offers X kW but the
  car isn't drawing" with the charger's own reason when the vehicle
  declines, and a plain warning when nothing (schedule, PV-only, Start)
  will ever start a charge. GET /api/loadpoints carries the new fields:
  plan_next_start_ms / plan_next_end_ms / plan_next_wh /
  plan_total_wh, grid_deferred, and commanded_w / commanded_known.

Patch Changes

• 940783e: Bundle easee_cloud 1.2.0 (feat(easee_cloud): emit request_active so the host can tell car-declined from box-paused device-drivers#103): the driver now
  emits request_active, so Core can tell "the car has stopped
  requesting current" (Easee reason 50 / charging completed) from "the
  box paused it". This turns on three existing protections for Easee
  sites: the session-completion latch stops the planner allocating
  energy to a full car, a manual Start hold auto-releases instead of
  offering power all night, and the charging-interrupted notification
  stops firing on the car's own renegotiation bursts. The driver's HTTP
  transport is also pcall-hardened.

---

Note

Low Risk
Metadata-only release PR (version, changelog, changeset cleanup); functional risk depends on the already-merged features listed in the changelog, not on edits in this diff.

Overview
Release housekeeping for ftw@2.5.0: bumps package.json / lockfile from 2.4.0 to 2.5.0, folds three consumed Changesets into CHANGELOG.md, and deletes the corresponding .changeset/*.md files. No application source appears in this diff.

What ships with 2.5.0 per the new changelog entries: EV “Charge now → target” manual holds with release_at_soc_pct on POST /api/loadpoints/{id}/manual_hold; richer EV modal / GET /api/loadpoints plan and deferral fields; and a patch bundling easee_cloud 1.2.0 (request_active and related Easee protections).

^{Reviewed by Cursor Bugbot for commit c45445a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-30T07:56:32.561366Z	9f328e2	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Approved. Cursor Bugbot completed successfully with no findings that need human review. No reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}