Skip to content

test(workbook): qualify ambiguous alias rejection - #3

Open
rudycelekli wants to merge 3 commits into
mainfrom
validation/workbook-stable-id-alias-order-before-20261008
Open

rudycelekli wants to merge 3 commits into
mainfrom
validation/workbook-stable-id-alias-order-before-20261008

Conversation

@rudycelekli

@rudycelekli rudycelekli commented Oct 8, 2026 •

Copy link
Copy Markdown
Owner

Validation only

Tests-only baseline qualification against accepted upstream main 48aacfd. Production and the existing four CI gates are unchanged.

The prior supplemental head 87cdad4 incorrectly expected successful public resolution of duplicate display names; its two failures were fixture errors, not product defect evidence. Both calls returned the intentional ambiguous_column_reference contract. The signed correction freezes that rejection contract, including null value and unchanged original stored row/completed receipt. All original eight stable-ID cases remain unchanged.

Current corrected baseline CI is pending. The historical original cohort reproduced three stable-ID failures and five passing controls; no additional defect is claimed for the duplicate-name controls.

No upstream publication or merge is requested from this verification draft.

Add eight public HTTP and SQLite fixture cases without production changes.

Signed-off-by: Rudy Celekli <rudy@gradiahq.com>
Qualify both real HTTP and SQLite duplicate-name order controls against unchanged accepted production. Preserve the original eight stable-ID owners.

Signed-off-by: Rudy Celekli <rudy@gradiahq.com>
Correct the invalidated supplemental fixture expectation to the actual public ambiguous_column_reference contract. Preserve all original eight stable-ID cases and production sources.

Signed-off-by: Rudy Celekli <rudy@gradiahq.com>
@rudycelekli rudycelekli changed the title test(workbook): qualify duplicate display alias order test(workbook): qualify ambiguous alias rejection Oct 8, 2026
@rudycelekli
rudycelekli marked this pull request as ready for review October 10, 2026 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant