Add ADT web packaging flow and runtime assets#46
Merged
nicpottier merged 1 commit intomainfrom Feb 16, 2026
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
1 participant
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.
This PR adds end-to-end ADT web packaging across pipeline, API, and Studio UI, including a new package step in master and a dedicated /package-adt API flow. It introduces packaged ADT static serving, packaging status checks, and Studio controls to package and open the generated ADT app. It also vendors the web runtime assets under assets/web and adds raven TTS cache fixture files required by the packaging/master test flow. The changes include hardening around packaging preconditions and status validation plus new route and pipeline tests for packaging behavior.