Clarify Web Tasks Vision telemetry and Pose Landmarker model redistribution terms

### Product and integration context We are evaluating `@mediapipe/tasks-vision@0.10.35` and the versioned Pose Landmarker task bundles for an open-source Apache-2.0 browser application. The application processes user-selected video locally and requires an approved same-origin/offline-capable asset-delivery strategy. We need authoritative documentation before adopting the SDK or redistributing model assets. ### Web telemetry questions The MediaPipe terms describe Solution API metrics collection and informed-consent responsibilities. Could you clarify specifically for the Web npm package `@mediapipe/tasks-vision`: 1. Does the Web package or its included WASM make requests to Google services after all WASM and model assets are supplied from same-origin local paths? 2. Does it transmit performance, utilization, app, input, or system metadata? 3. If so, what fields and destination origins are used? 4. Is there a documented and supported mechanism to disable those requests? 5. Is operating the Web runtime with external requests blocked supported under the applicable terms? ### Pose Landmarker model-rights questions For this versioned model bundle: `https://storage.googleapis.com/mediapipe-models/pose_landmarker/pose_landmarker_full/float16/1/pose_landmarker_full.task` Could you provide the authoritative model license or terms covering: 1. Commercial use. 2. Redistribution in an open-source repository. 3. Same-origin hosting by an application distributor. 4. Browser/service-worker caching and offline use. 5. Required notices, attribution, or citations. 6. Modification restrictions, if any. The Web documentation instructs developers to download and store a compatible model inside a project directory, but we could not locate explicit redistribution terms for the model bundle. ### Compiled Web package artifacts The npm tarball includes compiled WASM but does not contain LICENSE or NOTICE files. Could you identify the authoritative license and required notices for those distributed WASM artifacts? ### Requested outcome Please provide links to authoritative documentation or clarify whether these questions require a separate Google licensing/support channel.