Release the rebuilt Media Assistant behind a developer flag - #9
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.
What changed
archive/media-assistant-development-2026-08-18.NEXT_PUBLIC_MEDIA_STUDIO_ASSISTANT_DEBUG=1.Why
Months of local Media Assistant development had accumulated as a large unpublished branch with stale review material, generated-schema drift, and no backend release switch. This PR preserves the validated product work while removing release-only clutter and establishing a safe, reviewable route to main.
User and developer impact
Normal Studio, Graph, Media Preset, Prompt Recipe, provider configuration, pricing, and media workflows remain available. The Assistant stays opt-in for development and is not exposed to general users. No database migration, reset, saved-workflow deletion, provider-default change, or automatic paid generation is introduced by the release-curation slices.
Validation
Merge safety
This is intentionally a draft while GitHub checks and final branch review complete. Merge without rewriting the archive tag or deleting local persistent data.