v0.6.0 — a page you can scroll, and it works where you put it

Four templates have shipped since 0.5.0, but everything describing this tool
still said Next.js, and there was nowhere to see what it produces. Both are
fixed, and building the demo turned up a bug that would have hit anyone
deploying the html template anywhere but a domain root.

Fixed

• A page from the html template 404'd every frame when deployed under a base
  path. The generated framePath returned /frames/…, which resolves to the
  site root — so a GitHub Pages project site at /<repo>/, or any static host
  serving the directory from a subfolder, loaded the page and then found no
  images. It now resolves against the page itself and returns an absolute url.

  Absolute rather than relative on purpose: the engine hands these urls to a
  worker, and a worker resolves a relative url against its own script in lib/
  rather than against the page, so a relative path would 404 there while the
  poster image worked.

  Only the html template changes. The other three serve frames from public/
  at the site root, where /frames/… is correct — and their generated contract
  still says, as it always did, that a deploy under a subdirectory needs that
  function edited.

• A zero-build page ignored the title and description in its own story.
  components/story.js declares both, and the framework templates put them in
  the document head on every render — Next reads them for <title> and for Open
  Graph. The html template has no render step, so they were dropped without a
  word: the body said one thing while the browser tab and every social preview
  said whatever the template shipped with. frames now writes both into the
  head, and rewrites only tags that are already there — a page whose author
  deleted its <title> did that on purpose.

Changed

• The package stops describing itself as a Next.js tool. Four stacks ship.
  The npm description and keywords, the plugin manifest, the marketplace entry
  and --help now name all four or none — a builder on Nuxt or Astro previously
  read the front page and correctly concluded, from what it said, that the tool
  was not for them.

• The README leads with what you get instead of with prose. The outcome, all
  four stacks and one install command are inside the first twenty lines. The CLI
  reference, the templates table, the deep half of Why it looks right, the
  git-and-frames explanation and the contributing instructions moved to
  docs/en/, linked rather than inlined. Nothing was deleted.

Added

• A live demo page, built by this tool from real footage and published from
  CI on every release.

• Two issue forms. One for showing a page you built — with a separate,
  refusable checkbox before it can appear in the README gallery, and a stated
  24-hour removal policy — and one for bug reports.

• npm run sample for anyone working on this repository: scaffolds a real
  project, runs the real pipeline, and starts it, so a change can be looked at
  rather than only tested.