TemaDeveloper / TemaDeveloper/personal_planner
feat(profile): Reconciliation review UX — close the Learn-back loop
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Size: L — needs design spec first.
/api/profile/reconcile and /api/profile/reconcile/apply are fully implemented (compute an add/remove/reprioritize diff, guard destructive deletes) but have no UI consumer anywhere in src/components — the reconciliation engine is currently dead code.
Scope
When the profile changes, surface a diff ("we'll add X, remove Y which holds N entries — confirm"), let the user approve/reject per change, then call apply. This closes the adaptive-profile "Learn-back" loop and is the single biggest vision gap. Write a design spec first (diff presentation, per-item accept/reject, data-preservation warnings).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading /api/profile/reconcile and /api/profile/reconcile/apply, then inspect src/components to confirm there is no UI consumer. Draft a design spec covering diff presentation, per-item accept/reject, and data-preservation warnings. Done means the spec defines the approval flow and how the approved changes reach apply.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100