@techspokes/typescript-wsdl-client 0.33.0 → 0.34.0

package/docs/releases/v0.34.0.md

@@ -0,0 +1,30 @@
+# TypeScript WSDL Client v0.34.0
+
+## Conformance Gate Readiness
+
+This release makes WSDL conformance coverage explicit in the release preflight path without adding a duplicate full test run.
+
+## What This Improves
+
+Maintainers can now see whether the focused conformance command, broad Vitest discovery, and CI script still line up before a release tag is created. The roadmap also now treats conformance gate wiring as shipped, which moves the 1.0 plan toward resolving remaining explicit deferrals and running release-candidate gates.
+
+## Highlights
+
+- Adds a release preflight `conformance-gate` check for `test:conformance`, `npm test`, and `npm run ci` wiring.
+- Documents `npm run test:conformance` as the focused command for WSDL capability rows and fixtures.
+- Updates the 1.0 roadmap so validation-gate wiring is no longer an open decision.
+
+## Upgrade Notes
+
+No special upgrade steps.
+
+## Validation
+
+- CI passed.
+- NPM package contents were validated.
+- Agent skill artifact was validated and packaged.
+- Release preflight passed against the target tag.
+
+## Notes
+
+Release tag: `v0.34.0`.

package/docs/roadmap/README.md

@@ -8,7 +8,7 @@ See the root [README.md](../../README.md) for project overview and the root [ROA
 
 This plan turns the 1.0 roadmap into implementation slices that can be picked up independently. Each slice has its own plan document with scope, testing strategy, acceptance gates, and release implications.
 
-The plan is optimized for preserving quality. The contract and compatibility baselines now exist, choice union mode is shipped, and JSON array streaming is shipped. The remaining readiness work is the capability conformance framework, WSDL coverage evidence, and the final release candidate gate pass.
+The plan is optimized for preserving quality. The contract and compatibility baselines now exist, choice union mode is shipped, JSON array streaming is shipped, and the conformance framework is wired into validation gates. The remaining readiness work is to resolve any explicit conformance deferrals and run the final release candidate gate pass.
 
 ## Route Summary
 
@@ -18,9 +18,9 @@ The plan is optimized for preserving quality. The contract and compatibility bas
 | OpenAPI compatibility | [OpenAPI Fastify Compatibility](v1.0-openapi-fastify-compatibility.md)       | baseline complete | Schema strategy is proven       |
 | Choice union mode     | [Choice Union Mode](v1.0-choice-union-mode.md)                               | complete          | Implemented in `0.26.0`         |
 | JSON array streaming  | [JSON Array Streaming](v1.0-json-array-streaming.md)                         | complete          | Implemented in `0.28.0`         |
-| Conformance framework | [Capability Conformance Framework](v1.0-capability-conformance-framework.md) | phase 4 shipped   | Pipeline claims are test-backed |
-| WSDL coverage matrix  | [WSDL Coverage Matrix](v1.0-wsdl-coverage-matrix.md)                         | generated artifacts proven | Feature support is test-backed |
-| Release candidate     | [Release Candidate Gates](v1.0-release-candidate-gates.md)                   | remaining         | 1.0 release is repeatable       |
+| Conformance framework | [Capability Conformance Framework](v1.0-capability-conformance-framework.md) | gate wired        | Pipeline claims are test-backed |
+| WSDL coverage matrix  | [WSDL Coverage Matrix](v1.0-wsdl-coverage-matrix.md)                         | gate wired        | Feature support is test-backed |
+| Release candidate     | [Release Candidate Gates](v1.0-release-candidate-gates.md)                   | next              | 1.0 release is repeatable       |
 
 ## Execution Order
 
@@ -42,11 +42,11 @@ JSON array streaming is complete in `0.28.0`. The default `ndjson` format remain
 
 ### Slice 5: Capability Conformance Framework
 
-The registry, fixture strategy, compile runner, client evidence, OpenAPI evidence, gateway runtime evidence, generated-test evidence, app evidence, documentation drift check, and generated support matrix are shipped. The next work is to wire the right conformance subset into validation gates without making local development too slow.
+The registry, fixture strategy, compile runner, client evidence, OpenAPI evidence, gateway runtime evidence, generated-test evidence, app evidence, documentation drift check, generated support matrix, and validation-gate wiring are shipped. Keep `npm run test:conformance` as the focused local command while broad Vitest discovery covers conformance in `npm test`, `npm run ci`, and release preflight.
 
 ### Slice 6: WSDL Coverage Matrix
 
-The first WSDL matrix rows now exist as conformance registry entries with compile, client, OpenAPI, gateway runtime, generated-test, app, and documentation evidence. The next work is to keep those rows current while release candidate gates are prepared.
+The first WSDL matrix rows now exist as conformance registry entries with compile, client, OpenAPI, gateway runtime, generated-test, app, documentation, and release-gate evidence. The next work is to keep those rows current while release candidate gates are prepared.
 
 ### Slice 7: Release Candidate Gates
 
@@ -54,7 +54,6 @@ Run the release candidate gates after feature work and documentation have conver
 
 ## Remaining Before 1.0
 
-- Decide which conformance checks should run in CI, release preflight, or local-only workflows.
 - Turn remaining unsupported, diagnostic, or partial matrix rows into diagnostics, documentation, or scoped fixes.
 - Confirm `docs/supported-patterns.md` matches the matrix.
 - Run the release-candidate gates.
@@ -84,7 +83,8 @@ Run the release candidate gates after feature work and documentation have conver
 
 ### Coverage Gate
 
-- A capability conformance matrix runs under test automation.
+- A capability conformance matrix runs under broad Vitest test automation.
+- Release preflight verifies the focused conformance command and CI wiring.
 - Each matrix entry has a fixture, status, and stage expectations.
 - Unsupported features fail loudly or are documented as deliberately unsupported.
 

package/docs/roadmap/v1.0-capability-conformance-framework.md

@@ -1,10 +1,10 @@
 # Version 1.0 Capability Conformance Framework
 
-Status: Phase 4 shipped; validation-gate wiring remaining before `1.0.0`.
+Status: Phase 5 shipped; release-candidate gate pass remaining before `1.0.0`.
 
 Plan for turning SOAP, WSDL, OpenAPI, gateway, app, generated-test, and documentation support claims into fixture-backed conformance evidence.
 
-Phase 1 shipped a TypeScript registry, reusable WSDL fixtures, compile-stage runner, documentation drift tests, and generated public support matrix. Phase 2 added generated client type-checking, OpenAPI validation, and executable diagnostics for terminal rows. Phase 3 added generated gateway type-checking and Fastify runtime evidence for current supported and partial rows. Phase 4 added generated-test and app scaffold evidence for those rows.
+Phase 1 shipped a TypeScript registry, reusable WSDL fixtures, compile-stage runner, documentation drift tests, and generated public support matrix. Phase 2 added generated client type-checking, OpenAPI validation, and executable diagnostics for terminal rows. Phase 3 added generated gateway type-checking and Fastify runtime evidence for current supported and partial rows. Phase 4 added generated-test and app scaffold evidence for those rows. Phase 5 wired conformance into validation gates through broad Vitest discovery and release preflight script verification.
 
 See the root [README.md](../../README.md) for project overview and [Version 1.0 Roadmap Plan](README.md) for the complete 1.0 route.
 
@@ -545,12 +545,15 @@ Acceptance criteria:
 
 ## Phase 5: Documentation And Release Gates
 
-Wire the conformance framework into docs validation, CI, or release preflight once runtime cost is acceptable. Keep a focused command for maintainers who want only conformance checks.
+Phase 5 is implemented. Keep this section as the baseline for conformance gate ownership.
+
+`npm run test:conformance` remains the focused maintainer command for WSDL capability rows. `npm test` and `npm run ci` cover conformance through broad Vitest discovery, so release preflight does not run a duplicate full conformance pass. Release preflight instead runs a cheap `conformance-gate` script check that fails if the focused command disappears, if `npm test` becomes scoped away from `test/conformance`, or if `npm run ci` stops running the broad test command.
 
 Acceptance criteria:
 
 - `docs/supported-patterns.md` cannot drift from the registry.
-- CI or release preflight runs the selected conformance subset.
+- CI runs conformance through broad Vitest discovery.
+- Release preflight verifies conformance command and CI wiring.
 - Full conformance can run locally before `1.0.0`.
 - Release notes can cite capability IDs for behavior changes.
 
@@ -567,7 +570,6 @@ Acceptance criteria:
 
 ## Open Decisions
 
-- Decide how much generated output type-checking is acceptable in CI runtime.
 - Decide which inspector output format becomes public before `1.0.0`.
 - Decide whether docs should remain manually maintained or eventually generated from the registry.
 

package/docs/roadmap/v1.0-release-candidate-gates.md

@@ -33,7 +33,11 @@ Run `npm run docs:validate`. Confirm README, CLI reference, API reference, confi
 
 ### Test Gate
 
-Run `npm test`. Confirm unit, snapshot, and integration suites cover the 1.0 contract.
+Run `npm test`. Confirm unit, snapshot, integration, and conformance suites cover the 1.0 contract.
+
+### Conformance Gate
+
+Run `npm run test:conformance` when changing capability rows or fixture-backed behavior. Confirm `npm test` and `npm run ci` keep broad Vitest discovery so `test/conformance` stays covered, and confirm release preflight reports a passing `conformance-gate` script check.
 
 ### Smoke Gate
 
@@ -53,7 +57,7 @@ Run the supported Node.js floor and the newest active Node.js line in CI before
 
 ### Release Gate
 
-Run `npm run release:preflight -- v1.0.0` during release preparation. Confirm release notes, changelog, dependency pins, generated examples, CI, and skill packaging pass.
+Run `npm run release:preflight -- v1.0.0` during release preparation. Confirm release notes, changelog, dependency pins, conformance wiring, generated examples, CI, and skill packaging pass.
 
 ## Documentation Checklist
 
@@ -62,6 +66,7 @@ Run `npm run release:preflight -- v1.0.0` during release preparation. Confirm re
 - API reference lists implemented options only.
 - Configuration docs describe both stream formats.
 - Supported patterns reflects the WSDL matrix.
+- The conformance gate documents `npm run test:conformance`, broad Vitest discovery, and release preflight wiring.
 - Production docs describe terminal-error behavior for both stream formats.
 - Migration docs explain any behavior changes since `0.x`.
 

package/docs/roadmap/v1.0-wsdl-coverage-matrix.md

@@ -1,10 +1,10 @@
 # Version 1.0 WSDL Coverage Matrix
 
-Status: generated-test and app evidence shipped; validation-gate wiring remaining before `1.0.0`.
+Status: generated-test, app evidence, and validation-gate wiring shipped before `1.0.0`.
 
 Plan for turning WSDL and XSD support claims into automated, fixture-backed evidence before 1.0. This is the first domain under the [Capability Conformance Framework](v1.0-capability-conformance-framework.md).
 
-The initial fixture-backed compile matrix shipped in `0.30.2` and `0.30.3`. Client, OpenAPI, gateway runtime, generated-test, and app evidence now prove the current supported and partial rows, and terminal rows have executable diagnostics. The remaining work is to decide which conformance checks belong in CI and release preflight.
+The initial fixture-backed compile matrix shipped in `0.30.2` and `0.30.3`. Client, OpenAPI, gateway runtime, generated-test, and app evidence now prove the current supported and partial rows, and terminal rows have executable diagnostics. `npm test` and `npm run ci` cover the conformance suite through broad Vitest discovery, and release preflight verifies that the script wiring remains intact.
 
 See the root [README.md](../../README.md) for project overview and [Version 1.0 Roadmap Plan](README.md) for the complete 1.0 route.
 
@@ -30,7 +30,6 @@ Each matrix row should have a minimal fixture, an expected support status, and a
 
 ## Remaining Scope
 
-- Decide which conformance checks should run in CI, release preflight, and focused local commands.
 - Keep diagnostics executable as more unsupported rows are added.
 - Keep fixture metadata useful for a future public conformance fixture corpus.
 - Preserve the weather smoke fixture as the canonical end-to-end happy path.
@@ -153,12 +152,13 @@ Partial rows must prove only the documented subset. `xs:anyAttribute` should not
 
 ### Next Slice
 
-The next slice is Phase 5 documentation and release-gate wiring. Implement it before adding more feature rows unless a production bug requires a focused diagnostic or support decision.
+The next slice is release-candidate preparation. Run it before adding more feature rows unless a production bug requires a focused diagnostic or support decision.
 
 Work items:
 
-- Decide whether `npm run test:conformance` should run in CI, release preflight, or both.
-- Keep a focused command for maintainers who want only conformance checks.
+- Keep `npm run test:conformance` as the focused command for maintainers who want only conformance checks.
+- Keep `npm test` and `npm run ci` broad enough for Vitest to discover `test/conformance`.
+- Keep release preflight's `conformance-gate` script check aligned with the package scripts.
 - Confirm release preflight runtime remains acceptable.
 - Keep diagnostic and unsupported rows stopped at compile.
 - Update public docs only when a row status or public contract changes.

package/docs/testing.md

@@ -21,6 +21,7 @@ npm test              # All Vitest tests
 npm run test:unit     # Unit tests only
 npm run test:snap     # Snapshot tests only
 npm run test:integration  # Integration tests only
+npm run test:conformance  # WSDL capability conformance tests only
 npm run test:watch    # Watch mode for development
 ```
 
@@ -169,6 +170,16 @@ import { pathToFileURL } from "node:url";
 const pluginModule = await import(pathToFileURL(join(outDir, "gateway", "plugin.ts")).href);
 ```
 
+## Conformance Tests
+
+Conformance tests live under `test/conformance/` and prove WSDL capability claims through committed fixtures, registry rows, generated artifacts, diagnostics, and documentation alignment. Use the focused command when changing capability rows or fixture-backed behavior:
+
+```bash
+npm run test:conformance
+```
+
+`npm test` includes the conformance suite through normal Vitest discovery. `npm run ci` and release preflight cover conformance through that broad test command, while release preflight also checks that the focused command and broad CI discovery remain wired.
+
 ## Known Issues
 
 ### ArrayOf* Schema-Type Mismatch (Resolved)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techspokes/typescript-wsdl-client",
-  "version": "0.33.0",
+  "version": "0.34.0",
   "description": "Turn legacy WSDL/SOAP services into typed TypeScript clients, OpenAPI 3.1 specs, and production-ready Fastify REST gateways. Built for enterprise SOAP modernization.",
   "keywords": [
     "wsdl",