[TS PBT] Pin capability-first real property candidate - #408
Draft
CaelmBleidd wants to merge 1 commit into
Draft
CaelmBleidd wants to merge 1 commit into
CaelmBleidd wants to merge 1 commit into
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.
Problem
The first #356 development manifest includes real properties whose
Set,flat, andeveryoperations may leave no common supported symbolic denominator for #405. Source selection must be based on language/API capability before measuring fault-finding results.This child checkpoint
wrapremains concrete-only with its currently unsupportedorderedPair, and why other candidates are outside the bounded core.isNonEmptyimplementation and original Vitest/fast-check suite at9deb33a6f6cdab3c03404217aa8e87626930733e, with verified Git blob IDs and complete LGPL/GPL notices.expect(isNonEmpty(arr)).toBe(true)assertion. Record the originalfc.anythingsupport and altered distribution separately.arr[0]/toBeDefinedconformance is checked. Preserve all development v1 fixtures and selection history.Verification
At
0f9a84cd3d3298d943f514f4ccf30eb0b616ab57:npm install --package-lock-only --ignore-scripts --no-audit --no-fundandnpm ci --ignore-scripts --no-audit --no-fund: passed in the isolated candidate directory.npm run validate: passed, unchanged upstream suite 3/3 tests and bounded subset 1/1 test.git hash-objectfor the unchanged implementation and suite matched pinned upstream Git blob IDs.git diff --cached --checkpassed.Capability boundary
This is a development v2 candidate, not admitted to the six-mode paired denominator yet. Direct EtsIR mapping, original-predicate symbolic search, and replay have not been run on this exact SUT; array-domain projection alone does not prove those capabilities. #395 owns registration of the original callback. The candidate has no known fault/mutant and demonstrates no feedback advantage. No production API or shared contract changes are included. #356/#357/#404/#405 remain open.
Stacked on draft #406 (
caelmbleidd/pbt-356-core-corpus), pending its integration. Refs #345 #356 #395 #405.