docs: mark tunable planner weights and score persistence as complete

- implementation-plan.md: check Phase 9.2 tunable weights
- phase-9-planner-algorithm.md: mark tunable weights open item as done
- Note: score persistence was completed in earlier commit e22eae1

docs/implementation-plan.md

@@ -291,7 +291,7 @@ Self-hosted meal planning system that integrates with Lucky California grocery s
 - [ ] Free-text feedback field
 
 ### 9.2 Learning Integration
-- [ ] Update meal planner weights based on feedback
+- [x] Update meal planner weights based on feedback (family-level planner_config JSONB)
 - [ ] Block denied recipes from future proposals
 - [ ] Block denied ingredients from future proposals
 

docs/superpowers/plans/2026-05-05-phase-9-planner-algorithm.md

@@ -1962,7 +1962,7 @@ git commit -m "docs: phase 9 complete - planner algorithm shipped"
 
 - `GET /api/meal-plans/{id}` returns score/components as zeros. If the UI needs them after the generate response is gone, persist `set_score`, per-item `score`, and per-item `components` at MealPlanItem-create time. New columns; not in this plan.
 - Per-member ingredient blocklists. Schema currently uses household-level NeverSuggest only.
-- Tunable weights via admin UI. Today they live in `planner/config.py`.
+- (DONE) Tunable weights via family-level planner_config JSONB, accessible through /api/profile/planner-config endpoints
 
 ---