Convert README files into PDFs for review

A README is often the best short-form explanation of a project, but not every audience wants to read it inside GitHub. Turning it into PDF makes it easier to circulate in approval flows, procurement, client handoff, or offline review.

The main cleanup step is usually reducing GitHub-specific clutter. Remove badges that do not matter for the audience, shorten long installation steps, and make sure screenshots are replaced with markdown-friendly explanations where needed.

What to keep

• Project overview
• Setup or usage steps
• Key links
• Important tables and code examples

What to trim

• Internal-only contribution notes
• Build badges that mean nothing to the reader
• Very long changelog sections