Make docs reachable from the published package (README relative links break on npm)

[jbrecht]

From umami's 0.10.0 dogfood (concern #2).

files: ["dist"] ships no markdown, and npm always includes README.md but does not reliably rewrite relative links — so the README's [writing tutorials](docs/writing-tutorials.md) etc. break on npmjs.com and from an installed package.

(The one shipped-code reference — the settleUntil JSDoc — was fixed to a hosted URL in PR #26.)

Options

• Recommended: rewrite README's relative docs/*.md links to absolute https://github.com/jbrecht/tutorial-forge/blob/main/docs/... URLs. Lightest, fixes npm rendering, no package-size cost.
• Or bundle docs/ into the package via files (heavier; unusual for a JS lib).

Pin to a tag instead of main if link drift across versions becomes a concern.

[jbrecht]

Looked closer — the premise doesn't hold, so closing.

npm publishes the per-package READMEs (packages/core/README.md, packages/cli/README.md), not the repo-root README. Both per-package READMEs already use absolute links (to npmjs.com and github.com/jbrecht/tutorial-forge) and contain no relative docs/ links — so the npm pages are already correct, and the npm → repo → docs path works end to end.

The root README's relative links are fine too: it's only ever rendered on GitHub, where relative links resolve correctly.

The one genuine shipped-code doc-path defect (the settleUntil JSDoc pointing at an uninstalled docs/writing-tutorials.md) — which was the real substance of the umami concern — is fixed in PR #29 (now a hosted URL). Nothing left to do here.