Add a 1440p (2560x1440) preset to render --resolution #6309

Problem

hyperframes render --resolution has no 1440p (2560x1440) preset. In 0.8.191 the accepted values are landscape, portrait, landscape-4k, portrait-4k, square and square-4k, plus their aliases. The shared CANVAS_DIMENSIONS table already has 720p and 480p entries, but none for 1440p.

A 1920x1080 composition also cannot reach 2560x1440 through supersampling. The output-resolution check rejects any non-integer device scale factor ("requires a non-integer device scale factor ... Pick a preset that's an integer multiple, or rescale the composition"), and 2560 / 1920 = 1.333.

Use case: long-form YouTube videos. A 1440p upload is a common delivery target for creators, and it gives sharper text and graphics than 1080p, with a much smaller render cost and file size than 4K.

Our current workaround is to render at --resolution landscape-4k and then scale the result down to 2560x1440 with ffmpeg. This works, but it captures 2.25x more pixels than 1440p needs and adds a second encode.

Proposed solution

1. Add landscape-1440p (2560x1440), portrait-1440p (1440x2560) and square-1440p (1440x1440) to the canvas and output-resolution presets, with aliases such as 1440p, 2k and qhd.
2. Allow a non-integer device scale factor for output-resolution supersampling when the aspect ratio matches, so a 1920x1080 composition can render with --resolution 1440p (scale 4/3). Chrome accepts fractional deviceScaleFactor values, and Page.captureScreenshot takes a fractional clip.scale.

Example:

hyperframes render . --quality delivery --resolution 1440p --output renders/main_1440p.mp4

If fractional scale factors are a concern (for example sub-pixel layout or text rounding), item 1 alone helps: authors could create 2560x1440 compositions, and a 1280x720 composition could supersample to 1440p at an integer 2x.

Alternatives considered

• Render at 4K and scale down with ffmpeg (current workaround): more capture time and a second encode.
• Author the composition at 2560x1440: this means changing every pixel value in an existing 1920x1080 project.
• Wrap the 1920x1080 stage in a CSS transform: scale(1.3333) inside a 2560x1440 root: possible, but fragile, and it relies on the browser rasterizing the scaled layers at the final size.

Additional context

• Version: hyperframes 0.8.191 (macOS, hardware GPU, screenshot capture).
• The --resolution help text already states the rule: "Aspect ratio must match the composition; the scale must be an integer multiple."

Plain simple English

HyperFrames can render a video at 1080p or 4K, but not at 1440p. Many YouTube creators upload at 1440p because it looks sharper than 1080p and costs less to make than 4K. Today they must render the video at 4K and then make it smaller, which takes more time.

Created with LLM: Opus 5.5 | high | Harness: Claude Code