ci(alloy): gate full scopes and document mapping

Author: lmeyerov

.github/workflows/ci.yml

@@ -126,9 +126,18 @@ jobs:
       run: |
         docker pull ghcr.io/graphistry/alloy6:6.2.0 || true
 
-    - name: Run Alloy checks (full scopes)
+    - name: Run Alloy checks (scoped on PR/push, full on schedule/dispatch)
+      env:
+        EVENT_NAME: ${{ github.event_name }}
       run: |
-        ALLOY_PUSH=1 FULL=1 bash alloy/check_fbf_where.sh
+        if [[ "$EVENT_NAME" == "schedule" || "$EVENT_NAME" == "workflow_dispatch" ]]; then
+          FULL=1
+          MULTI=1
+        else
+          FULL=0
+          MULTI=0
+        fi
+        ALLOY_PUSH=1 FULL=$FULL MULTI=$MULTI bash alloy/check_fbf_where.sh
 
   test-minimal-python:
     needs: [changes, python-lint-types]

alloy/gfql_fbf_where.als

@@ -6,6 +6,12 @@ open util/integer
 // Path semantics: bindings are sequences aligned to seqSteps with WHERE applied per binding.
 // Set semantics: forward/backward/forward collects per-alias node/edge sets, then checks WHERE via summaries.
 // Scopes (checks): up to 8 Nodes, 8 Edges, 4 Steps, 4 Values. Nulls/hashing omitted; bounded values only.
+// Mapping to Python hop/chain:
+// - seqSteps alternates NodeStep/EdgeStep like graphistry.compute.GSQL chain builder.
+// - aliasN/aliasE mirror user aliases; WHERE binds to NodeStep aliases only.
+// - nFilter/eFilter correspond to per-step filter columns; WHERE models cross-step predicates.
+// - Spec uses path bindings (sequence) like hop composition; Algo uses set semantics like executor.
+// - Null/NaN not modeled; hashing treated as prefilter and omitted here.
 
 abstract sig Value {}
 sig Val extends Value {}