Repository navigation
test(DEN-3828): certify explicit docs alias cardinality peers - #8
Merged
Merged
Conversation
ORESoftware
deleted the
DEN-3828-api-docs-cardinality-canary-20260911
branch
September 12, 2026 02:52
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.
Purpose
Re-certify
ORESoftware/api-docs#92after its Rust suite exposed a semantic hole in the docs-discovery aliases and the TypeSpec model was repaired without weakening tuple order.Exact immutable inputs
ORESoftware/api-docs@f6efa12a3ce5a01713464df6168082c289d85716;ORESoftware/typespec-json-schema-validator@93dd73cb246a09b0a1c62d7192cc62ca6ecbe405.Authority contract
TypeSpec and Draft 2020-12 JSON Schema remain independent, human-authored, first-class peers. TypeSpec is transpiled through the official JSON Schema emitter into generated Schema B solely as comparison evidence. The canary requires structural and differential convergence, zero unexplained findings, admissible non-editable Contract IR, and source immutability across all five API Docs contract pairs.
The docs-discovery TypeSpec authority remains an exact four-position tuple, preserving alias order. Because TypeSpec 1.15 does not permit
@minItems/@maxItemson a tuple and its JSON-Schema emitter otherwise omits tuple cardinality, the TypeSpec authority now attaches those two JSON-Schema keywords through@TypeSpec.JsonSchema.extension. The independently authored JSON Schema carries the sameminItems: 4/maxItems: 4constraint. The generated schema is still a witness, not an authority.This keeps missing, duplicate/fifth, and reordered aliases fail-closed while retaining independent authorities.
Merge only after real stepful exact-head CI passes. Zero-step runs are non-evidence.
Tracking: DEN-3828 / DEN-3938.