bug: explicitly declaring "finished" doesn't seem to work

[jdbaldry]

Here, I tell it that the last file is finished.md.

Then I declare it.

Then when KC imports it, it's missing

This sorta makes sense (because the parser ignores anything that isn't stepN.md)

but it's also quite suprising because I said what I'd declare and then I declared it.

(Also: I realize, there is a directive called finish.md but I declared finished.md and broke the process. Easy mistake to make)

Ideally:

• I don't need to define a "finished" state ever. Whatever my last state is, the parser knows that becomes my "finished" state
• If I do declare a "finished" state (like with a static file I put in the KC repo) then that's respected.

[jdbaldry]

Yeah, the tool only creates very specific files at the moment, those are:

• intro.md
• finish.md
• step<N>.md

I wonder if it would be more user friendly to create any file for a directive that has the .md suffix? Perhaps more future proof would be to modify the directive so it's <!-- INTERACTIVE file <FILENAME> START --> and then in theory we could even pull scripts or configuration out of source documentation.

@Jayclifford345 what do you think?