Changes to tools and references.

2026-07-21 · Production routing and legacy recovery

• Added a generated recovery manifest for every URL in the supplied backlink export.
• Made legacy redirects available in Astro development, Apache-compatible hosting and an explicit WPauto Nginx server-block include.
• Changed routes ending in .html or .htm into real files during the production build. This prevents a static server from appending a slash to a filename and avoids redirect loops or an HTTP scheme downgrade behind a TLS proxy.
• Added an exact-route audit that follows every request to one useful final response and rejects loops, multiple-hop chains, missing targets and recovered assets with the wrong content type.

The legacy manifest combines externally linked paths with maintained subject routes. Recoverable source files remain at their exact URL. When the original resource is unavailable, the path receives one permanent redirect to the closest complete reference rather than a generic homepage. Malformed strings that cannot represent safe HTTP requests stay documented in the manifest but are excluded from live redirect rules.

2026-07-21 · Reference and structured-content expansion

• Published DFDL, formal-language, functional-programming, Microformats, OWL, RDF, RDF Schema and expanded Schematron references.
• Deepened existing classic tutorials with implementation notes, failure modes, verification steps and review checklists.
• Added accessible technical diagrams and expanded the homepage, examples, standards map and editorial documentation.
• Added at least four page-specific questions to each maintained page and represented every FAQ as an accessible disclosure control with matching FAQPage structured data.

The new reference pages separate standards conformance, implementation behavior and local design advice. Dynamic legacy references now inherit the same evidence-oriented FAQ baseline as hand-authored guides, while pages with subject-specific question sets retain their more detailed answers. The first answer is visible by default; every answer remains available without JavaScript and can be opened with the keyboard.

2026-07-21 · Tool documentation and review boundaries

Expanded all four workbench guides so the explanation stands on its own without relying on FAQ text. The XML Formatter now distinguishes serialization from information-set preservation. The XSD Pattern Analyzer explains how to read mixed-pattern results. Schema Diff documents a review packet for consumer-aware compatibility, and OpenAPI-to-MCP Readiness adds a staged semantic and safety review.

No workbench was promoted to a conformance validator. Each page identifies the accepted serialization, deterministic checks, unsupported features and the next authoritative test. Browser-local processing remains the default for the published tools; the privacy statement continues to exclude browser extensions, local device logging and other software outside the page.

2026-07-21 · Verification notes

The release gate builds the complete static site, checks internal links, canonical metadata, headings, descriptions, structured data and body depth, then probes the backlink recovery set over HTTP. Browser tests exercise the primary success and failure path of each interactive workbench at desktop and mobile widths. The deployment archive is created only from the verified build and includes the generated Apache and Nginx handoff artifacts required by static hosts.

A production check remains necessary after WPauto applies the package because edge configuration is outside Astro’s static output. That check must request both canonical routes and representative deep assets over HTTPS, confirm that relative redirect locations preserve the public scheme, and verify that the server uses the supplied exact-match rules before its generic static-file location.

2026-07-20 · Initial workbench release

• Published the XML Formatter with well-formedness diagnostics.
• Published the XSD Pattern Analyzer for global and local declaration structure.
• Published Schema Diff for basic JSON Schema and XSD changes.
• Published the OpenAPI-to-MCP readiness audit for JSON-formatted descriptions.
• Added updated XML Schema, REST and Schematron reference routes.

How to interpret this log

Dates identify when a change entered the maintained build, not when an older xFront topic was first published. A release note describes observable behavior and the evidence needed to verify it. Small spelling, spacing and non-semantic presentation fixes may ship without individual entries; corrections that change a technical conclusion, route, input boundary or tool result are recorded explicitly.