Repository navigation
Conversation
This branch has not been deployed
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.
Failed element bundle checks currently leave temporary build directories behind, and a checkout path containing spaces is passed to Bun as an encoded URL path. Let the cleanup finish before returning failure and convert the source URL to a filesystem path.
Seven subprocess regressions cover matching bundles, stale web/package bundles, storage leakage, oversized output, spaced checkout paths and compiler errors. They check scratch contents before fixture teardown and confirm committed bundles are unchanged. The existing
element-bundlestep runs them before the real 48,840-byte bundle check.Validation: the regressions fail before the fix (2 pass/5 fail) and pass afterward (7 pass). The complete native lane passed 322 Swift tests, 431 TypeScript tests, 115 Rust tests including doc tests, 17,991 cross-language imports, bundle verification and editor grammar. Latest released SpecSync 6.1.1 passed strict checks with 100% source coverage. An independent read-only GPT review found no actionable defect.
This is a draft for corvid-agent review. The included SpecSync definition is unapproved; human definition/implementation acceptance and lifecycle finalization remain pending. Codex provenance is unsigned and does not satisfy the repository's pinned Claude/human signer policy; Trust's configured progressive provenance must be read with that limitation. No human review, permitted signature, hosted CI result, merge or release is claimed.
Exact feature commit
abbb2890b44800bd59bf7c7a50101f3639d7e58cpassed the complete pinned Trust 1.2.2 gate and a fresh strict SpecSync 6.1.1/100% check. Augur reports review risk 41 (below the unchanged block threshold); progressive provenance passes with the signer-policy limitation above. No protection was changed.