"Future-proofing" isn't simply "going the extra mile" or "adding random junk". Future-proofing is an attempt to anticipate how others might want to use your code beyond those use-cases you originally wrote it for. How well you "future-proof" depends heavily on how well you anticipate what people are likely to want further from your code. So, like many things, knowing your audience is key.
It's fine to anticipate, but in my book don't actually add those features until the "future" is the present. The thing about the future is that I can change.
I generally consider "future is present" to encompass "things I assume people will be opening tickets for inside the next 6-12 months".
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.