application-update

Run immediately after the track-application skill writes or updates {user_dir}/CareerNavigator/tracker.json (same conversation turn). There is no separate plugin hook file — orchestration is conversational or host-defined.

Workflow

1. Read tracker state

Application data uses the split layout defined in references/tracker-schema.md — read it before any read or write.

Read {user_dir}/CareerNavigator/tracker.json and inspect the summary rows only:

• latest application updates — status, latest_stage, latest_stage_date, and the notes_count / stage_count / contact_count counters show what changed without opening a single detail file
• outcome distribution
• whether search_performance exists and has as_of

Do not walk applications/<application_id>.json or contacts/<company-slug>.json here. Open one detail file only when a specific application's consistency check in §1.5 fails and you need to see the underlying array.

1.5 Verify the write that just ran

track-application writes a multi-file transaction. Before advising anything, confirm it completed for the applications that just changed:

• the row's detail_file resolves under {user_dir}/CareerNavigator/
• notes_count and stage_count equal the lengths of the detail file's notes[] and stage_history[]
• latest_stage and latest_stage_date match the last stage_history entry
• if the row has a contacts_file, its contact_count matches the number of entries in that file whose application equals the row's application label

If a check fails, say exactly which file and field are out of sync and tell the user to re-run /career-navigator:track-application for that application. Repair it only per the write rules in references/tracker-schema.md — recompute the counters from the detail and contacts files and write every affected file in the same pass; never patch tracker.json alone.