Figure out how auth would work for the query

Basically you just want this: https://github.com/codeday/labs-gql/blob/main/src/resolvers/Stats.ts#L17

and what I need to do to get myself a token to test

If you're running it locally you can sign a JWT of this format - https://github.com/codeday/labs-gql/blob/main/src/context/auth/JwtToken.ts - probably just { "typ": "a" } in this case

Once you have it ready I can deploy it and give you a testing token.

Create a new matching result graphql type possibly?

I think that's the best way, even if another type could be repurposed using a dedicated one offers more type safety for clients.

Create mutation for saving a valid match back to database after human review
Figure out how to store a given match into the database

That's already done @ https://github.com/codeday/labs-gql/blob/main/src/resolvers/Project.ts#L71

Once it's possible to download a match-list, I can create a frontend which has a "confirm" button for each possible match.

A few more follow up questions!

1. Will the database have multiple years / lab sessions worth of projects in it? If so, should I filter on createdAt or updatedAt or something like that?
2. Any other things I should filter out of a matching? Planing on not processing draft projects but that's all I really see.
3. Would you prefer if I return a list of students and their matched projects or projects and their matched students? How much data would you like to receive? The project mutation you linked me to could be compatible pretty easily with either approach so it really comes down to what would be more convenient for the planned frontend. To make some progress I'm going to just return it per project as that's more inline with the way data is stored internally but it would be pretty much trivial to transform it later, just let me know!
   Thanks!

1. Yes but don't worry about it for now. There's another branch with a sessionId which I haven't finished yet, but I can add that in later.
2. That's it!
3. You could return a new MatchTuple type so we can display it either way. Might make final matching adjustments easier.

Ok cool! I've created the response with the MatchTuple, it should work properly but I cannot get the auth to load correctly for me on Playground so I can't test it right now. I think it's also kind of dependent on elastic to run, I tried to rip it out the best I could but it wasn't really enough to test properly. The types all check out and I'm pretty confident it should work though! Specifically, I return the matching stats and the MatchTuples so you can get an idea of some properties of the matching if you want as well but that could totally be removed if you'd like. If you could test this on some setup that has everything that'd be great.

Also, I've gone and re-named all the old "Matching" stuff (related to elastic and things) to "Recommendation". I think this is a better name and should reduce confusion between the two types, although editing the GraphQL names of these may cause issues and I'm not sure how to deal with that properly in GraphQL so I may need to put those back. Can you advise on this?

This looks great to me, I have to change the queries in www-labs before merging however

Sounds good! Please let me know once this is good to be tested, I'd like to validate it on prod before it's ready for prime time.