# Reference implementations Inspection date: **2026-07-24**. The references were cloned beside av-tools under `/mnt/DATA/git/references/`; no reference repository was nested in this working tree. Revisions are full immutable commit ids. | Repository | Revision inspected | Used for | Copied or adapted | | -------------------------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | av-tools, `git@git.add-ideas.de:zemion/av-tools.git` | no revision: canonical `main` was unborn and had no commits | canonical destination and licence/history check | the empty repository was scaffolded in place; no prior code existed | | Toolbox SDK, `https://git.add-ideas.de/zemion/toolbox-sdk.git` | `53c40a61ba1581246f65773fcbb1c1cfd31ac98e` (SDK 0.2.2) | manifest schema/definition, `AppShell`, context behavior, shared styles, token-free registry, nested-path checks and toolchain baseline | published 0.2.2 packages are direct dependencies; documented usage patterns were followed; no SDK source file was copied | | Toolbox Portal, `https://git.add-ideas.de/zemion/toolbox-portal.git` | `bda9da044d61c109afd9969d357cc27f76648938` | release ZIP/sidecar/lock formats, independent assembly, catalogue behavior, path security, nested deployment and production headers | no portal application source was copied; the documented artifact contract informed an independent release packager and smoke harness | | ffmpeg.wasm, `https://github.com/ffmpegwasm/ffmpeg.wasm.git` | `f876f907c7e9b9bf51d4ed0b913a855a63ae63fc` | current API, worker lifecycle, filesystem, loading, ST/MT behavior, licence documentation and build layout | no reference-worktree code was copied; exact published npm packages are dependencies and their five core assets are copied verbatim by the vendor script | For the **pinned** package set, the more specific upstream release tag `v12.15` at `71aa99d37c02a7b4c435275ca9ef50e612f6efa1` was also inspected. It contains `@ffmpeg/ffmpeg` 0.12.15 and core/core-mt 0.12.10. That revision's build selects FFmpeg n5.1.4. The user's active `/mnt/DATA/git/toolbox-portal` worktree still has Portal revision `bda9da044d61c109afd9969d357cc27f76648938` as `HEAD`, but currently contains a local `media-src 'self' blob:` nginx CSP patch. That mutable worktree state is documented for deployment testing only; it does not replace the immutable reference in the table. Official behavior references: - `https://ffmpegwasm.netlify.app/docs/overview/` - `https://ffmpegwasm.netlify.app/docs/getting-started/usage/` - `https://ffmpegwasm.netlify.app/docs/api/ffmpeg/classes/ffmpeg/` - `https://ffmpegwasm.netlify.app/docs/faq/` - `https://ffmpeg.org/ffmpeg.html` - `https://ffmpeg.org/ffprobe.html` - `https://ffmpeg.org/ffmpeg-formats.html` - `https://ffmpeg.org/ffmpeg-filters.html` - `https://ffmpeg.org/ffmpeg-utils.html` Command plans are based on those primary references and runtime capability queries, not unverified command snippets.