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@3.1.0

Minor Changes

• a7f8f70: Plan sites with no home battery, several batteries or several EVs with the bundled Energyplan worker. Keep each asset's limits and energy target, validate worker identities and deadlines, and carry each battery's energy budget through Core control. Only count verified PV generation control, and stop using its plan when the driver or its health changes. Keep the previous plan for diagnosis when the fallback cannot represent the site.

Patch Changes

• 522f29f: Drain queued FTWDB shadow history for up to two seconds on normal shutdown and update, after hardware stops. Retry lost acknowledgements with the same commit and report any unconfirmed ticks when the sidecar cannot complete the copy.
• d30576c: Show Updates from the mobile More page while the header menu is closed.
  Keep the backup section open and preserve its scroll position during creation,
  verification and completion.
  Let backup controls and timestamps fit the mobile dialog.
• a45fda4: Keep sites without a home battery unavailable when Core DP is selected, and report the same reason in planner diagnostics. Keep Energyplan available for those sites. Match the documented worker budget to the request: Core's PV downside adjustment does not add scenarios or extend the budget on its own.
• f9cb680: Keep official driver signature checks and read-only limits after repository names change. Use the trust recorded at installation and verify the saved manifest again; refuse an official driver if its saved manifest cannot be verified.
• a001d50: Keep each managed driver's metadata format through restarts and rollback. A
  Device Support package now requires its verified runtime policy even when
  control is not selected, its repository is removed, or its envelope is missing.
  Verified legacy installs retain their normal autonomous default. Older installs
  with no recorded format need matching verified metadata; restore their repository
  or reinstall them if that metadata is unavailable.
• fed3695: Check retained package metadata before reinstalling a driver from an older
  database. Reject a change to direct-manifest format while a package envelope
  remains, and require signed legacy metadata when its format is unknown.
  A rejected reinstall preserves the active artifact and rollback record.
• 2e77a0f: Restore startup and autonomous default mode for retained legacy v1 drivers after their configured repository is removed. Keep official signature checks and control-v2 trust requirements unchanged.
• 0a98614: Move focus into Settings when it opens, keep Tab within its visible controls,
  and let Escape close it. Closing Settings returns focus to its opening button,
  including the shortcut in More. The restart prompt keeps focus while open,
  blocks the background, and returns focus when Restart later or Escape closes
  the prompt. During a pending restart, focus stays in the prompt and Escape
  does not close it.
  Show restart progress only after Restart now starts the request.
• f2ae6c6: Match signed driver updates to the configured driver ID when bundled and repository filenames differ. Save the selected path, restore the bundled file by ID, and report fresh telemetry only for instances that actually restarted. Tell an open Settings dialog when it must reload the saved config before saving again.

---

Note

Low Risk
Version and changelog-only changes with no application code modifications in this diff.

Overview
Bumps ftw from 3.0.3 to 3.1.0 via the Changesets release flow: package.json and package-lock.json versions update, pending .changeset/*.md entries are removed, and their text is folded into a new 3.1.0 section in CHANGELOG.md.

This PR does not change runtime code; it records what already landed for the release. 3.1.0 includes one minor item (multi-battery / multi-EV / no-battery site planning with the bundled Energyplan worker) plus patches for FTWDB shadow drain on shutdown, mobile Updates/backup UI, planner admission and Core DP rules, driver trust/format/reinstall behavior, Settings/restart focus management, and driver update path matching by configured ID.

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_30f8090d-6b33-4fbb-9fd7-3e65f2752c1b)

[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-09-07T18:16:30.368687Z	2d9c5eb	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]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_289430a3-0031-4992-81de-ea301f464405)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_f47fdd4c-71be-4fd5-81c6-78db85aab609)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_91fe542b-f31f-4c8d-a125-c13747b1336a)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_4990a45e-7b45-4f6f-aaa8-f4ca3ec35537)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_02eb7cb5-5c51-493b-8315-f5e9726b831c)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_cde09b1d-ede7-4b0c-b8c9-93a8bcecce64)

[miravoss26]

Reviewed. Standard Changesets release PR: version bump 3.0.3 → 3.0.4 in package.json/lockfile, folds 7 pending changesets into CHANGELOG.md. No runtime code changes in the diff, no secrets, no new dependencies. CI green.

Safe to merge from my read (this repo's not on my auto-merge allowlist, so leaving the actual merge to whoever owns the release).

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_46a78035-3ff9-41cb-917c-69e645160ff5)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_8cc74a10-5efc-4f44-9c5d-77a97a63779b)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_5d5aa627-9f4b-4f45-bc2a-8e9847c47cb3)