fix: rewrite the README, repair the dead docs link and stale job types

[a-essawy]

Two defects and a rewrite. 202 lines to 158.

The dead link

The header "MCP docs" link pointed at rendobar.com/docs/mcp/, which has answered 405 since the docs site consolidated those pages into /docs/mcp-server. It is one of four nav links and the first thing a reader clicks from npm.

server.json and package.json carried the same stale path and were fixed in #83. The repo homepageUrl was already correct. The README was the last holdout.

The stale job types

The table listed three of six. Missing compose, compress.target, ffprobe.

This is the same list that used to live in src as FEATURED_JOB_TYPES, deleted in #85 once discovery went public. The README was the last place it survived. It now lists all six with the media kinds each accepts, and states that list_job_types reads the registry live and should be preferred over the table.

Why a rewrite rather than a patch

I looked at how the most-used MCP servers structure theirs:

Repo	Lines
supabase-community/supabase-mcp	135
upstash/context7	163
modelcontextprotocol/servers	170
github/github-mcp-server	1695
microsoft/playwright-mcp	1592

The short ones read like a product page. The long ones read like reference manuals, which is a reasonable choice for a server with dozens of toolsets and the wrong one for a server with seven tools.

Context7's opener is the pattern worth copying: a before/after, not an install block. It shows the outcome before asking anyone to configure anything. Ours uses the case where the value is most obvious, hitting a size budget without installing FFmpeg or guessing at CRF.

Seven per-client config blocks ate ninety lines and pushed the tools table below the fold. Four of the seven take a byte-identical config, so they are grouped into two <details> blocks.

Retrieval

The opening paragraph is now a standalone summary that names the subject and defines the terms without depending on earlier context, so it holds up quoted on its own. Headings segment by task rather than by feature.

Repo metadata needed nothing: the description is accurate, homepageUrl already points at /docs/mcp-server, and there are twelve relevant topics.

Why fix: and not docs:

The README is the npm landing page. A docs: commit does not cut a release, so the broken link would sit on npm until something else shipped.

Verification

• All 16 URLs resolve. The only non-200s are the OAuth-protected /mcp endpoint and fabricated example URLs inside code samples
• Zero banned words from rendobar-docs-writing rules
• Zero em dashes
• The compress.target example is checked against the live schema endpoint, and switched from maxBytes to maxSize: "50mb", which the schema accepts and which matches the surrounding prose
• "Eleven presets" verified against the live captions.animate schema: exactly 11
• Tests 78/78, lint and typecheck clean, registry guard passes