update comments

Author: shmax

src/Validator/ValidationCache.php

@@ -10,8 +10,8 @@
 /**
  * Implement this interface and pass an instance to GraphQL::executeQuery to enable caching of successful query validations.
  *
- * This can improve performance by skipping validation for known-good query and schema combinations.
- * You are responsible for defining how cache keys are computed, and when validation should be skipped.
+ * This can improve performance by skipping validation for known-good query, schema, and rules combinations.
+ * You are responsible for defining how cache keys are computed.
  *
  * @see PsrValidationCacheAdapter for a toy implementation.
  */
@@ -35,7 +35,7 @@ public function isValidated(Schema $schema, DocumentNode $ast, array $rules = nu
     /**
      * @param array<ValidationRule>|null $rules
      *
-     * Mark the given schema + AST pair as successfully validated.
+     * Mark the given schema/AST/rules set as successfully validated.
      *
      * This is typically called after a query passes validation.
      * You should store enough information to recognize this combination on future requests.

tests/PsrValidationCacheAdapter.php

@@ -70,7 +70,7 @@ public function markValidated(Schema $schema, DocumentNode $ast, array $rules =
     private function buildKey(Schema $schema, DocumentNode $ast, array $rules = null): string
     {
         /**
-         * This default strategy generates a cache key by hashing the printed schema and AST.
+         * This default strategy generates a cache key by hashing the printed schema, AST, and any custom rules.
          * You'll likely want to replace this with a more stable or efficient method for fingerprinting the schema.
          * For example, you may use a build-time hash, schema version number, or an environment-based identifier.
          */