docs(gfql): clarify cypher translation intent

Author: lmeyerov

docs/source/gfql/hop_bounds.ipynb

@@ -7,7 +7,7 @@
    "source": [
     "# Hop ranges, slices, and labels\n",
     "\n",
-    "GFQL examples for bounded hops, output slices, and labeling (Cypher-style patterns like `(a)-[*2..4]->(b)`).\n",
+    "GFQL examples for bounded hops, output slices, and labeling, including the same traversal intent often written in Cypher as `(a)-[*2..4]->(b)` after translation into native GFQL.\n",
     "\n",
     "- Exact and ranged hops (`min_hops`/`max_hops`)\n",
     "- Post-filtered output slices (`output_min_hops`/`output_max_hops`)\n",
@@ -558,7 +558,7 @@
    "id": "3468c224",
    "metadata": {},
    "source": [
-    "Range 1..3 hops from 'a' (unlabeled) to mirror a Cypher pattern like `(a)-[*1..3]->(?)`.\n"
+    "Range 1..3 hops from 'a' (unlabeled), expressing the same traversal intent as a Cypher pattern like `(a)-[*1..3]->(?)` after translation into native GFQL.\n"
    ]
   },
   {

docs/source/gfql/spec/cypher_mapping.md

@@ -256,8 +256,8 @@ Rows using `[*...]` below show the native GFQL rewrite for the same traversal
 intent. They are semantic mappings, not a claim that direct
 `g.gfql("MATCH ...")` currently accepts those `[*...]` string forms.
 
-| Cypher | Python | Wire Protocol (compact) |
-|--------|--------|-------------------------|
+| Cypher / intent | Python | Wire Protocol (compact) |
+|-----------------|--------|-------------------------|
 | `-[]->` | `e_forward()` | `{"type": "Edge", "direction": "forward"}` |
 | `-[r:KNOWS]->` | `e_forward({"type": "KNOWS"}, name="r")` | `{"type": "Edge", "direction": "forward", "edge_match": {"type": "KNOWS"}, "name": "r"}` |
 | `<-[r]-` | `e_reverse(name="r")` | `{"type": "Edge", "direction": "reverse", "name": "r"}` |

docs/source/gfql/translate.rst

@@ -12,6 +12,12 @@ GFQL (GraphFrame Query Language) is designed to be intuitive for users familiar
 
 GFQL operates on graph DataFrames - graphs represented as node and edge DataFrames. This DataFrame-native approach enables seamless integration with the PyData ecosystem and natural vectorization for both CPU and GPU processing.
 
+This page is translation-first rather than a support matrix for direct
+``g.gfql("MATCH ...")`` string execution. Some Cypher snippets below express
+the same graph-query intent as native GFQL but are not yet accepted verbatim by
+the current direct Cypher surface. For the currently supported direct string
+forms, see :doc:`/gfql/cypher`.
+
 Who Is This Guide For?
 ----------------------