@techspokes/typescript-wsdl-client 1.1.4 → 1.1.8

package/docs/releases/v1.1.2.md

@@ -1,42 +0,0 @@
-# TypeScript WSDL Client v1.1.2
-
-## Consistent arrays from wrapping sequences
-
-This patch corrects generated array contracts and singleton SOAP response conversion for wrapping sequences. See the [project overview](../../README.md) for the generation pipeline.
-
-## What This Improves
-
-An element inside a repeated `xs:sequence` now receives the sequence's occurrence bounds in the compiled catalog and generated types. A single returned address becomes a one-element array, and multiple addresses retain their order. Generated REST gateways can serialize both responses successfully.
-
-The generated client uses existing catalog metadata to normalize repeated properties, so direct client consumers receive the same correction as gateways. Optional properties remain absent when omitted, and existing null handling is preserved.
-
-## Highlights
-
-- Propagate occurrence bounds through uninterrupted sequences, including nested sequences.
-- Normalize singleton primitive and complex responses to their declared array shape.
-- Preserve inherited and aliased type metadata during response conversion.
-- Verify real SOAP responses with REST wrapper flattening enabled and disabled.
-- Exercise the correction through an installed package and its generated client.
-
-## Upgrade Notes
-
-Update the package and regenerate clients, OpenAPI specifications, and gateways. Review affected scalar properties that become arrays and required properties that become optional. Corrected array metadata can also activate existing REST wrapper flattening, changing an object wrapper into an array.
-
-This release retains previous sequence-boundary handling for `xs:choice`, `xs:all`, zero-maximum sequences, disabled elements, and wildcards. It adds no finite-array-length or sequence-order validation and no CLI options or catalog fields. The generated metadata interface adds an optional `RepeatedElements` map; custom metadata without that map retains its previous behavior.
-
-Version 1.1.1 was abandoned before publication. This release includes its sequence compiler correction and dependency maintenance, together with the runtime correction discovered during final review.
-
-## Validation
-
-- Real SOAP transport tests cover singleton and repeated responses and optional request omission.
-- Generated client and gateway tests cover both REST wrapper representations.
-- Full CI, conformance, and pipeline smoke validation passed.
-- Installed package generation, TypeScript contracts, and SOAP response conversion passed.
-- NPM package contents and the agent skill artifact were validated.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.1.2`.
-
-The sequence compiler correction originated in [PR #145](https://github.com/TechSpokes/typescript-wsdl-client/pull/145) for [issue #141](https://github.com/TechSpokes/typescript-wsdl-client/issues/141). Thanks to [BCsabaEngine](https://github.com/BCsabaEngine) for the original diagnosis and contribution.

package/docs/releases/v1.1.3.md

@@ -1,36 +0,0 @@
-# TypeScript WSDL Client v1.1.3
-
-## Updated dependencies for clients and gateways
-
-This patch refreshes runtime and development dependencies and aligns generated app dependency ranges. See the [project overview](../../README.md) for the generation pipeline.
-
-## What This Improves
-
-The refreshed dependency tree addresses upstream HTTP transport, URI normalization, brace expansion, and source map advisories. Generated applications use the updated SOAP runtime range, and local development selects the supported Node 24 floor.
-
-The compiler remains on TypeScript 6 to preserve compatibility with the lint tooling and compiler API validators. Generated client and gateway contracts remain unchanged.
-
-## Highlights
-
-- Refresh compatible runtime, development, and transitive dependencies.
-- Align generated app SOAP runtime and Node type dependency ranges with the root package.
-- Replace the stale Node 20 development pin with Node 24.
-- Retain TypeScript 6 and the existing Node 24 minimum.
-
-## Upgrade Notes
-
-Update the package and refresh your dependency lockfile. Existing applications can update their SOAP runtime dependencies directly; regenerating an app scaffold preserves existing files unless explicitly forced.
-
-TypeScript 7 is excluded from this release. No generated API or configuration migration is required.
-
-## Validation
-
-- Full, production-only, and fresh generated app dependency audits report zero vulnerabilities.
-- Node 26 compatibility checks passed with 423 unit tests and pipeline generation and typecheck.
-- Full CI includes unit, snapshot, integration, conformance, and pipeline smoke checks.
-- Installed package checks exercise consumer generation, type contracts, and real local SOAP transport.
-- Release preflight verifies package contents, dependency alignment, and the agent skill ZIP and checksums.
-
-## Notes
-
-Release tag: `v1.1.3`.

package/docs/releases/v1.1.4.md

@@ -1,36 +0,0 @@
-# TypeScript WSDL Client v1.1.4
-
-## Explicit SOAP imports in generated clients
-
-This patch replaces generated SOAP namespace imports with named runtime imports and explicit type-only imports. See the [project overview](../../README.md) for the generation pipeline.
-
-## What This Improves
-
-Generated clients compile with strict NodeNext and verbatim module syntax while importing only the SOAP runtime function they use. Custom client names that match SOAP exports receive local aliases, so client generation stays valid for names such as `Client`, `IOptions`, `ISecurity`, and `createClientAsync`.
-
-Buffered and streamed clients retain their existing behavior. Integration tests now have a dedicated typecheck, and both Node 24 and Node 26 CI exercise compiled generated clients.
-
-## Highlights
-
-- Generate a named `createClientAsync` import and type-only `Client`, `IOptions`, and `ISecurity` imports.
-- Alias SOAP imports when a custom generated client name would collide with an imported identifier.
-- Validate buffered and streamed clients against the actual SOAP declarations and Node runtime.
-- Typecheck integration tests and run compiled-client coverage in Node 26 CI.
-
-## Upgrade Notes
-
-Update the package and regenerate clients to receive the new imports. No generated API or configuration migration is required.
-
-Updates from v1.1.2 also include the dependency security maintenance prepared in v1.1.3. TypeScript remains on the maintained 6.x line, and Node 24 remains the minimum supported runtime.
-
-## Validation
-
-- Full CI passed with 662 unit, snapshot, integration, and conformance tests.
-- Buffered and streamed generated clients compile and execute under Node 24 and Node 26 checks.
-- Installed package checks validate 73 generated TypeScript artifacts and exercise local SOAP transport.
-- Release preflight validates package contents, dependency alignment, generated examples, and workflow gates.
-- The agent skill ZIP and checksum manifest are validated and packaged.
-
-## Notes
-
-Release tag: `v1.1.4`.

package/docs/roadmap/README.md

@@ -1,107 +0,0 @@
-# Version 1.0 Roadmap Plan
-
-Completed plan for moving `@techspokes/typescript-wsdl-client` from the `0.x` line to the stable `1.0.0` release.
-
-See the root [README.md](../../README.md) for project overview and the root [ROADMAP.md](../../ROADMAP.md) for the public roadmap summary.
-
-## Purpose
-
-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 preserves the stable 1.0 contract. Choice union mode, JSON array streaming, `xs:anyAttribute` wildcard bags, stage-specific conformance, executable unsupported diagnostics, and repeatable release gates shipped before or with `1.0.0`.
-
-## Route Summary
-
-| Slice                 | Document                                                                     | Status            | Outcome                         |
-|-----------------------|------------------------------------------------------------------------------|-------------------|---------------------------------|
-| Contract audit        | [Contract Audit](v1.0-contract-audit.md)                                     | complete          | Public surfaces match behavior  |
-| 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) | gate wired        | Pipeline claims are test-backed |
-| WSDL coverage matrix  | [WSDL Coverage Matrix](v1.0-wsdl-coverage-matrix.md)                         | baseline complete | Public support is test-backed |
-| `xs:anyAttribute` bag | [`xs:anyAttribute` Wildcard Bag](v1.0-xs-anyattribute-wildcard-bag.md)        | complete          | Implemented in `0.36.0`         |
-| Release candidate     | [Release Candidate Gates](v1.0-release-candidate-gates.md)                   | complete          | 1.0 release is repeatable       |
-
-## Execution Order
-
-### Slice 1: Contract Audit
-
-The baseline contract audit is complete. Keep it active as release hygiene so CLI docs, API docs, configuration docs, examples, roadmap statements, and generated behavior stay aligned.
-
-### Slice 2: OpenAPI Fastify Compatibility
-
-Compatibility research is complete for choice union mode and JSON array streaming. Run the same local Fastify probes before any future schema output changes.
-
-### Slice 3: Choice Union Mode
-
-Choice union mode is complete in `0.26.0`. The default `all-optional` mode remains unchanged for backwards compatibility.
-
-### Slice 4: JSON Array Streaming
-
-JSON array streaming is complete in `0.28.0`. The default `ndjson` format remains unchanged, and `format: "json-array"` streams records incrementally without buffering the full SOAP response.
-
-### 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, generated support matrix, and validation-gate wiring are shipped. The registry is the public baseline support source, while examples remain demos. 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 WSDL matrix rows now exist as conformance registry entries with compile, client, OpenAPI, gateway runtime, generated-test, app, documentation, and release-gate evidence. Version `0.40.1` accepts the remaining partial and terminal rows as the 1.0 boundary. Keep those rows current while preparing release candidate gates.
-
-### Slice 7: xs:anyAttribute Wildcard Bag
-
-The [`xs:anyAttribute` wildcard bag plan](v1.0-xs-anyattribute-wildcard-bag.md) shipped in `0.36.0`. It promoted the previous metadata-only partial row to supported by emitting a configured wildcard attribute bag through TypeScript, OpenAPI, gateway, generated-test, app, and documentation evidence.
-
-### Slice 8: Release Candidate Gates
-
-Run the release candidate gates after feature work and documentation have converged. This slice validates docs, tests, generated examples, package contents, skill artifact, release notes, and provenance workflow readiness.
-
-## 1.0 Release State
-
-- Public contract surfaces are audited against implementation and tests.
-- Capability boundaries are documented and backed by executable evidence.
-- Release metadata and the final candidate pass release preflight before tagging.
-
-## Quality Principles
-
-- Keep default generated output stable unless a slice explicitly changes it.
-- Add failing tests before generator changes.
-- Prefer fixture-driven WSDL behavior over ad hoc string assertions.
-- Keep OpenAPI output compatible with generated Fastify gateways.
-- Preserve deterministic output ordering in catalogs, generated TypeScript, schemas, and route files.
-- Keep unsupported behavior explicit in diagnostics and documentation.
-
-## 1.0 Gates
-
-### Contract Gate
-
-- `--client-choice-mode union` is implemented and documented in `0.26.0`.
-- `format: "json-array"` is implemented and documented.
-- CLI docs, API docs, configuration docs, and generated behavior agree.
-
-### Compatibility Gate
-
-- Choice union schemas are validated against Fastify request handling.
-- Gateway response schemas stay inside Fastify serialization limits.
-- JSON array streams have documented terminal-error behavior.
-
-### Coverage Gate
-
-- A capability conformance matrix runs under broad Vitest test automation.
-- Release preflight verifies the focused conformance command and CI wiring.
-- Release preflight verifies CI covers Node 24 and Node 26 and release workflows use Node 24.
-- Each matrix entry has a fixture, status, and stage expectations.
-- Unsupported features fail loudly or are documented as deliberately unsupported.
-
-### Release Gate
-
-- `npm run docs:validate` passes.
-- `npm test` passes.
-- `npm run smoke:pipeline` passes.
-- `npm run ci` passes.
-- `npm run release:preflight -- v1.0.0` passes during release preparation.
-
-## Changelog Strategy
-
-Each implementation slice should add one concise `CHANGELOG.md` entry under `## [Unreleased]`. Release-only changes move those entries into the release section during normal release preparation.