Problem
The WordPress.org package audit for #2424 found Extra Chill-specific domains, usernames, agent names, and transport examples in generic Data Machine runtime source. The generic-layer policy explicitly treats vendor/site names in field docs and examples as layering violations.
Examples include:
inc/Core/Auth/AgentAuthorize.php describing the generic multisite host check as *.extrachill.cominc/Core/Auth/AgentAuthCallback.php examples using extrachill.com/saraiinc/Cli/Commands/ExternalCommand.php, MemoryCommand.php, and AgentsCommand.php examples using Extra Chill identities/domainsinc/Abilities/AgentRemoteCall/AgentRemoteCallAbility.php and inc/Core/Auth/RemoteAgentClient.php examples using chubes.net
Author/package ownership metadata such as the plugin Author URI and Composer package name is not in scope.
Acceptance
- Replace site-specific runtime examples with RFC-safe generic examples such as
example.com, remote.example, and content-agent.
- Keep actual runtime behavior generic and unchanged.
- Add a packaged-source grep gate so private-site examples do not return.
Refs #2424.
Problem
The WordPress.org package audit for #2424 found Extra Chill-specific domains, usernames, agent names, and transport examples in generic Data Machine runtime source. The generic-layer policy explicitly treats vendor/site names in field docs and examples as layering violations.
Examples include:
inc/Core/Auth/AgentAuthorize.phpdescribing the generic multisite host check as*.extrachill.cominc/Core/Auth/AgentAuthCallback.phpexamples usingextrachill.com/saraiinc/Cli/Commands/ExternalCommand.php,MemoryCommand.php, andAgentsCommand.phpexamples using Extra Chill identities/domainsinc/Abilities/AgentRemoteCall/AgentRemoteCallAbility.phpandinc/Core/Auth/RemoteAgentClient.phpexamples usingchubes.netAuthor/package ownership metadata such as the plugin Author URI and Composer package name is not in scope.
Acceptance
example.com,remote.example, andcontent-agent.Refs #2424.