Correct upstream attribution and add AI-generated disclosure

The crate was built from discord's forks, not Intel's repos directly:
discord/cros-libva @ discord-0.0.13 and discord/cros-codecs @ discord-0.0.5
(both BSD-3-Clause, ChromiumOS copyright). Point the README, Cargo.toml,
and lib.rs at the actual sources + tags, soften the "verbatim" claim
(how closely files track upstream varies), and add the missing
attribution header to src/encode.rs (adapted from cros-codecs).

Also disclose that the crate is AI-generated and bitstream-unvalidated
in the description and README.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: kixelated

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "moq-vaapi"
 version = "0.0.1"
-description = "VA-API H.264 hardware encoder, vendored and trimmed from cros-libva + discord/cros-codecs"
+description = "(AI GENERATED) VA-API H.264 hardware encoder, derived from discord/cros-libva + discord/cros-codecs"
 authors = ["The ChromiumOS Authors", "Discord", "Luke Curley <kixelated@gmail.com>"]
 repository = "https://github.com/moq-dev/vaapi"
 license = "BSD-3-Clause"

README.md

@@ -1,8 +1,17 @@
 # moq-vaapi
 
+> **⚠️ AI GENERATED.** This crate was written by an AI agent (Claude), using the
+> repositories below as references. How closely individual files track upstream
+> varies and the emitted bitstream has not been validated at playback — treat the
+> whole thing as derived, unverified work and review before relying on it.
+
 A small, self-contained **VA-API H.264 hardware encoder** for Linux (Intel / AMD),
-vendored and trimmed from [cros-libva](https://github.com/intel/cros-libva) and
-[discord/cros-codecs](https://github.com/discord/cros-codecs) (BSD-3-Clause).
+derived from
+[discord/cros-libva @ discord-0.0.13](https://github.com/discord/cros-libva/tree/discord-0.0.13)
+and
+[discord/cros-codecs @ discord-0.0.5](https://github.com/discord/cros-codecs/tree/discord-0.0.5)
+— both BSD-3-Clause, themselves forks of Intel's
+[cros-libva](https://github.com/intel/cros-libva) (ChromiumOS).
 
 It exists to give [moq](https://github.com/moq-dev/moq)'s `moq-video` a thin,
 crates.io-publishable VA-API encoder brick instead of a multi-backend framework

src/encode.rs

@@ -1,3 +1,10 @@
+// Copyright 2022 The ChromiumOS Authors
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+//
+// Adapted from discord/cros-codecs (encoder/stateless/h264/vaapi.rs), itself
+// BSD-3-Clause / Copyright The ChromiumOS Authors. See LICENSE.cros-codecs.
+
 //! Thin VA-API H.264 encoder built on the vendored libva binding.
 //!
 //! Reuses the backend-agnostic bitstream layer ([`crate::codec::h264`]) from

src/lib.rs

@@ -7,7 +7,7 @@
 //! The starting point to using this crate is to open a [`Display`], from which a [`Context`] and
 //! [`Surface`]s can be allocated and used for doing actual work.
 
-// Most of this crate is vendored verbatim from cros-libva + discord/cros-codecs
+// Most of this crate is derived from discord/cros-libva + discord/cros-codecs
 // (BSD-3-Clause). Don't subject upstream code to this workspace's strict lints;
 // the build script also emits custom `libva_*_or_higher` cfgs.
 #![allow(dead_code, unused_imports, unexpected_cfgs, mismatched_lifetime_syntaxes)]