- Artifact Contract
1.1 Repository output must remain a WordPress object-cache drop-in delivered as
object-cache.php. a. Publicwp_cache_*function signatures and return-value contracts must remain backward compatible unless a deliberate breaking change is requested. - Integration Boundary
2.1 The drop-in must stay directly loadable by WordPress from
wp-content/object-cache.php. a. Changes that require additional bootstrap files or dependency loaders are out of scope unless explicitly requested. - Runtime Behavior 3.1 Cache behavior must support APCu-backed persistence when APCu is available. 3.2 When APCu is unavailable, behavior must continue to function through non-persistent in-memory caching semantics.
- Multisite and Group Isolation 4.1 Changes to cache key construction or namespace invalidation must preserve site and group isolation semantics for single-site and multisite installs.
- Admin Security Surface 5.1 The cache stats admin screen must remain capability-gated and output-escaped.
- PHP Coding Standards Gate
1.1 For PHP changes, run the following commands against modified files before finalizing work:
a.
phpcbf --standard=WordPress-Extra object-cache.phpb.phpcs --standard=WordPress-Extra object-cache.php1.2 Final validation requires a zero-violationphpcsresult. - Ignore-Rule Exception Policy
2.1 Introducing or expanding
phpcs:ignoreorphpcs:disableusage is allowed only when it does not weaken security-relevant behavior. 2.2 Each new ignore directive must include a specific inline justification comment.