Two setup docs in one bundle will disagree the moment anything changes

A client bundle shipped with both an INSTALL and a SETUP document covering the same flow. Within a couple of hours the packages were made public, and the older document still instructed the reader to authenticate to the registry with a token that no longer existed -- while the newer one correctly said no login was needed. The reader has no way to tell which is current, and the stale one is often the one they open first because it is named more obviously. Deleting the redundant document is better than updating both, because updating both only defers the divergence to the next change. The same rule that applies to code comments applies here: a second statement of the same fact is a second thing to keep true, and the cost is paid by whoever is least equipped to notice the contradiction.