Two circular dependencies

Not that they are bad, but they smell like possible o crap mistakes.

run-context.ts imports command.ts and vice versa. It’s via a function, but still not immune.

Also a more complex circular dependency: run-context.ts -> plugin.ts -> extensions.ts -> run-context.ts

It’s worth checking if we can properly structure the code so there could be no chance of a circular dependency.

[skellock]

The relationship from Command to RunContext is interface only, not data, so it wouldn’t cause any runtime issues like serialization problems.

Same with the plugin/extension gauntlet. Ownership is only 1 way, even though the interfaces are in both spots.

I love how TypeScript knows what to do.

[jamonholmgren]

I’m going to call this one wontfix … but feel free to bring it up again if we run into any issues!