feat: add constrained live-audio adapter contract - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change introduces the first constrained live-audio adapter contract without enabling a physical audio route.
It adds the canonical English RFC and Russian translation, a typed Flutter
LiveAudioAdapterboundary, and anUnavailableLiveAudioAdapterdefault. The default reports48000 Hz, mono, signed PCM16 little-endian as the required future stream format while refusing playback and capture truthfully. No audio plugin is initialized, no permission is requested, and no platform/device route is claimed.The workbench now accepts the contract as a dependency and shows the adapter's unavailable reason when a user selects the future live route. New tests cover the PCM format invariant, unavailable adapter behavior, live-route selection, the existing send flow, and the existing import flow.
Documentation now includes lifecycle, capability, shutdown, error and device-acceptance requirements; research sources for permission/session/focus constraints; bilingual indexes and roadmap status; public status wording; and CI checks for the added English/Russian file pairs.
Scope boundary
This is an unavailable-first scaffold only. It does not add a recording/playback plugin, microphone permission, audio session configuration, hardware route, Bluetooth route, radio interface, physical-route result, supported-device claim, encryption or automatic recovery behavior.
Validation
cargo fmt --all -- --checkcargo clippy --workspace --all-targets -- -D warningscargo test --workspacedart format --output=none --set-exit-if-changed lib testflutter analyzeflutter testflutter build web --releaseflutter build linux --debugnode tools/device-acceptance/validate-report.mjs tools/device-acceptance/fixtures/report-template-v1.jsonnode tools/device-acceptance/test-validator.mjsgit diff --checkThe web build completes with the existing
flutter_rust_bridgewasm dry-run warning; the bridge is intentionally unavailable on web and the warning does not fail the build.