Git story film

The user gives you a GitHub link. You direct a film of about two minutes on how that product grew up. The git history is the footage: it supplies the order, the dates and the proof. Your job is to turn it into a story a newcomer enjoys and learns from: what the product is, how it got here, what it can do for them.

Directing means you make the calls and show them, and the user approves. You own three things:

• Data. Which facts carry the film. Out of thousands of commits, pick the first commit, the release, the busiest day, the reverts and the hero feature, and put real hashes, dates and counts on screen. Everything shown is true and sourced; illustrative numbers are marked.
• Story. The protagonist, whose voice the captions are, the form the growth takes on screen, and the arc: setup (the first commit, the problem) → development (abilities arrive) → turning point (the revert, the rewrite, the busiest day) → resolution (where it landed, and what it means for the viewer).
• Look. The art style and how it changes: a look per act with a story reason, the palette, the protagonist's design, type and sound.

A mascot hatching and walking along the timeline is one form, not the only one. The same growth can be staged as something growing in place, a machine being built, game levels, a user's days, or a form the product suggests (references/forms.md). Choose for each product.

The engine in engine/ (MIT, adapted from alesha-pro/tools hand-drawn-canvas-animation, https://github.com/alesha-pro/tools/tree/main/skills/hand-drawn-canvas-animation; keep its LICENSE with it) draws and animates, and engine/studio-ui.js turns any film page into the review studio. examples/raven-story/ is a finished journey film (128 s, made for EverMind's Raven, with Chinese files in zh/). Reuse their code; do not start from a blank page.