narrate 0.1.1

The GitHub Action is now narrate video, ready for the GitHub Marketplace, and uses: bricef/narrate@v0 follows narrate's 0.x releases, building with each release's own image.

Get it:

• GitHub Action: uses: bricef/narrate@v0 (or @v0.1.1 to pin this release); no image input needed (docs)
• Docker: docker pull ghcr.io/bricef/narrate:0.1.1 (amd64 and arm64)
• uv: uv tool install --python 3.12 --with-executables-from playwright git+https://github.com/bricef/narrate@v0.1.1, then playwright install chromium (README)

The image's ffmpeg is unchanged from 0.1.0 (9.0.2); its source tarball is attached to v0.1.0.

Added

• A major tag for the GitHub Action: uses: bricef/narrate@v0 follows the
  0.x releases. Each release moves it, and the image tag 0, once its image
  has passed its checks. Only a newer release moves them, never an older one
  run again.

Changed

• The GitHub Action builds with its own release's image, with no image
  input: @v1.2.3 uses ghcr.io/bricef/narrate:1.2.3, and @v0 uses
  ghcr.io/bricef/narrate:0. A branch or a commit still uses latest, and
  image still overrides it. 0.1.0's action uses latest unless given
  image.
• Only release tags build images: v1.2.3, and pre-releases such as
  v1.3.0-rc.1, which publish only their own image tag.
• The GitHub Action is named "narrate video", so that it can be listed on
  the GitHub Marketplace, which refuses narrate: an organisation has that
  name. uses: bricef/narrate@… doesn't change.
• Dependencies: Pillow 13 (narrate now needs it), Playwright 1.64 with
  its newer headless Chromium, Starlette 1.8, NumPy 2.5.4 and certifi
  2026.10.19. From a checkout or a uv install, run
  playwright install chromium again after updating if narrate doctor
  says Chromium is missing.