Currently, answering it that, telling it about, and asking it
about require that the person being talked to be touchable. It is proposed
that this be changed to "visible" instead. There are some implications for
the conceptual picture of what is going on - speaking in this way becomes,
perhaps, a less intimate act - but it seems more rather than less
realistic.

Requests to recompile and replay will not perform any actions taken in the last play-through prior to a "> restart" command being issued.

The ability to declare a column of a table to have a default
(non-null) value unless the author overrides this; as in

Table of Drugs
drug cost
a drug a price (usually $1.99)

For instance:

Before turning the hourglass:
if the time until the sand runs out is less than 3 turns:
instead say “There’s only a little sand left on top; you might as well let it run its course.”

This would require some additional syntax to determine whether this event is in fact scheduled at all; otherwise, checking for the time remaining until it runs out would have to return a runtime error.

It may be possible to optimize searches
and loops using relations that are declared to remain static from compile time
onward.

A quick way to write rules about actions in which the noun and second noun are equivalent, as in

Instead of tying the blue rope to the red rope or vice versa: ...

Jon Ingold's work with Glk and type-ahead command hints is wonderful, but it's also a very complex piece of code.

I believe that this is a significant path to follow outside of the user interface and strictly within the game engine.

My suggestion to enable the author the ability to list "potential" commands, sort them on some probability of success, and let the author review them programmatically.

...so that gameinfo.dbg is available for debugging.

The ability to use a strict setting so that the compiler will catch
unnamed rules (as for extensions which ought to name all of their rules
for the convenience of subsequent authors).

I
don't use much the skein or transcript concept, but I find the "test me"
command very useful. I'd like to be able to keep it after the release of the
game, or convert the command into a "walkthrough" option, which could either
display the whole solution, only a part of it, or replay the game
automatically (useful for testing a game with different interpreters). At the
moment I must export all the "test me" commands, clean up the code, and use it
with the replay command.

Currently when you first create a project, the index is empty. It would be nice for users to be able to explore this and especially to have access to the phrasebook right from the outset.

For "if we have..." tense-conditions to be replaced by some other syntax, because authors are confused by who this "we" might be, and/or wish they could say "if the player has...".

In the new Inform 7 builds, Use options can be "active" or not "active". There seems to be little reason to use such a common term for such an obscure feature, especially since it breaks at least one oft-used extension, Simple Chat. (Updating the extension may seem like little work, but updating all the games that have made use of it, including its "active" property which the writer will constantly use, is not.) Please choose some other word to describe the status of use options.

Currently if we have a number of instances of a kind (A block is a kind of thing. Two blocks are in the kitchen.), the grouping activity does not allow one to override the description of these objects, though it would if the blocks had individual names. Moreover, it would be nice to be able to get the number of items being grouped together and manipulate that information.