# Area Guide upload fixture

`tiny-h264.mp4` is a generated 32×32 blue frame sequence, H.264 video with no audio, lasting 0.2 seconds. It contains no external content or project imagery. The HTTP upload test passes it through the actual `ffprobe` validation rule.

Generated locally with ffmpeg 8.1.1:

```text
ffmpeg -f lavfi -i color=c=blue:s=32x32:r=5 -t 0.2 -an -c:v libx264 -pix_fmt yuv420p -movflags +faststart tiny-h264.mp4
```

`tiny-h264.mov` (QuickTime, ftyp major brand `qt  `) and `tiny-h264.3gp` (3GPP, major brand `3gp6`) carry the SAME H.264 stream in the containers that ffprobe reports under the same `mov,mp4,m4a,3gp,3g2,mj2` demuxer name. The upload test uses them to prove the rule rejects non-MP4 containers by brand. They were generated with the same command, changing only the output name:

```text
ffmpeg -f lavfi -i color=c=blue:s=32x32:r=5 -t 0.2 -an -c:v libx264 -pix_fmt yuv420p -movflags +faststart tiny-h264.mov
ffmpeg -f lavfi -i color=c=blue:s=32x32:r=5 -t 0.2 -an -c:v libx264 -pix_fmt yuv420p -movflags +faststart tiny-h264.3gp
```

Run the upload test with `ffprobe` installed on `PATH` or configure `area_guide_content.ffprobe` / `AREA_GUIDE_FFPROBE` to the local executable. The test deliberately fails if codec inspection is unavailable; it never mocks codec acceptance.