pipeline-status

Generate the pipeline status page — a static, self-contained HTML dashboard covering the user's full job search pipeline — and open it in their browser.

---

1. Verify Career Navigator setup

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, {user_dir}/CareerNavigator/recommendations.json, and {user_dir}/CareerNavigator/passed.json. All three are core files created by /career-navigator:launch.

If any is missing, output:

Pipeline status not set up: run /career-navigator:launch first to initialize Career Navigator.

Then stop.

---

2. Read and normalize the data

• tracker.json — summary rows only. For each row with stage_count > 0, load its detail_file under applications/ for stage_history[] (needed for the closed-section duration calc). Rows with stage_count: 0 need no extra read.
• recommendations.json — pre-application roles, status: "considering" (or "recommended" if priority is "high" — normalize this the same way as the historical generator: if a considering/recommended record's status doesn't match its priority tier, correct it in place and write the file back).
• passed.json — roles explicitly passed on (status: "pass").

Slim each record down to what the page renders — do not embed full stage history, notes, or contacts:

• Applications: company, role, status, job_link, priority, date_applied, follow_up_date, location, next_step, and stage_history reduced to [{date}, ...] (dates only, for duration math).
• Recommendations / passed: company, role, status, job_link, priority, date_added (fall back through date_discovered → added_date → first note date → first stage_history date, in that order, using whichever is present first), date_researched, location, next_step, and the same slimmed stage_history.