@techspokes/typescript-wsdl-client 1.1.5 → 1.1.8

package/docs/releases/v1.0.2.md

@@ -1,51 +0,0 @@
-# TypeScript WSDL Client v1.0.2
-
-## The Complete Stable Typed SOAP Modernization Contract
-
-Version 1.0.2 is the complete supported stable release narrative for the TypeScript client, OpenAPI 3.1, Fastify gateway, runnable app, test generation, and programmatic APIs developed throughout the 0.x series.
-
-## What This Improves
-
-Teams can adopt the generator with an explicit compatibility baseline. Default generated behavior remains aligned with `0.40.1`, supported WSDL patterns have fixture-backed evidence through every generated stage, and unsupported polymorphic or attachment constructs stop with diagnostics instead of producing misleading contracts.
-
-The stable migration contract makes opt-in behavior clear. Choice unions remain optional, NDJSON remains the default streaming format, JSON arrays remain available per operation, and multiple SOAP bindings continue using deterministic first-binding selection.
-
-Release delivery is now equally explicit. npmjs is the sole package registry, publication uses the tested npm 12 toolchain with provenance, and package validation accepts both npm 11 and npm 12 manifest formats. Rejected candidates keep immutable release and marker tags, while their maintainer-only draft releases may be retired after the remote marker is verified.
-
-## Highlights
-
-- Stabilizes typed SOAP clients, OpenAPI specifications, Fastify gateways, apps, and generated tests.
-- Requires Node.js 24 or newer and keeps Node 26 compatibility coverage.
-- Preserves `all-optional` as the default `xs:choice` strategy.
-- Preserves NDJSON as the default configured streaming format.
-- Supports per-operation JSON array streaming as an opt-in alternative.
-- Carries fixture-backed conformance evidence across compile and generated consumer stages.
-- Rejects abstract types, substitution groups, and MTOM/XOP attachments with explicit diagnostics.
-- Documents deterministic multi-binding behavior and unresolved external policy references.
-- Keeps the public WSDL inspector as a post-1.0 candidate.
-- Publishes only to npmjs with OIDC provenance and a pinned npm release.
-- Accepts package manifests emitted by npm 11 and npm 12.
-- Retires abandoned drafts without deleting or reusing immutable tags.
-
-## Upgrade Notes
-
-No intentional generated-code or runtime behavior break is introduced relative to `0.40.1` or `1.0.1`. Consumers must run Node.js 24 or newer, regenerate owned output, review the generated diff, and run their TypeScript build and tests.
-
-Install `1.0.2` as the current stable package. Existing `1.0.1` consumers may update without a migration.
-
-## Validation
-
-- CI passed.
-- The complete WSDL capability conformance suite passed.
-- NPM package contents were validated with npm 11 and npm 12.
-- The npm publication lifecycle passed with npm 12 in dry-run mode.
-- Agent skill artifact was validated and packaged.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.0.2`.
-
-Candidate `v1.0.0` was permanently abandoned before npmjs publication. Version `1.0.1` delivered the first supported stable package and the npmjs correction, but its concise incident-focused notes did not carry forward the complete major-release narrative. Version `1.0.2` restores that standalone release context.
-
-The abandoned-draft retirement policy is tracked in [LAWXER-SAS/general-issue-tracker issue #77](https://github.com/LAWXER-SAS/general-issue-tracker/issues/77).

package/docs/releases/v1.0.3.md

@@ -1,37 +0,0 @@
-# TypeScript WSDL Client v1.0.3
-
-## Stable Dependency Tooling
-
-Version 1.0.3 refreshes the SOAP runtime and TypeScript execution tooling while preserving the compiler compatibility required by repository validation and generated projects.
-
-## What This Improves
-
-The package and generated app scaffold now use `soap` 1.10.0 and `tsx` 4.23.1. These updates keep runtime SOAP integration and TypeScript execution current without changing generated client, OpenAPI, gateway, or app behavior.
-
-TypeScript remains on the supported 6.x line because TypeScript 7 changes the compiler package exports and JavaScript API used by validation and conformance tests. Dependabot now defers only TypeScript 7.x updates until that compiler migration is implemented and validated separately.
-
-## Highlights
-
-- Updates the `soap` runtime dependency minimum to 1.10.0.
-- Updates the `tsx` development dependency minimum to 4.23.1.
-- Aligns generated app dependency pins with the refreshed root dependencies.
-- Retains TypeScript 6.0.3 compatibility for compiler API and CLI validation.
-- Defers TypeScript 7.x Dependabot updates pending a dedicated migration.
-
-## Upgrade Notes
-
-No generated-code or public API changes are introduced. Existing consumers can update normally, and newly generated apps receive the refreshed `soap` and `tsx` dependency ranges.
-
-## Validation
-
-- CI passed.
-- The complete WSDL capability conformance suite passed.
-- NPM package contents were validated.
-- Agent skill artifact was validated and packaged.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.0.3`.
-
-TypeScript 7 adoption remains a separate maintenance task because its native compiler package does not preserve the TypeScript 6 JavaScript compiler API and CLI export behavior used by this repository.

package/docs/releases/v1.0.4.md

@@ -1,45 +0,0 @@
-# TypeScript WSDL Client v1.0.4
-
-## Secure Dependency Delivery
-
-Version 1.0.4 is the next public patch after the retired v1.0.3 candidate. It refreshes SOAP and TypeScript execution tooling, remediates vulnerable direct and transitive dependencies, and updates release workflows without changing generated client, OpenAPI, gateway, or app behavior.
-
-## What This Improves
-
-The package and generated app scaffold now use `soap` 1.10.0 and `tsx` 4.23.1. The direct `fast-xml-parser` and `js-yaml` dependency floors are updated to secure versions, while the refreshed lockfile resolves the reported Axios, brace expansion, routing, URI, and YAML advisories.
-
-TypeScript remains on the supported 6.x line because TypeScript 7 changes compiler package exports and JavaScript APIs used by validation and conformance tests. Dependabot continues to defer only TypeScript 7.x updates until that compiler migration is implemented and validated separately.
-
-GitHub Actions workflows now use `actions/setup-node` v7. Security reporting guidance is aligned with Node.js 24 and GitHub private vulnerability reporting.
-
-## Highlights
-
-- Updates the `soap` runtime dependency minimum to 1.10.0.
-- Updates the `tsx` development dependency minimum to 4.23.1.
-- Updates `fast-xml-parser` to 5.10.1 and `js-yaml` to 5.2.2 or newer compatible releases.
-- Refreshes transitive HTTP, brace expansion, routing, URI, and YAML dependencies.
-- Aligns generated app dependency pins with the refreshed root dependencies.
-- Retains TypeScript 6.0.3 compatibility for compiler API and CLI validation.
-- Defers TypeScript 7.x Dependabot updates pending a dedicated migration.
-- Upgrades GitHub workflows to `actions/setup-node` v7.
-
-## Upgrade Notes
-
-No generated-code or public API changes are introduced. Existing consumers can update normally, and newly generated apps receive the refreshed `soap` and `tsx` dependency ranges.
-
-Users upgrading from v1.0.2 receive the dependency tooling changes originally planned for v1.0.3 together with the security remediation in this release. Version 1.0.3 was retired before publication and never shipped to npm.
-
-## Validation
-
-- CI passed.
-- The complete WSDL capability conformance suite passed.
-- npm package contents were validated.
-- `npm audit` reported zero vulnerabilities.
-- The agent skill artifact was validated and packaged.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.0.4`.
-
-Version 1.0.3 remains permanently marked as an abandoned release candidate and was never published to npm.

package/docs/releases/v1.0.5.md

@@ -1,41 +0,0 @@
-# TypeScript WSDL Client v1.0.5
-
-## Verifiable Agent Skill Delivery
-
-This patch release makes the agent skill release artifact reproducible, checksummed, attested, and independently installable while refreshing maintained dependencies and remediating all current audit findings.
-
-## What This Improves
-
-Agent skill releases now include a deterministic ZIP, a conventional `SHA256SUMS` file, and GitHub build provenance. The draft workflow downloads its own uploaded assets into a clean directory, verifies their checksum and attestation, installs the skill in isolation, and exercises a representative weather WSDL pipeline.
-
-Forced skill installation is now an exact, rollback-safe replacement. Existing installations remain untouched without `--force`; with `--force`, stale and locally modified files are removed as the complete candidate replaces the prior copy.
-
-Behavior fixtures now cover command selection, generated-output refusal, environment guidance, and incomplete WSDL or catalog input. Incomplete-input guidance directs agents to inspect the consumer project before asking only for the missing source location and intended generation surface.
-
-## Highlights
-
-- Add deterministic agent skill archives, checksums, inventory validation, source-map validation, and MIT license metadata.
-- Add release provenance and clean-runner verification of downloaded draft assets.
-- Verify previous-release-to-candidate replacement without altering host or global configuration.
-- Retain the release ZIP as the supported installation and update boundary while recording GitHub CLI dry-run compatibility.
-- Refresh maintained direct dependency floors and remediate current transitive vulnerability alerts.
-
-## Upgrade Notes
-
-This release does not change the TypeScript API, generated-client contract, or `wsdl-tsc` CLI behavior. Package consumers can update normally.
-
-Agent skill users should continue installing from the release ZIP. Install to an explicit target outside the extracted archive, and use `--force` only when a complete replacement of an existing installation is intended.
-
-## Validation
-
-- CI passed.
-- The complete WSDL capability conformance suite passed.
-- npm package contents were validated.
-- `npm audit` reported zero vulnerabilities.
-- Agent skill artifact checksums and provenance were validated.
-- The uploaded agent skill was installed and smoke-tested.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.0.5`.

package/docs/releases/v1.0.6.md

@@ -1,35 +0,0 @@
-# TypeScript WSDL Client v1.0.6
-
-## Security and Dependency Maintenance
-
-This patch release applies the Fastify 5.12.1 security fixes and refreshes maintained runtime, development, and generated application dependencies.
-
-## What This Improves
-
-Consumers and generated Fastify applications now resolve the current Fastify security patch. The generated application scaffold also uses the maintained `soap` and Node type floors.
-
-Repository validation now runs on Vitest 4.1.11 and current parser, YAML, SOAP, and Node type dependencies. These updates keep the supported Node 24 and Node 26 lines current without changing generated contracts.
-
-## Highlights
-
-- Apply the Fastify 5.12.1 security release.
-- Update Vitest to 4.1.11 for current test-runner fixes.
-- Refresh `fast-xml-parser`, `js-yaml`, `soap`, and `@types/node` dependency floors.
-- Refresh generated app pins for Fastify, `soap`, and `@types/node`.
-
-## Upgrade Notes
-
-This release does not change the TypeScript API, generated-client contract, or `wsdl-tsc` CLI behavior. Package consumers can update normally.
-
-## Validation
-
-- CI passed.
-- The complete WSDL capability conformance suite passed.
-- npm package contents were validated.
-- `npm audit` reported zero vulnerabilities.
-- Agent skill artifact checksums and provenance were validated.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.0.6`.

package/docs/releases/v1.0.7.md

@@ -1,36 +0,0 @@
-# TypeScript WSDL Client v1.0.7
-
-## Security and dependency maintenance
-
-This patch release applies upstream security fixes in XML, URI, and OpenAPI parsing dependencies, refreshes maintained dependency floors, and keeps generated-test verification compatible with the latest Vitest output format.
-
-## What This Improves
-
-The XML and URI parser updates address upstream security fixes, while the OpenAPI parser and YAML updates keep the internal validation stack current. Generated applications and repository tooling also start from refreshed dependency floors.
-
-Generated-test verification now reads Vitest's JSON report file directly, preserving consumer-style test evidence as the test runner evolves. The Node 26 stream test also waits for the readable stream to close before checking source iterator cleanup.
-
-## Highlights
-
-- Update `fast-uri`, `@xmldom/xmldom`, `@apidevtools/swagger-parser`, and `js-yaml` for upstream fixes.
-- Refresh `soap`, `yargs`, Fastify, Node types, `tsx`, and Vitest dependency floors.
-- Refresh generated app pins for Fastify, `soap`, `@types/node`, and `tsx`.
-- Update generated-test and conformance runners for Vitest 5 JSON reports.
-- Stabilize stream cancellation cleanup verification on Node 26.
-
-## Upgrade Notes
-
-No special upgrade steps.
-
-## Validation
-
-- CI passed on Node 24 and Node 26.
-- The complete WSDL capability conformance suite passed.
-- NPM package contents were validated.
-- `npm audit` reported zero vulnerabilities.
-- The agent skill artifact was validated and packaged.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.0.7`.

package/docs/releases/v1.1.0.md

@@ -1,42 +0,0 @@
-# TypeScript WSDL Client v1.1.0
-
-## Generated TypeScript with explicit lint ownership
-
-This minor release adds automatic ESLint suppression preambles to newly emitted TypeScript and documents path exclusions for consumers with restrictive lint policies.
-
-## What This Improves
-
-Regenerated client and gateway files carry their ESLint directive automatically, eliminating repeated manual edits. App and generated-test scaffolds use distinct wording that explains when to remove suppression as those files become maintained source.
-
-Preambles are packaged resources selected by logical artifact scope and applied at the final file-write boundary. Resource validation and installed-package consumer tests ensure the behavior works outside the repository checkout, including conditional helpers and programmatic generation.
-
-## Highlights
-
-- Add one preamble to every complete generated TypeScript file, including streaming helpers and stub routes.
-- Preserve existing app/test files unless their existing force option requests regeneration.
-- Propagate TypeScript generation failures instead of logging write failures as successful generation.
-- Document consumer global ignores, strict inline policies, parser limitations, and hook behavior.
-- Verify real ESLint suppression alongside maintained-source controls and installed-package tests.
-
-## Upgrade Notes
-
-CLI syntax, public API signatures, catalog semantics, and runtime behavior are unchanged. Regeneration adds a comment preamble to TypeScript output; existing editable scaffolds retain their current contents unless explicitly regenerated.
-
-`/* eslint-disable */` suppresses rule reports only when inline configuration is allowed. It does not bypass parsing or TypeScript checking, and clean files may produce unused-disable diagnostics. Use the [consumer ESLint guidance](../generated-code.md#generated-preambles-and-eslint) to exclude generated paths while keeping maintained-source policies intact.
-
-Remove the suppression when adopting an app or test scaffold as maintained source, and keep adopted files outside ignored generated directories. No runtime or schema migration is required.
-
-## Validation
-
-- Generated-file, resource-validation, and ESLint tests passed on Node 24 and Node 26.
-- Full CI, generated-artifact conformance, and pipeline smoke validation passed.
-- Installed tarball generation, consumer typechecking, and generated tests passed outside the checkout.
-- NPM package contents and comment-only resources were validated.
-- The agent skill artifact was validated and packaged with the new consumer guidance.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.1.0`.
-
-Implements [issue #142](https://github.com/TechSpokes/typescript-wsdl-client/issues/142).

package/docs/releases/v1.1.1.md

@@ -1,44 +0,0 @@
-# TypeScript WSDL Client v1.1.1
-
-## Correct array types from wrapping sequences
-
-This patch preserves occurrence bounds declared on wrapping `xs:sequence` nodes when generating element types. See the [project overview](../../README.md) for the generation pipeline.
-
-## What This Improves
-
-A sequence with `maxOccurs="2"` around an address element now generates `address: AddressType[]` instead of a scalar address. Sequences with `minOccurs="0"` and repeated bounds generate optional arrays, including finite limits and `unbounded`.
-
-The corrected catalog metadata flows into client types, OpenAPI schemas, and gateway responses. Consumer fixtures verify that both addresses survive the existing array-wrapper flattening behavior.
-
-## Highlights
-
-- Preserve occurrence bounds through uninterrupted sequence ancestry, including nested sequences.
-- Verify required and optional arrays in generated TypeScript and OpenAPI schemas.
-- Preserve repeated response items through gateway wrapper flattening.
-- Check the regression through the installed package CLI and consumer TypeScript compilation.
-- Refresh the soap runtime and generated app floor to 1.13.1 and Vitest tooling to 5.0.2.
-
-## Upgrade Notes
-
-Update the package and regenerate your clients, OpenAPI specifications, and gateways from their WSDL sources. Review the generated diff: affected scalar properties become arrays, and properties inside optional sequences can become optional. Adapt consuming code to these corrected types.
-
-Corrected array metadata can activate existing OpenAPI wrapper flattening, changing an affected REST object wrapper into an array. Review REST payload schemas and consumers when regenerating gateways; existing wrapper-flattening options retain their meanings.
-
-This patch preserves the previous behavior across `xs:choice`, `xs:all`, zero-maximum sequence subtrees, disabled elements, and wildcards. It adds no finite-array-length or sequence-order runtime enforcement, CLI options, or catalog fields. See [supported patterns](../supported-patterns.md#fully-supported) for the compatibility boundary.
-
-## Validation
-
-- Focused occurrence and unchanged choice-mode regression tests passed.
-- Full CI, generated-artifact conformance, and pipeline smoke validation passed.
-- Installed package generation and consumer TypeScript checks passed, including rejection of scalar addresses.
-- NPM package contents were validated.
-- The agent skill artifact was validated and packaged with its checksum manifest.
-- Release preflight passed against the target tag.
-
-## Notes
-
-Release tag: `v1.1.1`.
-
-This candidate was abandoned before publication. Singleton SOAP responses could remain scalar and fail gateway serialization despite generated array contracts. The immutable tag and abandonment marker retain its release identity.
-
-Fixes [issue #141](https://github.com/TechSpokes/typescript-wsdl-client/issues/141) through [PR #145](https://github.com/TechSpokes/typescript-wsdl-client/pull/145). Thanks to [BCsabaEngine](https://github.com/BCsabaEngine) for the original diagnosis and contribution.

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/releases/v1.1.5.md

@@ -1,38 +0,0 @@
-# TypeScript WSDL Client v1.1.5
-
-## Checked direct-client execution with explicit host control
-
-This patch adds an opt-in, versioned package-root binding for independently installed checked direct clients. It also advances native WSDL/XSD qualification and research diagnostics while retaining the existing generated-client and gateway defaults.
-
-## What This Improves
-
-Generated checked direct clients can import `checkedDirectRuntimeV1` from the installed package root and execute supported document/literal SOAP 1.1 requests against explicitly authorized owned IPv4-loopback services. Native schema, scalar and payload validation, source identity, and compatibility checks remain in force. Typed response values and declared SOAP faults are independently exercised through installed-client tests.
-
-Normal generated calls no longer inherit profiling work quotas, payload caps or default deadlines. Applications may deliberately select capacity limits, cancellation, deadlines and size controls according to their own operational requirements.
-
-The checked path is deliberately narrow. It does not enable arbitrary production SOAP endpoints, remote source loading, TLS/authentication/WS-Security, general XSD support or public admission of unqualified operations. The broader content-model research and mathematical decision procedures remain separate from production support claims.
-
-## Highlights
-
-- Export the versioned `checkedDirectRuntimeV1` binding from the package root for installed checked direct clients.
-- Preserve source-authorized native-plan and schema checks when constructing and invoking supported generated clients.
-- Exercise ordered scalar requests, responses and declared SOAP faults through an owned local SOAP 1.1 adapter.
-- Remove inherited profiling quotas and default execution ceilings from ordinary calls while keeping explicit caller-selected controls.
-- Improve direct-schema correspondence, original-source reconstruction, diagnostic evidence and reference conformance without changing legacy defaults.
-- Refresh the compatible dependency and generated-app pins, including security fixes for the transitive URI parser and HTTP client.
-
-## Upgrade Notes
-
-Update the package to `1.1.5` and regenerate checked clients when using the new binding. Existing client and gateway defaults remain unchanged. Do not direct the restricted checked runtime to production or third-party SOAP endpoints; unsupported grammar, source, scalar, binding and endpoint cases continue to refuse execution.
-
-## Validation
-
-- Full CI, native semantic reference, strict TypeScript, conformance and generated-consumer tests passed on the release candidate.
-- Installed package checks exercised typed local SOAP calls and refusal boundaries.
-- The production dependency audit reported no known vulnerabilities on the candidate lockfile.
-- Linux and Windows Node 24 and Node 26 checks are required on the final release pull request and merged main.
-- Release preflight validates package contents, documentation, agent skill artifacts and the candidate tag before release.
-
-## Notes
-
-Release tag: `v1.1.5`.

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 [current roadmap](../../ROADMAP.md#active-backlog) for the active backlog and delivery milestones. This document is the historical 1.0 plan; its original version-specific gates are preserved below.
-
-## Purpose
-
-This plan organized the 1.0 roadmap into implementation slices. Each slice retains its 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.