ingest-resumelisted

# ingest-resume Bring the user's resume into the pipeline as the working master, in their own template, and give an honest read on whether it has what a software-engineering resume needs. This skill does not design or author a resume: apply-kit imposes no template, and missing content is reported, never fabricated. ## Input - A path to a resume file: `.tex` or `.docx`. - `.pdf` is not supported yet (a PDF has no layout structure to preserve; see the roadmap). If given a PDF, say so and ask for the `.tex` or `.docx` source, or for the content pasted as text. ## Procedure 1. **Detect the format** by extension. 2. **Produce the working master** in the session scratchpad as `master.tex`, preserving the user's template: - `.tex` → copy the file verbatim. This fully preserves their template, macros, and design. Do not reformat it. - `.docx` → convert with `pandoc "<file>" -o master.tex --standalone`. This preserves content and structure (headings, bold, bullets) but not the exact Word styling; tell the user the converted LaTeX is a faithful-content starting point, not a pixel copy of their Word layout. If `pandoc` is not installed, stop and give the install hint (`brew install pandoc`). 3. **Section-completeness check (for software-engineering roles).** Read the working master and classify each section: - **Required:** Contact (name plus at least one of email / phone / LinkedIn / GitHub), Experience (work history), Skills (