UAIX now publishes a reusable conformance fixture pack inside the adoption kit and conformance pack so launch reviewers can run the current positive and negative validator expectations without assembling cases by hand.
What changed
- 接入套件 now carries a fixture pack beside the starter message, validator request, mock-exchange request, conformance record, and implementation evidence checklist.
- 一致性包 now exposes the same fixture pack with positive keyed, minified-keyed, and keyless cases; canonical-hash equivalence metadata; and negative missing-profile, missing-required-field, undeclared-field, invalid-traceparent, DID/VC trust-evidence, keyless-shape, keyless-overflow, and unsupported-alias cases.
- 路线图 now treats reusable fixture evidence as part of the current conformance path while keeping alias and binary transports future-bound.
- The production response-surface check now verifies that the conformance packet includes the checklist, required fixture IDs, and canonical-hash equivalence metadata.
How to use this update
- Fetch the current packet from 接入套件 or 一致性包.
- Run each fixture against the validate route and compare status, 规范化模式, and expected issue codes.
- Carry the fixture result beside the implementation evidence checklist before widening support language.
- Attach the 变更日志 and this news record when fixture behavior supports a public release.
Why this matters
Reusable fixture cases make validator behavior harder to misread. They show what currently passes, what must fail, and which future formats still need public evidence before UAIX describes them as supported.