alexzmsandClaude Opus 5.5
16e412f5e0
Conflict in request_adapter.py with #2001, which adds continuation_video and materializes it through _materialize_video. This branch replaced that helper with materialize_clip, so continuation_video now goes through materialize_clip as well, with the same "continuation" upload name. As a result it gets the same policy as the other video fields: media_roots, the private-URL check, the size cap, and base64 data:video/... URLs. - docs/design/server_contracts/openai.md: continuation_video is listed in the video row of the media-source table. - docs/inference/fasth3_omniref.md: continuation_video may be a data:video URL. - test_openai_serving_engine.py: an inline continuation video is decoded, tracked and removed, and a data:audio one is refused. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
FastVideo documentation
Canonical guides live in this directory. The Blume application in docs-site builds and publishes them at haoailab.com/FastVideo.
See Documenting FastVideo for local setup,
source ownership, page structure, validation, and deployment. The existing
GitHub Pages workflow publishes Blume from main with the same domain and base
path. MkDocs is no longer part of the build.
Cookbook sources
Recipe metadata, shared JavaScript, and tests remain under docs/. From the
repository root:
npm ci --prefix docs
npm run build:catalog --prefix docs
npm run check:cookbook --prefix docs
npm run test:cookbook --prefix docs
python -m unittest discover -s docs/tests -p 'test_*.py'
The combined browser bundle, notices, index and catalogs are generated together
under assets/cookbook-config/. Do not hand-edit or commit those outputs.
The site preparation builds and copies them into Blume's public assets.
See the recipe authoring guide and
configuration API contract before changing the schema.
The capacity estimation guide covers reusable
hardware/component catalogs and optional recorded inference runs in existing
model manifests.