Thanks! One less file cluttering up every folder. And still there when you need it. Well done.

Thanks to Abhinav & the whole team for realizing my feature request!

Any ETA on availability in Public Release builds?

Maybe you want to consider making the file in fact useful by omitting screen angles, printer specs, and RGB warnings (or switch to CMYK warnings instead) and on the other hand adding specs for InDesign version, page sizes, page numbers, bleed and slug settings, ICC profiles, rendering intents, file names (and paths?) for all linked files, INDB relations, …

Thanks Folks for your comments, this is really helpful.
For now I am moving the feature request status to "Under Review" for us to consider fixing.

There are 2 reasons why the instructions.txt file is a problem:

1. People that don't understand what this file is for. I've seen several cases where people see the prompt "Filename" at the top of the instructions box, and think they are supposed to type the name of their InDesign file in this field. The package command doesn't all the instructions file to be the same name as their ID file, thankfully, but then they'll name it something like "myfile2.indd" or something like that. Then, later on, they try to open the "indesign" file they created (which is really the instructions.txt file), and InDesign gives them the message that the file can't be opened or is damaged, and they freak out.

2. Many people use the Package command more often for just organizing files on their local storage than for actually submitting files to printers. In this case, their storage gets littered with hundreds of "instructions.txt" files, which droves obsessive compulsive people like myself crazy!

It's not a big problem at all but I've been using indesign from the very beginning and I've never used it. I don't know anyone else who has either. The reason for my vote? It's more a case of 'oh yes, why is that silly little txt file always there. Let's get rid.' And don't most people just send pdfs to printers anyway

A suggestion: why not move it to the next screen, where you check if fonts, idml etc are included. A new checkbox if annotations should be included.
If not checked, no annotations. If yes, the already existing dialog pops up.

In the last 15 years I never passed a package with that file.
In a modern workflow passing PDF is a more common way.
If I pass a package with open data, I can assume that the recipient is fit enough to understand what we've done. Colors, imports, typefaces, all is in place.
No need for such a file.