list-artifacts

Display the user's artifact inventory in a readable format.

Workflow

1. Read the inventory

Read {user_dir}/CareerNavigator/artifacts-index.json. If the file does not exist or the artifacts array is empty:

"No artifacts yet. Run /career-navigator:tailor-resume for a resume, or /career-navigator:content-suggest and ask for a full post draft to save a LinkedIn draft to disk."

2. Cross-reference with tracker

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. For each artifact, check whether it appears in any summary row's artifacts[] array. If so, note that row's current status, its application label ("<company> — <role>"), and its outcome — this lets the user see which resumes and cover letters are attached to live applications and what outcome (if any) they produced.

The summary rows carry everything this listing needs. Do not open applications/<application_id>.json or contacts/<company-slug>.json here — artifact links live on the row, and loading detail files for every application to print a list is exactly what the split layout exists to avoid.

3. Organize the output

Group artifacts by type: resumes first, then cover letters, then linkedin_post (saved post drafts from writer), then any other types. Within each group, sort by date_created descending (most recent first).

Format for each artifact:

{n}. {filename}
   Target:   {Company} — {Role}  (or "Base / unattached" if no target; for linkedin_post use "—" or notes topic)
   Created:  {date_created}
   ATS score: {ats_score}/100  (omit if not available or not applicable)
   Used in:  {row's `application` label, status: {status}}  (omit if not linked to any application)

For type: "linkedin_post", omit ATS and usually Used in; show notes or path if helpful so the user can find the draft on disk.