At the risk of stripping any ambiguity from this whatsoever, what I originally envisioned was such:
A twine game is entered into a comp, maybe SpringThing, maybe EctoComp, whichever.
When the player chooses to save their game, they press the SAVE GAME button provided.
This game has a save system that tracks an arbitrary and limited amount of game states in the form of a table saved into a txt file. The structure of this file is formatted in a manner that it meets the requirements for Inform to read the table successfully.
This save file has a default name which could be changed by the player, breaking the intended the effect.
This save file can be saved anywhere the player wishes; there is only one location they could coincidentally save it that wouldn’t break this effect.
When they chose to, they could select this file to load a saved game by selecting the LOAD GAME button provided, and navigating to and selecting the desired save file.
For most players, this is the full functionality of this feature. Full stop.
We are now done with the Twine game.
Months later at a subsequent Comp, perhaps IFComp, perhaps not, an Inform game is submitted without a play online option to maximize the number of people playing the game through a downloaded interpreter at the cost of total plays.
Then, assuming the earlier file still exists, wasn’t renamed, and was coincidentally saved in the same folder this Inform game was saved to, the Inform game looks for and finds a txt file by the default save game name upon running.
Upon finding it, it reads the table and applies certain specific game state info saved from this player’s session with the Twine game and applies relevant changes to the player’s session with the Inform game.
As the player then plays this Inform game something happens that reflects the game’s knowledge of choices made in the player’s earlier playthrough of the Twine game.
This only needs to happen a few times, perhaps even just once, before a player brings word of it to the greater community.
I expect this to fail the vast majority of the time, but it only needs to work once to be worthwhile.
It’s messy, unreliable, and clumsy. But it’s also discrete.