@techspokes/typescript-wsdl-client 1.1.5 → 1.1.8

package/docs/content-model-analysis.md

@@ -1,92 +0,0 @@
-# Exact Particle Analysis
-
-Internal S06 occurrence and emptiness contracts over the immutable graph. See the root [README](../README.md).
-
-## API and guarantees
-
-[`analyzeOccurrences`](../src/compiler/occurrenceAnalysis.ts) consumes the `ComposedGraph` from [the common source/catalog entry](content-model-companions.md).
-It returns `analyzed {analysis}` or `failure {diagnostic}` without partial success on exhaustion.
-The analysis retains the original composed/resolved/canonical graph and the `requires-schema-assessment` gate.
-
-Each particle summary records exact named-element and wildcard contributions, `nullable` and `hasRealization`.
-It also records `effectiveTotalRange` and `schemaEmptiable`, the formal XSD schema predicates, using the same exact occurrence algebra.
-Type summaries combine the ordered composed roots, preserving restriction replacement versus extension concatenation.
-The particle table and original graph retain alternative-local guarantees and ordered relationships; object-wide intervals cannot replace them.
-
-Finite bounds remain canonical decimal strings; `unbounded` is a distinct maximum.
-The shared occurrence algebra uses exact `BigInt` after charging operand/result work.
-Zero dominates multiplication in either position, including beneath unbounded descendants; finite repetitions are never expanded.
-
-## Contributions and emptiness
-
-Sequences and legal all groups add member contributions.
-Choices take minima/maxima across realizable alternatives, inserting zero for absent members.
-A single required branch stays required; a member in every branch retains their minimum guarantee.
-Local repetition multiplies contributions without changing declared occurrences or group definitions.
-
-An empty sequence or all group admits epsilon.
-An empty required choice admits no sequence; an optional empty choice admits epsilon through zero repetitions.
-A choice with an epsilon branch is nullable even with a positive occurrence minimum.
-Unrealizable alternatives supply no accepted branch; `hasRealization` distinguishes empty language from epsilon.
-
-Elements are atomic child events, independently of their type's child-content emptiness.
-`hasRealization` describes the particle language with elements as terminals; it does not certify finite recursively nested values or scalar validity.
-Scalar/mixed text, nil, attributes and defaults remain later owners' responsibilities.
-
-Legal element/type recursion terminates without empty definition stubs.
-Group/containment expansion uses iterative active/done traversal and memoization; S05 already rejects cycles in those edges.
-No recursive emptiness equation crosses element type edges because an element is never epsilon.
-S05's missing-reference and forbidden-cycle diagnostics remain applicable beneath zero bounds.
-
-## Intervals and opaque scope
-
-A repeated pair can have interval `2..4` while admitting only counts 2 and 4.
-Order, gaps and correlated branches remain in the original grammar for #180/#181; summaries are not payload validators.
-An opaque builtin contribution remains original data.
-The scope `declared-particles-with-opaque-builtin` qualifies every child summary, including named/wildcard counts, effective total range and both emptiness predicates.
-They describe declared contributions only; they cannot certify the counts or emptiness of the whole opaque content language.
-Analysis never promotes builtin or skip/lax content to full concrete validation.
-
-## Budgets and evidence
-
-Analysis independently applies S05's inclusive 100,000-node and 1,000,000-work-step defaults.
-Indexing, traversal, arithmetic digits, conservative multiplication work and contribution/provenance copying count before allocation.
-Positive safe-integer overrides follow existing semantic policy; exhausted analysis returns `resource-limit` without partial success.
-Later matcher, payload scalar and generated-output budgets retain their [ADR-003 D09 owners](decisions/003-content-model-contracts.md#provisional-resource-budgets-s02-d09).
-
-[`analysis.xsd`](../test/conformance/fixtures/xsd/analysis/analysis.xsd) and [Node reference checks](../test/conformance/reference/analysis-contract.test.ts) retain historical qualification separately from current primary and scoped payload checks under [NT-CONT-01](reference-validation.md). Original huge-schema construction remains unqualified; the adjusted small copy is a separately hashed input.
-The historical reference check raised xmlschema's model-depth setting from 15 to 32 and treated warnings as errors. Current libxml2 observations use the explicitly separate small copy; the original exact schema retains historical xmlschema qualification and current unsupported status.
-
-### Nested empty-choice qualification
-
-XSD 1.0 second-edition [Element Sequence Valid](https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#cvc-model-group) expressly states that no sequence is valid against an empty choice, while epsilon is valid against an empty sequence or all group.
-[Particle validity](https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#cvc-particle) applies that rule to each repetition; an optional enclosing particle can choose zero repetitions.
-The [restriction rule](https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#cos-particle-restrict) only calls an empty choice pointless when its minimum is zero, and does not remove a required empty choice during payload assessment.
-The complete original second-edition XML source was read through a [pinned mirror](https://github.com/jacoelho/xsd/blob/142f25ee187e17f041af87b6bfcfc82385254520/docs/spec/xml/structures.xml), whose publication URI and October 2004 source header identify the Recommendation; direct W3C retrieval was unavailable in the managed network.
-
-The executable `deadRequired`, `deadOptional`, `deadAndRequired` and `deadWildcard` cases retain a pinned-engine disagreement.
-Xmlschema 4.2.0 skips the nested required empty choice and accepts the preceding child, although it rejects an isolated required empty choice.
-Libxml2 2.14.6 rejects those children and accepts only zero enclosing repetitions where applicable, matching the primary rule.
-The analysis follows that primary rule; the test records both engine observations without declaring the primary engine's acceptance normative.
-#180/#181 must retain these cases when qualifying payload matching and independent enumeration; #179 retains schema validity separately.
-
-The formal [Particle Emptiable](https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#cos-group-emptiable) predicate uses [effective total range](https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#cos-choice-range), which assigns an empty choice a zero range.
-Consequently a required empty choice has `schemaEmptiable: true` and `nullable: false`.
-#179 uses the former only where the specification invokes that formal schema predicate; #180 uses language nullability.
-Formal ranges include unrealizable branches and are not accepted count intervals.
-Declared zero-maximum particles remain in the graph for diagnostics and provenance; their range is zero as for the absent particle in the XSD component mapping, including an unbounded descendant.
-Zero-bound children are omitted from their containing choice's alternatives, while an optional non-disabled empty sequence remains an epsilon alternative.
-Root zero repetitions still admit epsilon.
-The `disabledChoice` and `disabledElementChoice` cases record pinned-engine deviations from this mapping; the terminal case preserves the S01/#181 zero-bound attribution qualification.
-
-### Commands and measurements
-
-[Unit tests](../test/unit/occurrence-analysis.test.ts) cover arithmetic, zero, alternatives, recursion, immutability and configured boundaries.
-Ignored measurements go to `tmp/conformance/analysis/measurements.json`; platform/broad qualification remains #208's responsibility.
-S01/#181 and S05 oracle disagreements and [S02 security qualifications](content-model-decisions.md) remain assigned downstream.
-
-```bash
-npx vitest run test/unit/occurrence-analysis.test.ts
-npx tsc -p test/unit/tsconfig.json
-npm run test:reference:full
-```

package/docs/content-model-baseline.md

@@ -1,121 +0,0 @@
-# Content Model Baseline
-
-Bounded S01 evidence for current output and independent XSD 1.0 validation. See the root [README.md](../README.md) for documentation navigation.
-
-## Purpose and boundary
-
-[Task #166](https://github.com/TechSpokes/typescript-wsdl-client/issues/166) characterizes the finite corpus agreed in [S01 #148](https://github.com/TechSpokes/typescript-wsdl-client/issues/148). It preserves the shipped #141 correction and public defaults; remaining semantic repairs belong to [epic #147](https://github.com/TechSpokes/typescript-wsdl-client/issues/147).
-
-The source baseline is main at `b633cd1561ccb2689134a7289cf48bb097b0d1f1`, with package v1.1.4, TypeScript 6.0.3 and Node 24.19.0. The runner reports the actual checked-out commit and tracked dirty state separately from this production baseline; PR and issue acceptance records pin the final tested delivery commits.
-
-## One authoritative manifest
-
-[`semantic-baseline.json`](../test/conformance/semantic-baseline.json) owns the 14 case IDs, inputs, expected reference outcomes, current generated behavior, intended semantics and gap disposition. Each case links a capability in the existing [registry](../test/conformance/registry.ts); the two new research rows record limitations rather than increasing supported-feature claims.
-
-The corpus reuses the [occurrence fixture](../test/conformance/fixtures/xsd/sequences/sequence-occurrence-wrappers.wsdl) from the public #141 example and the existing [simple-choice fixture](../test/conformance/fixtures/xsd/compositors/choice-union-simple.wsdl). The [boundary fixture](../test/conformance/fixtures/xsd/compositors/content-model-boundaries.wsdl) adds legal minimal cases, while [invalid-all](../test/conformance/fixtures/xsd/compositors/content-model-invalid-all.wsdl) preserves a historical illegal input with an explicit schema-rejection disposition.
-
-### Manifest fields
-
-| Field | Meaning |
-|---|---|
-| `id`, `family` | Stable case and bounded semantic family |
-| `capabilityId`, `fixture`, `provenance` | Existing registry link and sanitized source |
-| `findings` | Stable CM identifiers from epic #147 |
-| `schema` | Expected independent schema-compilation outcome |
-| `instances` | Committed XML inputs and expected reference outcomes |
-| `current` | Observed catalog, scoped TypeScript and OpenAPI assertions |
-| `current.defaultChoice` | Separate current default-mode assertions for choices |
-| `intended` | Desired schema meaning, not production expectations |
-| `disposition` | Remaining gap and numbered downstream owners |
-| `downstream` | Real transport, registry mock, unrun or inapplicable evidence |
-| `referenceDisagreement` | Explicit validator disagreement and resolution owner |
-| `fast` | Membership in the required deterministic subset |
-
-All fixture paths are relative to `test/conformance/fixtures/`. Current OpenAPI assertions use `flattenArrayWrappers: false` to expose the element properties; the existing occurrence transport suite separately exercises both wrapped and flattened HTTP responses.
-
-The [characterization suite](../test/conformance/semantic-baseline.test.ts) compiles the fixtures and compares current catalog/type/schema results with literal manifest expectations. Choice cases execute opt-in `union` and current default `all-optional` independently; neither mode's name serves as evidence of its behavior.
-
-## Setup and reproduction
-
-Node 24 or 26 and npm provide reference qualification through pinned test-only `libxml2-wasm@0.7.2` and libxml2 2.15.1. [NT-CONT-01](reference-validation.md) retains fresh scoped TypeScript checks and historical xmlschema observations separately; it does not claim two live general-purpose validators.
-
-Run setup once with package-index access, then validation requires only committed inputs and installed tools. No production dependency or runtime validator is introduced.
-
-```bash
-npm ci --cache tmp/cache/npm
-npm run reference:setup
-npm run test:reference
-npm run test:reference:full
-npx vitest run test/conformance/semantic-baseline.test.ts test/integration/sequence-occurrence-transport.test.ts
-npx tsc -p test/conformance/tsconfig.json
-```
-
-`reference:setup` checks the installed package version and executes a schema-construction control. Normal `npm ci` installs the prebuilt artifact; no interpreter environment or activation is needed.
-
-The engine remains a development dependency outside generated consumer artifacts. Reports stay under `tmp/conformance/reference`; ordinary pipeline resets remove only `tmp/smoke`.
-
-### Required and full lanes
-
-`npm run test:reference` runs six deterministic cases and 15 instances: original-sequence, simple-choice, sequence-order, zero-group-unbounded, finite-count-gap and invalid-all-sequence. Node 24/26 CI requires this command, the toolchain guard and scoped strict TypeScript checks.
-
-`npm run test:reference:full` executes all 14 schemas and 40 instances, including the selected contract and historical secondary answer for the disabled-element disagreement. Both selections execute all 53 mapped methods and reject missing execution; setup, input, version and observation failures exit nonzero.
-
-The launcher also exercises setup/input/schema failures, observation disagreements, offline boundaries and resource limits. Unit controls reject unsupported Node versions, empty discovery and failed test commands.
-
-The launcher writes machine-readable evidence and actual executed-method traceability automatically:
-
-```bash
-npm run test:reference:full
-```
-
-## Reference adapter responsibilities
-
-The [Node adapter](../test/conformance/reference/adapter.ts) extracts one embedded schema and materializes inherited namespace bindings before compiling it. This preserves prefixes used only in QName-valued attributes, such as `type="tns:AddressType"`; losing those bindings would manufacture schema failures.
-
-libxml2 supplies primary schema and instance results without importing production semantic helpers. Expected results are literal independent assertions in the manifest, not computations from catalog bounds.
-
-The adapter rejects DTDs, unknown external resources and path escapes, and confines inputs to the committed fixture root. Composition requires an explicit local registered resource set; broader schema loading remains with downstream owners.
-
-Schema compilation and instance validation have separate output fields. A rejected schema produces no instance results; malformed or missing inputs and missing tooling are setup/input failures rather than expected instance rejection. Successful qualification means recorded observations agree, including explicitly assigned disagreements; it does not prove the future faithful model is implemented.
-
-## Executed outcomes
-
-Full qualification covers 14 cases: 13 schema-accepted cases, one schema-rejected case and 40 primary instance checks. These span four distinct WSDL fixtures and report each case independently. The required subset covers six cases and 15 instances.
-
-The illegal nested sequence beneath `xs:all` fails schema compilation before instance evaluation. Its legal optional-all counterpart accepts the empty group and a single item, and rejects two items; production output still requires the item.
-
-### Validator disagreement
-
-For `zero-element-unbounded`, historical libxml2 2.14.6 and current 2.15.1 accept both the empty instance and the disabled `row`. Historical xmlschema 4.2.0 rejects the row; the fresh scoped rule also rejects it from its original `maxOccurs=0` source. The runner labels these distinct evidence kinds and leaves fresh full second-engine validation unqualified.
-
-The primary `accepted` expectation characterizes libxml2's limitation, not valid XSD semantics. [#181](https://github.com/TechSpokes/typescript-wsdl-client/issues/181) owns reference-oracle follow-up under CM-15, while schema analysis, matching and projection owners retain the implementation gap. Do not use primary acceptance here to approve a future codec.
-
-## Consumer evidence and limitations
-
-The [real SOAP transport test](../test/integration/sequence-occurrence-transport.test.ts) and [shared harness](../test/helpers/occurrenceTransport.mjs) verify singleton and two-item response arrays, omitted optional requests, repeated bounded/unbounded request XML and gateway JSON bytes after serialization. Both wrapper-flattening modes execute, and installed-package smoke reuses this harness.
-
-This proves the focused occurrence shape correction and singleton normalization, not complete XML-instance validation. Other boundary cases have catalog/type/OpenAPI evidence only unless their manifest explicitly links registry mock evidence; no production vendor WSDL or later buffered/streaming architecture probe is claimed.
-
-Finite lengths and the 2-or-4 count hole remain unenforced in generated arrays. Repeated `(a,b)` sequence order and group correlation are lost in independent property arrays. Disabled groups, optional all, inherited choice bounds, repeated selections and empty alternatives retain current limitations.
-
-Current default choice output requires scalar fields for the selected minimal fixtures, while opt-in union expresses a single exclusive branch. A required repeated choice needs two selections, potentially of the same branch; neither current representation captures that language.
-
-Wildcard metadata retains local bounds, but the current TypeScript/OpenAPI projection omits ordered wildcard elements and enclosing repetition. These are characterization results, not new supported-pattern claims.
-
-## Downstream ownership and S02 inputs
-
-Each manifest disposition records concrete issue numbers. Subsequent consumer qualification owns the applicable client/gateway behavior; the existing public [support matrix](supported-patterns.md) remains authoritative for released claims.
-
-| Responsibility | Owning issue |
-|---|---|
-| Bounds, choice presence and count analysis | [#178](https://github.com/TechSpokes/typescript-wsdl-client/issues/178) |
-| Schema legality and reachable support | [#179](https://github.com/TechSpokes/typescript-wsdl-client/issues/179) |
-| Ordered particle matching | [#180](https://github.com/TechSpokes/typescript-wsdl-client/issues/180) |
-| Independent oracle disagreement | [#181](https://github.com/TechSpokes/typescript-wsdl-client/issues/181) |
-| Reversible value and branch projection | [#182](https://github.com/TechSpokes/typescript-wsdl-client/issues/182) |
-| Faithful XML encoding | [#188](https://github.com/TechSpokes/typescript-wsdl-client/issues/188) |
-| HTTP representation validation | [#198](https://github.com/TechSpokes/typescript-wsdl-client/issues/198) |
-
-[S02 #149](https://github.com/TechSpokes/typescript-wsdl-client/issues/149) must decide how ordered/group-correlated data is represented, what XML equivalence means for invisible groups and empty branches, and how the declared XSD/datatype/wildcard profile is enforced. It must assign validation versus normalization and serialization boundaries, compatible artifact routing, public activation policy and bounded resource failures.
-
-These are inputs to [#168](https://github.com/TechSpokes/typescript-wsdl-client/issues/168), not an S01 architecture implementation. The SOAP and gateway feasibility probes remain blocked until a reviewed ADR draft supplies their concrete contracts.

package/docs/content-model-catalog.md

@@ -1,116 +0,0 @@
-# Semantic Catalog Format 2
-
-Internal S04 persistence and compatibility boundaries for the unreleased faithful compiler. See the root [README](../README.md).
-
-## Versions and entry points
-
-[ADR-003 D04/D09/D10](decisions/003-content-model-contracts.md) and the [decision register](content-model-decisions.md) own profile, budgets and compatibility.
-[The graph contract](content-model-graph.md) remains authoritative; a compatibility view is always derived.
-[Catalog entry points](../src/compiler/semanticCatalog.ts) are internal modules, outside the package entry point.
-
-`SemanticCatalog` contains `catalogFormat: 2`, `model: "xsd10-faithful-v1"`, `profile: "xsd10-faithful-v1"`, `graph` and `semanticFingerprint`.
-`createSemanticCatalog(graph, limits?)` creates an immutable portable snapshot.
-`serializeSemanticCatalog(catalog, limits?)` emits canonical JSON and one trailing newline.
-`readCatalog(text, {mode?, maxBytes?, maxDepth?, maxNodes?})` returns a discriminated legacy, semantic or regeneration-required result.
-`readCatalogFile(file, options)` applies the same boundary through a bounded regular-file read and strict UTF-8 decoding.
-`readLegacyCatalogFile` is the explicit adapter used by existing CLI, OpenAPI, gateway, app, generated-test and companion-catalog readers.
-
-No new faithful CLI flag, public export or emitter is activated.
-Source compilation through `prepareCompilationInput` defaults to the existing legacy loader/compiler and preserves legacy names/options.
-An explicit internal `mode: "faithful"` builds only the ordered graph/catalog through [S03 loading](content-model-loading.md), with caller-authorized policy.
-It does not certify support or produce the later portable bundle.
-
-## Canonical persistence and validation
-
-Object keys use ECMAScript UTF-16 code-unit ordering and compact JSON encoding.
-Node/global display tables sort by ID; origin tables sort by their canonical representation.
-Particle children, union members, facets, attributes, ordered syntax and WSDL reference arrays retain their declaration order.
-The reader normalizes display tables, so accepted permutations serialize identically.
-
-Global IDs are compact JSON tuples from the graph contract.
-Scoped IDs hash UTF-8 bytes of compact `JSON.stringify([owner, path, role])`, with JSON string escaping and no whitespace.
-For `owner = "parent"`, `path = "/0/1"`, `role = "type"`, the input bytes encode `["parent","/0/1","type"]` and the ID is `scoped:f325bc3d3205fbca17c95034c3a1093ed14ce66b9db6347931ad6890c026f65f`.
-The explicit identity tuple remains serialized for verification by another language.
-
-Finite bounds remain exact canonical unsigned decimal strings; `unbounded` is a distinct maximum.
-Every discriminant, required field, node identity, index, reference role/target, QName namespace context and structural ownership is checked before returning an immutable catalog.
-Scoped structural use sites have one parent; semantic references can share declarations and recurse.
-Containment/ownership cycles, malformed bounds, nested all, illegal all children, empty unions, unknown mandatory fields and duplicate JSON keys fail explicitly.
-WSDL reference indexes must agree with the ordered declaring syntax, lexical scope and source context.
-Validation of complete derivation/reference visibility, facet legality, UPA and supported capabilities remains with S05/S06.
-
-## Provenance and fingerprints
-
-Internal graph retrieval URIs never become global or scoped identity.
-Portable source locations retain digest, source path and exact start/end positions with `urn:source:sha256:<original-byte-digest>`.
-Inherited bases and loading-reference URIs use `urn:base:sha256:<digest>` tokens.
-Same-resource bases hash source digest, document-relative placement and an optional query digest; relocating the complete fixture tree does not change catalog bytes.
-Interpretation tuples retain namespace/adoption/resolution distinctions using portable source/base tokens, independently of symbol identity.
-The reader rejects raw retrieval provenance rather than silently redacting an input artifact.
-
-Retrieval attributes such as `xml:base`, schema locations and documentation source URIs become digest tokens.
-Binding endpoint addresses remain ordered semantic syntax; credential-bearing URI userinfo and recognizable secret query parameters on binding addresses are rejected.
-Credentials belong to external runtime configuration.
-No serialization can infer secrets embedded in arbitrary schema text: input annotations/lexical values must be suitable for the intended artifact audience.
-
-The SHA-256 semantic fingerprint excludes source digests/locations, retrieval bases, loading policy/edges, origin tables, documentation and annotations.
-Reference fingerprints use expanded role-qualified names, rather than prefix spelling, while the artifact preserves original lexical QName context for validation and later interpretation.
-Fingerprint-only scoped IDs follow ordered structural containment; serialized source-relative identities and WSDL syntax paths remain unchanged.
-This keeps inserted documentation and element-only formatting whitespace out of semantic identity without changing semantic child order.
-Remaining scalar/facet/default/fixed lexical values and namespace context participate conservatively; S04 does not assert datatype equivalence.
-The fingerprint detects semantic mismatch, not authenticity or provenance tampering; this is not the later bundle fingerprint combining projections/binding/capabilities/scope.
-#185/#186 own bundle format 1 and integrated compatibility checks.
-
-## Early compatibility matrix
-
-| Input / selected mode | S04 behavior |
-|---|---|
-| Legacy unversioned catalog / legacy | Explicit legacy adapter; retain existing metadata, names and options |
-| Legacy catalog / faithful | Regeneration-required, category `incompatible-artifact`, original source required |
-| Original WSDL / legacy | Existing loader/compiler; default unchanged |
-| Original WSDL/XSD / internal faithful | Controlled ordered loader, immutable graph and format 2 catalog only |
-| Format 2 catalog / internal faithful | Typed validation, exact version/model/profile and fingerprint check |
-| Format 2 catalog / legacy consumer | Reject `incompatible-artifact`; regenerate matched legacy artifacts from original source |
-| Unknown format/model/profile, versioned bundle at catalog boundary | Reject explicitly; no fallback to the flattened reader |
-| Mixed generated artifacts or faithful OpenAPI-only gateway | Deferred to #185/#186/#195/#196/#201; require the original source and portable bundle |
-
-The legacy reader checks the historical envelope and named table entries without inventing missing ordered structure or renaming metadata.
-Its compatibility boundary is not a new complete validator for every historical compiler field.
-The regeneration result supplies the internal source-compilation call, with placeholders for the original source and authorized roots.
-For example, import `prepareCompilationInput` in a repository development program and call:
-
-```typescript
-await prepareCompilationInput(
-  {kind: "source", source: originalSource},
-  {mode: "faithful", loading: {policy: {fileRoots: authorizedRoots}}},
-);
-```
-
-The shipped `wsdl-tsc compile` command still emits the legacy catalog.
-There is no supported faithful generation command during S04.
-The architecture release train remains 2.0.0, with integrated S17/S18 evidence and separately approved default activation.
-
-## Limits, evidence and downstream readiness
-
-The catalog boundary defaults to 64 MiB of UTF-8 JSON, 100,000 graph nodes and JSON nesting depth 1,024, inclusive.
-Byte/node overrides require positive safe integers; nesting can be lowered but cannot exceed the reader safety ceiling.
-Configured byte boundaries, multibyte input, node rejection, 1,024/1,025 nesting, corrupt UTF-8 and Linux FIFO rejection have executable tests.
-The full default 64 MiB catalog boundary and Windows special-file behavior are not platform-qualified by these tests.
-S03 loading limits, denial defaults and conservative cyclic-depth behavior are consumed unchanged.
-Later scalar/projection/codec budgets retain their [assigned owners](content-model-decisions.md).
-
-[Catalog tests](../test/unit/semantic-catalog.test.ts) reuse independent graph, chameleon and SOAP fixtures and cover relocation, lexical facets, large bounds, recursion, corrupt artifacts and consumer rejection.
-[Independent graph schema evidence](../test/conformance/reference/graph-contract.test.ts) retains the historical xmlschema/libxml2 large-bound distinction and explicit current qualification limits under [NT-CONT-01](reference-validation.md).
-
-```bash
-npx vitest run test/unit/semantic-catalog.test.ts test/unit/canonical-graph.test.ts
-npx tsc -p test/unit/tsconfig.json
-npm run ci
-npm run test:reference:full
-```
-
-#151's final handoff pins reviewed heads, merge revisions, versions, fixtures, exact commands/results and S05 readiness.
-#175 resolves references, #176 implements derivation/attribute composition, and #177 integrates companion closures and diagnostics.
-#178 owns later occurrence summaries.
-S02's open streaming/incoming-security qualifications and S01's #181-owned oracle disagreement remain downstream gates.
-Production codecs, projections, emitter rewrites, package publication and default activation remain outside S04.

package/docs/content-model-companions.md

@@ -1,90 +0,0 @@
-# Structural Companion Catalogs
-
-Internal S05 reuse over the [canonical graph](content-model-graph.md), [typed reader](content-model-catalog.md), [reference resolution](content-model-resolution.md) and [composition](content-model-composition.md). See the root [README](../README.md).
-
-## Reader and common semantic result
-
-`prepareResolvedCompilationInput(input, options)` is the internal faithful counterpart exposed from [`semanticCatalog.ts`](../src/compiler/semanticCatalog.ts) and [`shapeResolver.ts`](../src/compiler/shapeResolver.ts).
-It accepts original source, catalog text or a catalog file, plus companion requests containing input and explicit global `NodeId` roots.
-Source loading requires the same explicit policy as S03; file/text inputs pass through the bounded S04 reader.
-An unused companion with no roots is never read or loaded.
-
-The result contains one `SemanticCatalog`, its `ResolvedGraph`, its `ComposedGraph`, and copy/deduplication evidence.
-Resolution and composition consume the same persisted declared graph after reuse.
-The union refreshes typed symbol-target links immutably before catalog validation; missing definitions supplied in either direction become ordinary resolved references.
-No catalog-specific derived representation feeds downstream consumers.
-
-Catalog format remains 2 and model/profile remain `xsd10-faithful-v1`.
-Derived views and merge metrics are recomputed, not persisted.
-Flattened legacy input returns the existing `regeneration-required` result with `requiredInput: "original-source"`; no structural semantics are inferred from TypeScript expressions.
-Unknown versions/models/profiles and corrupt catalogs retain existing reader diagnostics.
-
-Public `applyShapeCatalogs` and the CLI continue to use the legacy default adapter.
-The new internal entry does not activate faithful generation, projections, codecs or streaming transport.
-
-## Required closure and provenance
-
-`mergeStructuralCompanions(primary, companions, limits)` walks typed containment and reference slots from each requested global root.
-The visited set terminates self/mutual element-type recursion while retaining complete definitions.
-Groups, attribute groups, derivation bases, anonymous types and scalar/list/union references participate in the same closure.
-An unavailable imported definition may be supplied by the primary graph; the common resolver still verifies every use's original import visibility.
-Requested companion pools are indexed before traversal; required dependencies can be supplied by another pool regardless of request order.
-Unrelated operation/type nodes and their node-local unsupported constraints are not copied.
-
-Namespace, local name and symbol role define global identity.
-Loading interpretations never create extra global identities, and scoped declarations remain owned by their original containing components.
-No public symbol is renamed to make a collision disappear.
-
-Equal scoped definitions at normalized containment positions retain the primary declaration IDs and merge all corresponding origins.
-New definitions retain their original scoped IDs.
-Required schema-level retained syntax, annotations and import/include provenance accompany selected interpretations; source paths and digests remain available for diagnostics and assessment.
-The merged graph retains the primary loading-limit record; each companion was independently read/loaded under its own input limits, and reuse applies a separate semantic work budget.
-
-## Actual structural equality
-
-Equality compares normalized structural data from each global declaration and its owned local closure, using the shared [`semanticGraphRepresentation`](../src/compiler/catalogProvenance.ts).
-The full normalized structures must match; a matching fingerprint alone never establishes equality.
-Every reachable global dependency is independently copied or compared, including recursive dependencies.
-
-The comparison includes expanded namespace/role identity, ordered particles and compositors, exact occurrences, typed references, derivation kind/base/local content, scalar variety/facets, attribute use/value constraints, wildcard namespace/processing and retained unassessed syntax.
-It excludes retrieval locations, source digests, documentation and optional stored symbol-target hints.
-Scope positions normalize documentation-induced source-path shifts; lexical value contexts remain intact.
-
-This is conservative declared-structure equality, not a scalar value-equivalence or particle-language proof.
-Different lexical constraints or namespace contexts can require source reconciliation even when later assessment might prove them equivalent.
-It does not flatten inline content and group references into a claimed equivalence.
-The existing format-2 fingerprint algorithm remains unchanged; companion comparison separately ignores stored target-hint availability.
-
-Meaningful collisions throw `SemanticError` with category `invalid-schema`, the global component, the companion source and the existing source in `related`.
-The message asks for reconciliation of original declarations.
-Required missing references, forbidden cycles and import visibility failures flow through the common resolver.
-Unsupported retained constraints remain visible for #179; successful reuse does not certify their legality or capability.
-
-## Resource and support evidence
-
-Closure indexing/traversal, structural normalization and provenance copying consume bounded work.
-Normalization input and copied strings are counted before serialization; copied graph size is checked while adding definitions.
-Dynamic object keys, including namespace prefixes, count as copied strings.
-Defaults remain 100,000 nodes and 1,000,000 steps, with positive safe-integer overrides.
-Exhaustion returns `resource-limit` without modifying any input or returning a partial result.
-Input gathering bounds aggregate retained nodes and structural data before retaining each additional read, including redundant definitions.
-Gathering, merge, resolution and composition each apply that configured budget independently.
-S03's conservative cyclic-depth loading behavior remains unchanged.
-
-[Integration tests](../test/integration/structural-companions.test.ts) cover reader/source/file dispatch, recursive required closures, differing bounds, namespace/role collisions, chameleon and anonymous owners, source-path deduplication, missing references/cycles, structural collisions, legacy regeneration and catalog round trips.
-The [public characterization fixture](../test/conformance/fixtures/xsd/composition/derivation-boundaries.wsdl) is qualified for schema/payload behavior by both pinned reference engines.
-Its executable [registry row](../test/conformance/registry.ts) records legacy group omission, appended restriction content, ineffective prohibitions and named recursive references.
-[Supported patterns](supported-patterns.md) distinguishes this public characterization from internal faithful evidence.
-
-```bash
-npx tsc -p test/unit/tsconfig.json
-npx tsc -p test/integration/tsconfig.json
-npx tsc -p test/conformance/tsconfig.json
-npx vitest run test/integration/structural-companions.test.ts
-npm run test:conformance
-npm run test:reference:full
-npm run ci
-```
-
-#178 owns occurrence summaries/emptiness, #179 owns complete legality and reachable capability assessment, and #184 owns payload scalar enforcement.
-The documented oracle disagreements and S02 platform/security qualifications still apply.

package/docs/content-model-composition.md

@@ -1,103 +0,0 @@
-# Canonical Derivation Composition
-
-Internal S05 derivation views over immutable declarations. See the root [README](../README.md).
-
-## Input, result and assessment gate
-
-[`composeCanonicalGraph`](../src/compiler/composeCanonicalGraph.ts) consumes the reviewed [resolved-reference contract](content-model-resolution.md).
-It returns `ComposedGraph {resolved, types, metrics}` without changing the [canonical graph](content-model-graph.md).
-Each `ComposedType` retains its declaration ID, original derivation edge, effective content contributions, attributes, wildcard, scalar layers and explicit legality obligations.
-
-All results carry `assessment: "requires-schema-assessment"`.
-This boundary computes composition; it never certifies complete XSD legality, capability support or payload validity.
-No emitter accepts these internal views; #179 must discharge obligations before downstream planning under [ADR-003 D04](decisions/003-content-model-contracts.md#xsd-10-profile-and-enforcement-s02-d04).
-
-Content contributions reference declared particle IDs, preserving order and local bounds rather than flattening children.
-Builtin `anyType` remains an explicit opaque contribution with its original builtin reference.
-Attribute/wildcard source IDs and scalar owner layers trace every contribution to the declared graph.
-
-## Distinct derivation operations
-
-`extendContent(base, local)` concatenates the base root contributions followed by the local root particle.
-`restrictContent(local)` returns only the local root, or empty content when no particle is declared.
-Neither operation expands group definitions, calculates occurrences or mutates base and sibling types.
-
-```text
-Base:       optional a, optional b
-Extension:  Base roots, local extra
-Restriction: local optional a
-Empty restriction: no child particles
-```
-
-Complex-content derivation requires a complex base; simple-content extension requires a scalar-bearing base.
-Simple-content restriction retains facets and optional inline scalar types as ordered owner layers.
-Its mixed-base check uses the composed base, including effective mixed content inherited through an empty `anyType` extension.
-Named scalar restriction/list/union definitions and lexical contexts remain original graph data for #179/#184.
-
-Extension with no local content inherits the base's effective mixed content.
-An empty extension of `anyType` preserves opaque child content and its `##any` lax attribute wildcard.
-Restriction of `anyType` replaces child content and permits declared attributes through that base wildcard, while an omitted derived wildcard is removed.
-
-## Attribute-use composition
-
-Attribute groups are traversed separately from child model groups.
-Omitted restriction uses inherit base required/optional uses and their constraints.
-A declared prohibition removes an explicit optional use; weakening or prohibiting a required base attribute fails with `invalid-schema`.
-This applies to a direct type restriction; a prohibited use inside an attribute group contributes no attribute use and leaves inherited uses intact.
-
-Prohibitions remain traceable tombstones in the view rather than becoming wildcard QName exclusions.
-A matching retained wildcard can still admit that QName; prohibition removes an explicit use only.
-Extension prohibition contributes no new use and never removes a base use; conflicting inherited cases retain a legality obligation.
-
-Local redeclarations retain their actual declared types and default/fixed values.
-No missing local type is inferred from the base, and scalar values are never compared through Number or plain lexical equality.
-New restricted attributes require a matching base wildcard; type narrowing and applicable fixed-value equivalence retain both reference/value contexts for their enforcement owners.
-
-## Wildcard composition
-
-Each wildcard namespace is interpreted using its original effective namespace.
-`##other` excludes that namespace and the absent namespace; imported groups can therefore have different constraints despite identical lexical spelling.
-Finite sets and complements support exact union, intersection and subset checks without replacing lexical declarations.
-
-Group wildcards intersect namespace sets and preserve the first group wildcard's processing mode.
-Extension unions base and local namespace sets using the local processing mode, or inherits the base wildcard when no local wildcard exists.
-Restriction removes an omitted wildcard; an explicit wildcard must be a namespace subset with equal or stronger processing (`skip < lax < strict`).
-
-An intersection or union need not be expressible as one legal XSD 1.0 wildcard.
-The view retains the mathematical result and source operands; `wildcard-expressibility` remains an explicit #179 gate.
-Impossible restriction subsets and weakened processing fail here rather than being silently accepted.
-
-## Independent disagreements and remaining obligations
-
-Pinned xmlschema 4.2.0 and lxml 6.1.0/libxml2 2.14.6 disagree on duplicate extension uses and some extension prohibitions.
-They also disagree on fixed-value restrictions, group-plus-local wildcard processing and imported `##other` combinations.
-These cases are not added to verified support from either engine alone.
-
-Conflicting group/local processing returns `assessment-required` alternatives and original wildcard sources, with no invented selected mode.
-Each nested attribute group preserves its own processing obligation through callers.
-Fixed-value obligations retain both lexical values and type context, including value-equivalent integer spellings such as `1` and `+01`.
-Particle language inclusion, extension/mixed legality, attribute-type derivation, wildcard expressibility and scalar derivation remain explicit #179 obligations; #184 owns payload scalar enforcement.
-
-This division follows the existing S06 legality ownership rather than narrowing the approved profile.
-The [decision register](content-model-decisions.md) assigns these concrete evidence qualifications to #179; they block affected assessed plans.
-The S01/#181 disagreement and S02 transport/security qualifications remain unchanged.
-
-## Resources and evidence
-
-Composition defaults to 100,000 graph nodes and 1,000,000 work steps with positive safe-integer overrides.
-Iterative derivation order and bounded attribute-group expansion terminate independently of legal element/type recursion.
-Inherited content, attribute, wildcard and obligation copying consumes work; exhaustion returns `resource-limit` without a partial view.
-Provenance source-array copying is counted before allocation, including repeated references and derived merges.
-
-[Unit tests](../test/unit/composed-graph.test.ts) exercise contrasting extension/restriction, empty content, immutable siblings, attributes, wildcard operations, scalar/list/union contexts, opaque bases, catalog round trips and exact configured budgets.
-[Independent fixtures](../test/conformance/fixtures/xsd/composition/derivations.xsd) and [Node qualification](../test/conformance/reference/composition-contract.test.ts) assert current schema observations, scoped ordered payload contracts and separately recorded historical disagreements under [NT-CONT-01](reference-validation.md).
-
-```bash
-npx vitest run test/unit/composed-graph.test.ts test/unit/resolved-graph.test.ts
-npx tsc -p test/unit/tsconfig.json
-npm run test:reference:full
-npm run ci
-```
-
-These are internal faithful results; legacy default generation remains active.
-No occurrence summaries, complete legality checker, scalar payload engine, projection, codec or emitter rewrite belongs to S05.