Follow Core: drop priority/weighted modes; keep a boost beside Charge now - #73
Conversation
Core removes ModePriority and ModeWeighted: nothing ever set a priority order, so neither regulated. The registry loses both keys, byte for byte the copy in srcfl/ftw, and the demo box and the mode test follow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MuerPFZFG88kgu8sWVHeq7
Core now keeps a battery boost when Charge now starts and accepts one asked for while it runs (srcfl/ftw#1450): Charge now sets what the car draws, the boost lets the house battery cover it. The demo box follows, and the test says so. The operator_hold label stays for older boxes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MuerPFZFG88kgu8sWVHeq7
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ftw-webapp | b6a8589 | Commit Preview URL Branch Preview URL |
Sep 27 2026, 06:32 AM |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b6a8589f6f
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| return | ||
| } | ||
| if (this.#evHold || this.#evSurplusOnly) { | ||
| if (this.#evSurplusOnly) { |
There was a problem hiding this comment.
When a manual charge is already running, this change makes the simulator accept a boost, but EvPanel.svelte still branches on lp.manualActive to hide the “Boost from the house battery” button and display “Available after returning to the plan”; its existing test at EvPanel.svelte.test.ts:908-917 enforces that stale behavior. Consequently, owners cannot initiate the newly supported boost-under-Charge-now flow through the product UI, despite the store and box accepting it; update that UI guard and test alongside this condition.
Useful? React with 👍 / 👎.
1 participant
Contract-pair: srcfl/ftw@refactor/remove-priority-weighted-modes
Paired with two Core changes:
contract/registry.yamldrops both keys and is byte for byte the Core branch's copy (npm run check:contractagainst it passes).operator_holdlabel stays for older boxes.Checks:
npm run checkfinds 0 errors.npm testwithLANG=Cpasses 1033 of 1033; one test is skipped.EvPanel.svelte.test.tsfails onmaintoo, on "4.6 kWh" against "4,6".🤖 Generated with Claude Code
https://claude.ai/code/session_01MuerPFZFG88kgu8sWVHeq7