UAIX Endpoint and Package Surface Update

UAIX has made the current machine-facing route family and packaged WordPress artifact surface more explicit across the public record so adopters can see what exists now without inferring unpublished SDKs or services.

What changed#

• About and References and Contributors now name the current published attribution, the public artifact family, and the concrete route family more directly.
• Tools and Validator now point readers to the machine-facing catalog, discovery, status, modules, schema, registry, example, and validate routes as part of the current tooling surface.
• Implementations, WordPress Publication Track, and .NET Bridge Track now describe the current package family more concretely and state more directly what is not yet published.

How to use this update#

1. Use References and Contributors when you need the shortest public list of current machine routes and packaged artifacts.
2. Use Tools and Validator when you need the automation-facing REST surface, including /wp-json/uaix/v1/catalog, /wp-json/uaix/v1/discovery, /wp-json/uaix/v1/status, /wp-json/uaix/v1/modules, /wp-json/uaix/v1/schemas, /wp-json/uaix/v1/registry, /wp-json/uaix/v1/examples, and /wp-json/uaix/v1/validate.
3. Use Implementations, WordPress Publication Track, and .NET Bridge Track when you need the current package family and support-boundary explanation around uaix-authority-theme-v2.8.0.zip, uaix-theme-v2.8.0.zip, uaix-core-v2.8.0.zip, uaix-modules-v2.8.0.zip, uaix-bridge-v2.8.0.zip, uaix-locale-router-v3.0.0.zip, and uaix-seo-sweep-v2.8.0.zip.
4. Keep the Changelog, News, and References and Contributors attached when those surfaces support a public release or support claim.

Why this matters#

UAIX becomes easier to trust when running code and published record surfaces are named concretely. This update improves that credibility without inventing a standalone package registry, public SDK catalog, or runtime support surface that the site has not yet published.