md-to-pdflisted

# md-to-pdf Converts Markdown → Stratcore-branded PDF using the local **StratcoreReport** generator at `~/Documents/CodeProjects/StratcoreReport-html/`. Same theme, cover, and footer as [pdf-report]; the difference is the input. `pdf-report` interviews the user and assembles a JSON payload; this skill takes a document that already exists and gets out of the way. Brand source of truth: `Company/Stratcore/Stratcore Design System/` in the Obsidian vault. Theme is dark-only. ## Run it ```bash cd ~/Documents/CodeProjects/StratcoreReport-html node src/render.mjs <document.md> [out.pdf] ``` Output defaults to `out/<document>.pdf` inside the generator. Pass an explicit second argument to write next to the source document instead — usually what the user wants for a vault note. Debug flags: `--payload` prints the intermediate JSON (use this when a block renders wrong — it shows whether the problem is parsing or styling), `--html` emits the HTML to `.build/` without launching Chrome. ## Process 1. **Resolve the file.** If the user named a note rather than a path, find it before rendering. Don't guess between two similar filenames — ask. 2. **Check the frontmatter.** It drives the cover page (see mapping below). If the document has none, or has no `title`, the title falls back to the first H1 and then to the filename. Offer to add a `subtitle`/`client`/`period` if the cover looks bare, but don't edit the user's note without asking. 3. **Render**, writing the PDF next