validate the gamepad and robot dataflows in CI

Both pull sibling nodes by `git:`, but dora resolves the wiring without
fetching them, so this stays offline. It is what catches a drift between the
robot dataflow's output_types block and the tag it pins.

Also ignore `git/`, where dora build leaves those clones.

.gitea/workflows/validate.yml

@@ -35,6 +35,18 @@ jobs:
       - name: Validate the dataflow
         run: dora validate dataflow.yml
 
+      # The gamepad dataflow pulls dora-joy by `git:`, but validation resolves
+      # the wiring without fetching it, so this stays offline and still catches
+      # a mistyped port.
+      - name: Validate the gamepad dataflow
+        run: dora validate dataflow-gamepad.yml
+
+      # Same again for the real-arm stack. Its `output_types:` block is what
+      # lets this pass without an arm or a clone of the arm node, so a drift
+      # between it and the tag it pins fails here.
+      - name: Validate the robot dataflow
+        run: dora validate dataflow-robot.yml
+
   test:
     runs-on: ubuntu-latest
     steps:

.gitignore

@@ -12,3 +12,6 @@ build/
 .ruff_cache/
 out/
 .dora/
+# Where `dora build` clones a `git:` node source, which
+# dataflow-robot.yml and dataflow-gamepad.yml both have.
+git/