Contact channel
What to include
- The page URL or case ID involved.
- A concise description of what appears incorrect or inaccessible.
- The browser, operating system, viewport, and steps needed to reproduce a technical problem.
- Links to primary technical sources when proposing a factual correction.
Do not send sensitive access
Do not send passwords, session cookies, API keys, remote desktop credentials, private source repositories, or personal account exports. A report should contain only the minimum information needed to understand the issue.
How messages are handled
Relevant reports are reviewed against the project fixtures, evidence, source links, and current browser behavior. A correction may require a new reproducible fixture and evidence run before the published conclusion changes. See the corrections process for the recorded workflow.