@techspokes/typescript-wsdl-client 0.35.0 → 0.39.0

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 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.
+`ROADMAP.md` must reflect the current released `0.38.x` line. Choice union mode, JSON array streaming, conformance gate wiring, baseline WSDL coverage, wildcard attribute bags, and the dependency refresh must be treated as shipped work, while final 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.30.x` work accurately.
+- `ROADMAP.md` names released `0.35.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/roadmap/v1.0-release-candidate-gates.md

@@ -29,7 +29,7 @@ The release candidate gates define what must be true before tagging `v1.0.0`. Th
 
 ### Documentation Gate
 
-Run `npm run docs:validate`. Confirm README, CLI reference, API reference, configuration docs, supported patterns, production docs, and roadmap agree on choice union mode and JSON array streaming.
+Run `npm run docs:validate`. Confirm README, CLI reference, API reference, configuration docs, supported patterns, production docs, and roadmap agree on choice union mode, JSON array streaming, baseline conformance coverage, and Node support.
 
 ### Test Gate
 
@@ -59,6 +59,8 @@ Run Node 24 as the supported Node.js floor and Node 26 as the current line in CI
 
 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.
 
+The post-release package workflow should run `npm run release:publish-check` before publishing from the tag. It must not rerun full CI because `release:preflight` is the release-blocking gate before the tag is pushed.
+
 ## Documentation Checklist
 
 - README names supported 1.0 capabilities accurately.
@@ -69,6 +71,7 @@ Run `npm run release:preflight -- v1.0.0` during release preparation. Confirm re
 - The conformance gate documents `npm run test:conformance`, broad Vitest discovery, and release preflight wiring.
 - The Node gate documents Node 24 as the package floor and Node 26 as the current-line CI check.
 - Production docs describe terminal-error behavior for both stream formats.
+- Release docs include release-preflight validation as a consumer-facing outcome.
 - Migration docs explain any behavior changes since `0.x`.
 
 ## Acceptance Criteria
@@ -78,7 +81,7 @@ Run `npm run release:preflight -- v1.0.0` during release preparation. Confirm re
 - `CHANGELOG.md` has a dated `1.0.0` section during release preparation.
 - The package dry-run contents include required runtime templates and docs.
 - The agent skill artifact validates and packages deterministically.
-- The release workflow can publish with provenance.
+- The release workflow can publish with provenance after the targeted publish check passes.
 
 ## Release Implications
 

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

@@ -1,10 +1,10 @@
 # Version 1.0 WSDL Coverage Matrix
 
-Status: baseline support registry, generated-test evidence, app evidence, and validation-gate wiring shipped before `1.0.0`.
+Status: baseline support registry expanded through `0.36.0`; generated-test evidence, app evidence, validation-gate wiring, and `xs:anyAttribute` wildcard-bag support 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 matrix is now the public baseline support registry. Examples remain demos, while conformance fixtures are the durable support evidence. `npm test` and `npm run ci` cover the conformance suite through broad Vitest discovery, and release preflight verifies that the script wiring remains intact.
+The initial fixture-backed compile matrix shipped in `0.30.2` and `0.30.3`, with the baseline support corpus expanded in `0.35.0` and `xs:anyAttribute` promoted to supported in `0.36.0`. Client, OpenAPI, gateway runtime, generated-test, and app evidence now prove the current supported and partial rows, and terminal rows have executable diagnostics. The matrix is now the public baseline support registry. Examples remain demos, while conformance fixtures are the durable support evidence. `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.
 
@@ -59,7 +59,7 @@ Each matrix row should have a minimal fixture, an expected support status, and a
 | Multi-binding WSDLs        | documented behavior     | First binding or explicit selection   |
 | External `PolicyReference` | partial or diagnostic   | Inline policy already exists          |
 | Deep composition           | supported               | Prove current recursion behavior      |
-| `xs:anyAttribute`          | partial                 | Metadata retained; generated wildcard attributes deferred |
+| `xs:anyAttribute`          | supported               | Metadata retained; wildcard attribute bag emitted |
 | MTOM/XOP attachments       | unsupported diagnostic  | Keep out of 1.0 scope unless required |
 
 ## Manifest Shape
@@ -147,12 +147,12 @@ Rows that should stay compile-terminal:
 
 Each gateway-enabled row should prove plugin import, plugin registration, and at least one `fastify.inject` request when route behavior is relevant. Assertions should inspect the generated success or error envelope, not just the existence of generated files.
 
-Partial rows must prove only the documented subset. `xs:anyAttribute` should not imply generated wildcard attribute bags. External `PolicyReference` should not imply fetched or enforced external policy.
+Partial rows must prove only the documented subset. External `PolicyReference` should not imply fetched or enforced external policy. The `xs:anyAttribute` row is supported through generated wildcard attribute bag evidence.
 
 ### Phase 3 Gotchas
 
 - Do not overclaim `supported` when gateway behavior is relevant but unproven.
-- Do not snapshot whole generated files for conformance rows; assert stable contract surfaces instead.
+- Do not snapshoot whole generated files for conformance rows; assert stable contract surfaces instead.
 - Do not share temporary output directories across rows.
 - Do not let diagnostic or unsupported rows proceed to client, OpenAPI, or gateway generation.
 - Do not add a public inspector command in this slice.
@@ -169,6 +169,7 @@ Work items:
 - Keep release preflight's Node gate aligned with the package engine, Node 24 CI coverage, Node 26 CI coverage, and Node 24 release workflows.
 - Confirm release preflight runtime remains acceptable.
 - Keep diagnostic and unsupported rows stopped at compile.
+- Decide whether the remaining partial rows stay partial for 1.0 or need one scoped pre-1.0 fix.
 - Update public docs only when a row status or public contract changes.
 
 ### Verification