fix(pixel): teach preview runtime constraints before writes - #6587
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
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.
Pixel generated date editors using
prompt(), which the Dashboard preview sandbox blocks. The pre-write contracts explained opaque-origin storage but omitted modal-dialog and external-resource restrictions.Share the actual preview runtime boundary across full, lean and small-context prompts, workspace/verification guides, and the publication tool description. Direct generated apps to use inline DOM controls, including date inputs, and bundled relative assets. The iframe sandbox, CSP and historical prompt core remain unchanged. The workspace guide cap increases from 2,600 to 2,800 characters to accommodate the explicit runtime boundary; the compact prompt stays below 3,800.
Validation: 56 focused tests passed (
prompt_contract.test.mjs,agent-skills.test.mjs,workspace_preview.test.mjs);git diff --checkpassed. Route tests verify the guidance arrives before tool discovery on sandbox and native gateway execution. This is guidance delivery evidence, not fresh fleet/model behavior acceptance; that remains in the qualification loop.