Feature/muse

[VinceIngram07]

1.40 update

[Copilot]

Pull request overview

Updates the app to v1.4.0 with VEX AIM integration (Python WebSocket server + Electron IPC), new VEX/EMG Blockly capabilities, and a new blocks↔text viewing/editing experience.

Changes:

• Add Python VEX server (prod + dev mock), Electron main-process lifecycle management, IPC bridges, and UI reconnect/status controls.
• Add new Blockly blocks/categories (VEX movement/kicker, EMG muscle energy) plus wrapper/interpreter support.
• Add text-mode tooling (Monaco-based editor, simple text view, block-to-text converter demos) and refresh docs/build configuration.

Reviewed changes

Copilot reviewed 38 out of 51 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
test_vex_server.py	Adds a manual Python WebSocket test script for the VEX server.
test-reconnect.js	Adds a Node-based WebSocket reconnect smoke test.
test-converter.html	Adds a browser test harness for the block-to-text converter.
src/renderer/js/wrapper-functions.js	Adds safer band-power getters and VEX wrapper functions (incl. kicker).
src/renderer/js/text-editor.js	Adds Monaco-based text editor component loaded from CDN.
src/renderer/js/simple-text-view.js	Adds a basic blocks→text display mode with export/toast messages.
src/renderer/js/muse-client.js	Changes BLE requestDevice options for Muse service access.
src/renderer/js/main.js	Initializes global band powers and adds a command helper + sanitize logic.
src/renderer/js/interpreter-api.js	Exposes new VEX and EMG functions to the Blockly interpreter.
src/renderer/js/feature-extractor.js	Hardens relative band power calculation against divide-by-zero.
src/renderer/js/events.js	Adds exportCode and VEX reconnect UI events.
src/renderer/js/customblock.js	Adds VEX/muscle blocks and changes some drone block labels/colors (but introduces syntax/runtime issues).
src/renderer/js/console.js	Adds a custom console UI inside the “bands” panel.
src/renderer/js/coding-mode-manager.js	Adds a Blockly↔text mode manager using Monaco + JS generator.
src/renderer/js/categories.js	Adds VEX category and adds muscle_energy to Data category.
src/renderer/js/blockly-main.js	Registers new toolbox categories/modules (incl. VEX + muscle_energy).
src/renderer/js/block-to-text-converter.js	Adds a converter from Blockly AST to Python-like text.
src/renderer/index.html	Updates UI layout and adds mode toggle, export, VEX status/reconnect controls.
src/main/tello.js	Switches Tello initialization to lazy creation.
src/main/preload.js	Adds VEX IPC API and exposes sendCommand to renderer.
src/main/index.js	Adds Python server lifecycle + WebSocket bridge, VEX IPC handlers, packaging path updates, status polling, cleanup hooks.
src/main/index copy.js	Minor formatting tweak.
setup-venv.sh	Adds a helper script to create/activate a Python venv and install deps.
resources/python/vex/vex_types.py	Adds VEX AIM types/enums (but contains a critical constant bug).
resources/python/vex/vex_messages.py	Adds VEX AIM WebSocket message builders.
resources/python/vex/vex_globals.py	Adds VEX-style global constants.
resources/python/vex/settings.py	Adds JSON settings loader for VEX host config.
resources/python/vex/settings.json	Adds default VEX host configuration.
resources/python/vex/init.py	Exposes the VEX package API.
resources/python/VexTest.py	Adds a Python VEX WebSocket test script.
resources/python/VEXServer_dev.py	Adds a mock VEX server for development without hardware.
resources/python/VEXServer.py	Adds the production VEX WebSocket server with reconnect/status/kicker actions.
requirements.txt	Adds Python dependencies for VEX server and packaging.
programs/maze_program_emg.xml	Adds a sample Blockly program using muscle_energy and VEX actions.
package.json	Bumps to 1.4.0; changes dev server port; adds ws/wait-on; adds Python build step and packaging resources.
block-text-demo.html	Adds a standalone block-to-text demo page.
VEXServer.spec	Adds PyInstaller spec to bundle the Python server + VEX package.
README.md	Expands documentation for usage, adding blocks, and production builds.
Neuroscope.bat	Adds a Windows helper to run yarn serve with a venv.
.gitignore	Adds ignores for build artifacts, venv, and pycache.

Comments suppressed due to low confidence (8)

src/renderer/js/customblock.js:1

• This line is syntactically invalid JavaScript and will prevent the renderer bundle from loading. Restore a valid initialization (e.g., let drone_blocks_color = 70;) and remove the stray text.
  src/renderer/js/customblock.js:1
• The generated code calls electronAPI.sendCommand(...), but electronAPI is not a global in the js-interpreter runtime (and in the renderer it’s typically window.electronAPI). These blocks will fail at execution time. Generate code that calls an interpreter-exposed function (e.g., a wrapper like sendCommand(...) / a dedicated wrapper function) rather than referencing electronAPI directly.
  src/renderer/js/customblock.js:1
• The generated code calls electronAPI.sendCommand(...), but electronAPI is not a global in the js-interpreter runtime (and in the renderer it’s typically window.electronAPI). These blocks will fail at execution time. Generate code that calls an interpreter-exposed function (e.g., a wrapper like sendCommand(...) / a dedicated wrapper function) rather than referencing electronAPI directly.
  src/renderer/js/coding-mode-manager.js:1
• Blockly is used but not imported in this module, which will throw a ReferenceError when switching modes. Add an explicit import (e.g., import * as Blockly from \"blockly/core\";) or route resizing through an existing component that already imports Blockly.
  src/renderer/js/muse-client.js:1
• The navigator.bluetooth.requestDevice(...) options object now lacks filters and acceptAllDevices, which are required by the Web Bluetooth API. Using only optionalServices will cause requestDevice to reject. Keep a filters entry (e.g., by service UUID and/or namePrefix) and use optionalServices only to request additional services.
  src/renderer/index.html:1
• Both exportCode and bluetooth buttons are positioned at the exact same coordinates (top: 260px; right: 5px) with the same z-index, so one will overlap the other and become unclickable. Adjust positioning (different top values) or group the buttons into a vertical stack container.
  src/renderer/js/block-to-text-converter.js:1
• The converter is reading input names that don’t match the blocks defined in customblock.js (e.g., the print block uses name: \"val\", and drone movement blocks use name: \"value\"). This will cause generated text to fall back to defaults instead of reflecting the workspace. Update the converter to use the actual field/input names used by your blocks (or centralize block field-name constants shared by both definitions and converter).
  src/renderer/js/text-editor.js:1
• Loading Monaco from a remote CDN inside an Electron renderer increases supply-chain risk and typically conflicts with Electron hardening guidance (CSP, remote content, offline use). Prefer bundling Monaco with the app build or pin+verify integrity (SRI) with a restrictive CSP; at minimum, document why remote loading is acceptable for this app.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

vex is not defined in this module (you import from vex import *, which does not create a vex namespace). This will raise NameError on turn actions. Use TurnType.LEFT/RIGHT (or the imported global LEFT/RIGHT) instead of vex.TurnType.*.

Suggested change

	robot.turn_for(vex.TurnType.LEFT, degrees) # Correct VEX method
	# Send a response back to the client
	await websocket.send(json.dumps({"status": "success", "action": "turn_left", "degrees": degrees}))
	elif action == "turn_right":
	degrees = command.get("degrees", 90)
	print(f"Turning robot right: {degrees} degrees")
	robot.turn_for(vex.TurnType.RIGHT, degrees) # Correct VEX method
	robot.turn_for(TurnType.LEFT, degrees) # Use imported TurnType enum
	# Send a response back to the client
	await websocket.send(json.dumps({"status": "success", "action": "turn_left", "degrees": degrees}))
	elif action == "turn_right":
	degrees = command.get("degrees", 90)
	print(f"Turning robot right: {degrees} degrees")
	robot.turn_for(TurnType.RIGHT, degrees) # Use imported TurnType enum

[Copilot]

RIGHT is incorrectly assigned to TurnType.LEFT, which will invert/merge semantics for any consumer importing this global. Change it to RIGHT = TurnType.RIGHT.

Suggested change

	RIGHT = TurnType.LEFT
	RIGHT = TurnType.RIGHT

[Copilot]

The Electron main process sends { action: \"turn_left\", degrees: ... } / {...degrees...} but the dev server reads angle. This means turns will always default to 90° in dev mode. Accept degrees as well (e.g., data.get(\"degrees\") fallback to angle).

Suggested change

	angle = data.get("angle", 90)
	response = self.robot.turn_left(angle)
	elif action == "turn_right":
	angle = data.get("angle", 90)
	angle = data.get("degrees", data.get("angle", 90))
	response = self.robot.turn_left(angle)
	elif action == "turn_right":
	angle = data.get("degrees", data.get("angle", 90))

[Copilot]

You compute a clamped numeric value (rightVal) but send distance: response (the unclamped original, potentially a non-numeric string). Send the clamped number instead to ensure speed/limits are actually enforced (same pattern appears in other movement handlers).

[Copilot]

This activation path is Windows-specific. For bash on macOS/Linux, the virtualenv activation script is typically venv/bin/activate. If this script is intended to be cross-platform, detect the OS and choose the correct activation path (or provide separate scripts).

[Copilot]

Two packaging blockers:\n1) python:build uses an absolute, machine-specific path to PyInstaller, which will fail on other environments/CI.\n2) extraResources.from points at dist/VEXServer.exe, but Electron Builder also uses dist/ as its output directory by default—this risks overwriting/removing the PyInstaller output during electron:build.\nRecommendation: call pyinstaller via the active venv (.venv/Scripts/pyinstaller or python -m PyInstaller) and configure PyInstaller to output to a non-conflicting directory (e.g., python-dist/) or set --distpath.

[Copilot]

Two packaging blockers:\n1) python:build uses an absolute, machine-specific path to PyInstaller, which will fail on other environments/CI.\n2) extraResources.from points at dist/VEXServer.exe, but Electron Builder also uses dist/ as its output directory by default—this risks overwriting/removing the PyInstaller output during electron:build.\nRecommendation: call pyinstaller via the active venv (.venv/Scripts/pyinstaller or python -m PyInstaller) and configure PyInstaller to output to a non-conflicting directory (e.g., python-dist/) or set --distpath.