@techspokes/typescript-wsdl-client 0.39.0 → 1.0.1

package/README.md

@@ -43,12 +43,14 @@ Requirements: Node.js 24+ and the `soap` package as a runtime dependency.
 
 ## Quick Start
 
+The CLI requires explicit output paths. These examples use the git-ignored `.generated/` directory for disposable consumer output; repository automation uses `tmp/` separately.
+
 ### Generate a typed client
 
 ```bash
 npx wsdl-tsc client \
   --wsdl-source examples/minimal/weather.wsdl \
-  --client-dir ./generated/client
+  --client-dir ./.generated/client
 ```
 
 This produces `types.ts`, `client.ts`, `operations.ts`, and `utils.ts` in the output directory.
@@ -58,7 +60,7 @@ This produces `types.ts`, `client.ts`, `operations.ts`, and `utils.ts` in the ou
 ```bash
 npx wsdl-tsc openapi \
   --wsdl-source examples/minimal/weather.wsdl \
-  --openapi-file ./generated/openapi.json
+  --openapi-file ./.generated/openapi.json
 ```
 
 ### Generate the full stack
@@ -66,9 +68,9 @@ npx wsdl-tsc openapi \
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source examples/minimal/weather.wsdl \
-  --client-dir ./generated/client \
-  --openapi-file ./generated/openapi.json \
-  --gateway-dir ./generated/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name weather \
   --gateway-version-prefix v1 \
   --init-app
@@ -77,7 +79,7 @@ npx wsdl-tsc pipeline \
 ### Run and test
 
 ```bash
-cd generated/app && npm install && cp .env.example .env && npm start
+cd .generated/app && npm install && cp .env.example .env && npm start
 ```
 
 ```bash
@@ -165,7 +167,7 @@ See [Core Concepts](docs/concepts.md) and [Supported Patterns](docs/supported-pa
 The generated `operations.ts` provides a typed interface for mocking the SOAP client without importing the concrete class or the `soap` package:
 
 ```typescript
-import type { WeatherOperations } from "./generated/client/operations.js";
+import type { WeatherOperations } from "./.generated/client/operations.js";
 
 const mockClient: WeatherOperations = {
   GetCityWeatherByZIP: async (args) => ({
@@ -175,7 +177,7 @@ const mockClient: WeatherOperations = {
 };
 
 import Fastify from "fastify";
-import { weatherGateway } from "./generated/gateway/plugin.js";
+import { weatherGateway } from "./.generated/gateway/plugin.js";
 
 const app = Fastify();
 await app.register(weatherGateway, { client: mockClient, prefix: "/v1/weather" });

package/dist/app/generateApp.js

@@ -525,13 +525,13 @@ function generatePackageJson(appDir, force) {
             dev: "tsx watch server.ts",
         },
         dependencies: {
-            fastify: "^5.9.0",
+            fastify: "^5.10.0",
             "fastify-plugin": "^6.0.0",
             saxes: "^6.0.0",
             soap: "^1.9.3",
         },
         devDependencies: {
-            "@types/node": "^26.1.0",
+            "@types/node": "^26.1.1",
             tsx: "^4.23.0",
             typescript: "^6.0.3",
         },

package/dist/cli.js

@@ -143,7 +143,7 @@ if (rawArgs[0] === "client") {
     })
         .option("catalog-file", {
         type: "string",
-        desc: "Existing compiled catalog.json (for input), or output path when compiling from WSDL (default: tmp/catalog.json)"
+        desc: "Existing catalog input, or WSDL compilation output (default: {client-dir}/catalog.json)"
     })
         .option("client-dir", {
         type: "string",
@@ -238,7 +238,7 @@ if (rawArgs[0] === "openapi") {
         .scriptName("wsdl-tsc openapi")
         .usage("$0 [--wsdl-source <file|url> | --catalog-file <file>] --openapi-file <path> [options]")
         .option("wsdl-source", { type: "string", desc: "Path or URL to the WSDL (exclusive with --catalog-file)" })
-        .option("catalog-file", { type: "string", desc: "Existing compiled catalog.json (default: tmp/catalog.json if --wsdl-source not provided)" })
+        .option("catalog-file", { type: "string", desc: "Existing catalog input (default: {openapi-file-dir}/catalog.json when --wsdl-source is omitted)" })
         .option("openapi-file", { type: "string", demandOption: true, desc: "Output file or base path for OpenAPI" })
         .option("openapi-format", {
         type: "string",
@@ -590,7 +590,7 @@ if (rawArgs[0] === "pipeline") {
     })
         .option("catalog-file", {
         type: "string",
-        desc: "Output path for catalog.json (default: tmp/catalog.json)"
+        desc: "Output path for catalog.json (default: co-located with the first selected output)"
     })
         .option("clean", {
         type: "boolean",
@@ -737,7 +737,7 @@ if (rawArgs[0] === "pipeline") {
     const gatewayOut = pipelineArgv["gateway-dir"];
     const catalogOutArg = pipelineArgv["catalog-file"];
     if (!clientOut && !openapiOut && !gatewayOut) {
-        handleCLIError("At least one of --catalog-file, --client-dir, --openapi-file, or --gateway-dir must be provided for pipeline generation.");
+        handleCLIError("At least one of --client-dir, --openapi-file, or --gateway-dir must be provided for pipeline generation. Use compile for catalog-only output.");
     }
     // Determine catalog output path (always required since we always compile WSDL)
     let catalogOut;
@@ -758,8 +758,7 @@ if (rawArgs[0] === "pipeline") {
         catalogOut = path.join(path.resolve(gatewayOut), "catalog.json");
     }
     else {
-        // Fallback to tmp/catalog.json (should rarely happen due to validation above)
-        catalogOut = path.resolve("tmp/catalog.json");
+        throw new Error("Pipeline output validation did not select a catalog location.");
     }
     // Handle --clean flag for client output
     if (pipelineArgv.clean && clientOut) {

package/dist/compiler/schemaCompiler.d.ts

@@ -24,13 +24,13 @@ export type QName = {
     local: string;
 };
 /**
- * Represents an xs:any wildcard particle retained on a complex type.
+ * Represents a xs:any wildcard particle retained on a complex type.
  *
  * The base compiler previously dropped wildcards silently. Keeping them as
  * explicit markers lets downstream tools (stream-candidate detection,
  * streaming XML converter) reason honestly about types whose payload lives
  * outside the statically-typed schema — e.g. Escapia's content-service
- * stream wrappers that mix an xs:schema marker with an xs:any payload.
+ * stream wrappers that mix a xs:schema marker with a xs:any payload.
  */
 export type CompiledWildcard = {
     min: number;

package/dist/compiler/shapeResolver.js

@@ -3,7 +3,7 @@
  *
  * For stream operations whose record types live in a different WSDL (e.g.
  * Escapia's main EVRN service provides the concrete UnitDescriptiveContentType
- * while the content-service WSDL only exposes an xs:any-wrapped envelope),
+ * while the content-service WSDL only exposes a xs:any-wrapped envelope),
  * load the companion catalog and copy the reachable record-type graph into
  * the current catalog.
  *

package/docs/api-reference.md

@@ -211,13 +211,13 @@ Programmatic callers opt into choice union mode by passing `compiler: { choice:
 ```typescript
 await runGenerationPipeline({
   wsdl: "./service.wsdl",
-  catalogOut: "./generated/catalog.json",
-  clientOutDir: "./generated/client",
+  catalogOut: "./.generated/catalog.json",
+  clientOutDir: "./.generated/client",
   openapi: {
-    outFile: "./generated/openapi.json"
+    outFile: "./.generated/openapi.json"
   },
   gateway: {
-    outDir: "./generated/gateway",
+    outDir: "./.generated/gateway",
     serviceSlug: "service",
     versionSlug: "v1"
   },

package/docs/cli-reference.md

@@ -2,6 +2,8 @@
 
 The `wsdl-tsc` tool generates TypeScript SOAP clients, OpenAPI specifications, and Fastify gateways from WSDL files.
 
+Generation paths are explicit. Examples use the git-ignored `.generated/` directory for disposable consumer output, while this repository reserves `tmp/` for its own test and release automation.
+
 ## Commands Overview
 
 The tool provides six commands for different integration scenarios.
@@ -183,9 +185,9 @@ Complete stack:
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source examples/minimal/weather.wsdl \
-  --client-dir tmp/client \
-  --openapi-file tmp/openapi.json \
-  --gateway-dir tmp/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name weather \
   --gateway-version-prefix v1
 ```
@@ -195,9 +197,9 @@ With app scaffold:
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source https://example.com/weather?wsdl \
-  --client-dir ./generated/client \
-  --openapi-file ./generated/openapi.json \
-  --gateway-dir ./generated/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name weather \
   --gateway-version-prefix v1 \
   --init-app
@@ -208,9 +210,9 @@ With union-mode choice modeling:
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source ./service.wsdl \
-  --client-dir ./generated/client \
-  --openapi-file ./generated/openapi.json \
-  --gateway-dir ./generated/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name service \
   --gateway-version-prefix v1 \
   --client-choice-mode union
@@ -221,12 +223,12 @@ With generated test suite:
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source examples/minimal/weather.wsdl \
-  --client-dir tmp/client \
-  --openapi-file tmp/openapi.json \
-  --gateway-dir tmp/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name weather \
   --gateway-version-prefix v1 \
-  --test-dir tmp/tests
+  --test-dir ./.generated/tests
 ```
 
 Client and OpenAPI only:
@@ -294,7 +296,7 @@ Basic:
 ```bash
 npx wsdl-tsc client \
   --wsdl-source examples/minimal/weather.wsdl \
-  --client-dir tmp/client
+  --client-dir ./.generated/client
 ```
 
 From catalog:
@@ -521,7 +523,7 @@ app/
 | `LOGGER` | true | Fastify logger |
 | `OPENAPI_SERVER_URL` | (empty) | Override OpenAPI spec server URL at runtime |
 
-When `--security-config-file` is supplied and it contains an `upstream` profile, `.env.example` also lists the environment variables referenced by that profile.
+When `--security-config-file` is supplied, and it contains an `upstream` profile, `.env.example` also lists the environment variables referenced by that profile.
 
 ### Endpoints
 
@@ -575,7 +577,7 @@ Default behavior varies by command:
 | compile | Always requires explicit `--catalog-file` |
 | client | `{client-dir}/catalog.json` |
 | openapi | `{openapi-file-dir}/catalog.json` |
-| pipeline | Cascade: `{client-dir}` then `{openapi-dir}` then `{gateway-dir}` then `tmp/` |
+| pipeline | Cascade: `{client-dir}` then `{openapi-dir}` then `{gateway-dir}` |
 
 ## Common Workflows
 

package/docs/gateway-guide.md

@@ -34,7 +34,7 @@ await app.listen({ port: 3000 });
 
 The plugin automatically decorates Fastify with the SOAP client, registers JSON schemas, installs a centralized error handler, and registers all routes.
 
-Route paths are determined by `--openapi-base-path` during generation. The prefix option adds an additional runtime prefix on top of generated paths.
+Route paths are determined by `--openapi-base-path` during generation. The prefix option adds a runtime prefix on top of generated paths.
 
 ## Inbound Gateway Enforcement
 
@@ -256,10 +256,10 @@ When integrating multiple SOAP services, each service gets its own client, gatew
 
 ```typescript
 import Fastify from "fastify";
-import weatherPlugin from "./generated/weather/gateway/plugin.js";
-import inventoryPlugin from "./generated/inventory/gateway/plugin.js";
-import { Weather } from "./generated/weather/client/client.js";
-import { Inventory } from "./generated/inventory/client/client.js";
+import weatherPlugin from "./.generated/weather/gateway/plugin.js";
+import inventoryPlugin from "./.generated/inventory/gateway/plugin.js";
+import { Weather } from "./.generated/weather/client/client.js";
+import { Inventory } from "./.generated/inventory/client/client.js";
 
 const app = Fastify({ logger: true });
 

package/docs/migration-playbook.md

@@ -25,7 +25,7 @@ Start by generating a typed client from your WSDL.
 ```bash
 npx wsdl-tsc client \
   --wsdl-source https://your-service.example.com/service.svc?wsdl \
-  --client-dir ./generated/client
+  --client-dir ./.generated/client
 ```
 
 Inspect the generated `types.ts` to confirm that your WSDL types are represented correctly. Check that operation signatures in `operations.ts` match your expectations.
@@ -33,7 +33,7 @@ Inspect the generated `types.ts` to confirm that your WSDL types are represented
 Test a single operation to verify connectivity:
 
 ```typescript
-import { YourService } from "./generated/client/client.js";
+import { YourService } from "./.generated/client/client.js";
 
 const client = new YourService({
   source: "https://your-service.example.com/service.svc?wsdl",
@@ -51,7 +51,7 @@ Once the client types look correct, generate an OpenAPI 3.1 specification.
 ```bash
 npx wsdl-tsc openapi \
   --wsdl-source https://your-service.example.com/service.svc?wsdl \
-  --openapi-file ./generated/openapi.json
+  --openapi-file ./.generated/openapi.json
 ```
 
 Open `openapi.json` and review the paths, request/response schemas, and descriptions. The spec is derived from the same compiled catalog as the TypeScript types, so they stay aligned.
@@ -80,9 +80,9 @@ Regenerate with `--stream-config`:
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source your-service.wsdl \
-  --client-dir ./generated/client \
-  --openapi-file ./generated/openapi.json \
-  --gateway-dir ./generated/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name your-service \
   --gateway-version-prefix v1 \
   --stream-config ./stream.config.json \
@@ -97,8 +97,8 @@ Generate Fastify route handlers that translate JSON HTTP requests into SOAP call
 
 ```bash
 npx wsdl-tsc gateway \
-  --openapi-file ./generated/openapi.json \
-  --gateway-dir ./generated/gateway \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name your-service \
   --gateway-version-prefix v1
 ```
@@ -108,9 +108,9 @@ Or run all stages at once with the `pipeline` command and `--init-app`:
 ```bash
 npx wsdl-tsc pipeline \
   --wsdl-source https://your-service.example.com/service.svc?wsdl \
-  --client-dir ./generated/client \
-  --openapi-file ./generated/openapi.json \
-  --gateway-dir ./generated/gateway \
+  --client-dir ./.generated/client \
+  --openapi-file ./.generated/openapi.json \
+  --gateway-dir ./.generated/gateway \
   --gateway-service-name your-service \
   --gateway-version-prefix v1 \
   --init-app
@@ -159,7 +159,7 @@ The security config describes gateway authentication in OpenAPI and can scaffold
 
 ```typescript
 import Fastify from "fastify";
-import { yourServiceGateway } from "./generated/gateway/plugin.js";
+import { yourServiceGateway } from "./.generated/gateway/plugin.js";
 
 const app = Fastify({ logger: true });
 
@@ -177,7 +177,7 @@ await app.listen({ port: 3000 });
 The generated `operations.ts` interface lets you test gateway routes without a live SOAP connection.
 
 ```typescript
-import type { YourServiceOperations } from "./generated/client/operations.js";
+import type { YourServiceOperations } from "./.generated/client/operations.js";
 
 const mockClient: YourServiceOperations = {
   SomeOperation: async (args) => ({
@@ -191,7 +191,7 @@ Use this mock client when registering the gateway plugin in tests:
 
 ```typescript
 import Fastify from "fastify";
-import { yourServiceGateway } from "./generated/gateway/plugin.js";
+import { yourServiceGateway } from "./.generated/gateway/plugin.js";
 
 const app = Fastify();
 await app.register(yourServiceGateway, { client: mockClient, prefix: "/v1" });
@@ -230,14 +230,14 @@ NODE_DEBUG=soap node app.js
 
 ### CI/CD regeneration
 
-Add a regeneration step to your CI pipeline. Because output is deterministic, you can regenerate and check for unexpected diffs:
+Add a generation and validation step to your CI pipeline. The `.generated/` directory is disposable and should be recreated for each build:
 
 ```bash
 npx wsdl-tsc pipeline --wsdl-source $WSDL_URL ...
-git diff --exit-code generated/
+npx vitest run --config ./.generated/tests/vitest.config.ts
 ```
 
-If the diff is non-empty, the WSDL contract has changed. Review and commit the updated files.
+If generation or the generated tests fail, review the WSDL contract change before deployment.
 
 See [Production Guide](production.md) for validation, logging, and deployment details.
 
@@ -247,7 +247,7 @@ You do not have to expose all WSDL operations at once.
 
 ### Route-by-route migration
 
-Use the operations configuration file to control which operations are included in the OpenAPI spec and gateway. Generate only the operations you are ready to expose, then add more over time.
+Use the operations configuration file to control which operations are included in the OpenAPI spec and gateway. Generate only the operations you are ready to expose, then add more overtime.
 
 See [Configuration](configuration.md) for the operations config file format.
 

package/docs/migration.md

@@ -18,6 +18,7 @@ These steps apply to every version upgrade:
 
 | wsdl-tsc | Node.js | TypeScript | soap | Fastify | saxes |
 |----------|---------|------------|------|---------|-------|
+| 1.0.x | >= 24.0 | >= 6.0 | >= 1.9 | >= 5.10 | >= 6.0 |
 | 0.35.x and later | >= 24.0 | >= 6.0 | >= 1.9 | >= 5.8 | >= 6.0 |
 | 0.17.x | >= 20.0 | >= 6.0 | >= 1.9 | >= 5.8 | >= 6.0 |
 | 0.16.x | >= 20.0 | >= 6.0 | >= 1.9 | >= 5.8 | N/A |
@@ -30,6 +31,40 @@ These steps apply to every version upgrade:
 
 Versions 0.11 through 0.16 are additive and non-breaking. See `CHANGELOG.md` for per-version detail rather than dedicated upgrade sections here.
 
+## Upgrading to 1.0.0 from 0.40.1
+
+Version `1.0.0` stabilizes the public behavior shipped through `0.40.1`. It does not intentionally change generated client, OpenAPI, gateway, app, or runtime contracts.
+
+### Stable 1.0 Contract
+
+- Node.js 24 is the supported runtime floor.
+- The package and generated code remain ESM-only.
+- `all-optional` remains the default `xs:choice` strategy.
+- Choice union mode remains opt-in through `--client-choice-mode union`.
+- NDJSON remains the default configured stream format.
+- JSON array streaming remains opt-in per operation.
+- Generated output remains replaceable and should be regenerated from WSDL or catalog inputs.
+
+### Accepted 1.0 Limitations
+
+- Multiple SOAP bindings use deterministic first SOAP binding selection.
+- External `PolicyReference` documents are not fetched or resolved.
+- Abstract complex types fail with a diagnostic.
+- Substitution groups fail with a diagnostic.
+- MTOM/XOP attachments fail with a diagnostic.
+
+### Steps to Upgrade to 1.0.0
+
+1. Upgrade the development dependency to `@techspokes/typescript-wsdl-client@^1.0.0`.
+2. Confirm the project runs Node.js 24 or newer.
+3. Keep `soap` installed as a runtime dependency.
+4. Regenerate every owned client, OpenAPI, gateway, app, and generated-test artifact.
+5. Review the generated diff and run the consumer TypeScript build and tests.
+
+### Is 1.0.0 Breaking?
+
+No intentional behavior break is introduced relative to `0.40.1`. The major version declares the documented surface stable, so future incompatible changes require a new major release.
+
 ## Upgrading to 0.17.x from 0.16.x
 
 This upgrade adds opt-in streamable SOAP responses. No breaking changes; generated output is byte-for-byte unchanged when `--stream-config` is not provided.

package/docs/output-anatomy.md

@@ -151,8 +151,8 @@ The generated plugin exports a Fastify plugin function. Register it with your Fa
 
 ```typescript
 import Fastify from "fastify";
-import { myServiceGateway } from "./generated/gateway/plugin.js";
-import { createMyServiceClient } from "./generated/client/client.js";
+import { myServiceGateway } from "./.generated/gateway/plugin.js";
+import { createMyServiceClient } from "./.generated/client/client.js";
 
 const app = Fastify();
 const client = await createMyServiceClient("https://soap-endpoint.example.com");

package/docs/production.md

@@ -93,7 +93,7 @@ Default strategy: `all-optional`. The opt-in `--client-choice-mode union` mode e
 
 ### Union Types
 
-`--client-choice-mode union` is supported as an opt-in strategy. Future WSDL coverage matrix work will broaden fixture evidence for edge cases, but the released union mode is test-backed for compiler metadata, TypeScript output, OpenAPI constraints, generated mocks, and generated validation tests.
+`--client-choice-mode union` is supported as an opt-in strategy. The 1.0 conformance matrix backs the released mode across compiler metadata, TypeScript output, OpenAPI constraints, generated mocks, generated validation tests, gateway runtime behavior, and app generation.
 
 ### WS-Policy
 

package/docs/releases/README.md

@@ -52,3 +52,33 @@ Keep the H1 in the repository file so each release note remains a complete sourc
 Write validation as consumer-facing outcomes, not as maintainer command transcripts. Keep exact release operator commands in `.github/copilot-instructions.md` and workflow logs.
 
 Write release notes for users and maintainers, not as a file-by-file change log. Use `CHANGELOG.md` for the canonical version history.
+
+## Candidate Publication
+
+The supported release path keeps final-form tags immutable:
+
+1. Run release preflight on the final uncommitted tree.
+2. Commit the exact validated tree and create `vX.Y.Z`.
+3. Push the branch and tag so the draft workflow creates the release and skill asset.
+4. Review and publish the unmarked draft through GitHub's Release page.
+5. Let the guarded package workflow publish to npmjs with provenance.
+
+Manual package dispatch is a recovery path after the GitHub Release is published. It enforces the same tag, marker, reachability, draft, and prerelease checks.
+
+The normal path uses GitHub UI publication because a workflow publishing with its standard `GITHUB_TOKEN` does not trigger another workflow from the resulting event. Do not rely on recursive workflow delivery for package publication.
+
+## Abandoned Candidates
+
+Run the `Abandon Release Candidate` workflow before publishing a rejected draft. Supply the final-form tag, a permanent reason, and optional failed-validation evidence.
+
+The workflow creates annotated marker `abandoned/vX.Y.Z` on the same commit as `vX.Y.Z`, marks the draft visibly abandoned, and preserves its assets and evidence. The operation is idempotent when the marker already matches. A marker on another commit fails for maintainer review.
+
+Drafting, abandonment, and package publication are serialized per release tag so abandonment cannot race package delivery.
+
+Never move, delete for reuse, or force-update either tag. The rejected version is consumed, and the correction uses the next version.
+
+The marker cannot disable GitHub's Publish button. Draft and package automation enforce it, but a maintainer must still avoid publishing an abandoned draft through the GitHub UI.
+
+## Tag Ruleset Proposal
+
+Protect `v*` and `abandoned/v*` against updates and deletions. Consider restricted creation after testing the intended maintainer or GitHub App bypass identity. Repository settings remain a maintainer decision and are not changed by release automation.

package/docs/releases/v0.40.0.md

@@ -0,0 +1,45 @@
+# TypeScript WSDL Client v0.40.0
+
+## Current Dependency Baseline
+
+This release refreshes maintained dependency floors after the merged dependency updates and keeps generated app scaffolds aligned with the package baseline.
+
+## What This Improves
+
+Developers get current compatible dependency minimums in both the published package and newly scaffolded Fastify gateway apps. The XML parser, test stack, Fastify development dependency, and Node type definitions move to their maintained releases without changing the generated SOAP, OpenAPI, or gateway contracts. TypeScript remains on the maintained 6.x line because the repository documentation validator uses compiler-library APIs not exposed by TypeScript 7.
+
+Release preparation is also more direct: run targeted checks while editing, run release preflight once on the final uncommitted candidate, then commit and tag the exact validated tree without repeating the full gates.
+
+Generated output paths are clearer. Public examples use an explicit, git-ignored `.generated/` directory, while repository automation keeps smoke output, caches, and release work isolated under owned `tmp/` subfolders.
+
+The 1.0 roadmap remains focused on confirming explicit capability decisions and completing the release-candidate gates.
+
+## Highlights
+
+- Updates `fast-xml-parser` to `5.10.0`.
+- Updates Fastify to `5.10.0`.
+- Retains TypeScript `6.0.3` compatibility in the package and generated app.
+- Updates Vitest to `4.1.10`.
+- Updates `@types/node` to `26.1.1`.
+- Updates generated app scaffold pins for matching dependency floors.
+- Confirms zero known vulnerabilities in the root package and generated app dependency trees.
+- Aligns catalog help with the actual co-located output behavior.
+- Uses `.generated/` consistently for disposable consumer output examples.
+- Prevents smoke cleanup from deleting caches and unrelated automation workspaces.
+- Keeps release preflight helper declarations aligned across tests, TypeScript, and IDE inspections.
+- Defines a single final-candidate release preflight before the release commit.
+
+## 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.40.0`.

package/docs/releases/v0.40.1.md

@@ -0,0 +1,34 @@
+# TypeScript WSDL Client v0.40.1
+
+## Faster Conformance Feedback Before 1.0
+
+This maintenance release makes the capability conformance suite easier to run and diagnose while closing the remaining scope decisions before the stable 1.0 release candidate.
+
+## What This Improves
+
+Maintainers and contributors can run contracts, compile, client, OpenAPI, gateway, generated-test, or app conformance independently instead of waiting for every evidence layer after a focused change. The complete release-blocking suite remains intact and now reports visible per-capability progress during its longer generated-project checks.
+
+The 1.0 boundary is also explicit. Multiple bindings retain deterministic first SOAP binding selection, external policy documents remain unresolved, abstract types and substitution groups remain diagnostic, and MTOM/XOP attachments remain outside the typed SOAP-to-REST transport contract.
+
+## Highlights
+
+- Adds stage-specific conformance commands for focused maintainer feedback.
+- Keeps all 123 capability checks in the canonical full suite.
+- Documents the expected full-suite duration and agent timeout guidance.
+- Records the accepted partial and terminal capability boundaries for 1.0.
+- Defers the public WSDL inspector until after 1.0.
+
+## Upgrade Notes
+
+No special upgrade steps. Generated client, OpenAPI, gateway, app, and runtime contracts are unchanged.
+
+## 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.40.1`.

package/docs/releases/v1.0.0.md

@@ -0,0 +1,42 @@
+# TypeScript WSDL Client v1.0.0
+
+## A Stable Typed SOAP Modernization Contract
+
+Version 1.0 declares the documented TypeScript client, OpenAPI 3.1, Fastify gateway, runnable app, test generation, and programmatic APIs stable after the complete 0.x implementation and conformance program.
+
+## 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 migration contract also 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 now preserves rejected candidate evidence. An annotated abandonment marker blocks draft mutation and package publication while consuming the rejected version permanently.
+
+## 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.
+- 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.
+- Blocks GitHub Packages and npm publication for permanently abandoned release candidates.
+
+## Upgrade Notes
+
+No intentional behavior break is introduced relative to `0.40.1`. Consumers must run Node.js 24 or newer, regenerate owned output, review the generated diff, and run their TypeScript build and tests.
+
+## 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: `v1.0.0`.
+
+Release candidate abandonment guards address [GitHub issue #117](https://github.com/TechSpokes/typescript-wsdl-client/issues/117).