@techspokes/typescript-wsdl-client 0.30.0 → 0.30.1

package/dist/app/generateApp.js

@@ -515,7 +515,7 @@ function generatePackageJson(appDir, force) {
             soap: "^1.9.3",
         },
         devDependencies: {
-            "@types/node": "^26.0.0",
+            "@types/node": "^26.0.1",
             tsx: "^4.22.4",
             typescript: "^6.0.3",
         },

package/docs/releases/v0.30.1.md

@@ -0,0 +1,31 @@
+# TypeScript WSDL Client v0.30.1
+
+## Roadmap And Dependency Patch
+
+This patch release refreshes the 1.0 readiness documentation after the `0.30.0` maintenance release and advances the Node type definitions used by the package and generated app scaffold.
+
+## What This Improves
+
+Maintainers get roadmap and supported-pattern documentation that matches the current release line before starting the conformance framework work. Contributors also get clearer guidance about optional IDE MCP tooling in public-repository workflows.
+
+## Highlights
+
+- Aligns roadmap documentation with the current `0.30.x` release state.
+- Clarifies that `xs:any` wildcard metadata is retained for selected compiler and streaming workflows, but full wildcard serialization is not a typed contract.
+- Documents optional IDE MCP routing while preserving terminal-based contributor fallbacks.
+- Updates `@types/node` to 26.0.1 in both the package and generated app scaffold pins.
+
+## Upgrade Notes
+
+No special upgrade steps. Regenerate generated Fastify app scaffolds when you want new app projects to start with the updated `@types/node` pin.
+
+## Validation
+
+- CI passed.
+- NPM package contents were validated.
+- Documentation links and TypeScript fenced snippets were validated.
+- Agent skill artifact was validated and packaged.
+
+## Notes
+
+Release tag: `v0.30.1`.

package/docs/roadmap/README.md

@@ -1,6 +1,6 @@
 # Version 1.0 Roadmap Plan
 
-Detailed plan for moving `@techspokes/typescript-wsdl-client` from the released `0.28.x` line to a stable `1.0.0` release.
+Detailed plan for moving `@techspokes/typescript-wsdl-client` from the released `0.30.x` line to a 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.
 
@@ -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 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, 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.
 
 ## Route Summary
 
@@ -54,7 +54,7 @@ Run the release candidate gates after feature work and documentation have conver
 
 ## Remaining Before 1.0
 
-- Build the capability conformance registry and runner.
+- Build the capability conformance registry and compile-stage runner.
 - Build and run the WSDL feature matrix as the first conformance domain.
 - Turn unsupported or partial matrix rows into diagnostics, documentation, or scoped fixes.
 - Confirm `docs/supported-patterns.md` matches the matrix.

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

@@ -214,6 +214,6 @@ Acceptance criteria:
 
 ## Release Implications
 
-This framework is 1.0 readiness infrastructure. It can ship incrementally in `0.28.x` or later patch releases as tests, docs, and diagnostics improve.
+This framework is 1.0 readiness infrastructure. It can ship incrementally in `0.30.x` or later patch releases as tests, docs, and diagnostics improve.
 
 Do not block the first conformance slice on the WSDL inspector. The registry and runner create the durable foundation; the inspector should reuse that foundation after it proves useful.

package/docs/roadmap/v1.0-contract-audit.md

@@ -41,7 +41,7 @@ This slice prevents later work from building on ambiguous behavior. Choice union
 
 ### Roadmap State
 
-`ROADMAP.md` must reflect the released `0.28.x` line. Choice union mode and JSON array streaming must be treated as shipped work, while WSDL coverage and release-candidate gates remain the active 1.0 work.
+`ROADMAP.md` must reflect the current released `0.30.x` line. Choice union mode and JSON array streaming must be treated as shipped work, while capability conformance, WSDL coverage, and release-candidate gates remain the active 1.0 work.
 
 ### Release Metadata
 
@@ -63,7 +63,7 @@ Add negative tests only for newly identified contract gaps that a follow-up slic
 
 ## Acceptance Criteria
 
-- `ROADMAP.md` names released `0.28.x` work accurately.
+- `ROADMAP.md` names released `0.30.x` work accurately.
 - `docs/roadmap/README.md` links every 1.0 slice.
 - CLI, API, and configuration docs agree on required 1.0 behavior.
 - Known contract gaps are linked to implementation slices.

package/docs/supported-patterns.md

@@ -21,7 +21,7 @@ These patterns are handled end-to-end: WSDL parsing, TypeScript type generation,
 - Multiple WSDL ports and bindings; the first SOAP binding is selected, all ports are documented in service metadata
 - SOAP 1.1 and SOAP 1.2 binding detection
 - Streamable SOAP responses, opt-in per operation via `--stream-config` (ADR-002): client exposes `AsyncIterable<RecordType>`, gateway emits NDJSON or JSON array streams with backpressure, OpenAPI advertises the record schema via `x-wsdl-tsc-stream`
-- `xs:any` wildcard particles retained on compiled types (they used to be dropped silently) — enables honest stream-candidate detection and companion-catalog shape resolution
+- `xs:any` wildcard particles retained on compiled types for stream-candidate detection and companion-catalog shape resolution
 
 ### Named simple types and same-name elements
 
@@ -69,7 +69,7 @@ List types with an `itemType` attribute are detected and generate array types (`
 
 These features are not currently handled. Contributions are welcome.
 
-- `xs:any` and `xs:anyAttribute`: unrecognized elements fall through to an untyped representation
+- Full `xs:any` serialization and `xs:anyAttribute`: arbitrary wildcard content is not emitted as a typed contract
 - `xs:union` types: only union members expressed as restriction enumerations are captured
 - Abstract types: treated as regular concrete types without substitution logic
 - Substitution groups: not resolved during schema compilation

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techspokes/typescript-wsdl-client",
-  "version": "0.30.0",
+  "version": "0.30.1",
   "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",
@@ -90,7 +90,7 @@
   },
   "devDependencies": {
     "@types/js-yaml": "^4.0.9",
-    "@types/node": "^26.0.0",
+    "@types/node": "^26.0.1",
     "@types/yargs": "^17.0.35",
     "fastify": "^5.8.5",
     "fastify-plugin": "^6.0.0",