Add Swift keyed persistence prototype and verified evidence - #253
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
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.
Description
Stock CodeQL Swift has no keyed UserDefaults transfer, and the first receiver-local prototype misses aliases and separate instances sharing a suite. This adds an isolated, non-scored ordered suite-state prototype with immutable successful and failed development evidence. It does not activate scored results or claim general preference semantics.
Key Changes:
Touch Points:
adapters/codeql/swift-resolved-native-v1/patches/and canonical persistence plan/queriesevidence/swift-keyed-persistence-v1/scripts/.github/workflows/ci.ymldocs/swift-keyed-persistence-prototype.mdValidation: fresh extraction 97.961s; canonical extractions 110.552s/96.342s; all eight fresh and nine per-canonical queries/decodes succeeded. Portable tests: 30 passed across retained attempts, fresh controls and canonical fixtures.
cargo fmt --checkand whitespace checks pass. Analysis requests remain 60s/2048MiB; aggregate memory compliance and whole-profile completeness remain unproven.Refs #220 and #215. Both issues remain open; acceptance is incomplete.