feat: publish av-tools 0.2.0

docs/KNOWN_LIMITATIONS.md

@@ -1,6 +1,6 @@
 # Known limitations
 
-This is the conservative 0.1.0 development baseline. A capability appearing in
+This is the conservative 0.2.0 release baseline. A capability appearing in
 FFmpeg output does not remove these product/browser/resource limits.
 
 ## Functional
@@ -13,6 +13,9 @@ FFmpeg output does not remove these product/browser/resource limits.
   frame-accurate. Accurate mode requires decoding/re-encoding.
 - Stream-copy concatenate works only when selected streams and codec/container
   parameters are compatible. Other input needs normalized re-encoding.
+- Crossfades are uniform fade/triangular-curve transitions on normalized
+  sequential joins, not arbitrary transition effects or overlapping timeline
+  tracks. They require enough material on both sides of every internal edit.
 - Re-encoding is not lossless. PCM/FLAC can preserve decoded audio samples but
   cannot restore information already lost in a source.
 - Metadata removal is best effort. Muxers may add structural/encoder fields,
@@ -26,6 +29,12 @@ FFmpeg output does not remove these product/browser/resource limits.
   page discards queued work.
 - A file-generating batch and its managed result collection are bounded to 255
   outputs, leaving the 256th ZIP entry available for an optional export report.
+- Scene analysis scans the source until it finds the requested changes or
+  reaches the end, retains at most 100 exact PTS results and can therefore take
+  about as long as a full decode. It does not begin an export implicitly when
+  no frame meets the chosen threshold.
+- Labelled contact sheets require a core with `drawtext`; the reviewed local
+  font does not make that filter available on a core that omits it.
 - Preview proxies are bounded, lossy H.264/AAC derivatives for local playback;
   they do not replace the source or guarantee that every browser can play the
   result.
@@ -38,8 +47,9 @@ FFmpeg output does not remove these product/browser/resource limits.
   support fewer container/codec combinations.
 - Browser support, codec policy and memory differ across Chromium, Firefox and
   Safari and across desktop/mobile versions.
-- Core 0.12.10 has an Opus regression risk. Opus remains release-gated until
-  non-empty, re-probeable ST and MT fixture outputs pass.
+- The reviewed 0.12.10 core profile passes the non-empty Opus encode/re-probe
+  gate in isolated Chromium ST and MT runs. That evidence is not a
+  cross-browser or every-input Opus guarantee.
 - MT needs HTTPS, COOP/COEP/CORP and `SharedArrayBuffer`. ST fallback works
   without isolation but is not a guarantee that a large job fits.
 - Top-level navigation is supported; iframe embedding is not.
@@ -69,7 +79,7 @@ FFmpeg output does not remove these product/browser/resource limits.
   verification against the live container.
 - The application is GPL-3.0-or-later and its native legal files and pinned
   source identities are included in the release record. Publish the production
-  ZIP/checksum, exact `v0.1.0` source and FFmpeg Corresponding Source bundle
+  ZIP/checksum, exact `v0.2.0` source and FFmpeg Corresponding Source bundle
   together; development-only smoke artifacts must not be distributed.
 - Chromium covers a broad real pinned-core ST operation matrix, a real MT
   H.264/AAC conversion, MT-to-ST fallback, nested static/Toolbox-context