feat(app): save household planner prefs over the session - #1479
Merged
Merged
Conversation
POST /api/planner/prefs changes dispatch, so the phone writes safety_k and battery_export with planner.prefs.set. The box still maps that permission onto a planner mode. Signed-off-by: Cursor Agent <cursoragent@cursor.com>
This was referenced Sep 29, 2026
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
frahlg
marked this pull request as ready for review
October 4, 2026 16:08
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contract-pair: srcfl/ftw-webapp@cursor/plan-household-prefs-1a28
The phone app needs the same household planning preferences as the box UI. The session cannot call the actuating
POST /api/planner/prefsroute, soplanner.prefs.setapplies that intent through Core's existing preference write.The command accepts safety_k, battery_export, or both. Core preserves each omitted value under the existing preference lock. A style choice therefore keeps the export permission stored by another client. Manual control stays in place until the user chooses Use the plan. Existing expiry, scope and revision checks still apply, and Core validates any resulting dispatch.
Paired with srcfl/ftw-webapp#76. Native app PR srcfl/ftw-app#7 keeps its registry snapshot in step. All three registry copies match byte for byte.
Validation:
make verifypassed: tests, migration and release checks, vet and build.