chore(release): 0.8.1

[LeadcodeDev]

Four lines in the root manifest plus the lockfile. The version lives in [workspace.package] and in the three internal dependency pins; one missed there fails the publish after the earlier crates have already gone up, which does not come back.

Rebased onto main. The branch was opened before the toolchain pin and clippy was its one red check: CI installed the floating stable channel, rustc moved to 1.99.0, and a lint fired on code this branch does not touch. #467 fixed the cause and is in main, so the rebase is what makes this green rather than anything in the diff. The rebase was clean — the lockfile did not conflict, because none of the three commits main gained adds a dependency.

A patch bump rather than 0.9. The cycle is seven fixes, a subcommand and a schema that stopped lying, and no public type gained or lost a field. Two things in here argue the other way and are worth disagreeing with. The first is a removal: rustmotion::studio::command(), with no caller anywhere in the repository, behind the studio feature, in the module that is the application rather than anything a library consumer builds against. The second is four public additions in rustmotion-core::engine::renderer — css_font_weight, draw_photo, photo_sampling, device_axis_scales, each the single place a rule is now expressed. Additions break no caller, so they do not force a minor; under cargo's 0.x rules the removal is the one that argues for 0.9.0, and calling it a patch is a judgement rather than a reading of the rule.

What an installing user gets, over 0.8.0:

• rustmotion studio exists when the feature is on (No rustmotion studio subcommand: the studio is only reachable as a second binary #458, feat(cli): add a studio subcommand behind the studio feature #459)
• --codec h265 produces a file QuickTime, Safari and avconvert open (H.265 output is tagged hev1, which QuickTime and Safari refuse: -tag:v hvc1 is never passed to ffmpeg #457, fix(encode): tag HEVC as hvc1 so AVFoundation players open the file #460)
• text no longer steps by whole pixels under slow motion (Text snaps to whole pixels while everything around it moves sub-pixel: fonts are created with Skia's default subpixel/baseline-snap settings #456, fix(text): position glyphs at their fractional coordinates #461)
• rustmotion schema accepts a templated scenario and names the property that is wrong (The exported schema rejects every templated scenario: $-placeholders are not modelled #424, fix(schema): make the exported schema accept what the engine accepts #463)
• photos stop aliasing when drawn smaller than their source and stop breaking into blocks under a camera zoom (Photos alias when shrunk and turn blocky under camera zoom: image and video sample with nearest neighbour and no mipmaps #465, fix(paint): sample photos from their on-screen size instead of nearest neighbour #468)
• a numeric font-weight of 600 or more is painted at the weight it declares instead of 700, so a title measured on one face and painted with a wider one no longer wraps over its next sibling (font-weight 800/900 is painted as 700 while measured at its real weight, so text wraps over its next sibling when several weights are loaded #466, fix(text): resolve a declared font weight in one place, so paint and measure agree #469)

The last two landed after this branch was opened and are the reason the version list is longer than the body first claimed.

cargo publish --dry-run was re-run after the rebase and passes for rustmotion-core and rustmotion-html at 0.8.1, reporting no yanked dependency. The other two cannot be dry-run until their dependencies exist on crates.io, so publish in this order: rustmotion-core, rustmotion-html, rustmotion-components, rustmotion.

cargo fmt --all --check, cargo clippy --workspace --all-targets --features rustmotion/studio -- -D warnings, cargo test --workspace --features rustmotion/studio: 2157 passed, 0 failed, 10 ignored across 53 suites, on the pinned 1.99.0. cargo audit with CI's ignore list: no blocking advisory, twelve allowed unsound/unmaintained warnings. cargo metadata reports all four crates at 0.8.1 with every internal pin at ^0.8.1 — read from cargo rather than grepped, since version.workspace = true makes a grep lie. The built binary reports rustmotion 0.8.1.

No issue: a version bump is not work anyone filed.