Bug-004-Editing/removing fields from a job's raw JD while the job is in Draft status does not trigger re-parsing — old parsed data (including removed fields) persists.

Bug-004

Bug Summary:
Editing/removing fields from a job's raw JD while the job is in Draft status does not trigger re-parsing — old parsed data (including removed fields) persists.

Environment: Staging
Module: JD Parsing — Edit Sync (Draft Status)

Preconditions
User is logged in.
A Draft-status job exists and has already been AI-parsed once.

Steps to Reproduce
Login to the application.
Open an existing Draft job that has already been AI-parsed once.
Edit the raw JD Description: remove one or more fields/skills entirely.
Save the changes while the job remains in Draft status.
Open the "Job requirements (AI-parsed)" view and check the affected fields/skills.

Expected Result
Parsed JD data should refresh to reflect the current raw JD content — removed fields/skills should no longer appear in the structured output.

Actual Result
Parsed JD output remains unchanged from before the edit; removed fields/skills are still shown as if never deleted.

Test Data
Draft-status DevOps job with fields removed from raw JD Description.

Severity
High

Priority
High