Repository navigation
Preserve API-key first delivery in the exact validated Web172 tree - #164
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.
This signed single-commit branch replaces #163 without changing one source-tree byte. Tested source daab6e8 and tree 8f6c8eb930fe77d6983a37e9b30912a384af5e7e passed formal Validate 37109872791: 808/808, zero failure/skip/todo; 14 actual Store cases and 2 save-owner cases, personal/project first-delivery barriers 100 each. Both production archives are identical, SHA256 9a21c5e6ff9fbb274dbc7c45ec1ccffdbff33a945544b64d5976b14ee9752bfa. The component tag will point to that exact signed tested source, and assets will be the exact CI outputs without rebuilding.
The new branch resolves unsigned-ancestor protection, not a bypass. It has one verified signed commit based on current main and the identical tested tree. API-key editor alone opts into schema-bound one-time fields delivered to its detached clone; cache identity/store/generation/base/account/save-owner cleanup and other consumers remain unchanged. Protected branch CodeQL checks are still required before merge. Original failed/cancelled CI evidence stays retained.
Server packaged native delivery and the full permission/resource/locale matrix remain separate and incomplete. No company deployment, zero-CVE assertion, or historical HOLD promotion.