I want to check with @tess323 here because originally, she wanted to re-use this same pilot going forward, but I'm not sure she had strong conviction on that and I'm sort of leaning towards having a fresh pilot at this point, but want to check if there has been any communication with previous pilot participants so far that would make setting up a new pilot / having them re-join a new pilot problematic.

yeah, I think we need to start fresh but I will double check at checkin tomorrow. it looked like the original pilot was for teachers enabling tutor per section, but it didn't seem to be wired up anymore?

Im okay with a new name - I cant think of any downside, other than maybe chatting with the few folks who are in there

there were about 70 in the old pilot when I checked. I'm not sure how they were invited and what their expectations might be, but since the new pilot will be specific to enabled levels and not based on sections (I think this was how it worked in the past?) it seems reasonable to start a new pilot 🤷

Looks like appOptions is added to the window object and used in a number of places, but this addition to the global Window interface seems to indicate this is the first time it's used in a TypeScript file. I wonder if there is another way to make this aiTutorAvailable flag available where it is needed as it's generally considered bad practice to add anything to the global window object.

Or is this no longer actually needed (I don't see where this appOptions.level.aiTutorAvailable is actually set) as you mentioned:

I had put it in appOptions (in levels helper) originally due to requirements to check the unit/level there, but those are no longer needed now that we're using the level property.

yeah, I double checked and the level data is not loaded into redux for the legacy labs, they use window.appOptions.level which is set in loadApp.js. I'm also not a fan of using the window object 😬

Or is this no longer actually needed (I don't see where this appOptions.level.aiTutorAvailable is actually set)

it is unfortunately. I moved the check for the user being in the pilot to the current user endpoint but the level setting aiTutorAvailable will still be on appOptions.level

Ok, is window.appOptions.level of type LevelProperties from apps/src/lab2/types.ts? If so, should we use:

import {LevelProperties} from '@cdo/apps/lab2/types';

Interface Window {
  getWebLab?: () => WebLabInstance | undefined;
  appOptions?: {
    level?: LevelProperties;
  };
}