Continues correcting JSDoc types for Typescript tooling compatibility

[ChrisC]

No description provided.

[ChrisC]

@jugglinmike there are two clusters of files remaining that would complete the typescript formalization work:
shared/job and the source and test files for shared/file-record.

I anticipate that fixing the types for both of these modules will be a bit difficult and probably require some amount of re-factoring. That being the case, I'm wondering if we might want to hold off on correcting these types for now, since a bigger refactor to simplify the harness is coming.

In particular, I'm wondering if we might want to do away with the shared/jobs abstraction altogether? I'm a little less clear on whether or not we may need the file-record abstraction going forward, but I do think this module would benefit from a substantial simplification if we do decide to keep it.

@jugglinmike @gnarf It might be a good idea for us to plan out that bigger refactor in a little more detail, so that we can make sure to only correct the types we know we'll continue using after the refactor?

[jugglinmike]

@jugglinmike @gnarf It might be a good idea for us to plan out that bigger refactor in a little more detail, so that we can make sure to only correct the types we know we'll continue using after the refactor?

Agreed. We prioritized this work because we'd have more confidence refactoring a well-typed project. There's no sense spending a lot of time fixing doomed files.

[ChrisC]

Agreed. We prioritized this work because we'd have more confidence refactoring a well-typed project. There's no sense spending a lot of time fixing doomed files.

Got it. In that case, I'll go ahead and submit this PR and we'll determine later whether or not those last files will make it into the upcoming refactor.

[jugglinmike]

Thanks, Chris!