[email protected]
Include the page URL, release identifier, filename, and the change or question. For sensitive security reports, use [email protected] instead.
Questions are routed by subject so catalog corrections, documentation requests, and security reports reach the right review path with enough context.
Include the page URL, release identifier, filename, and the change or question. For sensitive security reports, use [email protected] instead.
We can clarify the published schema, catalog records, release notes, cache guidance, and Aether Static endpoints. We cannot debug private infrastructure, accept credentials, or operate another team's release pipeline.