[codex] Fix photo-only generation manifest - #3
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Root cause
Photo-mode Markdown still serialized the complete inactive
subjectProfile, including the default Taiwan black bear IDs. Migrated projects could also retain the old black bear prompt inextraDetails, creating conflicting instructions for ChatGPT and Gemini.User impact
Newly downloaded photo-mode Markdown contains no inactive catalog subject. Existing users must reload the site, download a new Markdown file, and upload it with their photos in a new provider conversation.
Validation
npm run typechecknpm test(31 passed)npm run buildnpm run test:e2e(1 passed)