"course-sdk test c" fails due to non existent files

when running course-sdk test c inside a build-your-own-bittorrent repo fails with the following errors:

     #22 exporting to image
     #22 exporting layers
     #22 exporting layers 0.2s done
     #22 writing image sha256:1fe2529d62b20f787c5d00eeaa59e789adf3a46ecbd7feff57234e46610d0ea8 0.0s done
     #22 naming to docker.io/library/bittorrent-c 0.0s done
     #22 DONE 0.4s

  - Executing starter repo script
18068 |     const command = `docker build -t ${this.slug} -f ${this.dockerfile.processedPath} ${this.copiedStarterDir}`;
18069 |     const expectedOutput = `naming to docker.io/library/${this.slug}`;
18070 |     await this.assertStderrContains(command, expectedOutput);
18071 |   }
18072 |   async assertScriptOutput(expectedOutput, expectedExitCode = 0) {
18073 |     await writeFile3(testScriptPath, fs15.readFileSync(test_default).toString());
                                                              ^
ENOENT: no such file or directory, open
 syscall: "open",
   errno: -2,
    code: "ENOENT"

      at assertScriptOutput (/$bunfs/root/main.out:18073:55)
      at assertScriptOutput (/$bunfs/root/main.out:18071:30)
      at assertTimeUnder (/$bunfs/root/main.out:16544:13)
      at assertTimeUnder (/$bunfs/root/main.out:16542:27)
      at doTest (/$bunfs/root/main.out:17987:33)

Bun v1.2.11 (Linux x64)

I guess it is because of a nonexistent test_default file somewhere? If anyone could help I'd be thankful.

P.S: It also fails exactly like this in every build-your-own-x repos

Reproduce course-sdk test c in a build-your-own-bittorrent repository and start at assertScriptOutput, where the stack trace shows test_default being read for testScriptPath. Trace how that path is set and why the starter repository lacks the expected file. Done means the command runs without the ENOENT failure across the affected build-your-own-x repositories.