The article closed the job, not the feature
An article closes the job the customer came to do, instead of describing the feature.
Most knowledge bases document the product. The customer did not come to learn the product. They came to finish something.
A resolving article names the job, the exact steps, and the state you should be in when you are done. It does not require the reader to translate “I cannot share this vault” into the vendor’s information architecture.
That is the difference between a library and a path.