bug: apply-to-profile does not establish default_resume_id link — profile→library sync broken after apply #128

New issue

Open

opened 2026-06-15 16:42:29 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-06-15 16:42:29 -07:00

Owner

Summary

When a user clicks "⇩ Apply to profile" in the Resume Library, the POST /api/resumes/{id}/apply-to-profile endpoint syncs that library entry into plain_text_resume.yaml but does not set default_resume_id in user.yaml. As a result, future saves in Settings → Resume Profile do not sync back to the library (the PUT /api/settings/resume endpoint reads default_resume_id to find the linked entry).

Fix

After a successful apply-to-profile, call set_default_resume(db, resume_id) and write default_resume_id = resume_id into user.yaml, establishing the bidirectional link.

Impact

Users who use "Apply to profile" expect their subsequent profile edits to stay in sync with the library, but they silently diverge.

## Summary When a user clicks "⇩ Apply to profile" in the Resume Library, the `POST /api/resumes/{id}/apply-to-profile` endpoint syncs that library entry into `plain_text_resume.yaml` but does not set `default_resume_id` in `user.yaml`. As a result, future saves in Settings → Resume Profile do not sync back to the library (the `PUT /api/settings/resume` endpoint reads `default_resume_id` to find the linked entry). ## Fix After a successful apply-to-profile, call `set_default_resume(db, resume_id)` and write `default_resume_id = resume_id` into `user.yaml`, establishing the bidirectional link. ## Impact Users who use "Apply to profile" expect their subsequent profile edits to stay in sync with the library, but they silently diverge.