Branch remote runner plugin fixe

[proto-aiken-13]

plugins repo PR description
Title:
feat(ev3): add conductor-based EV3 evaluator bundle
Description:

Overview

Adds a conductor-compatible EV3 evaluator to the remoteExecution runner
package as part of the py-slang EV3 integration. This replaces the
js-slang compilation step in the existing EV3 remote execution flow
with py-slang's EV3Engine, which compiles Python code to SVML.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 764ee5b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "@sourceacademy/web-stepper" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch

[gemini-code-assist]

Code Review

This pull request introduces a new remote execution runner package (@sourceacademy/runner-remote-execution) integrating with the py-slang EV3 engine, along with corresponding Rollup and TypeScript configurations, and updates the test suite to verify its behavior. The review feedback identifies critical issues including a missing entry file (src/entry.ts) in the Rollup configuration, an invalid noCheck compiler option in tsconfig.json, and potential unhandled promise rejections in the asynchronous subscription callback. Additionally, the reviewer suggests renaming remoteRunnerPlugin to RemoteRunnerPlugin to follow PascalCase conventions, and improving type safety in the constructor to avoid using any.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If this.engine.execute or JSON.stringify throws an error, the asynchronous subscription callback will result in an unhandled promise rejection. Wrapping the execution in a try-catch block allows us to handle the error gracefully and send an error message back through the channel using the error message type defined in PySlangMessage.

    this.__channel.subscribe(async message => {
      if (message.type === "run") {
        try {
          const result = await this.engine.execute(message.code);
          console.log("Engine response:", result);
          this.__channel.send({ type: "result", output: JSON.stringify(result) });
        } catch (error) {
          console.error("Engine execution failed:", error);
          this.__channel.send({
            type: "error",
            message: error instanceof Error ? error.message : String(error),
          });
        }
      }
    });

[gemini-code-assist]

The file src/entry.ts specified as the input for the EV3 conductor worker bundle does not exist in the repository. This will cause the Rollup build to fail. Please correct the input path or add the missing src/entry.ts file.

[gemini-code-assist]

Class names in TypeScript should follow the PascalCase naming convention (e.g., as per standard TypeScript style guides). Renaming remoteRunnerPlugin to RemoteRunnerPlugin improves readability and consistency with standard naming conventions.

Suggested change

	export class remoteRunnerPlugin implements IPlugin {
	export class RemoteRunnerPlugin implements IPlugin {

[gemini-code-assist]

Instead of using any and disabling the ESLint rule, we can type the channel parameter directly as IChannel<PySlangMessage>[]. This preserves type safety and removes the need for the ESLint disable comment.

  constructor(_conduit: IConduit, [channel]: IChannel<PySlangMessage>[]) {

[gemini-code-assist]

noCheck is not a valid TypeScript compiler option in tsconfig.json. If the intention is to skip type checking of declaration files, use skipLibCheck: true. If the intention is to disable type checking entirely, it is highly discouraged as it defeats the purpose of using TypeScript.

Suggested change

	"noCheck": true
	"skipLibCheck": true

[gemini-code-assist]

Update the export to use the PascalCase class name RemoteRunnerPlugin.

Suggested change

	export { remoteRunnerPlugin } from "../index";
	export { RemoteRunnerPlugin } from "../index";

[gemini-code-assist]

Update the import to use the PascalCase class name RemoteRunnerPlugin.

Suggested change

	import { remoteRunnerPlugin } from "@sourceacademy/runner-remote-execution";
	import { RemoteRunnerPlugin } from "@sourceacademy/runner-remote-execution";

[gemini-code-assist]

Update the instantiation to use the PascalCase class name RemoteRunnerPlugin.

Suggested change

	new remoteRunnerPlugin(mockConduit, [mockChannel as any]);
	new RemoteRunnerPlugin(mockConduit, [mockChannel as any]);