Add direct Compilation output - #29
Merged
Merged
Conversation
Let agents materialize the exact reviewed Compilation into an absent local directory without requiring GitHub publication. Preserve the existing no-flag publication journey and make ambiguous Compilation starts non-retryable.
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
firstdraft plan compile --output <absent-directory>as a direct local materialization mode.git, formatting, repair, overwrite, or merge behavior0.2.1because published0.2.0is immutableContract
POST202, include the last validated retained Compilation in every recoverable status, artifact, authentication, or materialization failurecompilation statusandcompilation download; after a wait timeout, checkcurrent.compilation.idwith the read-only status command rather than rerunning Compile--output .and automatic design-file relocation outside this packetVerification
npm run checknpm audit --audit-level=lowreports zero vulnerabilitiesExact candidate
a251df7870491d5b9bdc390c27373933563f99fdcdc2bd1eaf4b6d1ccb3b701fa295afee672a723bf5e6641f982ffa2b6eb1f50d5230847b86b59ced12637857836ad0edd184fe636846bfa807bdb26b89ca49b3046ae86e540886868887eb0e60970ad5e62ee3ff1fb6d188c5d2c5a6e5e0efd50b40245f